Yes, win is 64 bit. I assumed this had to be Win32 tools, so all downloaded items were 32 bit except mercurial, which i didnt think should matter
Thanks for the patience. I think there is more to the win setup than you are aware of running nix; any win users that can clarify?
...sent from my cell phone
On Dec 27, 2012, at 10:21, Dan Smith dsmith@danplanet.com wrote:
No, I am fine at the command line, but assumed path was somehow taken care of by the env, since it wasn't noted.
Okay, I'll tweak the documentation.
Traceback (most recent call last): File "chirpw", line 42, in <module> platform.get_platform().os_version_string(), File "P:\chirp.hg\chirp\platform.py", line 384, in os_version_string import win32api ImportError: DLL load failed: %1 is not a valid Win32 application.
Hmm, well, I'm not sure what to do about that. That means the place it tries to import the win32 module (as installed from pywin32) fails. From the error, I'd expect that it's actually failing inside the pywin32 bits.
Are you on 64-bit Windows? Did you match the bitness of all the components you installed? In other words, did you get 32-bit python, 32-bit pywin32, and 32-bit pygtk?
I dunno if 32-bit versions of the dependencies are available for Windows, nor do I know much about how Win64 works, other than that it seems to have the same sort of expectation as other OSes, that everything in a single process be the same bitness.
-- Dan Smith www.danplanet.com KK7DS