Skip to main content

Custom Display Resolutions in XP

Having purchased a snazzy new 22" wide screen flat panel monitor and finding everything hunky dory in Windows Vista I tried the same monitor with a Windows XP machine only to find disappointment kicking down my door. When I went to Display Settings in Control Panel and dragged the Resolution slider up, the native resolution of the monitor was not there.

Now every flat panel monitor should be run at its native resolution in order to look its best - every "virtual" pixel maps to a real one (or actually a real triad of red, green, and blue) on the screen. The monitor wanted to run at 1680x1050 but my only options were along the lines of 1280x1024, 1600x1200, 1920x1080 and so on. This was disappointing because the text and images looked either squashed or stretched.

So what to do then? Well, the fix involved a little bit of registry hacking. The registry is essentially Windows' own internal database in which it keeps all its various settings. It's not usually supposed to be tweaked by humans but rather by Windows itself and if you get things wrong the results could be an un-bootable PC. Also, if you inadvertently set a resolution too high for your monitor you could damage it and/or your graphics card. So I obviously don't recommend doing any of this! You have been warned.

Important
Always back up your registry before tweaking it! The best way is probably to capture a System Restore point - Start Programs Accessories System Tools System Restore Create a restore point. If things go wrong you can always boot into Safe Mode (hit F8 at boot time) and choose "Restore my computer to an earlier time" in the System Restore utility.

So here we go
  1. Open RegEdit - Start Run and type "regedit"
  2. Browse to HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\VIDEO{the address of your primary video card...it often begins with "23A77BF7"}\0000
  3. The Default Settings.XResolution data value is the horizontal resolution, and the Default Settings.YResolution data value is the vertical.
  4. Double-click the Default Settings.XResolution data entry, select the Decimal radio button, and in the Value Data field, enter your desired horizontal resolution.
  5. Then do the same with Default Settings.YResolution to change the vertical resolution.
  6. Exit RegEdit and reboot your PC.
  7. You should now be able to choose the required resolution.

Note
If you're scared of tweaking your registry (and you probably should be!), there's a handy application on the web called PowerStrip which allows you similar resolution-changing functionality. However, although many on the web recommend it, I didn't find it to be of any help at all.

Comments

Petra said…
Thanks for your tip.
I had a problem with my new widescreen monitor that Windows XP stretched the height. But I solved the problem by changing the default yresolution to 640 (it was 1024 x 768 (4:3) on my old CRT) and matched the new 16:10 ratio and now it starts up correctly and changes to the default resolution to 1680 x 1050.
24 January 2009 at 21:05
Post a Comment

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS
Post a Comment
Read more

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...
Post a Comment
Read more

Convert Ruckus AP from Unleashed to ZoneDirector-managed

Here is the method to convert a Ruckus Unleashed AP to one which can be managed by a Ruckus ZoneDirector controller: - Login to https://support.ruckuswireless.com/ - Click "Downloads" - Choose the correct product, e.g. Ruckus R550 - Choose a "standalone" version along the lines of 118.2.0.0.875.bl7 or something similar - Agree to terms and download the software - Connect to the AP's IP address - It should open the setup wizard, showing "Unleashed Installation" - Click "Local Upgrade" - Choose the firmware image file you just downloaded - It will upload, process, and then be ready for upgrade when you click "Yes" - After this, the ZD should detect the new AP - The new AP will then need to be approved - The new AP will then be upgraded to the correct software by the ZD - The new AP will then reboot and should be ready to use - Don't forget that, for the ZD to even detect, let alone manage the new AP, it must have enough licenses
Post a Comment
Read more