Export (0) Print
Expand All

Tricks & Traps: Ask Dr. Bob Your Windows NT Questions

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Bob Chronister

Windows NT Magazine, October 1999

Potential SP5 Glitch

I recently upgraded from Service Pack 4 (SP4) to SP5. When I tried to dial in and use Internet Explorer, the Internet kicked me off within 5 minutes. I checked all my modem's settings, and everything seemed fine. I uninstalled SP5, but the problems continued. After I replaced the old modem with a new modem, the problems disappeared. The SP5 upgrade seems to have corrupted the old modem's settings. This service pack upgrade is the first to cause me any problems. Perhaps my problem was coincidental, but the rumor mill says others are experiencing it.

Q: My company has several hundred systems running Windows NT 4.0 Service Pack 3 (SP3). Microsoft released SP5 just as we were about to install SP4. Do we need to install SP4 before installing SP5, or can we go straight to SP5?

A: Your question highlights a common misconception about service packs. Microsoft Windows NT® service packs are cumulative with regard to system files and fixes, but SP5 doesn't duplicate the optional features and utilities that SP4 provides. Therefore, I'd install SP4 before installing SP5. SP5 doesn't include the following SP4 features:

  • NetShow Services—This enhancement lets ISPs and corporations deliver the highest-quality audio and video at every possible bandwidth across the Internet or enterprise networks.

  • Microsoft Windows Media® Player—This utility replaces Microsoft ActiveMovie® and NetShow Player and adds many new features that are essential to today's media content. For example, Media Player uses sophisticated compression and buffering techniques to deliver live and on-demand audio, video, and illustrated audio. Media Player continuously decompresses content and plays it in real time, letting users listen to and watch live audio and video programs or navigate on-demand audio and video content.

  • Internet Explorer 4.01 SP1—A service pack update.

  • Microsoft Web-Based Enterprise Management (WBEM)—This feature represents an industry-wide (i.e., BMC Software, Cisco Systems, Compaq, Intel, and Microsoft) initiative to develop a standardized technology for accessing management information in enterprise environments.

  • Microsoft Site Server Express—This utility collects and analyzes Microsoft Internet Information Server (IIS) log files from one server.

Q: I know that most BIOS manufacturers post beep codes, but I don't know how to fix the errors these codes represent. Can you summarize known fixes to the most common beep code errors?

A: Beep codes vary according to the BIOS manufacturer. However, the various codes' fixes are fairly uniform. The following codes apply to the AMI WinBIOS setup for most new Pentium II and III systems.

  • 1, 2, or 3 beeps—Memory failures. In all three cases, reseat the DIMMs. If the beeps recur at boot, remove the DIMMs and ensure that the DIMMs' contacts and sockets are clean, then reseat the DIMMs. If the errors continue, replace the DIMMs. Make certain that the speed and voltage of the DIMMs are correct. If you still have problems, you probably need to replace the motherboard.

  • 4 beeps—The timer isn't operational. Replace the motherboard.

  • 5 beeps—A CPU error. Replace the motherboard.

  • 6 beeps—Gate A20 failure. Reseat the keyboard controller chip. If this fix fails, replace the keyboard controller chip. If the socket is bad, you need a new motherboard.

  • 7 beeps—A processor exception interrupt error. Replace the motherboard.

  • 8 beeps—A video memory problem. Replace the adapter or the VRAM.

  • 9 beeps—The BIOS ROM chip is bad. Replace the chip.

  • 10 beeps—A shutdown error for the CMOS register. Replace the motherboard.

For more information about beep codes, see Michael D. Reilly, "The NT Boot Process," December 1998.

Q: I recently upgraded my system to a SCSI 3 Ultra 2 chipset. To my surprise, Windows NT 4.0 recognized only the first eight LUs of my new CD-ROM jukebox. How can I fix this problem?

A: Windows NT 4.0 detects only the first eight LUs on a SCSI device. To work around this limitation, install Service Pack 4 (SP4) and open a Registry editor (e.g., regedit.exe). Remember that altering the Registry can cause serious problems in Windows NT. Always update your Emergency Repair Disk (ERD) before proceeding. Go to the HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \ServicesDriver Service\Parameters Registry key, where Driver Service is your SCSI driver's name. Create the Devicen LargeLuns subkey (where n is the SCSI bus number) of type REG_DWORD, and set the value to 0x1. Screen 1 shows this value for an Adaptec 2940 Ultra Wide SCSI controller, where the SCSI bus number is 0.

Q: What is Synchronous DRAM (SDRAM), and what advantages does it offer?

A: SDRAM is a DRAM technology that synchronizes a system's memory to the timing of its CPU. SDRAM differs from standard DRAM in several ways:

  • Synchronous operation—Unlike conventional asynchronous DRAM, SDRAM has a clock input that lets the system clock control the CPU's step-by-step operation and SDRAM's operation. This arrangement produces effective communication (i.e., access) between the memory and the CPU.

  • Cell banks—The memory cells inside the SDRAM chip reside in two independent cell banks. These banks enable interleaving, which reduces the total memory cycle and results in faster transfer rates.

  • Burst mode—Bursting is a rapid data-transfer technique that automatically generates a block of data every time the processor requests an address. Bursting applies to read operations and write operations.

SDRAM supports data transfers as fast as 125MHz. In earlier memory designs, you had to set wait states on the CPU so that memory could supply needed data to the CPU. SDRAM seems to eliminate this bottleneck.

Q: Since I upgraded to Service Pack 4 (SP4), I can't stop my servers from logging crashes in their event logs. What's going on?

A: SP4 records three events in the system event log that are new to the service pack:

  1. Clean Shutdown Event (Event ID: 6006)—The Event Log Service records a clean shutdown event whenever a user or program initiates OS shutdown.

  2. Dirty Shutdown Event (Event ID: 6008)—The Event Log Service records a dirty shutdown event whenever the OS doesn't shut down cleanly. The most common dirty shutdown occurs because of power loss. The system records this event when you reboot. While Windows NT Server is running, the system periodically writes a timestamp to the Registry. Each time the system writes a last alive timestamp to the Registry, the timestamp also flushes to disk (so that you can read the event when you reboot). By default, the system writes the last alive timestamp every 5 minutes to the HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Windows \CurrentVersion \Reliability \LastAliveStamp Registry key. To change the interval, add the D_WORD value TimeStampInterval. When you set this value to 0 minutes, you prevent any last alive timestamp logging, and the system will write only the boot and Clean Shutdown stamps to the event log.

  3. Whenever you boot the system, the Event Log Service records a system version event containing OS version information. This event lets you easily analyze Windows NT system event logs by OS version.

Before SP4, logging OS crashes in the event log (Save Dump events) was optional. The system recorded crash events by default, but a systems administrator could disable this behavior in the System applet in Control Panel by clearing the Write an event to the system log check box on the Startup/Shutdown tab. In SP4, recording crashes in the event log is mandatory for Windows NT Server (i.e., an administrator can't disable it) but remains optional in Windows NT Workstation.

Q: I'm new to Windows NT 4.0 and am seeking setup tips. For example, how much disk space does an installation require? Does Windows NT support all hardware? If not, what do I need to avoid?

A: A standard installation requires a minimum of 124MB of hard disk space. If you copy the i386 directory to the local computer, you'll need 223MB of hard disk space. I always recommend that you also reserve sufficient space for your pagefile (i.e., RAM plus 12MB).

Window NT 4.0's hardware support is impressive. Check out the latest Hardware Compatibility List (HCL) on Microsoft's Web site at http://www.microsoft.com/isapi/hwtest/hcl.idc. If your computer uses nonstandard or proprietary bus components, Windows NT might incorrectly detect controllers and settings. In addition, some nonstandard enhancements (e.g., special bus drivers, caching chips for burst-mode transfer) don't follow industry standards. If the information that Windows NT gathers is incorrect, Setup might fail at a late stage. Incorrect detection is often a symptom of a hardware or configuration problem that might also cause Setup failure.

Q: I've heard that Windows NT can support up to 8 GB on the bootable partition. However, whenever I run Setup, Windows NT limits me to 4 GB on this volume. What can I do to get the full 8 GB?

A: Windows NT can support up to 8 GB on the system partition (i.e., the primary partition from which the system boots). However, to achieve this support, you need to work around a limitation in the Windows NT Setup utility.

Windows NT Setup always formats your hard disk as FAT, even if you select NTFS as the format type when managing disks during Setup. When you select NTFS, the hard disk first formats as FAT, then converts to NTFS later in the setup process. FAT volumes have a maximum size of 4 GB under Windows NT; this limitation effectively restricts the maximum size of the system partition that Windows NT Setup creates to 4 GB. (Typically, FAT16 is limited to 2 GB, but Windows NT supports 4 GB because of the operating system's support for 64 KB cluster sizes.)

One way around this problem is to connect the hard disk to another Windows NT computer and format the disk as an NTFS volume prior to running Windows NT Setup on the original system. Another option is to use a third-party disk-preparation utility capable of formatting the hard disk as NTFS. (I've had some problems using such third-party utilities, so I recommend using the first method if possible.) Using these methods, you can create bootable NTFS system partitions of up to 8 GB in size.

Editor's note: Sean Daily contributed to this Tricks & Traps.

About the Author

Bob Chronister is a contributing editor for Windows NT Magazine and president of Chronister Consultants in Mobile, Alabama. He is coauthor of Windows NT Backup and Recovery (Osborne/McGraw-Hill). You can reach him at bob@winntmag.com.

Send your tips and questions to Windows NT Magazine. You can also visit Bob Chronister's online Tricks & Traps at http://www.winntmag.com/forums/index.html.

The above article is courtesy of Windows NT Magazine. Click here to subscribe to Windows NT Magazine.

We at Microsoft Corporation hope that the information in this work is valuable to you. Your use of the information contained in this work, however, is at your sole risk. All information in this work is provided "as-is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Microsoft Corporation. Microsoft Corporation shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages. All prices for products mentioned in this document are subject to change without notice.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft