Judder using Mplayer... maybe force different resolution/refresh rate?

Hi!
(I posted this in the newbie section too, but this is maybe the most appropriate place??)
I've set up my computer as a media center using Freevo. As the main media player in Freevo I use Mplayer. The setup is working beautifully, but I'm getting some judder and it's a bit annoying. It's most noticable during bright, fast moving scenes.
So I've been trying to figure out how to remedy this, but it's harder than I thought. My setup is the following:
AMD 4200+ dual core, 2 gigs ram, Nvidia 7800GTX, 24" LCD and Pioneer LX508D plasma TV, and I'm using CoreAVC as decoder (amazing piece of software )
When I bought the 24" screen for my computer the sales guy (using windows) forced the resolution to 1920x1080. It looked a bit stretched, but if I could do this in Linux I'd avoid having parts of the picture missing on my TV. Now I have to use 1920x1200 resolution as main X session and since my TV is 1920x1080 parts of the desktop is out of view on my TV. This isn't too big of a deal though cause when playing movies they come out in 1920x1080. It'd be nice though to get the correct aspect ratio between my pc screen and my TV (I've been trying to use Twinview and clone, but it's impossible to use 1920x1200 on the 24" and 1920x1080 on the TV at the same time). I've tried to force my pc screen to use 1920x1080 (since it worked in windows it's supposed to be possible), but when I enable it through xorg.conf the screen goes blank. Using nvidia-settings doesn't give me the option of using 1920x1080 on the 24" at all.
So what I'm hoping to be able to do is to force the computer screen to use 1920x1080 and a refresh rate of 72Hz. This should eliminate alot of the judder and at the same time I won't have to use the "PC mode" on my TV (PC mode restrict the Hz to max 60Hz). Hopefully the TV will accept the 1920x1080 72Hz as any input and let me use the normal input (and then be able to use 72Hz... or 96Hz for that matter).
Anyone know how I might be able to do that? I'd really appreciate any help at all since this is the only thing that's not perfect with my setup.

Ok, I tried to change the xorg.conf file to 72Hz on the TV and it when black again. This is what the xorg.0.log shows:
X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.25-ARCH i686
Current Operating System: Linux arch 2.6.25-ARCH #1 SMP PREEMPT Mon Jul 14 15:25:51 UTC 2008 i686
Build Date: 21 June 2008 05:47:59PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 19 13:36:04 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Videocard0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "Xinerama" "0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) RgbPath set to "/usr/share/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81e0a60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 2.0
X.Org XInput driver : 2.0
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(--) using VT number 3
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1002,5950 card 103c,2a24 rev 10 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 1002,5a34 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:12:0: chip 1002,4379 card 103c,2a24 rev 00 class 01,01,8f hdr 00
(II) PCI: 00:13:0: chip 1002,4374 card 103c,2a24 rev 00 class 0c,03,10 hdr 80
(II) PCI: 00:13:1: chip 1002,4375 card 103c,2a24 rev 00 class 0c,03,10 hdr 00
(II) PCI: 00:13:2: chip 1002,4373 card 103c,2a24 rev 00 class 0c,03,20 hdr 00
(II) PCI: 00:14:0: chip 1002,4372 card 103c,2a24 rev 11 class 0c,05,00 hdr 80
(II) PCI: 00:14:1: chip 1002,4376 card 103c,2a24 rev 00 class 01,01,8a hdr 00
(II) PCI: 00:14:3: chip 1002,4377 card 103c,2a24 rev 00 class 06,01,00 hdr 80
(II) PCI: 00:14:4: chip 1002,4371 card 0000,0000 rev 00 class 06,04,01 hdr 81
(II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 01:00:0: chip 10de,0091 card 10de,02c2 rev a1 class 03,00,00 hdr 00
(II) PCI: 02:01:0: chip 13f6,0111 card 153b,1144 rev 10 class 04,01,00 hdr 00
(II) PCI: 02:03:0: chip 10ec,8139 card 103c,2a24 rev 10 class 02,00,00 hdr 00
(II) PCI: 02:04:0: chip 1106,3044 card 103c,2a24 rev 80 class 0c,00,10 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:2:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[b]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xfa000000 - 0xfcffffff (0x3000000) MX[b]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:20:3), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:20:4), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x0000d000 - 0x0000dfff (0x1000) IX[b]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xfde00000 - 0xfdefffff (0x100000) MX[b]
(II) Bus 2 prefetchable memory range:
[0] -1 0 0xfdd00000 - 0xfddfffff (0x100000) MX[b]
(--) PCI:*(1:0:0) nVidia Corporation G70 [GeForce 7800 GTX] rev 161, Mem @ 0xfa000000/24, 0xd0000000/28, 0xfb000000/24, I/O @ 0xef00/7
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) PCI I/O resource overlap reduced 0x00004100 from 0x0000411f to 0x000040ff
(II) PCI Memory resource overlap reduced 0xe0000000 from 0xe0000000 to 0xdfffffff
(II) Active PCI resource ranges:
[0] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
[1] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
[2] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
[3] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
[4] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
[5] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
[6] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
[7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[8] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
[9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
[10] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
[11] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
[12] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
[13] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
[14] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
[15] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[16] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[17] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[18] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[19] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
[20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
[21] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
[22] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
[23] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
[24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
[25] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
(II) Inactive PCI resource ranges:
[0] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
[1] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
[2] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
[3] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
[4] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
[5] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
[6] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
[7] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[8] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
[9] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
[10] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
[11] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
[12] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
[13] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
[14] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
[15] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[16] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[17] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[18] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[19] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
[20] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
[21] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
[22] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
[23] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
[24] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
[25] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
(II) Inactive PCI resource ranges after removing overlaps:
[0] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
[5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
[6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
[7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
[8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
[9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
[10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
[11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
[14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[17] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
[18] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
[19] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
[20] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
[21] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[22] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[25] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
[26] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
[27] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
[28] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
[29] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
[30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
[31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
[32] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 173.14.09 Thu Jun 5 00:07:40 PDT 2008
(II) Loading extension GLX
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DEC-XTRAP
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.4.2, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) NVIDIA dlloader X Driver 173.14.09 Wed Jun 4 23:47:25 PDT 2008
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
[5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
[6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
[7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
[8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
[9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
[10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
[11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
[14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[17] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
[18] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
[19] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
[20] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
[21] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[22] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[25] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
[26] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
[27] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
[28] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
[29] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
[30] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
[31] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
[32] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
(II) resource ranges after probing:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
[5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
[6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
[7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
[8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
[9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
[10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
[11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
[14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
[15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[20] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
[21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
[22] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
[23] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
[24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[28] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
[29] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
[30] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
[31] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
[32] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
[33] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
[34] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
[35] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
[36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "true"
(**) NVIDIA(0): Option "TwinView" "1"
(**) NVIDIA(0): Option "TwinViewOrientation" "Clone"
(**) NVIDIA(0): Option "MetaModes" "DFP-0: 1920x1200 +0+0, DFP-1: 1920x1080_72 +0+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
(**) NVIDIA(0): Enabling RENDER acceleration
(**) NVIDIA(0): TwinView enabled
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 7800 GTX (G70) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 262144 kBytes
(--) NVIDIA(0): VideoBIOS: 05.70.02.11.20
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 7800 GTX at PCI:1:0:0:
(--) NVIDIA(0): BenQ G2400W (DFP-0)
(--) NVIDIA(0): PIONEER_PDP. (DFP-1)
(--) NVIDIA(0): BenQ G2400W (DFP-0): 310.0 MHz maximum pixel clock
(--) NVIDIA(0): BenQ G2400W (DFP-0): Internal Dual Link TMDS
(--) NVIDIA(0): PIONEER_PDP. (DFP-1): 155.0 MHz maximum pixel clock
(--) NVIDIA(0): PIONEER_PDP. (DFP-1): Internal Single Link TMDS
(II) NVIDIA(0): Display Devices found referenced in MetaMode: DFP-0, DFP-1
(II) NVIDIA(0): Assigned Display Devices: DFP-0, DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "DFP-0:1920x1200+0+0,DFP-1:1920x1080_72+0+0"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
(--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfdefe000 - 0xfdefe7ff (0x800) MX[b]
[5] -1 0 0xfdeff000 - 0xfdeff0ff (0x100) MX[b]
[6] -1 0 0xfe02b000 - 0xfe02b3ff (0x400) MX[b]
[7] -1 0 0xfe02c000 - 0xfe02cfff (0x1000) MX[b]
[8] -1 0 0xfe02d000 - 0xfe02dfff (0x1000) MX[b]
[9] -1 0 0xfe02e000 - 0xfe02efff (0x1000) MX[b]
[10] -1 0 0xfe02f000 - 0xfe02f1ff (0x200) MX[b]
[11] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[12] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[b](B)
[13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
[14] -1 0 0xfa000000 - 0xfaffffff (0x1000000) MX[b](B)
[15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[20] -1 0 0x0000dd00 - 0x0000dd7f (0x80) IX[b]
[21] -1 0 0x0000de00 - 0x0000deff (0x100) IX[b]
[22] -1 0 0x0000df00 - 0x0000dfff (0x100) IX[b]
[23] -1 0 0x0000f800 - 0x0000f80f (0x10) IX[b]
[24] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[25] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[26] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[b]
[27] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[28] -1 0 0x00000500 - 0x0000050f (0x10) IX[b]
[29] -1 0 0x0000fa00 - 0x0000fa0f (0x10) IX[b]
[30] -1 0 0x0000fb00 - 0x0000fb03 (0x4) IX[b]
[31] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
[32] -1 0 0x0000fd00 - 0x0000fd03 (0x4) IX[b]
[33] -1 0 0x0000fe00 - 0x0000fe07 (0x8) IX[b]
[34] -1 0 0x0000ef00 - 0x0000ef7f (0x80) IX[b](B)
[35] -1 0 0x00004100 - 0x000040ff (0x0) IX[b]O
[36] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[37] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "DFP-0:1920x1200+0+0,DFP-1:1920x1080_72+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "Protocol" "auto"
(**) Mouse0: Device: "/dev/input/mice"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "yes"
(**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5 6 7"
(**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
(**) Mouse0: Buttons: 11
(**) Mouse0: Sensitivity: 1
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "trustda"
(**) Keyboard0: XkbModel: "trustda"
(**) Option "XkbLayout" "no"
(**) Keyboard0: XkbLayout: "no"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
Could not init font path element /usr/share/fonts/Type1, removing from list!
My xorg.conf looks like this now (I don't know what values to use for HorizSync and VertFresh on my TV, the ones that are in there I just made up ):
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder63) Mon May 19 00:34:28 PDT 2008
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "dbe"
Load "xtrap"
Load "extmod"
Load "record"
Load "freetype"
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "trustda"
Option "XkbLayout" "no"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
Option "Emulate3Buttons" "yes"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "BenQ G2400W"
HorizSync 31.0 - 94.0
VertRefresh 50.0 - 85.0
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "PIONEER_PDP."
# HorizSync 15.0 - 80.0
# VertRefresh 23.0 - 60.0
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G70 [GeForce 7800 GTX]"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7800 GTX"
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7800 GTX"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "NoLogo" "true"
Option "TwinViewOrientation" "Clone"
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "DFP-0: 1920x1200 +0+0, DFP-1: 1920x1080_72 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
I read somewhere that the TV is supposed to be able to show 1080p in 72Hz. But when I try that it goes blank. Maybe it has something to do with the monitor being 1920x1200 and the TV 1920x1080. The monitor won't accept 1920x1080 as resolution so I guess that can only be done in Windows...

Similar Messages

  • PowerMac G4 533DA & HDTV - video resolution / refresh rate problem

    Hope someone can help, I need to access more resolution / refresh rates than I currently get in the Leopard display control:
    I have a PowerMac G4 533 Digital Audio running Leopard 10.5.8 (unsupported).  It has an upgraded AGP videocard, a ( flashed PC - RV200 chipset) Radeon 7500 w/ 64MB and a DVI output w/ a VGA adapter.  I have used this Mac perfectly with my 19" widescreen Samsung SyncMaster 940BW, at a resolution of 1440 x 900 / 60Hz / millions of colors.  This monitor is actually for my MacPro, but I used it for the G4 to set it up.
    I  moved it to my living room to use as a basic HTPC.  Since it runs Leopard, it has up to date VLC, Quicktime for video files and a working Superdrive for movies.  I don't expect it to play anything more than 480p properly, I think that was the best I got on YouTube.  But if I have a DVD ripped to DivX or MP4 it plays them fine on the Samsung monitor.
    I connected it to my Viewsonic N3760w 37" 1080 HDTV.  It turns on, gray screen w/ Apple and gives me a working desktop.  The problem is that I cannot get it to give me the correct resolution and more importantly it seem to have the wrong refresh rate.  It is currently set at 1280 x 768 / 60Hz / millions of colors.  The screen give me like a small line slowly moving up across screen, higher refresh rates only make it movie faster up the screen.
    According to my Viewsonic, these are the resolutions for computer using the VGA plug on the tv:
    PC - 1360x768 (preferred) , 1024x768, 1280x768
    Mac G3/G4/G5 - up to 1280 x 1024, 1280x720 (preferred)
    Please note all of these are lower resolution than my Samsung monitor.  My Viewsonic also has on screen adjustment of " phase " and " frequency " as well as the usual color, contrast, etc available.  Is there a 3rd party app to manually adjust the resoluion and refresh rate?  I have seen Windows programs, does one exist for Mac OS X?
    TIA, sorry for the long post

    My Viewsonic also connected by VGA, no problem.
    I wish I knew more. I checked out the app you did a trial of. I noticed this statement on their web site:  Quote
    "After rebooting monitor stays blank
    For some reason your monitor does not accept the installed frequency. SWITCH IT OFF!"
    This is the type of statement that would 'worry me.' -- having the phrase: SWITCH IT OFF! all in caps seems to imply a possibility of damage...which I mentioned in my initial post. (and the site goes on to talk about how you should even then connect another monitor to change the settings you've made that were not accepted).
    As I said, though, I wish I knew more for sure about this. It seems that you not only did the obvious of checking System Peferences>Display, but also realize the Viewsonic has buttons that can influence it's screen image, most about position of the image on the screen but at least one item about resolution on mine. (under Setup Mode)
    For what it's worth, my Viewsonic is about 6 years old now, still fine, and has eight (8) possible resolutions shown in System Preferences.
    Re: Your numbers.
    It is currently set at 1280 x 768 / 60Hz / millions of colors. 
    PC - 1360x768 (preferred) , 1024x768, 1280x768
    Mac G3/G4/G5 - up to 1280 x 1024, 1280x720 (preferred)
    If you're only talking about a difference of 1280 x 768 and G4 1280 x 1024, perhaps just stretching the picture using the Viewsonic buttons is the way to go.
    Or, from the numbers, perhaps the G4 just wants a resolution closest to it's preferred state!?
    Anyhow, good luck.

  • Suggested Resolution & Refresh Rate for 19-inch Monitor

    Just had to replace my old 17-inch Apple Graphite Display. I stayed with a CRT and found a new 19-inch Dell M993s for pretty cheap.
    Now I'm trying to decide what the best screen resolution and refresh rate is...
    The HTML files that came on the Dell CD-ROM give recommended optimal settings for Windows OS's. But I'm not sure I should go by those for Tiger.
    Any suggestions?

    Just to make it completely clear
    You need to have the screen refresh rate set above 75hz so that screen refresh is less visible, the lower the number the slower the refresh rate and therefore the more visible it is and the more strain on the eye. The higher the refresh rate the better.
    Find the resolution which gives you 85hz or higher and which also makes best use of screen without making everything really small and hard to see or to read.
    I have a 19" Lacie and have it set to 1280 x 1024 85hz refresh rate.
    Mark

  • Maximum resolution/refresh rate the 5,6 model powerbooks can support? (15")

    Hiya, just checking out this program called DisplayConfigX which allows the user to add in modified resolutions that aren't listed automatically for your computer, and 2nd displays.
    before i really f* things over with my monitor, out of curiousity, is 1280x854 @ 60hz really the largest resolution those monitors can handle? (im of course referring to the powerbooks before the recently released models.

    Yes, 1280 x 854 really is the highest you can go. You are right to be cautious trying to enter anything higher. I can't recommend trying it.
    Some stand-alone monitors can perform a "downscaling" trick whereby they will fit a higher resolution into their native resolution by scaling down the input. The PowerBook lacks this ability. It can only upscale.

  • Xorg and refresh rates

    I'm running Solaris Express 10 x86 4/05 on a Dell Optiplex GX260. Xorg refuses to give me a refresh rate higher than 60Hz. This is using the i810 driver but it also happens with the VESA driver. Here's my xorg.conf:
    Section "Module"
    # This loads the DBE extension module.
        Load        "dbe"   # Double buffer extension
    # This loads the miscellaneous extensions module, and disables
    # initialisation of the XFree86-DGA extension within that module.
        SubSection  "extmod"
          Option    "omit xfree86-dga"   # don't initialise the DGA extension
        EndSubSection
    # This loads the font modules
        Load        "bitstream"
        Load        "type1"
    #    Load        "speedo"
    # This loads the Xst module
         Load       "Xst"
    # This loads the SolarisIA module
         Load       "IA"
    # This loads the GLX module
    #    Load       "glx"
    # This loads the DRI module
    #    Load       "dri"
    EndSection
    # Files section.  This allows default font and rgb paths to be set
    Section "Files"
    # The location of the RGB database.  Note, this is the name of the
    # file minus the extension (like ".txt" or ".db").  There is normally
    # no need to change the default.
        RgbPath     "/usr/X11/lib/X11/rgb"
    # Multiple FontPath entries are allowed (which are concatenated together),
    # as well as specifying multiple comma-separated entries in one FontPath
    # command (or a combination of both methods)
        FontPath   "/usr/X11/lib/X11/fonts/TrueType/"
        FontPath   "/usr/X11/lib/X11/fonts/Type1/"
        FontPath   "/usr/X11/lib/X11/fonts/Type1/sun/"
        FontPath   "/usr/X11/lib/X11/fonts/F3bitmaps/"
        FontPath   "/usr/X11/lib/X11/fonts/misc/"
        FontPath   "/usr/X11/lib/X11/fonts/100dpi/"
        FontPath   "/usr/X11/lib/X11/fonts/75dpi/"
    #    FontPath   "/usr/X11/lib/X11/fonts/local/"
    #    FontPath   "/usr/X11/lib/X11/fonts/Speedo/"
    #    FontPath   "/usr/X11/lib/X11/fonts/freefont/"
    # The module search path.  The default path is shown here.
    #    ModulePath "/usr/X11/lib/modules"
    EndSection
    # Server flags section.
    Section "ServerFlags"
    # Uncomment this to cause a core dump at the spot where a signal is
    # received.  This may leave the console in an unusable state, but may
    # provide a better stack trace in the core dump to aid in debugging
    #    Option "NoTrapSignals"
    # Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
    # (where n is 1 through 12).  This allows clients to receive these key
    # events.
    #    Option "DontVTSwitch"
    # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    #    Option "DontZap"
    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
    # sequences.  This allows clients to receive these key events.
    #    Option "Dont Zoom"
    # Uncomment this to disable tuning with the xvidtune client. With
    # it the client can still run and fetch card and monitor attributes,
    # but it will not be allowed to change them. If it tries it will
    # receive a protocol error.
    #    Option "DisableVidModeExtension"
    # Uncomment this to enable the use of a non-local xvidtune client.
    #    Option "AllowNonLocalXvidtune"
    # Uncomment this to disable dynamically modifying the input device
    # (mouse and keyboard) settings.
    #    Option "DisableModInDev"
    # Uncomment this to enable the use of a non-local client to
    # change the keyboard or mouse settings (currently only xset).
    #    Option "AllowNonLocalModInDev"
    EndSection
    # Input devices
    # Core keyboard's InputDevice section
    Section "InputDevice"
        Identifier  "Keyboard1"
        Driver      "Keyboard"
    # For most OSs the protocol can be omitted (it defaults to "Standard").
    # When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
    # uncomment the following line.
    #    Option     "Protocol"      "Xqueue"
        Option "AutoRepeat" "500 30"
    # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    #    Option     "Xleds"      "1 2 3"
    #    Option "LeftAlt"     "Meta"
    #    Option "RightAlt"    "ModeShift"
    # To customise the XKB settings to suit your keyboard, modify the
    # lines below (which are the defaults).  For example, for a non-U.S.
    # keyboard, you will probably want to use:
    #    Option "XkbModel"    "pc105"
    # If you have a US Microsoft Natural keyboard, you can use:
    #    Option "XkbModel"    "microsoft"
    # Then to change the language, change the Layout setting.
    # For example, a german layout can be obtained with:
    #    Option "XkbLayout"   "de"
    # or:
    #    Option "XkbLayout"   "de"
    #    Option "XkbVariant"  "nodeadkeys"
    # If you'd like to switch the positions of your capslock and
    # control keys, use:
    #    Option "XkbOptions"  "ctrl:swapcaps"
    # These are the default XKB settings for Xorg
    #    Option "XkbRules"    "xorg"
    #    Option "XkbModel"    "pc105"
    #    Option "XkbLayout"   "us"
    #    Option "XkbVariant"  ""
    #    Option "XkbOptions"  ""
    #    Option "XkbDisable"
        Option "XkbRules"   "xorg"
        Option "XkbModel"   "pc101"
        Option "XkbLayout"  "us"
    EndSection
    # Core Pointer's InputDevice section
    Section "InputDevice"
    # Identifier and driver
        Identifier  "Mouse1"
        Driver      "mouse"
        Option "Protocol"    "Auto"
        Option "Device"      "/dev/mouse"
    # Mouse-speed setting for PS/2 mouse.
    #    Option "Resolution"        "256"
    # When using XQUEUE, comment out the above two lines, and uncomment
    # the following line.
    #    Option "Protocol"  "Xqueue"
    # Baudrate and SampleRate are only for some Logitech mice. In
    # almost every case these lines should be omitted.
    #    Option "BaudRate"  "9600"
    #    Option "SampleRate"        "150"
    # Emulate3Buttons is an option for 2-button Microsoft mice
    # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
        Option "Emulate3Buttons"
    #    Option "Emulate3Timeout"    "50"
    # ChordMiddle is an option for some 3-button Logitech mice
    #    Option "ChordMiddle"
    EndSection
    # Other input device sections
    # this is optional and is required only if you
    # are using extended input devices.  This is for example only.  Refer
    # to the xorg.conf man page for a description of the options.
    # Section "InputDevice"
    #    Identifier  "Mouse2"
    #    Driver      "mouse"
    #    Option      "Protocol"      "MouseMan"
    #    Option      "Device"        "/dev/mouse2"
    # EndSection
    # Section "InputDevice"
    #    Identifier "spaceball"
    #    Driver     "magellan"
    #    Option     "Device"        "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    #    Identifier "spaceball2"
    #    Driver     "spaceorb"
    #    Option     "Device"        "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    #    Identifier "touchscreen0"
    #    Driver     "microtouch"
    #    Option     "Device"        "/dev/ttyS0"
    #    Option     "MinX"          "1412"
    #    Option     "MaxX"          "15184"
    #    Option     "MinY"          "15372"
    #    Option     "MaxY"          "1230"
    #    Option     "ScreenNumber"  "0"
    #    Option     "ReportingMode" "Scaled"
    #    Option     "ButtonNumber"  "1"
    #    Option     "SendCoreEvents"
    # EndSection
    # Section "InputDevice"
    #    Identifier "touchscreen1"
    #    Driver     "elo2300"
    #    Option     "Device"        "/dev/ttyS0"
    #    Option     "MinX"          "231"
    #    Option     "MaxX"          "3868"
    #    Option     "MinY"          "3858"
    #    Option     "MaxY"          "272"
    #    Option     "ScreenNumber"  "0"
    #    Option     "ReportingMode" "Scaled"
    #    Option     "ButtonThreshold"       "17"
    #    Option     "ButtonNumber"  "1"
    #    Option     "SendCoreEvents"
    # EndSection
    # Monitor section
    # Any number of monitor sections may be present
    Section "Monitor"
        Identifier  "My Monitor"
    # HorizSync is in kHz unless units are specified.
    # HorizSync may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
        HorizSync   30-85
    #    HorizSync  30-64         # multisync
    #    HorizSync  31.5, 35.2    # multiple fixed sync frequencies
    #    HorizSync  15-25, 30-50  # multiple ranges of sync frequencies
    # VertRefresh is in Hz unless units are specified.
    # VertRefresh may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
        VertRefresh 48-120
    EndSection
    # Graphics device section
    # Any number of graphics device sections may be present
    # Standard VGA Device:
    Section "Device"
        Identifier  "Standard VGA"
        VendorName  "Unknown"
        BoardName   "Unknown"
    # The chipset line is optional in most cases.  It can be used to override
    # the driver's chipset detection, and should not normally be specified.
    #    Chipset    "generic"
    # The Driver line must be present.  When using run-time loadable driver
    # modules, this line instructs the server to load the specified driver
    # module.  Even when not using loadable driver modules, this line
    # indicates which driver should interpret the information in this section.
        Driver     "vga"
    # The BusID line is used to specify which of possibly multiple devices
    # this section is intended for.  When this line isn't present, a device
    # section can only match up with the primary video device.  For PCI
    # devices a line like the following could be used.  This line should not
    # normally be included unless there is more than one video device
    # intalled.
    #    BusID      "PCI:0:10:0"
    #    VideoRam   256
    #    Clocks     25.2 28.3
    EndSection
    # Device configured by xorgconfig:
    Section "Device"
        Identifier  "** Intel i810 (generic)               [i810]"
        Driver      "i810"
        VideoRam    8192
        # Insert Clocks lines here if appropriate
    EndSection
    # Screen sections
    # Any number of screen sections may be present.  Each describes
    # the configuration of a single screen.  A single specific screen section
    # may be specified from the X server command line with the "-screen"
    # option.
    Section "Screen"
        Identifier  "Screen 1"
        Device      "** Intel i810 (generic)               [i810]"
        Monitor     "My Monitor"
        DefaultDepth 24
        Subsection "Display"
            Depth       8
            Modes       "1024x768"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth       16
            Modes       "1024x768"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth       24
            Modes       "1024x768"
            ViewPort    0 0
        EndSubsection
    EndSection
    # ServerLayout sections.
    # Any number of ServerLayout sections may be present.  Each describes
    # the way multiple screens are organised.  A specific ServerLayout
    # section may be specified from the X server command line with the
    # "-layout" option.  In the absence of this, the first section is used.
    # When now ServerLayout section is present, the first Screen section
    # is used alone.
    Section "ServerLayout"
    # The Identifier line must be present
        Identifier  "Simple Layout"
    # Each Screen line specifies a Screen section name, and optionally
    # the relative position of other screens.  The four names after
    # primary screen name are the screens to the top, bottom, left and right
    # of the primary screen.  In this example, screen 2 is located to the
    # right of screen 1.
        Screen "Screen 1"
    # Each InputDevice line specifies an InputDevice section name and
    # optionally some options to specify the way the device is to be
    # used.  Those options include "CorePointer", "CoreKeyboard" and
    # "SendCoreEvents".
        InputDevice "Mouse1" "CorePointer"
        InputDevice "Keyboard1" "CoreKeyboard"
    EndSection
    # Section "DRI"
    #    Mode 0666
    # EndSectionIf I use the Xsun server, everything works great. I get 1024x768 at 85Hz. With Xorg, I get 1024x768 at 60Hz. Why won't Xorg drive the display at a decent refresh rate?
    Thanks.

    I upped the log verbosity on Xorg and checked the Xorg.0.log file. I found some interesting things.
    First, I found this line:
    (II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs.
    Later on, I found these:
    (WW) I810(0): Extended BIOS function 0x5f05 not supported.
    (II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method.
    (WW) I810(0): Set VBE Mode rejected this modeline.
    Trying standard mode instead!
    Presumably, "standard mode" is an eye-watering 60Hz.
    This is on a Dell Optiplex GX260 with BIOS revision A09. The video chipset is an onboard Intel 82845 and the driver is Xorg's i810.
    Everything works fine with Sun's X server. I get a nice 87Hz refresh at 1024x768. I'm surprised that Xorg can't set the refresh on this machine. It's listed as Test Suite Level 2 certified in the HCL. Unless somebody can tell me what I'm doing wrong here, I'm going to post this incompatibility as a comment on the HCL.

  • Diablo II Refresh Rate (Solved)

    Whenever I start Diablo II it sets a werid Refresh Rate that causes my Monitor to be unable to display! Is there a way either in the xorg.conf or in Diablo II to specify a Refresh that must never be changed or safe ones that always must be met?
    Last edited by Sean-Der (2008-07-02 00:19:11)

    After the latest update with nvidia graphic's driver I had to add an entry in xorg.conf in order to force the apropriate refresh rate (for any resolution besides 1024x768)
    Section "Screen"
    Identifier "Screen 1"
    Device "NVIDIa GeForce FX 5200"
    Monitor "Belinea"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "TwinViewXineramaInfoOrder" "CRT-0"
    Option "metamodes" "1024x768_75 +0+0; 800x600_75 +0+0; 640x480_75 +0+0"
    Subsection "Display"
    Depth 8
    Modes "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 16
    Modes "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 24
    Modes "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    What you need to add is: (If, of course it's not already there)
    DefaultDepth 24
    Option "TwinView" "0"
    Option "TwinViewXineramaInfoOrder" "CRT-0"
    Option "metamodes" "1024x768_75 +0+0; 800x600_75 +0+0; 640x480_75 +0+0"

  • Nvidia 195.36.31-1 doesn't detect horizontal refresh rate correctly

    With both the nvidia driver 195.36.15 that was in the main repositories before the last update, and the nvidia-beta driver 256.35-1from aur my monitor's horizontal refresh rate is detected correctly(129.5khz with a 120hz vertical refresh rate).  However, the nvidia driver currently in the repositories 195.36.31-1 doesn't detect it correctly and forces a horizontal refresh rate of about 185khz.  This causes horizontal white lines to be seen all along the screen.
    I'm now happily using the beta driver from aur, but I can try to pinpoint the problem if someone can point me in the right direction.
    thanks.

    this is not a bug. this is a nvidia workaround so that xrandr is able to handle correctly multihead refresh rates. see the nvidia readme for details, and don't worry, the refresh rate is correct, else you would see garbage.
    Last edited by lloeki (2007-04-28 20:50:16)

  • How do I know if my Edge Animate compositions will scale up or down to fit each mobile phone platform's resolution? iPhone 3s, 4, 4s, 5, and 5s all have different resolutions. Do I use .png or svg?

    I want to use Edge Animate to create native app in PhoneGap Build. How do I know if my Edge Animate compositions will scale up or down to fit each mobile phone platform's resolution? iPhone 3s, 4, 4s, 5, and 5s all have different resolutions. And do I use .png or svg?

    If you use responsive scaling it will definitely scale .
    For best practises regarding graphics refer
    Edge Animate Help | Best practices for graphics in Adobe Edge Animate

  • Print a graph when used different resolutions

    Hello,
    my LV programm
    (using V8.5.1) must run on computers with different resolutions (1024x768,
    1280x1024...), so I used the option
    "new scaling of all frontpanel elements after changing the windows size" (free translating   )
    (German: "Alle Elemente des Frontpanels bei Änderung der Fenstergröße neu skalieren")
    in my VI.
    This works fine but now I have some trouble with the printout of a graph.
    Depending of the selected resolution of the computer, the graph will be printed complete or only partial, then the lower part of the graph is missing.
    To print out the graph I used the VI  "Append Control Image to Report.vi"
    Can anybody help me?
    Gruß
    jan91

    Hello Jan,
     you are right - when printing the report in landscape orientation, images will be cropped if higher than the paper size.This issue has already been reported to our LabVIEW R&D team (#36511) and should be solved in a forthcoming update of the report generation toolkit. In my opinion, the issue is linked to the problem that the image will not fill out the report page completely to the right margin (#36926), another nuisance you might also have encountered.
    I have created a workaround for the problem,  which you should find attached to this post. As you change the graphs background color for printing, I added another property to resize the graph to the maximum printable size (evaluated here in trial&error, depending on your printer, the maximum size might change a bit), and another one to restore the original size when the report is done. To reduce the "blink time" of the graph, I placed the restoring property node directly after the control image has been attached to the report, so that during printer initialization, the original layout is already visible again.
    Hopefully, this is acceptable for you, until these issues have been fixed.
    Best regards,
    Sebastian 
    Attachments:
    print graph (modified).vi ‏44 KB

  • Change refresh rates and resolution on another computer

    Hi, am i able to use a LAN cable from Computer A and connect to computer B then change B's refresh rates and resolution? for example from 800x600 to 1024x768 then change refresh rate from 60Hz to 75Hz. please advice thanks.

    Hi Trig,
    Thanks for your post and I hope your well today.
    There are two parts to this - in my mind:
    1. Changing Screen Resolution Programmatically From LabVIEW
    2. Use VI Server to remotely call a VI i.e. Computer A calling VI on Computer B which then runs the VI mentioned in 1. 
    1. 
    This link is a dev zone article which has code for programmatically changing the screen resolution
    http://zone.ni.com/devzone/cda/epd/p/id/1429
    Try it out. 
    2.
    VI Server
    The NI Example Finder contains some expamples for this.
    Building VI Server Applications
    http://zone.ni.com/reference/en-XX/help/371361E-01/lvconcepts/building_vi_server_applications/
    If you could provide more details, maybe versions of LabVIEW etc then maybe we can help you some more - have you got some code yet? And did you have any thoughts on how to do this?
    Another method I have consider is:
    Using a tool such that runs an exe or script which alters the resoltion.
    Then using the cmd (comand line) or in LabVIEW System Exec.vi to run the exe (via VI Server). 
    How To Change Your Screen Resolution From A Command Line
    http://desktopfeedbag.wordpress.com/2007/12/27/how-to-change-your-screen-resolution-from-a-command-line/
    Hope this helps, 
    Kind Regards
    James Hillman
    Applications Engineer 2008 to 2009 National Instruments UK & Ireland
    Loughborough University UK - 2006 to 2011
    Remember Kudos those who help!

  • Different resolutions for Macbook Pro display and External display

    Is it possible to have different resolutions for a Macbook Pro and an external display. I prefer to see less but larger on my Macbook Pro whilst seeing more but smaller on my external display. I use the DVI output to connect to an Acer 22in display.
    Thanks in advance
    Ian

    in4time wrote:
    I've actually tried that process and it doesn't work; I still get the same display qualities on both. Perhaps that process might work if one is not mirroring. Maybe there is a compatibility issue between my Macbook Pro and the Acer 223W. I'll persevere, but thanks for your help anyway.
    Ian
    Hi Ian,
    allow me to chime in:
    You are absolutely correct!
    In 'Mirroring Mode' both internal and external display have the same resolution.
    Only in 'Extended Mode' you can have different resolutions for both displays.
    Regards
    Stefan

  • Save several movies in different resolution in one go

    Hi everyone
    With Quicktime 7 there is an option to export an existing movie and save it with a different resolution such as 1280x840 to 640x480 Pixels etc.! Is there a possibility to make these changes to several files without repeating them for each and every movie (over 100 files)? Maybe with the help of AppleScript?
    Thanks for your help.

    Compress QuickTime Using Most Recent Settings (from Automator).
    The action only works on files (not folders of files). It would use the most recent QuickTime Player Pro export settings.
    Export a "dummy" file (say 30 seconds) from QuickTime Player Pro to your destination dimensions, codec and settings. The Automator action will "remember" those settings and use them in its action.
    Once done with those settings export the dummy file again using different settings and Automator will adjust to the new settings (if saved as a Workflow or Application).

  • How do I force a resolution on a second monitor

    I've connected a Samsung Syncmaster TV to my MacBook Pro through the miini display port via an HDMI adapter. The issue is that it can support up to 1920x1080 (this can easily be forced on a windows 7 laptop when connected the same way) but the option is not present on the options menu.
    com.Apple.boot.plist does have the ability to force resolutions but I can't find a resource that explains how to specify which display it applies to.
    How would I go about forcing the resolution on the TV through the above or otherwise. (SwitchResX has already been tried with no effect).

    When Mirrored mode is selected, the external display always operates at the same resolution setting as the built-in screen. If the external display's native resolution is higher than the built-in screen's, it will nevertheless be limited to the built-in screen's maximum setting, and it will be blurry, as any LCD display is when used below its native resolution. This makes using a high-res external monitor or HDTV in Mirrored mode with a 15" or especially a 13" MBP a really bad idea.
    When Extended Desktop mode is selected, each display can be set independently to its native resolution, giving superior image quality and more screen real estate. ED mode is usually vastly preferable to Mirrored mode when screens with different native resolutions are used together.

  • My back button and refresh button and my yahoo tool bar are dimmed a lot when I open up firefox. So as a result, I cannot use the back button nor my refresh button AND my yahoo toolbar disappears a lot. I have tried to get on your chat session but it is a

    <blockquote>Locked by Moderator as a duplicate/re-post.
    Please continue the discussion in this thread: [/forum/1/688252]
    Thanks - c</blockquote>
    == Issue
    ==
    I have another kind of problem with Firefox
    == Description
    ==
    My back button and refresh button and my yahoo tool bar are dimmed a lot when I open up firefox. So as a result, I cannot use the back button nor my refresh button AND my yahoo toolbar disappears a lot. I have tried to get on your chat session but it is always closed. I need one on one help. Please reply with resolution.
    == This happened
    ==
    Every time Firefox opened
    == two or three months ago
    ==
    == Firefox version
    ==
    3.6.3
    == Operating system
    ==
    Windows XP
    == User Agent
    ==
    Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 (BT-canvas) Firefox/3.6.3 GTB7.0 (.NET CLR 3.5.30729)
    == Plugins installed
    ==
    *-npdnu
    *npdnupdater2
    *Coupons, Inc. Coupon Printer DLL
    *Coupons, Inc. Coupon Printer Plugin
    *The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
    *6.0.12.448
    *RealPlayer(tm) LiveConnect-Enabled Plug-In
    *RealJukebox Netscape Plugin
    *Default Plug-in
    *Adobe PDF Plug-In For Firefox and Netscape "9.3.2"
    *BrowserPlus -- Improve your browser! -- http://browserplus.yahoo.com/
    *Shockwave Flash 10.0 r45
    *Yahoo Application State Plugin version 1.0.0.7
    *3.0.50106.0
    *My Web Search Plugin Stub for 32-bit Windows
    *Google Updater pluginhttp://pack.google.com/
    *Google Update
    *Next Generation Java Plug-in 1.6.0_20 for Mozilla browsers
    *Npdsplay dll

    * If the menu bar is hidden then press and hold the Alt key down, that should make the Menu bar appear (Firefox 3.6 on Windows) (see [[Menu bar is missing]]).
    * Make sure that you have the ''Navigation Toolbar'' and other toolbars visible: View > Toolbars .
    * If items are missing then see if you can find them in the View > Toolbars > Customize window.
    * If you see the item in the Customize window then drag it back from the Customize window to the Navigation toolbar.
    * If you do not see that item then click the Restore Default Set button in the View > Toolbars > Customize window.
    See also [[Back and forward or other toolbar buttons are missing]] and [[Navigation Toolbar items]]
    See http://kb.mozillazine.org/Toolbar_customization

  • Multiple displays with different resolutions

    The system is setup with two non-mirrored displays with the following resolutions: A) 1024x768 and B) 1280x1024 arranged as BA with A the menu'd display using an ATI 9000 Pro for Mac. During startup, approximately once inch worth of the menu's right items momentarily appear on the right side of display B 768 pixels down from the top. This problem only occurs in this BA configuration of differing resolutions and is independent of graphics cards (substituted the 9000 Pro with a mirror only AGP Navidia card and a mirror only PCI ATI Rage card combination which gave the same result). This problem first appeared using MacOS 10.3 which displayed several inches of menu instead of only an inch under MacOS 10.4. Anyone else seen this problem?
    Dual 800 MHz QuickSilver   Mac OS X (10.4.4)  

    Over the weekend, I explained this problem to one of the Apple Geniuses at an Apple store and then was able to duplicate the issue using a lap top and attached monitor in the store (not the same resolutions as my system; but, screens of similarly different resolutions). I raise this issue again because, as of late, additional things have been happening and I wonder if these are related to the core issue of an expanded desktop with two different screen resolutions. All of the widgets on the larger resolution screen desktop are drawing in the menu located in the smaller resolution screen when hitting the "i" to gain access to its control panel; however, not effecting the menu at all when moved to the smaller resolution screen. The other has to do with screen savers periodically blanking both monitors (as though the graphics card went to sleep) or having both monitors lose syncing (first occurrence today) where a cold start is required to bring the monitors on line again (I am going to have to figure out a way to test if the system is actually sleeping or the monitors have only gone blank before cold starting the system).

Maybe you are looking for