A little while ago I picked up a 26″ monitor (NEC MultiSync LCD2690WUXi). Unfortunately, I found that when I connected the monitor to my Ubuntu Linux box that I could only use up to 1280×1028 — even though the monitor’s native resolution was 1920×1080! I also had this problem on my Windows and SuSE machines, so I suspect the monitor is not properly reporting its maximum resolution via EDID.
I used the command-line utility xrandr to fix the problem. Running the tool with no arguments prints a list of displays and available display modes for each. This is handy since you need the name assigned to your display by your OS for the next step. Next, use the “–newmode” option with xrandr and specify the modeline which describes the display configuration you wish to use. This modeline generator might help you create the modeline you need. Once you create the new mode, use the “–addmode” option to add it to the list of modes supported by your monitor.
Finally, add this command to your ~/.xprofile file (or something similar) so that when you start your machine the new mode is automatically added and available (this way Ubuntu automatically reselects it too). This is what I ended up adding to my ~/.xprofile file:
xrandr --newmode "1920x1200_50Hz" 128,300 1920 1968 2000 2079 1200 1203 1209 1234 +hsync -vsync
xrandr --addmode HDMI-0 "1920x1200_50Hz"
Note: If you set your refresh rate too high, your monitor will probably flicker occasionally. If this happens, try lowering the refresh rate by lowering the pixel clock value (the first number in the modeline).
David Underhill Linux EDID, Linux, modeline, monitor, resolution, X11, xrandr
A little while ago I bought Adobe Creative Suite CS4 Design Standard so that I could use Photoshop and Acrobat Pro on my Windows 7 machine (which I use for photo editing and organizing). Installing, registering, and activating the 64-bit version was painless, except for one problem: whenever I launched Acrobat, it would work fine for a few seconds until I was interrupted by an annoying dialog box which stated: “Adobe Acrobat was installed as part of a suite. To enable Adobe Acrobat, please start another component of this suite (such as Adobe Photoshop).” After clicking “Ok” Acrobat would shutdown.
Needless to say, this made the Acrobat part of my installation useless. Strangely, the dialog persisted even if I was already running Photoshop when I started Acrobat. I tried deactivating and reactivating, reinstalling, and so forth — all to no avail.
Google didn’t seem to have any advice on the matter, so I gave in and tried calling technical support. Though the representative was nice, he unfortunately didn’t have an immediate solution to the problem. I kept playing around with my installation and stumbled across something that worked — instead of running the 64-bit version of Photoshop, I ran the ordinary version (it is installed in your start menu alongside the 64-bit version). Ever since then Acrobat has worked fine (even when it is the only Adobe product running)!
It seems like the 64-bit version of Photoshop doesn’t properly communicate the activation details to Acrobat — a pretty bizarre (and annoying) bug for an Adobe product (which I am usually very fond of). Thankfully, the workaround is pretty simple — just run the regular version of Photoshop (presumably running Illustrator or any of the other programs in the suite would also do the trick).
David Underhill Software Acrobat, Adobe, bug, workaround