| || |
GDI32.DLL causes application havoc
The original message somehow failed to get posted...so here it is again.
Segue support has already been notified and I'm waiting on a response. I'm hoping that by posting this in the user forum someone else will have some suggestions.
Basicly, when Silk installs it places a new (different) copy of GDI32.DLL in the system directory. This file has 4 bytes that are different than the original with the same version. At the very least, this difference allows Silk to recognize and record VB objects as VB objects instead of standard Windows or Custom objects.
The problem: I am writing scripts for a large VB5 app. We started on NT 4 sp3 and are now using Win59 OSR2. At some point we began having Dr Watson or Invalid Page faults (depending on the OS) in the app against other app related DLLs. We also found one specific place where the app would crash consistantly just by manually running the script and Silk unloaded. I discovered that the app does not crash with the Windows supplied GDI32.DLL. I can't prove that GDI32.DLL is also responsible for the other page faults because using the original invalidates my definitions, but there is reason to believe that there is a relationship.
The question: Has anyone else experienced this and what are my (our) options aside from using the original GDI32.DLL and adjusting or rerecording the definitions and scripts. Maybe there is something that should be done differently in the VB5 app.
Re: GDI32.DLL causes application havoc
Good news! SilkTest v5.0 appears to have solved the instability problems. The locations where crashes were consistant have been eliminated. Although this new version has only been in use for two days, a noticable improvement in testing the same test app version is observed.