Re: COM problem .py versus .exe

2005-06-30 Thread Greg Miller
That code works great, and is a tad bit cleaner than what I came up with, thanks again. -- http://mail.python.org/mailman/listinfo/python-list

RE: COM problem .py versus .exe

2005-06-30 Thread Tim Golden
[Greg Miller] | | Thanks for the information, I stumbled across that page yesterday. It | seems all the problems with this are solved. The executable | works just | like the Python version. Now I have to come up with an algorithm to | parse through the output data to come up with the version n

Re: COM problem .py versus .exe

2005-06-30 Thread Greg Miller
Thanks for the information, I stumbled across that page yesterday. It seems all the problems with this are solved. The executable works just like the Python version. Now I have to come up with an algorithm to parse through the output data to come up with the version numbers. Thanks for all your

Re: COM problem .py versus .exe

2005-06-29 Thread Tim G
Greg Miller wrote: > I tried the code snippet using win32api.GetFileVersionInfo(), what I > get now is the following when running on the executable machine: > > . . . FileFlagsMask => 63 > FileType => 2 > FileVersionMS => 65536 > FileVersionLS => 1 > Signature => -17890115 > FileSubtype => 0 > File

Re: COM problem .py versus .exe

2005-06-29 Thread Greg Miller
I tried the code snippet using win32api.GetFileVersionInfo(), what I get now is the following when running on the executable machine: . . . FileFlagsMask => 63 FileType => 2 FileVersionMS => 65536 FileVersionLS => 1 Signature => -17890115 FileSubtype => 0 FileFlags => 0 ProductVersionLS => 1 FileD

Re: COM problem .py versus .exe

2005-06-29 Thread Greg Miller
I didn't see the earlier post, thanks for the resend. The firefighting is just about over, I have to find the machine owner to get permission to try the code. Then back to the dll version battle. If I can keep away from dealing with the ctypes code I will. I'll see how this works for me. Thank

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Greg Miller] | Unfortunately I have a "fire" to put out with a patch to the existing | machine code, I'll get back to looking into the problem a | little later. | Thanks very much for you assistance with this! I really didn't look | into the GetFileVersionInfo, can I assume that is a cytypes fu

Re: COM problem .py versus .exe

2005-06-29 Thread Greg Miller
Unfortunately I have a "fire" to put out with a patch to the existing machine code, I'll get back to looking into the problem a little later. Thanks very much for you assistance with this! I really didn't look into the GetFileVersionInfo, can I assume that is a cytypes function? -- http://mail.

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Greg Miller] | line 157 is in fact where the traceback says the failure is: | | File "autoStart.py", line 241, in test | File "wmib.pyc", line 157, in ? | File "win32com\client\__init__.pyc", line 73, in GetObject | File "win32com\client\__init__.pyc", line 88, in Moniker | com_error: (-214722102

Re: COM problem .py versus .exe

2005-06-29 Thread Greg Miller
line 157 is in fact where the traceback says the failure is: File "autoStart.py", line 241, in test File "wmib.pyc", line 157, in ? File "win32com\client\__init__.pyc", line 73, in GetObject File "win32com\client\__init__.pyc", line 88, in Moniker com_error: (-2147221020, 'Invalid syntax', None, N

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Greg Miller] | | I put you code snippet into my code, running it from the desktop PC | gave me the following output ( I added a print statement ): | | . . . winmgmts: | T i.Caption is \\rocps00101\ROCPR001 | T i.Caption is \\ROCPS00101\ROCPR024 | TTT

Re: COM problem .py versus .exe

2005-06-29 Thread Greg Miller
I put you code snippet into my code, running it from the desktop PC gave me the following output ( I added a print statement ): . . . winmgmts: T i.Caption is \\rocps00101\ROCPR001 T i.Caption is \\ROCPS00101\ROCPR024 T i.Caption is \\ROCPS00101\R

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Tim Golden] | [Greg Miller] | | | I didn't have this problem on the | | first release | | as we weren't interested in displaying the file version of the .dll. | | With this improved version of the product the request has | come down to | | have all software package versions displayed, so that i

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Greg Miller] | | The two machines are both running Windows XP, the desktop is | running XP Pro, the "virgin" PC is running XP embedded. Well my first thought was: maybe XP Embedded has cut out WMI. A quick Google around suggests that it's still there, but maybe there's some restrictions in what

Re: COM problem .py versus .exe

2005-06-29 Thread Greg Miller
The two machines are both running Windows XP, the desktop is running XP Pro, the "virgin" PC is running XP embedded. I would say the biggest difference is that the embedded machine has only the py2exe executable running/installed, while the desktop has the full python24 installation. I get no bui

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Thomas Heller] | | "Tim Golden" <[EMAIL PROTECTED]> writes: | | > [Greg Miller] | > | Hello again, I put the executable on the "virgin" PC today. | > | I am using | > | the wmi(b) that you gave me. The error that I am | receiving now is: | > | | > | File "autoStart.pyc", line 241, in test |

Re: COM problem .py versus .exe

2005-06-29 Thread Thomas Heller
"Tim Golden" <[EMAIL PROTECTED]> writes: > [Greg Miller] > | Hello again, I put the executable on the "virgin" PC today. > | I am using > | the wmi(b) that you gave me. The error that I am receiving now is: > | > | File "autoStart.pyc", line 241, in test > | File "wmib.pyc", line 157, in ? > |

RE: COM problem .py versus .exe

2005-06-29 Thread Tim Golden
[Greg Miller] | Hello again, I put the executable on the "virgin" PC today. | I am using | the wmi(b) that you gave me. The error that I am receiving now is: | | File "autoStart.pyc", line 241, in test | File "wmib.pyc", line 157, in ? | File "win32com\client\__init__.pyc", line 73, in GetObjec

Re: COM problem .py versus .exe

2005-06-28 Thread Greg Miller
Hello again, I put the executable on the "virgin" PC today. I am using the wmi(b) that you gave me. The error that I am receiving now is: File "autoStart.pyc", line 241, in test File "wmib.pyc", line 157, in ? File "win32com\client\__init__.pyc", line 73, in GetObject File "win32com\client\__ini

RE: COM problem .py versus .exe

2005-06-27 Thread Tim Golden
[Greg Miller] | Thanks for the tweaked code, it worked on my desktop. Thanks for the confirmation; I don't use py2exe myself, and while I could run up a test case (and probably should given the number of queries I get like this) I've never got round to it. I'm close to releasing a version 1.0

Re: COM problem .py versus .exe

2005-06-27 Thread Greg Miller
Thanks for the tweaked code, it worked on my desktop. The acid test will be when I put it on one of the "virgin" PC's ( no python installed, just running the py2exe executable ) that run the machine. I won't be getting one of those until later in the week, but I'm hoping that since it cleared the

RE: COM problem .py versus .exe

2005-06-27 Thread Tim Golden
[Greg Miller] | I have a .DLL that I am extracting the file version from using wmi.py. | The specific code is: | | c = wmi.WMI() | for f in | c.CIM_DataFile(Name="c:\\glossersdmsservices\\bin\\glosscmanag | er.dll"): | sdmsver = f.Version | | this works fine when running the a

COM problem .py versus .exe

2005-06-27 Thread Greg Miller
I have a .DLL that I am extracting the file version from using wmi.py. The specific code is: c = wmi.WMI() for f in c.CIM_DataFile(Name="c:\\glossersdmsservices\\bin\\glosscmanager.dll"): sdmsver = f.Version this works fine when running the application as a python file, when I