D
Daniel
I have a Dell Dimension 8200 desktop with Windows XP Home Edition and a
GeForce3 Ti200 64mb AGP card (factory installed). I updated with NVIDIA
graphics drivers (WHQL certified) several times over the 2 plus years I've
had the system, with NVIDIA'S v.53.03 drivers installed until last week, and
have had no real problems.
Last week, I downloaded NVIDIA'S v.56.64 drivers for XP, and did not
discover the WHQL certification did not apply to my particular card until
halfway through the installation. I continued anyway, and here's where the
confusion starts - I don't recall what prompted me to remove the new
drivers, but after restarting Windows, the "found new hardware" icon
appeared in systray, and I went through all types of changes in my attempts
to restore the previous drivers. When all was said and done, I had to use
the Dell Resource CD for Drivers & Utilities to install the drivers that
originally came with my system. Once this was done, I was able to
install/update to v.53.03 drivers - however, I ran into problems when I
tried to use Coolbits to restore overclocking to the Display Properties.
Coolbits is a Registry tweak used to restore the overclocking option in the
GeForce3 Ti200 tab of Display Properties, and it can be downloaded from the
Guru of 3D site: http://downloads.guru3d.com/download.php?det=201. You can
also restore overclocking by manually editing the Registry as described
here: http://oc3dmark.octeams.com/tip02.html.
However, when I double-clicked coolbits.exe, I got the following error:
"Registry Editor (title bar)
Cannot import C:\DOCUME~1\Daniel\MYDOCU~1\TEMP\coolbits.reg: Not all data
was successfully written to the registry. Some keys are open by the system
or other processes."
And when I tried to manually edit the registry by writing a new DWORD value
for NVTweak in the NVIDIA Corporation key's right pane (HKLM\Software\NVIDIA
Corporation\NVTweak), I received the following error, and was not allowed to
do so:
"Error Creating Value (title bar)
Cannot create value: Error writing to the registry."
In the Screenshot shown on the instructions web page, the following appears
in the right pane of the registry for the NVTweak key:
"NcCplExposeWin2kDualView" (without quotes). This does not appear in the
right pane of my registry - only "Default" appears. In the past, when I used
the Coolbits registry tweak, it worked properly and access to overclocking
was restored to Display Properties.
In addition to the issues described above, inconsistent information
concerning the drivers appears in Display Properties. When I click the
Settings tab in Display Properties, and then the Advanced button, the "Dell
M991 and NVIDIA 64MB DDR GeForce Ti200 Properties" window opens, and here's
where inconsistencies appear. If I click the "Adapter" tab, then the
"Properties" button, followed by the "Driver" tab on the new "Properties"
window, it displays the following:
NVIDIA 64MB DDR GeForce Ti200 (Dell) Properties (title bar)
NVIDIA 64MB DDR GeForce Ti200 (Dell)
Driver Provider: NVIDIA
Driver Date: 08/16/01
Driver Version: 1.4.6.2
Digital Signer: Not digitally signed
AND THEN, when I click the "Driver Details" button, the following is
displayed:
NVIDIA 64MB DDR GeForce Ti200 (Dell)
Driver files:
C:\WINDOWS\System32\DRIVERS\nv4_mini.sys
Provider: NVIDIA Corporation
File version: 6.14.10.5303
Copyright: (C) NVIDIA Corporation. All rights reserved.
Digital Signer: Not digitally signed
NOTE THE DIFFERENCE IN FILE/DRIVER VERSIONS!
I'M HOPING SOMEONE CAN HELP ME UNDERSTAND:
1. Why the driver information differs from one place to another in
Properties, and whether this represents any type of problem...
AND ALSO:
2. How to restore OVERCLOCKING in Display Properties? Will something have to
be done to clean up the registry? Might returning to the original Dell
drivers, and then removing all the registry entries related to later NVIDIA
driver installations, followed by updating the drivers again make it
possible? How can this, or whatever is required, be accomplished? If you
provide a suggestion, please include step by step instructions - my tech
abilities and knowledge are pretty limited.
Any and all suggestions are welcome - if more information is needed, please
let me know, and I'll do my best to provide it - thank you!
Daniel D.
Santa Monica, CA
(e-mail address removed)
GeForce3 Ti200 64mb AGP card (factory installed). I updated with NVIDIA
graphics drivers (WHQL certified) several times over the 2 plus years I've
had the system, with NVIDIA'S v.53.03 drivers installed until last week, and
have had no real problems.
Last week, I downloaded NVIDIA'S v.56.64 drivers for XP, and did not
discover the WHQL certification did not apply to my particular card until
halfway through the installation. I continued anyway, and here's where the
confusion starts - I don't recall what prompted me to remove the new
drivers, but after restarting Windows, the "found new hardware" icon
appeared in systray, and I went through all types of changes in my attempts
to restore the previous drivers. When all was said and done, I had to use
the Dell Resource CD for Drivers & Utilities to install the drivers that
originally came with my system. Once this was done, I was able to
install/update to v.53.03 drivers - however, I ran into problems when I
tried to use Coolbits to restore overclocking to the Display Properties.
Coolbits is a Registry tweak used to restore the overclocking option in the
GeForce3 Ti200 tab of Display Properties, and it can be downloaded from the
Guru of 3D site: http://downloads.guru3d.com/download.php?det=201. You can
also restore overclocking by manually editing the Registry as described
here: http://oc3dmark.octeams.com/tip02.html.
However, when I double-clicked coolbits.exe, I got the following error:
"Registry Editor (title bar)
Cannot import C:\DOCUME~1\Daniel\MYDOCU~1\TEMP\coolbits.reg: Not all data
was successfully written to the registry. Some keys are open by the system
or other processes."
And when I tried to manually edit the registry by writing a new DWORD value
for NVTweak in the NVIDIA Corporation key's right pane (HKLM\Software\NVIDIA
Corporation\NVTweak), I received the following error, and was not allowed to
do so:
"Error Creating Value (title bar)
Cannot create value: Error writing to the registry."
In the Screenshot shown on the instructions web page, the following appears
in the right pane of the registry for the NVTweak key:
"NcCplExposeWin2kDualView" (without quotes). This does not appear in the
right pane of my registry - only "Default" appears. In the past, when I used
the Coolbits registry tweak, it worked properly and access to overclocking
was restored to Display Properties.
In addition to the issues described above, inconsistent information
concerning the drivers appears in Display Properties. When I click the
Settings tab in Display Properties, and then the Advanced button, the "Dell
M991 and NVIDIA 64MB DDR GeForce Ti200 Properties" window opens, and here's
where inconsistencies appear. If I click the "Adapter" tab, then the
"Properties" button, followed by the "Driver" tab on the new "Properties"
window, it displays the following:
NVIDIA 64MB DDR GeForce Ti200 (Dell) Properties (title bar)
NVIDIA 64MB DDR GeForce Ti200 (Dell)
Driver Provider: NVIDIA
Driver Date: 08/16/01
Driver Version: 1.4.6.2
Digital Signer: Not digitally signed
AND THEN, when I click the "Driver Details" button, the following is
displayed:
NVIDIA 64MB DDR GeForce Ti200 (Dell)
Driver files:
C:\WINDOWS\System32\DRIVERS\nv4_mini.sys
Provider: NVIDIA Corporation
File version: 6.14.10.5303
Copyright: (C) NVIDIA Corporation. All rights reserved.
Digital Signer: Not digitally signed
NOTE THE DIFFERENCE IN FILE/DRIVER VERSIONS!
I'M HOPING SOMEONE CAN HELP ME UNDERSTAND:
1. Why the driver information differs from one place to another in
Properties, and whether this represents any type of problem...
AND ALSO:
2. How to restore OVERCLOCKING in Display Properties? Will something have to
be done to clean up the registry? Might returning to the original Dell
drivers, and then removing all the registry entries related to later NVIDIA
driver installations, followed by updating the drivers again make it
possible? How can this, or whatever is required, be accomplished? If you
provide a suggestion, please include step by step instructions - my tech
abilities and knowledge are pretty limited.
Any and all suggestions are welcome - if more information is needed, please
let me know, and I'll do my best to provide it - thank you!
Daniel D.
Santa Monica, CA
(e-mail address removed)