I
Ian Hill
I am running an application (ISM3) developed in VB3 by the
British Computer Society. Under Windows 2000 SP1 it works
fine.
However, after Windows 2000 SP4 has been installed,
whenever I use the mouse to press on a menu in the
application, I get a dialog box displayed with the error
message: "ISM3 caused a General Protection fault in
module KRNL386.EXE at 0003:0BD4. Choose Close. ISM3 will
close."
The crash ALWAYS occurs in the same way as a result of
moving the mouse over one of the ISM3 menu buttons and
pressing the left mouse button.
It has been suggested to me that 'this "bug" is due to the
application of Windows2000 Service Pack 4. I have tested
out ISM3.3 on Win2000 SP2 with no problems lke the one
described. The problem appears when the user clicks on one
of the main menu items. This code is within the Microsoft
common controls and VB runtime, and is therefore not
strictly part of the ISM3 application. The application
does not exhibit this behaviour with SP2'. After receiving
this advice, I also tested the application on Windows 2000
SP1 and it was fine.
Appreciate any suggestions as to how to get around this
problem (apart from backing out of SP4!).
Thanks
Ian
British Computer Society. Under Windows 2000 SP1 it works
fine.
However, after Windows 2000 SP4 has been installed,
whenever I use the mouse to press on a menu in the
application, I get a dialog box displayed with the error
message: "ISM3 caused a General Protection fault in
module KRNL386.EXE at 0003:0BD4. Choose Close. ISM3 will
close."
The crash ALWAYS occurs in the same way as a result of
moving the mouse over one of the ISM3 menu buttons and
pressing the left mouse button.
It has been suggested to me that 'this "bug" is due to the
application of Windows2000 Service Pack 4. I have tested
out ISM3.3 on Win2000 SP2 with no problems lke the one
described. The problem appears when the user clicks on one
of the main menu items. This code is within the Microsoft
common controls and VB runtime, and is therefore not
strictly part of the ISM3 application. The application
does not exhibit this behaviour with SP2'. After receiving
this advice, I also tested the application on Windows 2000
SP1 and it was fine.
Appreciate any suggestions as to how to get around this
problem (apart from backing out of SP4!).
Thanks
Ian