|
Hardware Registry Secrets Table of contents |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Abstract In this chapter, you will find registry information pertaining to hardware peripherals, such as network adapters, disk controllers, and CD-ROMs. The chapter provides a practical road map to common hardware problems that can be solved by registry tweaking. MOUSE II-1 If you get an error message stating that the ring buffer of your mouse overflowed, you may want to increase the size of the ring buffer. Change this registry entry.
The default is 0x64; increase this value to increase the size of the buffer. Reboot for this change to take effect. KEYBOARD II-2 If you get an error message stating that the ring buffer of your keyboard overflowed, you might want to increase the size of the ring buffer. Change this registry entry.
The default is 0x64; increase this value to increase the size of the buffer. Reboot for this change to take effect. MODEMS II-3 NT 4.0 uses the unimodem protocol to recognize modems. If you have an old modem that isn�t unimodem-compliant and you want NT to use Modem.inf to set the parameters, change this entry.
II-4 If you need to find the firmware revision on your hard drive without physically removing it, these registry entries show you how.
These two entries control the first SCSI peripheral, or in this example, an IDE Quantum Fireball drive. Even though the Fireball is an IDE device, you can look at these keys to obtain the information. Note the Type value, which provides extra verification that you are indeed looking at the right peripheral.
These two entries control the second SCSI peripheral, or in this case, an IDE Toshiba 12 X CD-ROM. Again, note the Type value, which provides extra verification that you are indeed looking at the correct peripheral. CPU II-8 To see what kind of processor chip you are running on a remote computer, look in the registry. These entries give you information about the class of CPU the target machine is running. If you have more than one CPU, the CentralProcessor key has numbered subkeys (1, 2, 3).
This value gives you information about the specific CPU revision.
This value gives you the manufacturer of the CPU.
This value is the actual speed of the CPU. This example says my CPU is faster than 199 Mhz, which it is. I tested this on a 200 Mhz Pentium Pro. NETWORK CARDS Diamond Net Commander II-11 If you have installed a Diamond Multimedia Net Commander ISDN adapter and are having problems, you may want to check these registry entries.
If the Net Commander is functioning properly, the value for Status is In Service. If the value is anything else, the card is not functioning properly. II-12 Problem: after installing the software necessary to run the Net Commander, the configuration screen pop ups every time you reboot. Modify the following registry entry to keep the screen from popping up.
Delete anything in the Value field. Restart the machine for this change to take effect. Digiboard II-13 If RAS can�t see all the ports on your Digiboard multiport serial I/O board, make sure the following registry value is set correctly.
If you have eight ports available, this value should be 8. Restart the machine for these changes to take effect. Iomega Zip Drive II-14 You just bought an Iomega Zip Drive. From time to time you don�t have it connected to your computer, which generates an error. To disable the message, change this entry; it stops the driver from reporting an error to the system log.
Add the following value under the Parameters key:
VIDEO CARDS Diamond Fire GL II-15 When using your Diamond Multimedia Fire GL card, you get this error in the Event Viewer: �Glint Error: VideoPortGetAccessRanges failed.� Try changing this registry entry to solve the problem.
Add the following value:
Restart Windows NT for these values to take effect. STB Virge Velocity 3D II-16 To set the advanced parameters of your STB ViRGE Velcoity 3D Video Card under NT, change the parameters under the following registry key. Several parameters control these advanced settings.
II-23 If you need to find the system�s refresh rate, check this registry entry.
This example value is the refresh rate for an STB ViRGE video card. You must find the appropriate key for your video card, for example, an ATI or Matrox. The value is stored in hexadecimal. Matrox Millenium and Matrox Mystique If you invested in a top-flight video card, you deserve to get the most out of it. These registry settings let you maximize the performance of your Matrox video cards, both the Millenium and the Mystique models.
Device0 refers to the first video card installed on your system.
When set to 1, this value enables the faster AUTOLINE opcode of the drawing engine to draw lines defined by integer coordinates. The convention that determines which pixels contribute to a given line is slightly different in AUTOLINE and in Windows NT. Setting AlternateLines to 1 trades off compliance with the Windows NT conventions for performance. A value of 0 enforces compliance. Lines defined by non-integer endpoint coordinates are not affected by this setting.
Device0 in the key refers to the first video card installed on your system. When set to 1, this value lets your video card hardware accelerate some complex Raster OPerations (ROPs) by executing a sequence of simple ROPs (ORing, ANDing, etc.) on the display. Artifacts in the target display area may flash because an intermediate result, which will be replaced by the final image on the next cycle, is displayed in video RAM on a given refresh cycle. A value of 0 for the entry means that complex ROPs are performed in software.
Device0 in the key refers to the first video card installed on your system. Setting this value to 1 lets the hardware accelerate drawing bitmaps by using off-screen memory for caching them. A value of 0 disables bitmap caching and lets the CPU draw onto all bitmaps. Bitmap caching is internally disabled when a desktop requiring more than one card is in use, regardless of the registry setting.
Device0 refers to the first video card installed on your system. When set to 1, the value lets the frame buffer directly access the write-combining feature of the Pentium Pro processor. Setting this value to 0 may result in slightly slower performance.
Device0 refers to the first video card installed on your system. When set to 1, this value lets the MGA PowerDesk software control refresh rates. A value of 0 allows all available refresh rates to be listed.
Device0 refers to the first video card installed on your system. When set to 1, this value requests the driver to wait for a vertical sync before programming the ramdac with a new pointer shape or a new palette. If you notice stray pixels flashing around the pointer, setting this value to 1 might fix the problem. Setting it to 0 gives you slightly better performance.
Device0 refers to the first video card installed on your system. When set to 1, this value requires the driver to wait until the Millennium hardware is ready to accept new data before programming the next operation. Setting it to 0 results in better performance. On most x86-based systems, the PCI logic should ensure that such a check is redundant. If you�re experiencing problems that might be related to timing (with communication programs, for instance), setting this value to 1 may help.
Device0 refers to the first video card installed on your system. When set to 1, this value requires the Matrox Millennium or Mystique memory to allocate a back buffer. Set this value to 0 if you don�t require a back buffer. Set this value to 1 to fully accelerate 3D animation.
Device0 refers to the first video card installed on your system. When set to 1, this value requires the Matrox Millennium or Mystique memory to allocate a Z buffer. Set it to 0 if you don�t require a Z buffer. To accelerate your 3D rendering, set this value to 1. Setting this value and the User3D.DoubleBuffer to 0 effectively disables any 3D hardware acceleration. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2 |
next page |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||