Custom Resolution Utility (CRU)
|
07-19-2013, 10:11 PM
Post: #181
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
ToastyX,
you are the MAN! Here's why: For years I've used PowerStrip with an old PC running a Sapphire Radeon 9600XT hooked up to an old Sharp Aquos (circa 2005). That allowed me get near-native (1368x768; Aquos is 1366x768). I decided I wanted a better AGP card that would run madVR, and picked up a Radeon HD 3850, specifically because it's supported by PowerStrip. But when I installed it and the latest drivers from Guru3D, I could not make PowerStrip use 1368x768 (copied the timings from the 9600XT and pasted them in). This is under Windows 7 32-bit. And FWIW, PowerStrip worked fine with the 9600XT and the drivers Windows Update found. Then I remembered reading about your awesome utility. With it I was able to define the custom res., and then PowerStrip would take the timings. I used the PowerStrip Custom Resolution window to tweak CRU to use the same timings, as close as I could. And that all works great. I've got another, older PC that inherited the 9600XT, both going to the Aquos through a Monoprice DVI switch. Using the same timings in both instances of PowerStrip is a great benefit, as I don't have to fine tune the Aquos settings. Due praise concluded, I have a question: Is there any reason to use PowerStrip with the 3850, since I can define the timings in CRU? PowerStrip does have the added option of positioning the Windows desktop (handy to correct for the extra pixels). That said, is there any reason NOT to use PowerStrip, in terms of conflicts? From what I can tell, CRU is a run-once-set-and-reboot app, while PowerStrip can be set to load and adjust settings when Windows boots (that's how I set it). Anyway, thanks a lot for this brilliant little app |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 79 Guest(s)