Re: [PythonCE] Reverting to PythonCE 2.3

2006-05-12 Thread jeffbarish
Got it. Thanks to everyone for the advice. I finally figured out that I could install Python 2.3.5 even though 2.3.4 would not install, and everything (including wxPython) seems to run fine with 2.3.5 (although the error message (coming from wxPython) about needing a newer comctl32.dll looks mor

Re: [PythonCE] Reverting to PythonCE 2.3

2006-05-12 Thread jeffbarish
Got it. Thanks to everyone for the advice. I finally figured out that I could install Python 2.3.5 even though 2.3.4 would not install. Everything (including wxPython) seems to run fine with 2.3.5, although the error message (coming from wxPython) about needing a newer comctl32.dll looks more e

Re: [PythonCE] Reverting to PythonCE 2.3

2006-05-12 Thread Gonzalo Monzón
jeffbarish escribió: >Thank you for the suggestion. I should have mentioned before that I did try >to run setup-registry (and also Setup Registry). Both are still present in >the lib folder. However, neither will run, producing the same message I get >whenever I try to do anything (The file 's

Re: [PythonCE] Reverting to PythonCE 2.3

2006-05-12 Thread Shane Holloway (IEEE)
Well, it's actually easier than that. Look for a hard reset. It will simply wipe your RAM and revert to the ROM image on the device. Make sure you have everything you need backed up though -- it *will* be gone unless it is in a non-volatile storage area. On May 11, 2006, at 15:31, jeffba

Re: [PythonCE] Reverting to PythonCE 2.3

2006-05-12 Thread Luke Dunstan
Total Commander can edit the registry on the device or Remote Registry Editor from Microsoft eMbedded Visual C++ 4.0 can do it remotely, at least on Pocket PC 2003. I think at least one of them should work on WM5. If not, you can write a Python program on the PC using the ActiveSync Remote API