Home Original page

help installing wxPython

MikeZ mike.zaharkin at westgroup.com
Thu May 4 14:53:56 EDT 2000 
I had this same problem when I installed a new wxPython application on
Win95. Some machines worked fine, others didn't.

The way I fixed this problem was to also update the msvcrt.dll in the
windows/system directory. This seemed to fix it.

-Mike Z.

Robin Becker wrote in message ...
>In article <39119A7F.B6FE8B0B at cicei.ulpgc.es>, Enrique Castro
><ecastro at cicei.ulpgc.es> writes
>>Hi,
>...
>If this is 2.1.15 I had the same problem with my system. You need to get
>your system upgraded to use the ws2_32.dll I believe an upgrade is
>available from
>
>
>   ftp://ftp.microsoft.com/bussys/winsock/winsock2
>
>
>I upgraded and found a problem related to the outdated version of
>msvcrt.dll installed by this upgrade. Luckily it makes a backup in
>windows\ws2backup and I was able to copy the previous (actually newer
>version) msvcrt.dll back to c:\windows\system\ (I think I had to do this
>in safe mode though). Altogether a pain. I don't know whether it's
>wxPython's compile or the original wxWindows build which causes this
>nonsense. Python certainly doesn't need winsock2 so I guess this is an
>avoidable blunder.
>--
>Robin Becker
More information about the Python-list mailing list