FYI Last week we had strange bugs on Win9X due to not installing current
msvcrtl.dll
interesting point... things worked with my app very well on NT 4/2000 etc... but did strange things (eg didn't start up) on a win98 laptop. Hmmmm.
Well, if its msvcrtl.dll that's missing, would the simplest solution be to put it in the same dir as with the app itself? (ie not take the chance of overwriting the system one)
FYI Last week we had strange bugs on Win9X due to not installing current msvcrtl.dll
interesting point... things worked with my app very well on NT 4/2000 etc... but did strange things (eg didn't start up) on a win98 laptop. Hmmmm.
Well, if its msvcrtl.dll that's missing, would the simplest solution be to put it in the same dir as with the app itself? (ie not take the chance of overwriting the system one)
Hmmm...
This works only for NT/2000 (where it's not necessary)
>
> FYI Last week we had strange bugs on Win9X due to not installing current
> msvcrtl.dll
interesting point... things worked with my app very well on NT 4/2000
etc... but did strange things (eg didn't start up) on a win98 laptop. Hmmmm.
Well, if its msvcrtl.dll that's missing, would the simplest solution be to
put it in the same dir as with the app itself? (ie not take the chance of
overwriting the system one)
Please see the message that Bob posted a link to. In a nutshell some system
DLLs *must* be in the system dir. If you don't put them there then the old
ones will still be loaded from the system dir causing problems with your app
if you have DLLs (such as wxPython's .pyd files) that expect to be using the
new version.
Here is what I put in my InnoSetup script to ensure that if my copy of the
system DLLs are newer that they will get installed on the target system, and
left alone otherwise (rejoin broken lines):