No, I am fine at the command line, but assumed path was somehow taken care of by the env, since it wasn't noted.
If I cd to the new \chirp.hg directory and then run: python chirpw I get:
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.
-----Original Message----- From: Dan Smith [mailto:dsmith@danplanet.com] Sent: December 27, 2012 10:12 To: chirp_devel@intrepid.danplanet.com Cc: Drew Vonada-Smith Subject: Re: [chirp_devel] Development env?
I put it in my documents area now, but "python chirpw" does not find it. It must matter where it is placed for that line to work...
You have to be in the chirp.hg directory for that to work, yes. If it's in C:\Foo\chirp.hg, then you would do this:
c: cd \Foo\chirp.hg python chirp.hg
If you aren't comfortable at the command-line, you should probably be able to convince to the GUI to run chirpw with Python via some association mechanism...
-- Dan Smith www.danplanet.com KK7DS