VOGONS


First post, by Delerious

User metadata
Rank Newbie
Rank
Newbie

So, I bought the K1200, since it's a nice, cheap low profile GPU for SSF builds, but I find that, so far, it has way too many limitations in Windows XP.

Firstly, I'm trying to get a 1280x800 resolution on a Quadro K1200 in Windows XP. However, I can't seem to, no matter what I try. I've tried some registry hacks to try to enable the setting. And I've also tried using PowerStrip to enable custom resolutions, but it simply refuses enable them. I've been able to get the 1280x800 resolution on this display with a FirePro W4300, and using a K1200 in Windows 7 enables the resolution, as well, so I know it's possible on my display, and on the K1200. But I want to know if there's some other way around it that I'm unaware of in Windows XP, as NVIDIA versions 364.51 and 368.81 simply don't allow me to do it.

Additionally, these same drivers won't allow me to "Adjust desktop size and position" in the NVIDIA Control Panel. So if I want to use a 4:3 aspect ratio on a 16:10 display, I'm stuck with a stretched image. If anyone knows a workaround for this, that would also be great.

Current builds:
Asus A7N266-VM | AMD Athlon @ 1.0 GHz | 512 MB DDR RAM | ATI FireGL T2-S64 | Windows 98 SE/Windows 2000 Professional
Asus H61M-Plus | Intel Core i5-3570S | 8 GB DDR3 RAM | AMD FirePro W4300 | WinXP Pro x86/Win7 Pro x64

Reply 2 of 5, by Delerious

User metadata
Rank Newbie
Rank
Newbie
Barley wrote on Today, 01:14:

I would try two things:

1) For proper resolutions. try 355.98 driver
2) For aspect ratio scaling, follow the instructions here: Re: Building a Retro PC for the 21st century - please advise on what I missed

Thank you so much! Actually, it looks like the 355.98 driver alone resolved my issues (tentatively), as I now also have scaling options available in my NVIDIA Control Panel. More importantly, I can now use the 1280x800 resolution. Don't know about others, but I find that, for a 16:10 aspect ratio, it's pretty much the best resolution for Windows XP, since the UI was designed for around a 1024x768 resolution to begin with. Everything just looks too small at a 1680x1050 resolution.

Current builds:
Asus A7N266-VM | AMD Athlon @ 1.0 GHz | 512 MB DDR RAM | ATI FireGL T2-S64 | Windows 98 SE/Windows 2000 Professional
Asus H61M-Plus | Intel Core i5-3570S | 8 GB DDR3 RAM | AMD FirePro W4300 | WinXP Pro x86/Win7 Pro x64

Reply 3 of 5, by Barley

User metadata
Rank Newbie
Rank
Newbie

Glad I could help! I could only do so due to the diligence of those that came before me.

I also use a 16:10 (1920x1200) monitor for Windows XP. Most Windows XP era games were not optimized for widescreen, and widescreen mods mostly only work under Windows 7 and later. So I game at 1600x1200 using the aspect ratio trick I linked to above (I do not get scaling options in the NVIDIA Control Panel like you do). What connector are you using?

Reply 4 of 5, by Delerious

User metadata
Rank Newbie
Rank
Newbie

As far as connectors go, the K1200 only has MiniDP, so I'm using a MiniDP to DP cable for that. That said, I did also run the command you recommended before installing the 355.98 driver, as I was trying to see if that would enable scaling in the 364.51 driver, but to no avail. So it's also possible that it enabled it for me. If not, then maybe the display interface does have something to do with it.

Current builds:
Asus A7N266-VM | AMD Athlon @ 1.0 GHz | 512 MB DDR RAM | ATI FireGL T2-S64 | Windows 98 SE/Windows 2000 Professional
Asus H61M-Plus | Intel Core i5-3570S | 8 GB DDR3 RAM | AMD FirePro W4300 | WinXP Pro x86/Win7 Pro x64

Reply 5 of 5, by Barley

User metadata
Rank Newbie
Rank
Newbie
Delerious wrote on Today, 02:07:

As far as connectors go, the K1200 only has MiniDP, so I'm using a MiniDP to DP cable for that. That said, I did also run the command you recommended before installing the 355.98 driver, as I was trying to see if that would enable scaling in the 364.51 driver, but to no avail. So it's also possible that it enabled it for me. If not, then maybe the display interface does have something to do with it.

The scaling command probably didn't work initially because you didn't have the right resolution available in your driver at the time. No matter. You got it working now!