PDA

View Full Version : Registry hack to enable old control panel


Quick420
05-09-07, 10:37 AM
Someone told me about a registry change or 'hack' if you prefer to enable the old control panel,I should have written it down.Does anyone remember? I'll give the 160.03 a try if I can use the old cp.;)

My neighbour bookmarked a site....heres the hack:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NvCplApi\Policies]
"SedonaDisable"=dword:00000002
"ContextUIPolicy"=dword:00000001
"TaskbarUIPolicy"=dword:00000001
"CplGroupUIPolicy"=dword:00000002

This will enable the old control panel.

malonn
05-09-07, 11:46 AM
Or, you can add:
HKLM,"Software\NVIDIA Corporation\Global\NvCplApi\Policies",SedonaDisable, %REG_DWORD%,2
to the "[nv_ControlPanelSettings]" of you INF. This will allow you to switch between the old and new control panels also.

Quick420
05-09-07, 12:15 PM
Good work.I wonder why nVidia disabled the option of using either control panel? It would only tend to improve customer satisfaction if we had 2 cp's to choose from leaving the end decision to the consumer,but I digress.

Elvin Presler
05-09-07, 04:46 PM
Or, you can add:
HKLM,"Software\NVIDIA Corporation\Global\NvCplApi\Policies",SedonaDisable, %REG_DWORD%,2
to the "[nv_ControlPanelSettings]" of you INF. This will allow you to switch between the old and new control panels also.

I just did this and installed these drivers and this DOES NOT work.....*snip and edit*

EDIT #1:
Correction, it does work. The difference is, you now have to start the new control panel once (didn't used to require this step) and find the option to use the old CP in the pull down menu there. Then the old CP is back. Thanks and sorry for posting the misinformation for a second there before the edit.

Now to go test it and see if it actually still works properly, unlike the last few drivers beyond 8456 I tried.

EDIT #2:
No, it doesn't work properly. That took about 10 seconds to start finding broken items in it. Setting Antialiasing to application preference will not save, it goes back to manual settings. I stopped there. It's not worth jacking with any more. Nvidia has ruined the old CP and forced an unbelievably crappy, and overwhelmingly unwanted new one down our throats. Screw it, back to 8456 for me, and ATI for my next card probably.

gstanford
05-09-07, 09:54 PM
The only thing the control panel is useful for other than TV out is refresh overrides, if you are using a CRT. nHancer is more than capable of handling the rest and better than any control panel nvidia has ever come up with.

Asciicodeplus
05-10-07, 01:21 AM
Each time I use this or any other CP registry hack I just see the old CP once and I use it, then I click on my desktop properties and I can't see the options anymore, just the new control panel button, and this happens with all the drivers I install :/

I try to recover the old CP clicking the registry hack again but it doesn't work anymore, I have to reinstall the driver or install a new one and use the registry hack again to be able to use the old CP for a single time again b4 it disappears

F_L_C
05-10-07, 02:15 AM
[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NvCplApi\Policies]
"SedonaDisable"=dword:00000002
"ContextUIPolicy"=dword:00000001
"TaskbarUIPolicy"=dword:00000001
"CplGroupUIPolicy"=dword:00000002

The only entries you need to get the old CP back are:

"ContextUIPolicy"=dword:00000001
"TaskbarUIPolicy"=dword:00000001

Any other entry is unneccesary. Using a value of 2 will get you the new CP. And using a value of 3 will get you old and new.

For 6 and 7 series cards, they stopped supporting us over six months ago. You can tell the recent flood of driver leaks 1xx.xx are really not intended for anything other than 8 series cards by looking at the default new CP that comes with them: try to do something simple like get a temp reading and it tells you to install ntune, for christ's sake. Why is this new CP not capable of OCing and getting temp readings like in the past? Does noone see how fundamentally flawed their project is?

Asciicodeplus
05-10-07, 03:10 AM
Still the same problem

easyrider
05-10-07, 07:43 AM
thanx F_L_C, that's alot better than what I had, heh, much simpler

F_L_C
05-10-07, 03:47 PM
Still the same problem

My post wasn't intended to solve your problem. But if I remember correctly, others have experienced your problem and found out they needed to do a thorough uninstall (ie deleting leftover dirs and reg keys) before installing any of the recent leaks.

Asciicodeplus
05-10-07, 04:28 PM
I see, I'll try that

SJA06
05-12-07, 04:02 AM
Try this

Windows Registry Editor Version 5.00
;Enables Classic Nv Controll Panel
;Note: New CP is totally disabled

[HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\NvCplApi\Policies]
"DevPolicies"=dword:00000000
"ModePolicies"=dword:00000000
"ModePersist_GPU:0_Mode:0"=hex:00,00,00,00,40,00,00,00,00,00,00,00,00,00,00, 00,\
05,00,00,00,00,00,00,00,05,00,00,00,00,00,00,00,00 ,00,00,00
"LutPersistDesktop_GPU:0_Head:0"=hex:00,00,00,00,64,00,00,00,64,00,00,00,64,00,\
00,00,64,00,00,00,64,00,00,00,64,00,00,00,64,00,00 ,00,64,00,00,00,64,00,00,\
00
"LutPersistFSVM_GPU:0"=hex:00,00,00,00,64,00,00,00,47,00,00,00,47,00,00, 00,5a,\
00,00,00,45,00,00,00,45,00,00,00,00,00,00,00,00,00 ,00,00,00,00,00,00
"ContextUIPolicy"=dword:00000001
"CplGroupUIPolicy"=dword:00000001
"TaskbarUIPolicy"=dword:00000001

Asciicodeplus
05-13-07, 08:53 PM
Still the same, I still see the [Start Nvidia control panel] button as my only option in destop properties, :/

I haven't had time to uninstall the drivers an clean every remanant yet tho, btw does this work for all the cards or only for the new ones? I have a FX 5600 using 165.xx on Win XP

BDUB
05-15-07, 10:25 AM
The only entries you need to get the old CP back are:

"ContextUIPolicy"=dword:00000001
"TaskbarUIPolicy"=dword:00000001

Any other entry is unneccesary. Using a value of 2 will get you the new CP. And using a value of 3 will get you old and new.

For 6 and 7 series cards, they stopped supporting us over six months ago. You can tell the recent flood of driver leaks 1xx.xx are really not intended for anything other than 8 series cards by looking at the default new CP that comes with them: try to do something simple like get a temp reading and it tells you to install ntune, for christ's sake. Why is this new CP not capable of OCing and getting temp readings like in the past? Does noone see how fundamentally flawed their project is?

Especially when I paid 500 bucks for a 7900GTX not too long ago.. Yeah.. it's BS. I want to buy an 8800 or newer NV card, but they'll just stop supporting my 500+ dollar video card a year later. No Fing thanks NV.

Shaitan
05-19-07, 12:09 PM
I really can`t believe we have to resort to reg hacks to get the applet we PREFER. It fuxoring staggers the mind.