Recent Post-SP5 Hotfixes
There are 11 hotfixes for Windows NT Service Pack 5 (SP5)—four released or updated since the beginning of June of this year, and four issued since July 14, 1999. I’ve discussed the Client-Server Runtime Subsystem (CSRSS) fix and RAS/RRAS password hotfixes in previous columns, so I’ll address the three most recent hotfixes here. You’ll appreciate that Post-SP5 hotfixes have no interdependencies, so you can install them in any order.

The three hotfixes I discuss below are available for NT and Windows NT Server 4.0, Terminal Server Edition. The BIOS2 hotfix is available for both SP4 and SP5. You can download the English version of Post-SP5 hotfixes for NT at ftp://ftp.microsoft.com/bussys/ winnt/winnt-public/ fixes/usa/NT40/hotfixes-postSP5/. You can find Terminal Server hotfixes at ftp://ftp.microsoft.com/ bussys/winnt/winnt-public/fixes/usa/ NT40TSE/hotfixes-postSP5/. To locate the international version, select the appropriate country from the /fixes directory.

Y2K BIOS Hotfix. The BIOS2-fix hotfix was released last week to correct two Y2K-specific problems omitted from SP5. The BIOS2-fix correctly refreshes the realtime clock when located in a time zone that does not observe Daylight Saving Time; it also updates the multi-processor kernel, if one exists. There are two BIOS2-fix updates, one for SP4 and one for SP5, so be sure you download the correct version for your installed service pack. You can find the instructions for checking your installed hotfix version (there are three—the original, BIOS, and BIOS2) listed by filename and size in the file Q216913.txt, which is located in the hotfix directory.

Phone Dialer Hotfix. According to Microsoft Support Online article Q237185 (http://support.microsoft.com/support/kb/articles/q237/1/85.ASP), the phone dialer code does not properly remove entries from memory when the dialer.ini file contains a string between 128 and 256 characters in the \[Last Number Dialed\] field—a bug that generates an access violation when you exit the dialer code. If your system has this problem, you’ll see the following message in the Application event log:

The application, exe\dialer.dbg, generated an application error.
The error occurred on @