[CS3] Dual monitor : disable Flash interface windows effects (shadows   & transparency)

Sorry to "up" this question this way, but I've been on
holidays and this
problem is still a real pain for me !
I'm trying to work both with Flash and Director on a dual
monitor.
Director is quite tricky because you have to extend the
"background"
window so you can put your menus on the second screen, but it
works very
well afterwards.
While Flash should be a dream to use because you can freely
put windows
anywhere, every window on the second screen is awfully slow
(takes
seconds to move them).
I'm sure it would be a lot better if I could, at least,
disable those
effects.
Before you ask, I use an old S3Virge PCI card for my second
monitor...
Sorry, can't find any better PCI card...yet.
Thanks in advance.
PJ

Well, I bought a nice Matrox Mystique 220 in a car boot sale
and it's
much better, as long as I don't move windows (takes 3 seconds
to refresh !)
The card's got nice and stable resolutions, by the way !
I still would like to disable transparency, though...
PJ

Similar Messages

  • Dual monitors after upgrade to windows 10?

    I just upgraded to Windows 10 on an Envy 700-414.  My dual screens worked beautifully on Windows 8.1, but now my second monitor is not recognized.  This is not even a little bit OK.  How do I fix it?

     
    Hi DebiPGupta, 
    Welcome to Sony Community! 
    Disabling the ISB Utility from the System Configuration is part of the resolution for Widows 8 and 8.1 regarding battery issue. I'm happy that it worked on your Windows 10 machine. Sony will release the drivers and software for Windows 10 soon. Please check this page for further information: http://esupport.sony.com/US/p/os10upgrade.pl 
    Thanks,
    Vincent 
    If my post answers your question, please mark it as "Accept as Solution"
     

  • Dual monitor setup flashes constantly

    I am trying to set up a dual monitor setup with a Lenovo Thinkcentre Edge computer.  I reset the BIOS to enable multimonitor support and IGD Active Video.  One monitor is plugged into the VGA port.  But when I plug the second monitor into the DVI-D port, both monitors flash constantly and the speakers make the sound of a device being disconnected.  Unplugging the DVI-D monitor stops the problem on the VGA monitor.  I checked the drivers and they are all up to date.  Any ideas?

    Bad cable?
    Disclaimer: While I do work for Lenovo Partner, all my contributions are my personal, non-official and not that of Lenovo or my employer.

  • Mac Pro Dual Monitors in Boot Camp Windows 8.1 Pro

    I just set up my 2013 Mac Pro with Bootcamp using Windows 8.1 Pro x64 and so far everything works great (albeit the initial setup was a struggle) except that Windows won't use my 2nd monitor.  In device manager I see both displays but one has the exclamation on it saying there was a problem and it won't be enabled (yes, that generic too, gotta love Microsoft).  I really want to be able to use both displays when I am in boot camp, is there anything I can do to fix this?  I have made sure both Windows and Mac are fully updated and still no love.

    Thank you for the link but it wasn't helpful as it only really said compatibility.  What did finally resolve the issue was going directly to AMD and finding that they updated the BootCamp specific drivers.  For other that stumble upon this, you cannot use the normal drivers from AMD but you must search for the bootcamp specific drivers (which also includes an updated Catalyst utility and a couple extra things not included in Apples release of the drivers).

  • Satellite A30: Dual Monitor not recognised by windows

    I feed the second monitor output from my Satellite A30 to a frame converter for generating a composite video signal. In order for windows to enable the second monitor output on the laptop I have to have either a monitor or a projector attached. Is there a simple way of providing a 'dummy' device to trick the laptop into thinking it has a second monitor and removing the need carry extra kit around.

    I agree with you, to display the output on the second output can be done with the FN+5 keys. I am extending my desktop to the second graphics port so that programms such as powerpoint can "Display on second monitor" whilst opperating from the primary screen. The problem is that in order for the second port to be recognised by windows it has to have a monitor plugged in to it, but I have only got a SVGA to Composite video frame converter & the laptop dosen't recognise it as being a valid monitor.

  • Accessility zoom and dual monitor (disable zoom on one of the monitor)

    Hello,
    I am vision impaired user of the Mac. I'm having a problem. When I presenting something with PowerPoint or Keynote and using a projector.
    The zoom is enabled on the two monitor, so when I run the diaporama the Presentation Screen is not displayed, it display what I am sseing with the zoom on the computer zoom.
    So I would like to disable this behavior. I would like to see the presentation with the zoom on my computer screen and the Presentation mode on the projector.
    Do you know how to make this possible?
    Thank you,
    Best regards,
    Lionel

    I have figured it out today while looking for some other settings in Openbox. I have added to openbox's rc.xlm the following
    <application name="skype">
    <position force="yes">
    <x>100</x>
    <y>100</y>
    </position>
    </application>
    <application name="oblogout">
    <position force="yes">
    <x>0</x>
    <y>0</y>
    </position>
    <skip_pager>yes</skip_pager>
    <skip_taskbar>yes</skip_taskbar>
    <fullscreen>yes</fullscreen>
    </application>
    and now both application start in the main monitor.
    Last edited by VDP76 (2013-08-17 18:33:24)

  • Elements 11 Preview Window not visible in dual monitor mode

    When I go to dual monitor mode the preview window is hidden. I can still hear the audio from the clip but I can't see the video window. It is still hidden when I switch back to single monitor mode. The only way to bring it back is to close out the program and reopen it. Does anyone know where it goes and how to make it visible?

    MAINEEDIT
    I have just set up for Premiere Elements 11 Dual Monitor Mode in Windows 8 64 bit computer.
    How do you have your monitors set up...Extend Across.. or other?
    I am not having any problems keeping track of what I believe you are referring to as the "Preview Window". So please excuse
    if I double check with you via the following screenshot.
    Preview Window which can be brought up
    a. double clicking the file in Project Assets
    b. double clicking the file on the Expert workspace Timeline
    I am going to go over this one more time with my Premiere Elements 11 and Windows 8 64 bt computer to see
    if I can create the situation that I am interpreting that you have.
    Thanks.
    ATR
    Add On...This especially makes me ask....
    When I reopen the program the preview window appears in its normal position.
    The Preview Window is going to close when you save/close the project. As you saying that you re-opened the project
    to find the Preview Window opened?

  • Flash CS3 Crashes with Dual Monitors

    Flash CS3 crashes when I have the actions panel open on my
    secondary monitor and I close Flash. I have to actual move the
    action script panel to the primary monitor or close it completely.
    The same thing happens if I try to save my project space with the
    actions panel open.
    The other issue I have found is that when I open Flash up
    again, despite the fact that I have saved my work space profile,
    the pallets all appear on my primary monitor and not the secondary
    one. Didn't re amend this issue back in Flash 5 or 6?

    OK the problem isn't the DUAL Monitors, but rather having a
    custom workspace open while trying to close Flash. I have to change
    the workspace back to Default or it will not close at all. Any
    ideas.

  • Indesign CS3 Crashes Randomly on Windows x64, Dual Monitor Setup

    My coworker and I just had our computers upgraded Windows XP 64-bt on the following computer setup:
    Intel Core i7 920 2.66Ghz CPU
    8GB DDR3 RAM
    Gigabyte GA-EX58 Intel X58 Motherboard
    1TB Seagate ES.2 7200rpm 32MB Cache SATAII Hard  Drive
    We're running CS3. Indesign keeps crashing on her machine, randomly from what we can tell. It runs fine on my machine.
    We are running Indesign in compatibility mode for Windows XP on both machings (the crashing was much worse before we turned it on).
    The only difference between my computer and the workstation where Indesign CS3 crashes is she has a dual monitor setup.
    Any thoughts on what might be causing it?

    Thanks for the heads up.We're actually kinda banking on Windows 7 to be a bit more stable and switch to that, but it's a long few months when your program crashes every few minutes.
    I just realized that we don't have the latest update (5.0.4) on her machine, we've downloaded it and are hoping that will help to at least reduce the crashing...

  • Dual Monitors Windows 7 Problems

    Ok, this problem is getting really annoying and I think its a problem with windows 7 itself and not my computer.
    Basically I have a dual monitor setup with the left hand monitor as my secondary and right hand monitor as my primary.  Whenever I have an application with any graphics on it at all such as a progress bar on my left hand monitor moving windows around becomes laggy and juddery, yet this doesn't happen when the graphical app is on my primary monitor!
    My system Specs: 
    ASUS Striker Extreme MOBO
    OCZ 850W gameXtreme
    Core 2 Duo 2.4GHz CPU
    4GB (4x1GB) OCZ DDR2 1066MHz RAM
    Nvidia 8800GTX
    Sound blaster x-fi Xtreme Gamer (older PCI version)
    3 x 80GB HD for system drive in RAID 0
    1 x 500GB and 1 x 250GB drives for storage
    Monitors are 1680 x 1050 res
    Windows 7 Exp Index:
    CPU: 5.9
    Memory: 5.9
    Graphics: 6.8
    Gaming Graphics: 6.8
    Primary HD: 5.9
    What iv tried:
    Updating to latest drivers
    Upgraded system memory from 2GB to 4GB
    Installing 64-bit version
    removing sound card and re-installing windows from scratch
    upgraded my PSU
    Thanks for your help!

    (Latest update) This is the best I can do to alleviate the problem, and does reduce its severity immensely, but I found myself still noticing some slight playback glitches in videos on my second monitor which probably also translate to anything else with movement. I have tested with a panning scene in one of my videos and there is a subtle micro-stutter on my second monitor which I can find no way to fix. This doesn't occur if outputting to a single display, one or the other, nor does it occur when playing the video on my primary monitor in a dual-monitor configuration. Note that when I say "primary monitor", I am not referring to the monitor Windows has marked as primary, but my actual monitor rather than TV. In a dual-monitor configuration, this micro-stutter will only occur when playing video on my right monitor (TV), regardless of settings or which ports the monitors are connected to on the GPU. The micro-stutter occurs with no relation to the activity on the other screen, as it can be completely still. I can confirm the micro-stutter does not occur at all with Desktop Window Manager (Aero) disabled. In short, this is a nightmare.
    (Note that this micro-stutter is equally replicable in the 182.50 (WDDM1.1-less) driver, meaning there is no way to solve it other than disabling Aero or outputting to a single monitor.)
    I think I've solved the problem.. for me, anyway. I've divided this into short answer and "long answer", which is closer to a stream of consciousness in some ways, as I found out about Force10Level9 as I was writing.
    The short version:
    I've found some registry keys which seem to have fixed the problem for me. I haven't experienced any side effects, but use the tweaks at your own risk!
    I don't know exactly what they do. This comes from a lot of.. experimentation. I believe FrameRateMin tells the Desktop Window Manager that it's crucial to try to keep the framerate at or above the value specified (more details below), and Force10Level9 sounds like it forces DWM to use DirectX 9. I'm fairly certain about the former, not as certain about the latter, but together they do wonders.
    You can view the fix below. You can then save it as a .reg file and import it into your registry. Restart the Desktop Window Manager service or reboot to see the changes.
    Fix: http://pastebin.com/FFDbubw9
    Undo: http://pastebin.com/zA8CJY06
    (P.S. Just ran a FurMark test between fix applied and no fix. No difference in performance, with an inactive secondary monitor. I also noticed no difference in Physical Memory usage as reported by Task Manager. YMMV, let me know if you have any side effects.)
    (P.P.S. The screen fade that happens when you log in/out is just as choppy as before (or if it wasn't choppy for you, that shouldn't have changed). Oh well, how often do we see that thing, anyway? :))
    By the way, it appears 10Level9 is Windows 7's emulation platform for running DX10 on DX9 hardware. It's reported to be at least a 0.5x performance hit, so it's surprising that it actually makes Aero run better. If this article is anything to go by, Force10Level9 makes Aero run exactly the same as it does with older WDDM 1.0-only drivers like 182.50: http://www.techarp.com/showarticle.aspx?artno=637&pgno=1
    The long version:
    Well... I was able to do one more thing.
    There is an undocumented registry key which allows you to fine-tune the Desktop Window Manager's scheduling. Unfortunately, all of its values seem to be defunct in the final version of Windows 7 we all use today... except one: FrameRateMin.
    From what I gather, the Desktop Window Manager (Aero) carefully monitors the framerate it is able to achieve, and when it can't measure up to its own expectations, it will perform a "step down", or framerate reduction, and maintain this lower framerate for a given period of time (at one time specifiable with a registry value) before trying again at maximum speed.
    I presume it does all this to keep things looking "smooth".
    The problem is, in most cases, it doesn't help, and actually prolongs the stuttering duration. By "in most cases", I mean in every case it's happened in my personal usage of my Windows 7 computers.
    So what helped me was setting this FrameRateMin value to 60. That way, the Desktop Window Manager considers anything under 60fps to be unacceptable and will not remain at a lower framerate for purposes of perceived smoothness. Thus, the stuttering will take up as little time as possible, making it nearly unnoticeable most of the time.
    Keep in mind DWM shouldn't be having performance problems to begin with, but apparently in some cases, like with my particular hardware (desktop and laptop) and the latest NVIDIA drivers, it does.
    Down to brass tacks. The registry key is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM\Schedule. The value is FrameRateMin, a DWORD representing the minimum framerate DWM will consider as acceptable. I set it to 60, but you can set it to whatever you want.
    To repeat, this WILL NOT prevent Aero from ever getting below the framerate you specify; it simply prevents Aero from retaining a lower framerate after a stutter in order to give the illusion of smoothness (an illusion which fails).
    I imagine the main reason it fails so spectacularly in my usage is because I watch a lot of videos which play back at 24fps. Such a framerate plays back terribly with a 30Hz refresh rate, which is what Aero would reduce itself to for extended lengths of time. Now, performance hiccups are minimal, but sadly still existent.
    So this isn't a solution, but it does help. I am still uncertain of where the problem lies, considering GPU-Z shows graphics card loads to be as low as always when it's happening.
    Oh, and I found one more registry value. This one is far more important. :) It solves the problem for me entirely, from what I can tell.
    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics
    add the DWORD value Force10Level9 with a value of 1.
    I haven't noticed any side effects, just smooth performance.
    Apply these tweaks at your own risk!

  • Odd shadowing effects in XFCE with dual monitors and intel graphics

    Linux fowie-desktop 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 21:03:38 UTC 2010 i686 Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz GenuineIntel GNU/Linux
    lspci shows:
    00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
    00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
    00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
    not using an xorg.conf
    rc.conf (snippets)
    LOCALE="en_US.UTF-8"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/Denver"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(!usblp vboxdrv !saa7134 saa7134-dvb)
    DAEMONS=(syslog-ng dbus hal @network @netfs @crond @alsa @cups @sensors @samba @ddclient @sshd @httpd @mysqld @smartd)
    and my .xinitrc:
    /usr/bin/xrandr --output VGA1 --left-of DVI1 --output DVI1 --mode 1920x1080
    exec ck-launch-session startxfce4
    Xorg.0.log at http://pastebin.ca/1925313
    If I use the xf86-video-intel driver from extra, the xrandr command to do dual-outputs fails and I get both monitors showing the same desktop (mirrored mode).  I switched to use AUR's xf86-video-intel-git (reading the forums it said this would fix the dual-monitor issue until extra moves to 2.12.0-2) and I do get the dual monitors working propery with the xrandr command, but I'm experiencing wierd effects.  For every unminimized window on the desktop, if I put another window in front, the shadow of the window below stays on top of the window containing the focus.  Hard to explain, so I'll use a photo:
    That's what it looks like with xf89-video-intel-git, libdrm-git, dri-git, and anything else git and intel graphics related I can find.  Any ideas what's wrong, or what I would even call this problem so I can look around and see if anyone else is having the same issues?
    Last edited by fowie (2010-08-25 20:21:53)

    Ok, I went into the XFCE4 setting manager and opened the "Window Manager Tweaks" module, Under "Compositor" if I disable display compositing the shadowing effect is gone, making the display much more usable (thanks!).  But now compositing does not work.  Guess I'll go report this to XFCE, or is the XFCE compositing manager handled by someone else?
    Last edited by fowie (2010-08-25 23:11:54)

  • Bridge CS3 & ACR with dual monitors

    Question: In a dual-monitor Windows XP setup, how do I control which monitor ACR opens on when opened from Bridge?
    Background: In my workflow, I use Bridge to open small batches of DNGs in ACR. What I want is to have Bridge on monitor #2 (uncalibrated), but have ACR open on monitor #1 (calibrated). At first I had Bridge opening on #1 and couldn't get ACR to open on #2. Then I figured out how to move ACR to #2, but now it always opens on #2, regardless of where Bridge is. How to fix?
    Thanks,
    Andrew

    Okay, I think I've figured out how this works, although (1) the way it appears to function is exactly opposite to how I think it should function, and (2) I still can't figure out how to fix it.
    If I open ACR from Bridge on the primary monitor (#1 for short, as designated in Windows XP), ACR will open on the primary monitor by default. If I leave Bridge on the primary monitor but move ACR to the secondary monitor (#2 for short), ACR will continue to open on #2. If, however, I move Bridge to #2, there is no way to get ACR to open on #1; no matter what I do, it will always open on #2. If I then move Bridge back to #1, ACR might open on either monitor. If it continues then to open on #2 the only way to force it to move back to #1 is to open Photoshop on #1 and then open ACR from Photoshop.
    First of all, it's stupid that I can't tell ACR to open wherever I want it to. But it is particularly stupid that one cannot make ACR open on #1 unless Bridge is also open on #1. The reason is that Windows XP only has native support for color calibration on the primary monitor (#1). If I'm using Bridge and ACR next to each other, I naturally care more about color calibration in ACR, where I'm actually editing photos, than I do in Bridge. Yet it is impossible to get ACR to open on the calibrated monitor! This can only be described as a bug, albeit one that won't get fixed due to the age of XP and CS3.
    (Yes, I am aware that Microsoft makes a control-panel plugin that supposedly allows calibration of both monitors, but I have been unable to get it to work correctly. By all accounts it is somewhat fragile, doesn't offer support for all dual-monitor graphics cards, there isn't a list of cards it does and doesn't support, and Microsoft doesn't even offer support for the plugin. Way to go, Microsoft.)

  • MythTV Program Guide Slow/No Composite Effects On Dual Monitor

    Hello all,
    I am not entirely sure where this would belong, so I put it here.
    I am running Arch64 with an NVidia 8600GTS and dual monitors as seperate X screens. The second monitor is actually a TV not a monitor, and is using the S-Video output on the video card, but I'm not sure that that's relevant at all.
    On my primary monitor the program guide in MythTV runs fairly decent, however on the TV it runs unbearably slow. Pushing up on the remote a time or two will take a minute or so to happen. I have it set to the least demanding level possible.
    I originally thought that this was just a MythTV issue but I noticed that XCompmgr and Compiz-Fusion effects do not work at all on the TV either, so I think these issues are related.
    Also, I do not currently have a composite window manager installed, I am using Gnome with Metacity.
    Here is a copy of my xorg.conf:
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder62) Tue Jan 6 09:44:34 PST 2009
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder62) Tue Jan 6 09:43:54 PST 2009
    # Auto-generated by Archie mkxcfg
    # Auto-generated by Archie mkxcfg
    Section "ServerLayout"
    # Serial Mouse not detected
    # USB Mouse not detected
    Identifier "Xorg Configured"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "PS/2 Mouse" "CorePointer"
    EndSection
    Section "Files"
    # Additional fonts: Locale, Gimp, TTF...
    # FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
    # FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc:unscaled"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/PEX"
    FontPath "/usr/share/fonts/cyrillic"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/ttf/western"
    FontPath "/usr/share/fonts/ttf/decoratives"
    FontPath "/usr/share/fonts/truetype"
    FontPath "/usr/share/fonts/truetype/openoffice"
    FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath "/usr/share/fonts/latex-ttf-fonts"
    FontPath "/usr/share/fonts/defoma/CID"
    FontPath "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
    Load "ddc" # ddc probing of monitor
    Load "dbe"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "type1"
    Load "freetype"
    Load "record"
    # Load "synaptics"
    EndSection
    Section "ServerFlags"
    Option "AllowMouseOpenFail" "true"
    Option "AutoAddDevices" "False"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    Option "XkbVariant" ""
    EndSection
    Section "InputDevice"
    Identifier "Serial Mouse"
    Driver "mouse"
    Option "Protocol" "Microsoft"
    Option "Device" "/dev/ttyS0"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "ZAxisMapping" "4 5"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    Section "Monitor"
    # Warning: This may fry old Monitors
    # Very conservative. May flicker.
    # VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -hsync +vsync
    ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -hsync +vsync
    ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -hsync +vsync
    ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -hsync +vsync
    ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -hsync +vsync
    ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -hsync +vsync
    ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -hsync +vsync
    ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
    ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
    ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
    ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
    ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
    ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
    ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
    ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
    ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
    ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
    ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
    ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
    ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
    ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
    Option "DPMS" "true"
    # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 55.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "All"
    BoardName "All"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 16
    Option "TwinView" "0"
    Option "metamodes" "DFP: 1680x1050 +0+0; DFP: 800x600 +0+0; DFP: 640x480 +0+0"
    SubSection "Display"
    Depth 16
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 16
    Option "TVStandard" "NTSC-M"
    Option "TVOutFormat" "SVIDEO"
    Option "TwinView" "0"
    Option "metamodes" "TV: nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 16
    EndSubSection
    EndSection
    It's a bit of a mess at the moment. Last time I reinstalled I was having trouble with the keyboard and mouse not working in Gnome, so I've been hesitant to mess with it too much.
    On my previous install my xorg.conf looked like this:
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder58) Wed Oct 1 15:13:37 PDT 2008
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jul 17 18:39:00 PDT 2008
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    # RgbPath "/usr/lib/X11/rgb"
    EndSection
    Section "Module"
    Load "dbe"
    Load "extmod"
    # Load "type1"
    Load "freetype"
    Load "glx"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "keyboard"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    Option "DPMS"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 8600 GTS"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection
    Section "Screen"
    # Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "RenderAccel" "True"
    Option "NoRenderExtension" "False"
    Option "AllowGLXWithComposite" "True"
    Option "XvmcUsesTextures" "True"
    Option "LoadKernelModule" "True"
    Option "DamageEvents" "True"
    # Option "LogoPath" "/home/theavataroftime/Pictures"
    Option "NoLogo" "True"
    Option "TwinView" "0"
    Option "metamodes" "DFP: 1680x1050 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "RenderAccel" "True"
    Option "NoRenderExtension" "False"
    Option "AllowGLXWithComposite" "True"
    Option "XvmcUsesTextures" "True"
    Option "LoadKernelModule" "True"
    Option "DamageEvents" "True"
    Option "LogoPath" "/home/theavataroftime/Pictures"
    Option "NoLogo" "True"
    Option "TVStandard" "NTSC-M"
    Option "TVOutFormat" "SVIDEO"
    Option "TwinView" "0"
    Option "metamodes" "TV: nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    Option "RENDER" "Enable"
    EndSection
    I had the same issues with composite managers and that MythTV guide using this xorg.conf too.
    Has anyone had any similar issues? I am at a total loss here, so any help is greatly appreciated. Thank you.

    No one else has had troubles with the program guide or composite effects on dual monitors?

  • Mac Pro, Leopard 10.5.2, Photoshop CS3, 8800GT and Dual Monitors - Crashing

    Hi, I received my Mac Pro (with Nvidia 8800GT) earlier this week and set it up with my dual monitors. I soon discovered that Photoshop CS3 crashes when scrolling a 'zoomed in' image with dual monitors. Photoshop is setup so that all palettes are on the smaller samsung monitor and the main image window I'm working on is on the 23" cinema display.
    I've updated both the OS and CS3 but cannot solve the problem unless I switch to a single view setup, ie, drag all the palettes over to the larger monitor so that photoshop is no longer dual monitor. Then it works fine. Although it's a workaround, it's not an ideal situation. Has anyone else found this to be an issue? Have you found a solution?
    I've also re-installed Photoshop, visited a genius bar and changed mice!
    Thanks, any help would be appreciated.
    -N

    My Mac Pro had been running 3 Dell monitors on two NVIDIA GeForce 7300 GT cards for months, and with the (I think) Safari update all of a sudden the Mac freezes, 1 monitor displays garbledy gook, and the other is blank with a blinking power light. That is, until yesterday when the power light refused to come on. So I says to myself, "Self, how about testing them on my iBook?" The 1704FPT will not power on, plugged in to a computer or not. The 1707FP shakes like crazy when starting up on the iBook, then settles in and seems to work. Meanwhile, the SP2008WFP is working alone on the Mac Pro, but not totally trouble-free. What the heck is going on?

  • Mac: Full screen on dual monitors still doesn't work with Flash 10.2 upgrade

    Recently upgraded to Flash 10.2 specifically for the ability to work on a second monitor while watching fullscreen video on the first.  It's still not working at all.  The second I click on anything on the second screen, the video jumps back from full screen.  I checked to make sure that these sites work properly with dual monitors on a Windows machine.  Any tips to get this working?  Without this feature, certain websites are completely useless.
    Running: MAC 10,2,152,33 on OSX 10.6.6

    Hi, I think you are right about it being in this latest FP update. The "More like This" feature on the right hand side of the threads is not working. I think I have some info on Full Screen, but not the dual monitor issue. I'll check to be sure.
    I'll try to find some info on it. There were so many changes that came out with this last update.
    Will get back to you when I find the info.
    Thanks,
    eidnolb

Maybe you are looking for