About graphic drivers: Difference between revisions

adapted to wiki format
(New page: Category:Howto I just stumbled upon this post in forums. It's not yet formatted to wiki style so some parts might look confusing at first sight. But I am on it makeing it more clearly...)
 
(adapted to wiki format)
Line 1: Line 1:
[[Category:Howto]]
[[Category:Howto]]


I just stumbled upon this post in forums. It's not yet formatted to wiki style so some parts might look confusing at first sight. But I am on it makeing it more clearly represented.
I just stumbled on this post in forums.


[http://flightgear.org/forums/viewtopic.php?f=2&t=712&st=0&sk=t&sd=a&start=15#p7232 Link] to the original post in forums.
[http://flightgear.org/forums/viewtopic.php?f=2&t=712&st=0&sk=t&sd=a&start=15#p7232 Link] to the original post.


-----
-----
=== OpenGL and Video input/output ===


The following answer covers missing video input/output and knocked out OpenGL support after updating nVidia drivers.
The following answer covers missing video input/output and knocked out OpenGL support after updating nVidia drivers.
Line 40: Line 41:
To do so, I'd suggest the following procedure:
To do so, I'd suggest the following procedure:


1) Enter Control Panel > Add/Remove Programs
# Enter Control Panel > Add/Remove Programs<br /><br />
# Remove both drivers "NVIDIA Drivers" and "NVIDIA WDM Drivers".<br />If asked to remove stored nView profiles, answer "No"<br /><br />If your current driver was very old or if you have problems to install newer driver versions, perform steps 3) through 5):<br /><br />
# Reboot into "Safe Mode" (press F8 while booting)<br /><br />
# Remove C:\WINDOWS\system32\nv4_disp.dll and C:\WINDOWS\system32\drivers\nv4_mini.sys if present and any copies of these files in C:\WINDOWS\system32\dllcache (Note: directory has 'hidden' attribute). I don't think you need a commercial driver cleaner utility to get rid of the driver.<br /><br />
# Reboot and abort the "Found New Hardware Wizzard" that may pop up.<br /><br />
# If you need to try out several driver versions, you can speed up the test cycle by setting a "System Restore Point" entitled "No graphics driver" right now.<br /><br />
# Install the display driver. Do not install the WDM driver yet. System detects "NVIDIA GeForce4 MX 440" and uses newly installed driver. You only need to reboot the system immediately if the setup recommends to do so.<br /><br />
# Install WDM driver and reboot.<br /><br />
# "Found New Hardware Wizzards" will pop up and detect devices<br />"nVidia WDM A/V Crossbar" and<br />"nVidia WDM Video Capture (universal)"<br />and offer to search for a suitable driver.<br /><br />
# Select "No" for search and let the system install driver automatically.<br /><br />
# System will use the newly installed WDM drivers for both devices.<br />During installation, it may complain about missing certification - confirm to continue setup.<br /><br />
# If driver exposes any bugs, restore system to point "No graphics driver" and go back to step 7)<br /><br />
# Send a complain to NVIDIA or ATI if your hardware is in the "Products supported" list but not all features (like video capture) are supported by the newest driver version.<br />The NVIDIA and ATI programmers are still very busy to compete against each other. They apparently do not test new driver versions with all released hardware versions. So they need this kind of feedback in order to track down their bugs or at least publish compatibility issues on their web site.


2) Remove both drivers "NVIDIA Drivers" and "NVIDIA WDM Drivers"
  If asked to remove stored nView profiles, answer "No"


If your current driver was very old or if you have problems to install newer
=== Additional notes ===
driver versions, perform steps 3) through 5):


3) Reboot into "Safe Mode" (press F8 while booting)
4) Remove C:\WINDOWS\system32\nv4_disp.dll and C:\WINDOWS\system32\drivers\nv4_mini.sys if present
  and any copies of these files in C:\WINDOWS\system32\dllcache (Note: directory has 'hidden' attribute)
  I don't think you need a commertial driver cleaner utility to get rid of the driver.
5) Reboot and abort the "Found New Hardware Wizzard" that may pop up.
6) If you need to try out several driver versions, you can speed up the test cycle by
  setting a "System Restore Point" entitled "No graphics driver" right now.
7) Install the display driver. Do not install the WDM driver yet.
  System detects "NVIDIA GeForce4 MX 440" and uses newly installed driver.
  You only need to reboot the system immediately if the setup recommends to do so.
8) Install WDM driver and reboot.
9) "Found New Hardware Wizzards" will pop up and detect devices
    "nVidia WDM A/V Crossbar" and
    "nVidia WDM Video Capture (universal)"
  and offer to search for a suitable driver.
10) Select "No" for search and let the system install driver automatically.
11) System will use the newly installed WDM drivers for both devices.
    During installation, it may complain about missing certification - confirm to continue setup.
12) If driver exposes any bugs, restore system to point "No graphics driver" and go back to step 7)
13) Send a complain to NVIDIA or ATI if your hardware is in the "Products supported" list but not all
    features (like video capture) are supported by the newest driver version.
    The NVIDIA and ATI programmers are still very busy to compete against each other.
    They apparently do not test new driver versions with all released hardware versions.
    So they need this kind of feedback in order to track down their bugs or at least publish
    compatibility issues on their web site.
Additional notes:
-----------------
Although my system was shipped with driver version 28.32, after removing the graphics driver
Although my system was shipped with driver version 28.32, after removing the graphics driver
entirely, driver versions 45.33 and 53.04 did not even recognize the hardware automatically.
entirely, driver versions 45.33 and 53.04 did not even recognize the hardware automatically.
Line 103: Line 73:




Addendum:
=== Addendum ===
---------
 
The NVidia drivers have a "feature" that turns out to be a pretty nasty pitfall for unaware users,
The NVidia drivers have a "feature" that turns out to be a pretty nasty pitfall for unaware users,
namely "Standard OpenGL support". "Standard" here means hardware accelerated -OR- software emulated!
namely "Standard OpenGL support". "Standard" here means hardware accelerated -OR- software emulated!
Line 168: Line 138:




Overclocking
=== Overclocking ===
------------
 
The NVidia drivers supply builtin overclocking settings. For security reasons, these need to be unlocked
The NVidia drivers supply builtin overclocking settings. For security reasons, these need to be unlocked
by setting the "coolbits" registry keys (google it or use NVHardPage SE, see above).
by setting the "coolbits" registry keys (google it or use NVHardPage SE, see above).
Line 190: Line 160:
[] default clock rates for GeForce4 MX440
[] default clock rates for GeForce4 MX440
() stable overclocked rates for (MY!) GeForce4 MX440
() stable overclocked rates for (MY!) GeForce4 MX440


Overclocked Performance:
Overclocked Performance:
------------------------
 
The Geforce4 MX 440 is DirectX7 complient, not DirectX8 or later.
The Geforce4 MX 440 is DirectX7 complient, not DirectX8 or later.
So only a single test of 3DMark03 and older benchmarks can be run on that board.
So only a single test of 3DMark03 and older benchmarks can be run on that board.
Line 200: Line 171:
This should be about the maximum, you can get out of your MX440 board, I guess.
This should be about the maximum, you can get out of your MX440 board, I guess.


WARNING: The above mentioned rates are valid for MY OWN board. YOUR board may accept
'''WARNING:''' The above mentioned rates are valid for MY OWN board. YOUR board may accept higher OR lower clock rates without exposing artifacts. Watch your screen   carefully when running tests at newly overclocked rates and abort them as soon
        higher OR lower clock rates without exposing artifacts. Watch your screen
as artifacts or system freezes occur!
        carefully when running tests at newly overclocked rates and abort them as soon
        as artifacts or system freezes occur!




Greetings,
Greetings,
Frank Heimes
Frank Heimes
392

edits