It has just come to our attention that there is a serious problem between the security key driver we have distributed and Windows NT 4.0 Service Pack 4. The latest security driver for MC5 must be installed before installing Service Pack 4 otherwise on some systems the system will not be able to reboot into NT again. Below is the application note from Alladin about the problem.
HASP Technical Note
Summary:
To support the technological upgrade in Service Pack 4 for Windows NT 4.0, Aladdin released HASP Device Driver 3.72. Version 3.72 of the HASP Device Driver solves the following problem:
In many but not all cases if you upgrade to SP4 while an older version of the HASP Device Driver is installed you will receive a blue screen error upon reboot. This Windows NT error message will contain the following text "Kmode Exception Error". Versions of the HASP Device Driver that are affected include version 3.1 through 3.64 inclusive. Any version of the HASP Device Driver that is later than 3.7 will not trigger this behavior.
Prevention:
To prevent this problem we recommend downloading the latest security key driver at:
Spectrum Download page
Unzip this file and then run "hinstall /i" to install the latest driver.
Treatment:
If a customer installed SP4 on top of an installation that already had one of the affected HASP Device Driver versions the following treatment is recommended.
We recommend the following steps:
1. If you have a dual boot machine, enter through the alternative operating system and remove the file "haspnt.sys", located at:
<windows>\system32\drivers\
and then reboot.
2. During startup, when it says "Press spacebar now to invoke..." during the loading of NT, press the spacebar. Then chooses the option of restoring the "Last Known Good Configuration" and start NT. Note that this option will work best if the user followed instructions laid out in the Microsoft readme for SP4:
"...it's recommended that you do the following before installing the Service Pack:
1. Update the system Emergency Repair Disk using the Rdisk.exe command with the /s switch.
2. Perform a full backup of the system, including the system registry files.
3. Disable any nonessential third-party drivers and services (that is, drivers and services that aren't required to boot the system).
4. Contact the original equipment manufacturer (OEM) that provided the driver or service for the updated versions of the file(s).
5. Restart the computer and check Event Viewer to ensure there are no system problems that could interfere with the installation of SP4."
NTFS Cases:
NTFS poses special problems. If you want to access a NTFS partition from DOS you need special tools. There is a product called NTFSDOS that may allow you to fix this.
Information on this product can be found at
http://www.sysinternals.com/ntfs20.htm
This product is not in any way related to Aladdin Knowledge Systems and we cannot guarantee its functionality but it may provide an alternative to a complete reinstall.
|
