I've narrowed it down to this:

try:
    import pywinauto.application
    app = pywinauto.application.Application()
except:
    f = open('c:\output.txt', 'a')
    f.write('import error\n')
    f.close()

Here is the Application class: http://pastebin.com/m282d9e36

I wrapped the above in a try/except which writes to a file, when
running via "c:\python25\python.exe code.py" it works fine, but when
running from the PyInstaller EXE it will write to the output file
which shows there was an exception.

Batch file to run Build:

set PIP=c:\pyinstaller\
c:\python25\python.exe %PIP%Makespec.py --onefile --noconsole --upx
--tk c:\junk.py
c:\python25\python.exe %PIP%Build.py junk.spec

SPEC file:

a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'),
os.path.join(HOMEPATH,'support\\unpackTK.py'),
os.path.join(HOMEPATH,'support\\useTK.py'),
os.path.join(HOMEPATH,'support\\useUnicode.py'), 'c:\\junk.py',
os.path.join(HOMEPATH,'support\\removeTK.py')],
             pathex=['c:\\'])
pyz = PYZ(a.pure)
exe = EXE(TkPKG(), pyz,
          a.scripts,
          a.binaries,
          name='junk.exe',
          debug=False,
          strip=False,
          upx=True,
          console=False )


Again, all of this works on WinXP, but not on Win2K. I'm still hoping
this is my problem.



On Fri, May 16, 2008 at 9:08 AM, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
>
> On 5/15/2008 11:09 PM, Garland, Ken R wrote:
>> Looks like it is a problem on my end as I suspected, please ignore this.
>>
>>
>>
>> On Thu, May 15, 2008 at 4:34 PM, [EMAIL PROTECTED]
>> <[EMAIL PROTECTED]> wrote:
>>> I should have expected this since it is a different OS. How can I
>>> compile for a Windows 2000 Server machine from WinXP? The .exe works
>>> on my WinXP machine, but not the 2000 machine.
>>>
>>> I'm running Python 2.5.2, PyInstaller 1.3, Windows XP SP2
>>>
>>> At first I received a lot of 'could not be extracted' errors, so I
>>> grabbed the latest trunk (462 as of now). ran Configure and made a
>>> new .exe. The errors went away but my app still does not work on the
>>> Win2K machine.
>
> Yes. For the logs, there shouldn't be anything preventing a PyInstaller
> executable to run on all Windows versions (unless of course the source
> of incompatibility resides on your own code).
> --
> Giovanni Bajo
> Develer S.r.l.
> http://www.develer.com
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to