I have Win2k and this is what basic detective work has given me:
Win2k stores monitor information under the key
HKEY_LOCAL_MACHINE/System/ControlSet001/Enum/DISPLAY/
. I personally have three more keys under that one: Default_Monitor, nvWin2kDualView (which I presume is a Detonator thing since my graphics card doesn''t support dual view) and VSC5A44 (which I think is the real monitor driver key). These three keys are also duplicated under ControlSet002 and CurrentControlSet. Now, whereas the video driver key is uniquely referenced from a certain key, the monitor driver key isn''t which raises the following question: where should I look to find the currently active monitor information? CurrentControlSet seems like a reasonable place to start with for the root key.
As for the subkeys, there can be any number of them (for instance if you have more than one monitor installed). Quick checking shows that the correct monitor information can be found in places marked as bold:
HKEY_LOCAL_MACHINE/System/ControlSet001/Enum/DISPLAY/
.../ControlSet002/...
.../CurrentControlSet/...
+ Default_Monitor
+ 5&30377192&0&11223344&01&05
+ 5&30377192&1&11223344&01&05
+ nvWin2kDualView
+ 5&30377192&0&c9000001&01&05
+ 5&30377192&1&c9000001&01&05
+ VSC5A44
+ 5&30377192&1&22446688&01&05
I have no idea how to decide that these are the places I should read to find out the proper monitor information... Anybody got any experience with this?
Furthermore, I''m currently aiming at getting this thing to work on NT - is the registry structure the same on WinXP? I know pertty much for a fact that non-NT has it all messed up (or NT has it all messed up, depends on how you look at it)...
Cheers
"Literally, it means that Bob is everything you can think of, but not dead; i.e., Bob is a purple-spotted, yellow-striped bumblebee/dragon/pterodactyl hybrid with a voracious addiction to Twix candy bars, but not dead."- kSquared