Act.Python build100: win32ui.pyd error

[Robin Becker]

In article <8pvigl$l1h$1 at sshuraaa-i-1.production.compuserve.com>, Kees
de Laat <kdelaat at compuserve.com> writes
>

I suspect these problems are related to one that is present in 
the base win32all-134.exe for 2.0b1 ie win32ui.pyd refers to ToUnicodeEx 
in user32.dll; this seems not to be present in win95 versions of user32;
I can definitely say it is present on the Win98 SE at work and not
present on my home Win95 OSR2. Mark Hammond kindly issued a fixed
win32ui.pyd for the 134 version. I guess that Active Python has more
bureaucracy to go through before doing the same.

><gosselina at dfo-mpo.gc.ca> writes in 8pp0sm$rn5$1 at nnrp1.deja.com...
>> Every attempt to start Pythonwin installed through Active Python 1.6
>> Build 100 on my Win95 platform failed with this message:
>> "The application can not locate win32ui.pyd(31).
>>  A device attached to the system is not functionning".
>>
>> PATH includes the Python directory. Python starts OK though.
>>
>> Same problem with win32all-133.exe installed over final release of CNRI
>> Python 1.6.
>>
>> I did not have this problem with win32all-131.exe.
>>
>> Any help someone ?
>>
>
>This is no help, only a confirmation that you're not the
>only one having this problem.
>I get the same error on my Win95 system after de-installing
>Python 1.5.2 and win32all-132 and installing Python 2.0b1
>and win32all-134.
>The following session shows that the problem is not really
>in locating the file but that the OS somehow fails to actually
>load this particular DLL on our systems. Another DLL
>(e.g. mmapfile.pyd) loads without problems!

-- 
Robin Becker