HMS1000: General Protection Fault in Module ISINST30.DLL

Reviewed: May 9, 2001


  When installing HMS1000 on a Windows 95/98/ME system, the file copy process stops at approximately 80% of system System Manager Disk 2 with an Application Error. Upon canceling or closing this error results in a General Protection Fault with the folling information listed when the Details button is clicked:

  HMS1000 Caused a General Protection Fault in Module ISINST30.DLL  


  This is an issue known to affect InstallShield running on Windows 95/98/ME systems with the Microsoft IntelliPoint WheelMouse, or other pointing devices such as track mice and laptop touch pads (especially the Synaptics TouchPad).


  The workaround for this issue involves installing the HMS1000 System Manager while the conflicting driver is not loaded.

You may use one of the following methods to avoid this problem:

  1. Disable the Microsoft IntelliPoint Wheel before running the HMS1000 setup. To do this, press Ctrl-Alt-Del, highlight MSWHEEL in the Close Program window and select End Task. Do the same for POINT32 if present.

  2. Reboot the computer in Safe Mode before running the HMS1000 setup. If the driver name is not known, the system may be booted into Safe Mode. In Safe Mode, conventional hardware drivers are substituted for Windows virtual device drivers, thus avoiding any potential hardware conflicts.

    Choose Start->Run, type MSCONFIG in the Open text box and press Enter. When the Microsoft System Configuration Editor window opens, select Diagnostic Startup, press Enter to make the change and Enter again when prompted to restart the computer. Upon restarting, the Windows Startup Menu will appear. Select option 3 for Safe Mode. While running in Safe Mode, run the HMS1000 setup. When finished, run MSCONFIG again to set the Startup Mode back to Normal.

    Note - After System Manager Disk 2 has finished copying files, you will be prompted to restart the computer to complete the configuration of the HMS1000 System Manager. Upon restarting, you may choose the Normal Startup option from the Startup Menu. HMS1000 will then automatically load and you will be prompted to beghin installing the HMS1000 modules.

Once HMS1000 has been installed and the system is rebooted, the normal mouse driver is reloaded. Since the conflict is between this driver and the InstallShield installation routine used to install HMS1000, it will not affect the way HMS1000 operates after being successfully installed.

Related Files

Word (.doc) version