Non-native resolutions don't scale

I've installed Windows 7 RC on a Dell Latitude D820. There is a place in the BIOS where you define the behavior of the screen when you change to a non-native resolution. By default it should scale the image to take up the entire screen. This laptop has the Mobile Intel 945 Express onboard video. When I change the resolution below the native resolution (1680x1050) it shows in a smaller window and the rest of the screen is black. This also happens if I use a program or play a game that is in a lower resolution. I'm pretty sure this behaved as normal when I had XP installed. There is a FN+F7 key combo that is supposed to scale the picture but it does nothing for me. I've updated the BIOS to A09, updated the driver via device manager where it found an update automatically. I also tried a pre-release driver from Microsoft (8.15.10.1713) but nothing seems to fix this.

what about integrated intel gpus ??? the WDDM driver doesn't have an interface to adjust the scaling pls help i have windows 8.1 i can't install win 7 driver for my gma 4500mhd not even in test mode & stuff 
What about it?  This thread is not about Intel Opus.  And, this is not a Windows 8.1 forum, it's a Windows 7 forum.
Go to Windows 8 IT Pro Category for discussions about Windows 8.1.

Similar Messages

  • Bad to run screen at a non native resolution?

    Hey I'm playin CS in windows and there isn't a 1400x900 resolution for it so i;m just playing 1024x768 in a window. Is it ookay if I make it full screen @ 1024x760?

    Under the current OS's (Mac and Windows), displaying at a non-native resolution is "fuzzy" due to pixel interpolation. Leopard will have "resolution independence" - no fuzziness.
    Um, actually the fuzziness of non-native resolutions is a physical limitation of how LCD screens work. Leopard's resolution independence refers to something quite different (the ability to scale all UI elements to maintain their size consistently across resolutions).

  • 27" iMac non-native resolutions

    So, I'm doing what a lot of folks here are doing right now, (im)patiently waiting for my new quad core 27" iMac to ship. In the meantime, I've been doing some thinking. I intend to game quite a bit on this new system, and I'm concerned about the resolution of the screen. Obviously, even with the HD4850, most games are not going to tolerate the massive resolution required of this huge screen. So obviously, to maintain decent frame rates, I'm going to have to lower the resolution. Now, I don't know much about LCD technology, but what I've heard is that how good the image quality is at non-native resolutions is dependent on the hardware in the LCD panel. From what I've heard, this is an excellent display, with all the latest bells and whistles.
    So, my question, for anybody that has experience with this particular screen, or another like it, how does it handle non-native resolutions? Does it look good? Abysmal? Somewhere in between? And, if I'm going to play in a non-native resolution, I suppose my best choices would be 1920x1080 (3/4 res), or 1280x720 (1/2 res). Am I correct in that assumption?
    Thanks so much for taking the time to read this, and I hope this makes for some good discussion!

    It looks great. I have the 27" dual core which is the same screen. Obviously anything less than 2560x1440 resolution is going to be an interpolated resolution but the screen is extremely high quality and with that kind of pixel density to work with it's easy to make the screen look great.
    Is it as tack sharp as native resolution? No, but it still looks great. I've tried 1600x900 and 1920x1200 modes which are the same 16:9 format as the native res and they look stunning even on the desktop. No worries with your gaming. Enjoy!
    James

  • Windows 8.1 x64 Bit Black border in non-native resolution

    Hello : i have a GMA 4500mhd GPU & i installed windows 8.1 & the default driver was fine all screen resolution havn't got the black borders but after i did the windows update it installed the
    WDDM 1.1 driver. after a restart all non-native (under 1366x768) are not scaled to the monitor
    .. when i had windows 7 x64 ; the recommended driver 15.17.19.64.2869 was fine
    & it comes with it's own interface to adjust the options like performance & quality , scale full screen & stuff but windows 8.1 didn't let me install this driver so help me 

    Hello YellowMenace，
    When you use the default driver, it works normally? After the Windows Update installing the WDDM 1.1 driver, the monitor resolution is changed?
    Please share us a screenshot for better analyzation.
    Please change the scaling option as MVP S.Sengupta mentioned.
    If a new driver for your video card is causing problems, or an incorrect registry setting is preventing Windows from starting correctly, you can restart your computer using Last Known Good Configuration.
    http://windows.microsoft.com/en-us/windows/using-last-known-good-configuration#1TC=windows-7
    Best regards,
    Fangzhou CHEN
    Fangzhou CHEN
    TechNet Community Support

  • How to "un-zoom" non-native resolution screen?

    With older ThinkPads, I was able to display lower resolution output on the ThinkPad LCD at a 1:1 pixel ratio, instead of having it stretched/zoomed.
    On the W520, I don't seem to be able to do it.  And so, the result is that the BIOS boot screen, and Windows boot GUI look rahter "blurry".
    Anyone know how I can make the screen smaller again?

    Someone was asking a similar question:
    http://forums.lenovo.com/t5/IdeaPad-Y-U-V-and-Z-series/Y450-Screen-expansion-option/td-p/131647
    It's Point 4 under section "Unsatisfactory video display on the ThinkPad LCD display":
    http://support.lenovo.com/en_US/diagnose-and-fix/detail.page?LegacyDocID=MIGR-4YQHUC
    How come newer Thinkpads don't have this option?
    Some people like the scretched look, some don't (me being in this group).  Especially in non-Windows environment, because text/fonts looks REALLY odd when stretched on a 16:9 display.

  • Gaming in non-native resolution @ i3 wm

    whenever i exit a game that previously was running in a lower res than native (e.g. Soldier of Fortune with a max res of 1024x768), it lowers my desktop res (presumably to the game's own res) and in order to resolve it i have to call
    xrandr --output <device> --mode <res>
    each time.
    i wonder if anybody had this before, and if so, what did they do about it?
    thx in advance!
    Last edited by wootsgoinon (2014-08-09 16:33:14)

    I've come to just accept that this is what happens when playing some full-screen games in a tiling window manager. It's happened in every window manager I've ever used, and I just reset the resolution when I'm done.  I have a script that switches back-and-forth between my laptop display, and my laptop display plus an external monitor; I just run that after I'm done playing.
    Try running games in windowed mode and using i3's fullscreen toggle. It's worked for me a couple times, and "fullscreen" games in i3 never grab the mouse and keyboard anyway, if you follow me.

  • Can Anyone Explain Why Using the Hightest (Native) Resolution is Preferred?

    I have an '06 iMac with a 20" screen, my top resolution is 1680 x 1050, but when I try using it, yes I can "fit more on the screen", but the type is tiny, tiny, tiny, (& I can't seem to figure out how to enlarge it outside of my browsers. How do people function with microscopically small type? I have been using 1280 x 800, but am now trying 1344 x 840...
    The main issue I think occurs by using the lower resolution is that my message formatting, both via Mail & when posting stuff on line, ends up all skewed, sentences break off where they shouldn't etc., as if there is some default margin that is forcing all my copy to conform to, except when I'm writing it.

    Modern monitors have a fixed amount of pixels, in your case, 1680x1050 pixels. If you start sending it a signal in 1280x800 pixels, the monitor itself has to scale it up to 1680x1050 pixels in order to fit it on the screen.
    You can't cleanly divide 1680 by 1280, this means that the scaled up pixels won't all be the same size. Some pixels will be wider than others.
    Most people (including me) find that using a non-native resolution just looks messy.
    I do agree with you that the size of everything on the screen should not be coupled to the resolution you're using on that screen. This would solve a LOT of accessibility problems for people with less than perfect eyesight.
    Backwards compatibility with a lot of application frameworks and other technical things I won't get in to makes doing this very difficult (it will work for some applications, but not all, especially not older applications).

  • Monitor's native resolution no longer available

    I've got a Mini running 10.5.6 with a 22" LCD that runs at 1680x1050 natively. I recently disconnected the Mac and plugged it to my standard definition TV for some old school Nintendo gaming at 640x480 and it worked beautifully. Now, when I reconnect the Mac to my 22" LCD the native resolution is no longer available. The best I can get is 1600x1200 which is not the native widescreen resolution. At this resolution the display is stretched horizontally. I've tried using the "detect displays" button, rebooted several times, removed the monitor cable... none of that seems to help. Are there some sort of prefs that I can trash? I tried removing some files from /System/Library/PreferencePanes/Displays.prefPane/Contents/ but that only ended up making the pane in System Preferences disappear. Luckily the pane came back after I put the files back.
    Anyway, if anyone can help me with this I would really appreciate it!

    I tried Quix's solution but got a strange result.
    I don't have another monitor, but I disconnected the plasma and used Screen Sharing to log onto the machine and set the resolution to 1280x768 (that was the closest available resolution in a very long list of choices).
    When I plugged the plama back in, the image was offset. The left 1/3 of the screen was blank and only 2/3rd's of a finder window was visible. When I ran "Detect Displays" it revered to a lower resolution and only gave me 3 resolution choices.
    This is really frustrating.

  • Why does the MacBook Retina 15" do software scaling to the native resolution of 2880x1800?

    OS X does not allow changing the viewport resolution to the native 2880x1800, and it suggests 1440x900 as a retina optimized one. This means that software scaling is done on the fly. My question is, why?
    I have two suspicions:
    1. Running everything at the native resolution puts a bigger strain on the GPU, hence slowing down the OS, putting down battery time.
    2. The number of apps using retina-ready sprites is miniscule, hence Apple does not want to mess with the user experience. Although I doubt it, as software post-processing is done even now, and apps with non-retina sprites look slightly blurred. If the native resolution would have been used, they would just look a bit more blurry.
    Just some comments:
    1. Switching to the native resolution will make everything smaller, up to the point of not being usable. But this is a non-argument, as the OS could be smart enough to use bigger versions of the sprites/icons/text. Apple already demands that developers use hi-res sprites (OS X Human Interface Guidelines), hence everything could be scaled x2 and it would be the same size at 2880x1800, as it is at 1440x900 in the current version of the OS.
    2. Technically it is possible, as outlined here: Running the Retina MacBook Pro at Full 2880x1800 Resolution. Have a look at the comments too, there are some interesting observations in line with this question, but no definite answers.
    3. I am aware that the OS X Cocoa server is running at native resolution at all times. This question is concerned with the viewport resolution, which requires hacks to be set to the native one.
    Can answer on Quora if preferred (http://www.quora.com/OS-X/Why-does-the-MacBook-Retina-15-do-software-scaling-to- the-native-resolution-of-2880x1800)

    Ah right at the top.
    panic(cpu 0 caller 0xffffff7fa40cbf1a): "GPU Panic: [<None>] 5 0 a0 d9 9 8 0 3 :
    This is a common problem with new Mac notebooks. There arre many threads on this and other forums about it.
    Tae your Mac to an Apple store to be fixed or replaced.

  • Big Problem with Directx 11 and Games scaling when lower than native resolution

    Hi Guys,
    MY system is Windows 7 Home Premium (Korean version), and I have dual GPUs, Nvidia Geforce GT 630m for gaming, and Intel HD Graphics 4000 for all other display matters.  My native resolution is 1920 x 1080.
    This problem wasn't there couple of years back, but from 2~3 years ago, when I play recent games that require/favour directx 11 (such as Assassin's Creed IV Black Flag, Batman: Arkham Origins), it seems when I use lower than native resolution (such as 1280
    x 720) and select fullscreen, giant ugly black borders always appear around the game, and the game does not fill the whole screen.  
    I thought this was something which could be fixed in my GPU's control panel, but there was no scale fullscreen option under Nvidia's control panel.  So I went into Intel HD Graphics control panel, but there was no Scale fullscreen option there either (under
    native resolution.  With lower resolution there was).
    Anyway, after months and months of searching, I finally found an Intel forum which was discussing the same situation:
    https://communities.intel.com/thread/44539
    While going through the forum, I found out from other users that problem is not with GPU's drivers, but with Directx 11.  
    To test this theory, I put Batman: Arkham Origins in Force Directx 9 mode, and changed the game resolution to 1280x720.  And the game showed no black borders, it scaled up perfectly to fullscreen under Directx 9 (so no problem whatsoever under directx
    9).  I changed the setting to Directx 11, and the ugly black borders appeared again.
    Could someone please help with this?  I know I can change my screen's resolution every time I play the game, but it's a real nuisance to do that.  And more games are utilising Directx 11 or higher, and I don't think there are many games where I can
    force Directx 9 mode like I did for Arkham Origins.
    Or if someone connected could contact the people working on Directx 11 and ask about this issue (and get them to contact me through my email below), that would be much appreciated.
    my email:
    [email protected]
    p.s. : all my GPU drivers are currently up to date, and the black borders issue is still there

    Hello MeipoXu
    While yes, at first people on the Intel forum thought it was the display driver problem (hence the question was originally posted on the Intel forum).  But if you look closely through the pages especially Pages 2 onwards, there are some very astute
    comments by some posters:
    Update to black borders problem: The problem is DirectX11. Fx. Company of Heroes has a setting "Shader Quality" that when set to ULTRA it will run directX11 and when set below ULTRA it will run directX9. So the intel graphics driver is not
    responsible! It is Microsofts DirectX11 that does it - maybe only to computers with both Intel HD and a second graphics card for video games
    Different workarounds to the black border problem:
    Change resolution before running fullscreen
    Use directX9 instead of directX11
    Fx. in CoH2 there is a setting fx. 50% of resolution, so even in native resolution the graphics is only half and thus faster
    Try window mode without borders
    and here's also another:
    I can confirm that this problem still seems to exist, and that it definitely seems to be related to DirectX 11.
    In a variety of games, turning DirectX11 off (either in-game or using ini files in some games that don't present you with the choice) fixes the issue. But this is obviously not ideal.
    I have a laptop with a native resolution of 1920x1080, but tend to run games at 1280x720 because it provides much better performance on my HD 4400 graphics chip. This bug and the memory leak issue on Windows 8.1 are extremely annoying.
    Like the first poster, my PC has intel HD GPU, and a second graphics card for games (Nvidia).
    And all the members have mentioned that they updated the intel graphics driver, but it does not fix it - so it doesn't seem like a graphics driver problem (and more to do with Directx 11).
    And they are right.  With Batman Arkham Origins, if I set the resolution to 1366 x 768 and apply fullscreen, under Directx 11, ugly black borders appears.  Luckily Arkham Origins has "Force Directx 9 mode" which I use, but a lot of games
    don't have this mode (such as ACIV Black Flag, Watch Dogs, Sleeping Dogs etc) - you either play in ugly black borders, or can't play the game at all.
    And all my Graphics Drivers are currently up-to-date, and issue still exists, so I don't think it's the driver problem.
    I have already tried that registry method you just mentioned.  It didn't work.
    As for Directx 12, well I just hope it works better than Directx 11 (with its ugly black borders in games) does, and works well like Directx9 (with no problem in scaling).

  • LCD native resolution not available in system preferences

    I need to set my resolution to 1680 x 1050 and that resolution is not vailable. I have a original G4 Mac Mini with Tiger. The monitor has dual inputs for both VGA and DVI, sometimes it will work with the VGA input but not consistantly.
    I need to use the DVI input now to leave the VGA input free for my KVM.
    I have tried Zapping my PRAM multiple times, starting the Mini with the monitor unplugged, swapping between the DVI and VGA inputs on the LCD monitor, and swapping between my old CT monitor and the new LCD. None of this works.
    The LCD always detects as "LCD Display".
    I have been unable to find information on where the monitor resolutions are stored, one thing which I would have liked to try would be manually editing the file to the correct resolution.
    What else can I try?
    Thanks in advance!

    Hi Brian, sorry about your issue- it's frustrating isn't it? The file you need to edit is in system > library > frameworks > IOKit.frameworks > Versions > A > Resources, and it's called IOGraphicsProperties.plist. If you activate the root user temporarily using the NetInfo Manager, you can edit the file with textedit, save it to the desktop, then drag it into the Resources folder to replace. When you look in the file, you'll see the following:
    <key>gtf-resolutions</key>
    <array>
    <integer>640</integer>
    <integer>800</integer>
    <integer>1024</integer>
    <integer>1280</integer>
    <integer>50332928</integer>
    <integer>67110144</integer>
    <integer>1344</integer>
    <integer>1400</integer>
    <integer>1600</integer>
    <integer>1920</integer>
    <integer>2304</integer>
    </array>
    <key>gtf-resolutions-wide</key>
    <array>
    <integer>640</integer>
    <integer>800</integer>
    <integer>31458128</integer>
    <integer>1024</integer>
    <integer>1280</integer>
    <integer>67110144</integer>
    <integer>50333008</integer>
    <integer>1600</integer>
    <integer>1920</integer>
    <integer>2304</integer>
    I had the same problem as you. I bought an Acer 22" widescreen, with a native resolution of 1680 x 1050, which wasn't "available" in the displays control panel. After some swearing and lamenting the olden days in OS9 when you could just willy nilly see all the resolutions, i added my resolution the this file and it showed up in the control panel. You'll have to monkey with it to see how it works, but basically you're going to add another 'integer' line, like so:
    <integer>1680</integer>
    If this is too hairy for you, or just too much trouble, i highly recommend SwitchRes. It works perfectly for this problem, and you can input the specifications for your monitor exactly and it will install the resolution so that it's available to the system. Its cheap too.
    good luck to you!
    G5 1.8 dual   Mac OS X (10.4.3)  

  • External Display native resolution suddenly not available

    Hello,
    I'm using a Westinghouse LCM-22w3 external monitor with my MBP, connected via a DVI-to VGA adapter. I've used this computer/monitor setup for quite some time with no problem. Yesterday, I hooked my computer up to my 46" Samsung HDTV with no problem.
    When I hooked my computer back up to the Westinghouse, the native resolution (1680x1050) was no longer available. Instead, the monitor hooks up at 1600x1000. Strangely, though, the EDID information appears to suggest that 1680x1050 should be available. Here's the EDID:
    DDC block report generated by SwitchResX version 4.1.1 for display
    LCM-22w3
    ------------------- RAW DATA ------------------------
    0 1 2 3 4 5 6 7 8 9 A B C D E F
    0 | 00 FF FF FF FF 91 FF 00 5C 85 03 22 01 01 01 01
    1 | 13 11 01 03 68 2F 1E 78 2E C5 85 A4 59 49 9A 24
    2 | 12 50 54 BF EF 00 81 80 81 40 71 4F 95 00 95 0F
    3 | B3 00 81 C0 81 00 21 39 90 30 62 1A 27 40 68 B0
    4 | 36 00 D9 28 11 00 00 1C 00 00 00 FD 00 38 4C 1E
    5 | 52 10 00 0A 20 20 20 20 20 20 00 00 00 FF 00 30
    6 | 0A 20 20 20 20 20 20 20 20 20 20 20 00 00 00 FC
    7 | 00 4C 43 4D 2D 32 32 77 33 0A 20 20 20 20 00 1D
    < 00FFFFFF FF91FF00 5C850322 01010101 13110103 682F1E78 2EC585A4 59499A24 125054BF EF008180 8140714F 9500950F B30081C0 81002139 9030621A 274068B0 3600D928 1100001C 000000FD 00384C1E 5210000A 20202020 20200000 00FF0030 0A202020 20202020 20202020 000000FC 004C434D 2D323277 330A2020 2020001D >
    Invalid EDID block: checksum failed. Last byte should be 8B
    ------------------- MAIN EDID BLOCK -----------------
    EDID Version........1.3
    Manufacturer........WDE
    Product Code........802 (0322) (2203)
    Serial Number.......01010101
    Manufactured........Week 19 of year 2007
    Max H Size..........47 cm
    Max V Size..........30 cm
    Gamma...............2.20
    Display Supported Features:
    Power Management: Active off
    Display type:
    RGB color display
    Display is non continuous frequency
    Default color space is sRGB standard
    Preferred timing mode includes Native Pixel Format
    Input signal & sync:
    Analog input with: 0.700V / 0.000V
    Composite Sync
    Color info:
    Red x = 0.644 Green x = 0.286 Blue x = 0.143 White x = 0.313
    Red y = 0.348 Green y = 0.603 Blue y = 0.070 White y = 0.329
    Established Timings:
    720 x 400 @ 70Hz
    640 x 480 @ 60Hz
    640 x 480 @ 67Hz
    640 x 480 @ 72Hz
    640 x 480 @ 75Hz
    800 x 600 @ 56Hz
    800 x 600 @ 60Hz
    800 x 600 @ 72Hz
    800 x 600 @ 75Hz
    832 x 624 @ 75Hz
    1024 x 768 @ 60Hz
    1024 x 768 @ 70Hz
    1024 x 768 @ 75Hz
    1280 x 1024 @ 75Hz
    Manufacturer Reserved Timings:
    Standard Timing Identification:
    #0: 1280 x 1024 @ 60Hz (8180)
    #1: 1280 x 960 @ 60Hz (8140)
    #2: 1152 x 864 @ 75Hz (714F)
    #3: 1440 x 900 @ 60Hz (9500)
    #4: 1440 x 900 @ 75Hz (950F)
    #5: 1680 x 1050 @ 60Hz (B300)
    #6: 1280 x 720 @ 60Hz (81C0)
    #7: 1280 x 800 @ 60Hz (8100)
    Monitor Description blocks:
    Descriptor #0 - Timing definition:
    Mode = 1680 x 1050 @ 59.954Hz
    Pixel Clock............. 146.25 MHz Non-Interlaced
    Horizontal Vertical
    Active.................. 1680 pixels 1050 lines
    Front Porch............. 104 pixels 3 lines
    Sync Width.............. 176 pixels 6 lines
    Back Porch.............. 280 pixels 30 lines
    Blanking................ 560 pixels 39 lines
    Total................... 2240 pixels 1089 lines
    Scan Rate............... 65.290 kHz 59.954 Hz
    Image Size.............. 473 mm 296 mm
    Border.................. 0 pixels 0 lines
    Sync: Digital separate with
    * Positive vertical polarity
    * Negative horizontal polarity
    Descriptor #1 - Monitor limits:
    Horizontal frequency range.......30-82 kHz
    Vertical frequency range.........56-76 Hz
    Maximum bandwidth unspecified
    Descriptor #2 - Serial number:
    0
    Descriptor #3 - Monitor name:
    LCM-22w3
    Any ideas? Switchresx didn't work, either

    Well, you can move the file from the desktop back to its original location to at least get back to what you had before.
    The file structure under Snow Leopard has changed and it's hard to keep up with this stuff. There is also now a com.apple.WindowServer.plist file in /System/Library/LaunchDaemons that you could try moving to the desktop and restarting. I dunno. Same rule applies.....if it doesn't help, move the file from the desktop back to its original location.

  • Cisco 1702i WAP: how to get an interface in a non-native bridge group/ VLAN to be recognized by the internal DHCP server

    Does anyone know how the internal DHCP server in these access points connects to virtual interfaces and bridges in the unit?
    Is there some sort of default connection that connects the DHCP server to the native bridge group or VLAN?
    In a test case, with an SSID in the native VLAN and bridge group, the 1702i serves an IP address to a wireless client no problem. But with a second SSID in a non native VLAN and bridge group, no IP gets served. My only guess is that since the bvi1 defaults to the native bridge group and VLAN, sub-interfaces also in this group are assumed to be in the same subnet as bvi1, or in this case:
    interface bvi1
      ip address 192.168.1.205 255.255.255.0
      no ip route-cache
      exit
    It would be the ..1. subnet.
    Since the dhcp pool is set as:
    ip dhcp pool GeneralWiFi
      network 192.168.1.0 255.255.255.0
      lease 1
      default-router 192.168.1.1
      dns-server 8.8.8.8
      exit
    There may be an assumption that anything bvi1 can talk to is in the ..1. subnet, so the above pool gets activated on a request coming through bvi1.
    Is the DHCP server just hanging out waiting for a request from an "area" that is assumed to be on the same subnet as the given pool?
    Do I need to somehow show the device what subnet the 2nd SSID/ subinterfaces are in so the internal DHCP server can decide it needs to go to work, or is there some sort of bridging between the DHCP server and the interfaces that needs to be done? I am trying to use the same DHCP pool for the second subnet at this point, since I assume I will need another router to service an additional subnet and DHCP pool.

    Keep in mind that DHCP is a broadcast packet to start. So the AP can only listen in the subnet that it has an IP address for.
    Now, for any other subnet you can use the AP for DHCP but you have to have an IP helper address on your L3 pointing back to the AP.
    That being said, I wouldn't use the DHCP server on the AP as it is limited. You'd be better off using a Microsoft server or some other device that is designed for DHCP.
    HTH,
    Steve

  • Second monitor decided to stop allowing its native resolution.

    My external monitor (17" TruTech LCD screen) has a native resolution is 1440x900. Since the first time I plugged it in (using the DVI to VGA adapter and an extension cord), my Mac has recognized the monitor's native resolution automatically and worked perfectly, for the most part.
    Earlier today, after my computer crashed and I had to force shut-down, the Mac can no longer find the monitor's native resolution, and doesn't have it listed in the Display Preferences.
    I have done all of the following, to no avail:
    -Several hard power cycles of both my Mac and the monitor, with different combinations of the monitor being plugged in and unplugged before/after/during booting.
    -Reset PRAM/NVRAM
    -Repaired Disk Permissions
    -Unplug/re-plug the monitor to the computer (hitting "Detect Displays" while unplugged and again once plugged in)
    -Toggle mirroring on/off
    I installed SwitchResX, and after some tinkering with it was able to get the proper resolution on my external monitor. The problem is that it's only a 10 day trial, and I don't want to pay for software to fix a problem that I shouldn't be having. I'd also rather not have more software running in the background than I need.
    Is this an OS X problem, a Mac hardware problem, a problem with the monitor, or bad cables? If it's either of the latter two, I'm willing to purchase new cables or a new monitor. If it's an OS X problem, what can I do to fix it?
    Any help is very much appreciated.

    You may be able to trash the windowserver.plist files, but I'm not so sure if that works under Snow Leopard the same way it used to under Tiger and Leopard.
    When you build a custom timing using SRX, it just becomes part of a standard plist file. In other words, it writes to standard OS X framework files. So it's not like it's running in the background. You can delete SRX from your computer and that timing you made will still be there.

  • Native resolution of external monitor not appearing in System Prefs - Displays

    I have an Acer G206HL monitor, which has a 1600x900 native resolution. It's connected to a 13" MacBook Pro (the current non-retina model) via a Thunderbolt-to-VGA cable. The MBP is running Mountain Lion 10.8.3.
    When I go to System Preferences -> Displays -> Resolution: Scaled, 1600x900 doesn't appear in the list, and none of the listed resolutions are satisfactory.
    Anyone know of a way to add custom resolutions to Mountain Lion's Display preferences?

    I'm having the same issue with a a 2012 MBA running Yosemite 10.10.1 (14B25). I wish I could find a solution to this problem.

Maybe you are looking for