[wxPython-users] Re: Platform<=>version conflict or what?

[Robin Dunn]

Jorma Paavola wrote:
> Werner F. Bruhin kirjoitti:
>> Hi Jorma,
>>
>> Jorma Paavola wrote:
>>> ...
>>> Hi Werner,
>>>
>>> Good news:
>>> - I am pleased to confirm, that my original TestGui(.exe)(even 
>>> without GcCollect)generated on Win2k(without bundle-option) worked 
>>> today exellent on Me and Vista as well , propably also on Xp !! 
>>> (without any tracebacks as earlier on all Win´s!)
>>> - so all this mess means, that there must be A GENERAL BUG in 
>>> "bundle_files"-option of py2exe!!! - not only on win98 ! (Should 
>>> somebody contact developers concerning issue... ?)
>> Yes, I would check the py2exe list if it is not already reported and 
>> if not then report it with as much detail as possible.
>>
>> Werner
> 
> Hi Werner,
> 
> I ran my TestGUI also on win98-environment with "Dependency Walker" and 
> got similar warnings:
>>
>>> GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsAlloc") called from 
>>> "MSVCR71.DLL" at address 0x7C341950 and returned NULL. Error: The 
>>> specified procedure could not be found (127).
>>> GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsGetValue") called from 
>>> "MSVCR71.DLL" at address 0x7C34195D and returned NULL. Error: The 
>>> specified procedure could not be found (127).
>>> GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsSetValue") called from 
>>> "MSVCR71.DLL" at address 0x7C34196A and returned NULL. Error: The 
>>> specified procedure could not be found (127).
>>> GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsFree") called from 
>>> "MSVCR71.DLL" at address 0x7C341977 and returned NULL. Error: The 
>>> specified procedure could not be found (127)
>>> GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from 
>>> "OLEAUT32.DLL" at address 0x77A23F12 and returned NULL. Error: The 
>>> specified procedure could not be found (127). 
> 
> Also one missing file was claimed (as on Win2k): "APPHELP.DLL" (TestGui 
> ran OK in despite of that!)

These are harmless.  The GetProcAddress is how the MS DLL is dynamically 
testing at runtime if certain functionality is available on the system 
in other DLLs so it can work around it being missing if needed.  Same 
thing with the missing DLL, they are loaded dynamically on demand at 
runtime, but if they are never needed (because the functions using them 
are never called) then they are never loaded and so there is no problem. 
  All of this happens inside the MS DLLs and is completely hidden from 
us at the Python level.


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!