Display NVidia driver version from the command line

[art_l_j_PlanetAMD64]

I have made a couple of batch files, that can be run from the command line, to display the NVidia driver version from the Registry, and save it to a text file.

The display batch file "displaynvver.bat":

Code: Select all

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation" /s | find "Display.Driver" | find "Display.Update"

"getnvver.bat": Save the NVidia driver version to a text file:

Code: Select all

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation" /s | find "Display.Driver" | find "Display.Update" >nvver.txt

The "kludgy" look to how this is done, is necessary so that the same batch files can be used on both Windows XP and Windows 7/Vista. The idea is that even a non-technically inclined person can display or save the NVidia driver version on their computer.

This information could possibly even be added to the FAHClient "header" at the top of every log file in an NVidia-GPU system, perhaps after the "</config>" line. Having the NVidia driver version available in every log file could be a help, in diagnosing user's problems.

Here is what it looks like when run from the command line:

[k1wi]

If you're using PrecisionX (EVGA but I believe it works with any NVidia card) you can also get the driver version by clicking the i button in the gui.

[PantherX]

...The "kludgy" look to how this is done, is necessary so that the same batch files can be used on both Windows XP and Windows 7/Vista. The idea is that even a non-technically inclined person can display or save the NVidia driver version on their computer.

This information could possibly even be added to the FAHClient "header" at the top of every log file in an NVidia-GPU system, perhaps after the "</config>" line. Having the NVidia driver version available in every log file could be a help, in diagnosing user's problems...

If this would work on AMD systems and those systems that don't have an AMD/Nvidia GPU, then it might be possible to suggest it to the developers.

[art_l_j_PlanetAMD64]

If you're using PrecisionX (EVGA but I believe it works with any NVidia card) you can also get the driver version by clicking the i button in the gui.

Yes, CCleaner can display this information as well, but I was thinking of something that could be used automatically, for example to add the display driver info to the FAHClient log file.

[7im]

It would need to work with Win, Lin and OSX to be added to the log...

[art_l_j_PlanetAMD64]

If this would work on AMD systems and those systems that don't have an AMD/Nvidia GPU, then it might be possible to suggest it to the developers.

OK, I am going to try to find an AMD/ATI system, to see if a "universal" version of this can be made to work. The "/s" option means to recursively descend through the registry, so the command could be started from "HKEY_LOCAL_MACHINE\SOFTWARE". As long as the "Display.Driver" part stayed the same for all graphics chipset vendors (eg NVidia/ATI/Intel), it might be made to work "universally".

[PantherX]

It would need to work with Win, Lin and OSX to be added to the log...

IMO, since there isn't any GPU folding on Linux/OSX, why should Windows be deprived of this helpful feature? However, once GPU folding is available for Linux/OSX, then a OS specific method (or not) might be implemented... assuming this feature gets accepted in the first place.

[art_l_j_PlanetAMD64]

If this would work on AMD systems and those systems that don't have an AMD/Nvidia GPU, then it might be possible to suggest it to the developers.

OK, I just tried it, starting from "HKEY_LOCAL_MACHINE\SOFTWARE", and it does work, but it takes too long (40+ seconds) on my 3.4GHz Phenom II X4 965 system. It works very quickly when starting from "HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation".

Looking through the registry in that system, there is a key/value tree that starts at "HKEY_LOCAL_MACHINE\SOFTWARE\ATI Technologies". It's for the ASUS M4A79T motherboard, for the SouthBridge. If that also held true for the "Display.Driver" value, then the registry values for both NVidia and ATI can quickly be found. The same could be done, for any vendors whose cards were added to GPUs.txt. It should be a very simple job to find the "start" of the tree structure closest to the "Display.Driver" value, for any vendor whose cards were added to GPUs.txt.

[art_l_j_PlanetAMD64]

Well, here is someone who has a system with both AMD/ATI and NVidia:
successfully folding AMD + Nvidia + Intel in one PC ~64k PPD

I'm sure he could be asked to look into his registry, to see how to locate the AMD/ATI "Display.Driver" value.

[art_l_j_PlanetAMD64]

Here are batch files that work on an ATI system.

"displayativer.bat":

Code: Select all

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\ATI Technologies" /s | find "ReleaseVersion"

"getativer.bat":

Code: Select all

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\ATI Technologies" /s | find "ReleaseVersion" >ativer.txt

This is on a Windows XP Home SP3 32-bit version, that has an ATI All-In-Wonder 9600 XT

I don't know if ATI uses "ReleaseVersion" for their newer GPUs, someone who has a newer ATI GPU will have to answer that one. CCleaner also displays "8.593.100-100210a-095952E-ATI" as the ATI Display Driver on this computer.

Here is what it looks like in the Command Prompt window:

[7im]

It would need to work with Win, Lin and OSX to be added to the log...

IMO, since there isn't any GPU folding on Linux/OSX, why should Windows be deprived of this helpful feature? However, once GPU folding is available for Linux/OSX, then a OS specific method (or not) might be implemented... assuming this feature gets accepted in the first place.

Because PG are already working on GPU for linux, and because one of the big design goals for V7 is cross platform compatibility. Kluging multiple registry reads for a single platform likely falls out of that cross platform design goal.