We normally do our wxPython work under Windows NT, but a co-worker just
installed it on his Windows 95 laptop. However, attempting to start up the
wxPython demo or our own application on that laptop immediately GPFs in the
wxWindows DLL - this is true for both 2.1.16 and 2.2.0.
I'm guessing that there's some shared Windows DLL that the wxWindows DLL
uses that is an earlier version on his laptop (perhaps MSVCRT or MSVCIRT),
since that's really the only common denominator between the local wxPython
installation and our application (which is built with the installer package
and thus keeps all resources local), but am somewhat hesitant to just
randomly update those since with my luck I'll break something already on the
machine, or I'll find the versions on my NT systems incompatible with Win95
or something.
I think this issue came up recently on this list with respect to
distributing applications - are there any guidelines anywhere available on
just which system DLLs can be updated and what not?
Has anyone else run into this or might suggest how I could go about
identifying the problem. I'd like to avoid the time of building a debug
version of the wxWindows DLL, but am not sure if I have any other
alternatives.
Thanks.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: db3l@fitlinxx.com /
> FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/