[PythonCE] Python CE on a Intel XScale industrial device.

[Alexandre Delattre]

Hi,

In my opinion if you're able to run the python exe it means that is not processor related.

I think the problem comes from what you've pointed out, the OS versions constraints.

I think we should rebuild the .cab to allow os versions from 4.00 and 5.99 as you suggested. There's also a bug in the cab that would be worth fixing at the same time:

In one of the registry key that associates  .pyw to pythonce without shell we have to replace \nopcceshell by /nopcceshell.

Else this cause the error <NULL>:<NULL> to be raised when running .pyw.

For tKinter, the dll are not shipped with PythonCE and you have to copy them manually, more info on the wiki.

For ppygui I'll be very glad if you use my toolkit, and if you send me your traceback I'll make my possible to make it work for you.
I think the issue you described comes from that ppygui was designed for PocketPC 2003 and Windows Mobile, while it seems from screenshot your device has the 'classic' wince interface.

Regards,
Alexandre


----- Message d'origine -----
De: Lachezar Dobrev <l.dobrev at gmail.com>
Env: jeudi 31 juillet 2008 17:05
À: Alexandre Delattre <alexandre.delattre at enst-bretagne.fr>
Objet: Re: [PythonCE] Python CE on a Intel XScale industrial device.

  Update follows...

  People on this list were quite helpful in referencing a couple of
tools for Pocket PC CAB file mangling.
  1. I was able to extract the Python CE CAB file an uploaded the
extracted files to my device. The python executable had an icon, and I
was able to run it. It seemed to work. I was able to execute a few
minor tests my way: a few dir()-s, a few imports, a few Base64
encoding and decoding operations, and it seemed to work fine. Until I
tried to import Tkinter:

> >>> import sys
> >>> import Tkinter
> Traceback (most recent call last):
>   File "C:\devl\release\PythonCE-2.5-20061219\Python-2.5-wince\Lib\lib-tk\Tkinter.py", line 38, in <module>
> RuntimeError: Could not find CeLib DLL
> >>>

  Which led me to believe something is not right.
  Has anyone seen that? Does anyone know how to fix that?

  A similar error occurs when I try to install the PocketPyGui
(ppygui-0.7) which I thought I would use for the GUI part. However the
exception then has a bit longer stack trace (about 10 frames).

  2. Reading the documentation on the pocketpc-cab and lcab utilities
I found something that rang a bell:

    Appendix A: a list of processor architectures
    ...
    1824 - ARM 720
    2080 - ARM 820
    2336 - ARM 920
    2577 - StrongARM
    ...

    My device says in the System Properties: 'Intel, ARM920T-PXA27x'
    Could this be the culprit of my problems? Is ARM920 compatible
with Strong ARM? Should I give-up on trying to install the current
version and try to compile a version for my device personally?

  I also noted that the CAB files state, that the allowed OS version
is 4.00 up to 5.00, shouldn't it be up to 5.99 or something? Not that
my device has Windows 5.1 or anything, but I saw a the Smart Phone
version note a MAX OS Version of 5.99...

  I hope I get more feed-back on the subject.
  I feel I am getting closer, but I am neither a Mobile-Device expert,
nor a Python expert. I am fairly new to this stuff.