I have an application that I am having some trouble with on one Win95 workstation. I can run it on a number of other workstations running Windows 95, 98, and Me. I get an invalid page fault after unloading a modal form. The rest of the application runs fine, infact this same form can be loaded and unloaded from a couple of other locations without error. Any ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Invalid Page Fault - VB5
- Thread starter CMCDOJO
- Start date
One of the dependancies (a DLL or OCX) on the machine where you code is failing is either corrupt or out of date. Since it is only happening on that one machine and not other 95 boxes, I would be willing to bet that your code is fine. Try the following steps (in the specified order) to try and resolve the problem . . .
1) Reinstall your application (to restore the VB runtimes files)
2) Reapply any applicable service packs to the bad machine. This should update/repair any corrupt system files.
3)Compare dates and version numbers of the core system DLLs/OCXs (Kernel32.dll, Gdi32.dll, etc.) and make sure that the files on the bad machine match the files on the good machines. If not, replace them (you may need to boot to DOS from a basic boot disk to replace some of these since they are loaded into memory when Windows starts.)
4) Finally (and I do mean finally) if nothing else has worked, reinstall the OS. This sounds drastic, but at least you know you have a clean platform.
- Jeff Marler
(please note, that the page is under construction)
1) Reinstall your application (to restore the VB runtimes files)
2) Reapply any applicable service packs to the bad machine. This should update/repair any corrupt system files.
3)Compare dates and version numbers of the core system DLLs/OCXs (Kernel32.dll, Gdi32.dll, etc.) and make sure that the files on the bad machine match the files on the good machines. If not, replace them (you may need to boot to DOS from a basic boot disk to replace some of these since they are loaded into memory when Windows starts.)
4) Finally (and I do mean finally) if nothing else has worked, reinstall the OS. This sounds drastic, but at least you know you have a clean platform.
- Jeff Marler
(please note, that the page is under construction)
- Thread starter
- #3
Jeff,
Thanks for responding. I have tried each of your suggestions with the exception of 3. I skipped straight to 4. I am going to go back and try to replace some of the core DLL's from a machine that is functioning correctly.
Chris
cmc@fwi.com
Thanks for responding. I have tried each of your suggestions with the exception of 3. I skipped straight to 4. I am going to go back and try to replace some of the core DLL's from a machine that is functioning correctly.
Chris
cmc@fwi.com
You've already reinstalled the OS and the problem is still happening? - Jeff Marler
(please note, that the page is under construction)
(please note, that the page is under construction)
- Status
