it says error writing to registry i have 29.20 DetonatorXP Driver

On the NVRefresh Tool site:

http://www.xp-faq.com/nvrefreshtool/



It clearly describes the problems with the 29.20 drivers



Depending on what resolutions you run, you may still be able to use the proggy, with 29.20.

or try to use this what can help u with new detonator divers too so never again problem with 60Hz...



nVidia Refresh Rate Fix MKII v1.02 E

Thanks ebola, that's a new one (RRsolution) to me. I'll check it out.



A solution that has universal appeal seems to be RefreshLock. It's a small footprint & isn't driver version dependent. Check it out here:

http://www.pagehosting.co.uk/rl/





A well known solution, nvreffix, here: http://www.planetquake.com/ztn/nvreffix/index.html

works with many driver versions & most NV drivers are eventually posted with a modded ver, that is "nvreffix compatible."



When WinXPsp1 is released, all this will be resolved, since MS has finally supposedly corrected & announced (maybe not officially, thanks MagAKO for pointing this out) the OS refresh rate fix. It's about time.

Microsoft never announced anything. It's a rumor that's going around. It may or may not happen.

LongHorn: Try using version 0.76b of the software. We recently modified it and attempted to determine what the cause of that was. It *should* be fixed now. We have gotten reports by others that the program works correctly and no longer gives that error.

From: The Digital Resource http://www.thedigitalresource.com/



Here is article about possible Refresh Rate Fix in MS XPSP1:



There might be a solution in the works for the famous refresh rate issue in games under Win 2k/XP. Games are locked at 60 Hz in Win 2k/XP because of this "bug". A solution used to be nvreffix, but recent drivers have been incompatible with the utility.



But, according to NVChips-FR http://www.nvchips-fr.com/ Microsoft has fixed the issue in Win XP. Here's a translated snip (with slight corrections in the translation):



I learned very recently that Microsoft corrected this "bug" for Windows XP. The corrective measure will be integrated into Service Pack1 of Windows XP which will leave soon. We do not know the date of release for SP1, but Microsoft would be well inspired to accelerate the movement or at least to release a patch without awaiting SP1.



If this turns out to be true, then that's some very good news Well, for the Win XP users at least since there's no news about a solution for Win 2k. Let's see what happens in the near future...



You can read more over here http://www.nvchips-fr.com/News/news.php?da...04&newsnumber=4 (in French). Thanks goes out to Leaxim for reporting this bit.



News Source: Madonion http://gamershq.madonion.com/news/?newsart...0205/2002050500