Accessibility zoom unusable on multi-monitor setup

The accessibility zoom feature (ctrl-scoll when enabled) that always worked so well and fluidily in previous versions of OSX is now broken in Yosemite.
It works fine on my macbook pro retina's main display when there are no monitor connected, but on my usual dual external monitor setup the frame rate is so slow it makes is useless.
Does anyone have the same issue?

I just found a great workaround for the zoom and it works better than before.
The zoom defaults to fullscreen zoom and when you have multiple monitors it zooms all of them. Normally I don't need to zoom all just the one monitor that I'm working on.
Go to "system preferences " ,"accessibility ", set zoom style to "picture in picture" and then click "more options" and then click "adjust size and location" then you can set the zoom window to the size of a monitor. then when you zoom only the monitor you are on gets zoomed and is fast.
Works for me. Hopefully helps others as well.

Similar Messages

Mouse pointer is unchangeable at 100% scaling in multi monitor setup with different resolutions

Hi there, I have been asked by one of the moderators of the Windows 8.1 forums to post this topic here. You can see the thread relating to this post here
http://answers.microsoft.com/en-us/windows/forum/windows8_1-tms/cant-change-the-cursor-pointer/ae8ad8a0-3ded-4810-a3be-794f6c4830a4?msgId=2bd7082f-f5d1-4b01-8c70-e0d2a754d66f&page=1<o:p></o:p>
The problem: The mouse pointer becomes unchangeable in size, type, trails etc when 100% scaling is used. As in it reverts to the standard small white non-inverted, no trails,
no shadow 'pointer', no matter what options you select in the 'Mouse' control panel settings.<o:p></o:p>
This appears to be a scaling problem with the Windows 8/8.1 display, not an actual mouse problem. Judging by my own and other peoples experience it seems to happen mainly with multi
monitor setups where different screen resolutions are used. The issue occurs typically when 100% scaling for all monitors is used or this option is un-ticked and the 'change the size of all items' is on smallest (equivalent to 100%). <o:p></o:p>
If the scaling is set to 150% or greater the issue disappears and the mouse pointer becomes fully functional. Also bizarrely when the scaling is set to 100% if the screen is recorded
using a screen capture program, the recording of the screen shows the mouse pointer selected in the mouse options and not the default small white cursor that is present when recording it. Here is a link to a video where I explain and show the problem
happening on my system. http://youtu.be/xs2cxoeaq-A<o:p></o:p>
I have every update installed without exception, latest drivers etc. I use a 55" 4k screen with 2x1080p monitors in portrait on either side. All are connected through 1 Nvidia
GTX 780 6GB graphics card<o:p></o:p>
Hope you can help us<o:p></o:p>
thanks<o:p></o:p>
Jon M<o:p></o:p>

Hi Jon,
I'm looking into this issue but it will take me some time to provide a reply.
In the meantime I noticed that you have 3 monitors with 1x 55' and 2x27' - please have a try to only connect 1x27' monitor and see if issue persists.
Also please try to change the screen resolution to a lower size and see if issue persists.
Both suggestions are not solution, I just would like to know if it is related to multiple monitor or screen resolution.
If you have any feedback on our support, please send to [email protected]

How do I avoid errors on a Multi - monitor setup?

Hi.
I want to use Photoshop CS6 on a Multi - monitor setup, using iGPU multi-monitor + GPU system for 4 monitors.
Preiously, I used Photoshop on a Multi - monitor setup without useing iGPU multi-monitor.
And, Photoshop worked well.
However, when I wanted to use 1 more monitor, my GPU supports only 3 monitors.
Then, I enabled iGPU multi-monitor function. It supports 2 more monitors.
At first, It worked. But, after I use "Free transform", "Transform" or something like these tools, Photoshop hang up!
I couldn't figure out the reason why these errors happened.
I need ways to avoid these errors.
Thanks.

Thanks for viewing this discussion.
Finally, I brok through this problem.
I show you how to do, in case of when you face to this problem.
The way to solve this problem is, simple, "buy a new GPU."
But, there is 1 important point, you should buy a same bland's GPU.
In my case, I have SAPPHIRE'S RADEON HD5670, and I bought SAPPHIRE'S RADEON HD 6450.
I think that Photoshop GPUsniffer was confused about GPU driver.
Because there were 2 drivers -- Radeon and Intel Graphics -- exist.
That's why Photoshop hang up.
For your reference,
Best regards.

Does the new Keynote support multi monitor setup?

Keynote just got updated to yosemite and I'm wondering if it will support my use case of multi monitors... Let me explain. At Church we use Keynote for the pastors sermon presentation and so I have it set up to project the presentation to the main projector and have a rear stage display for the pastor in the back with his notes and such and then the display in the sound booth is basically useless because Keynote hijacks every display the computer is running. I'm hoping the update will allow me to keep my sound booth monitor available for other uses... (Recording in garageband) Thanks for the help!

Ok, just because the applications you mention don't work like that doesn't mean this is a hardware limitation. I haven't used any of the four programs you mention and have only actually heard of Lightroom. I believe you that these don't work in that way BUT... Check out the application ProPresenter. That is what we use at church for worship and announcements and stuff like that and that program functions exactly as i need it to. The two projectors project full screen setups just as I want and my desktop display is free for me to use and do whatever I want. So, with that said, obviously it's not a hardware limitation.y It could be a lack of APIs to make this happen, but ProPresenter has actually figured it out. It's is a great program for text, but not so great for a full presentation. I just wish Keynote would be able to do the same...

Photoshop, multi-monitor setup has wobbly lines at left of monitors

Hi All
I'm having a problem with jagged, wobbly lines in Photoshop CS5.1. This has nothing to do with Smoothing or anything (the wobble is more pronounched with smoothing off however).
I believe it has something to do with my 3 monitor setup in Windows 7 64bit, Nvidia GTX 460, and some sort of positioning error PS can't get it's head around (this affects NO other programs I have like Painter or Artrage). See below for my setup. I have the Cintiq 24HD and Intuos 4 and the problem occurs on both tablets. Any monitor that is set in Windows Display at '0' will have a wobbly line in Photoshop if I draw if the doc is at the left of the monitor and I then draw in that area.
If I place a doc from Photoshop in the centre of the Cintiq - no wobbles. As soon as I move it near the top left of the Cintiq (when it's monitor position in Windows is aligned directly under Monitor 1 as they are the same size), the wobble starts. Once it's started on a doc, it continues no matter where you try drawing on the screen after that until I close and reopen Photoshop.
This definitely has NOTHING to do with electromechanical interference to the tablets as I never physically move anything but can change it's occurance by moving the Display layout in Windows.
Any monitor For me it starts from the '0' position up to about the '474' position. If I aligned all my monitors one underneath the other so they were all started at '0', then they'd all do the wobble thing on the lefthand side (using either the Inutos4 or Cintiq). Windows makes you have your main monitor at '0', so I alway have a problem on that monitor. The other person I know of who has this problem (posted on the Wacom forum), has said they get around it on their Cintiq (which is the main monitor), by pushing on of their other monitors into a negative setting to the left.
It's a real pain. Anytime I want to use my Cintiq in Photoshop I have to go into Display setting and move it to the right. Once you get the wobbles they don't stop. ie they are then not restricted to the left of the doc, but all over. You have to close and reopen PS and start again.
Below is an example of the wobble. First I drew on the right... no wobble. Then I drew on the left. Lines are no longer smooth, but jiggly. Note smoothing is ON. Wiggling is worse with it off.
I haven't a clue if it's an Adobe problem or a Wacom one. Note that my graphic drivers etc are all up-to-date and I've uninstalled, reinstalled, cleaned reg, unplugged/replugged, tried just one tablet or other , stood on my head, for Wacom drivers (old versions and newest versions) till I'm blue in the face. No difference.
Anybody have an idea? PS Wacom (europe at least) do seem to know of the problem, but are not saying anything else at the moment.

No, it's got nothing to do with electromagnetic interference, or I couldn't change what happened by just altering the monitor position within Windows multimonitor display setup and not moving the tablets physically at all. And as you say, interference would happen on every program - not just Photoshop. There is no actual 'cursor' wobble. I've had interferance on older Intuos 3 tablets and at the edges of the old Cintiq 21UX, so know what that is like.
I think it's either the Windows OS or Wacom Driver, not telling PS something about the Monitor position Or PS not reading the info correctly.

Windows 10 hiding taskbar in multi-monitors setup bug.

This bug persists since windows 8.1 and is already discussed
here, but it wasn't fixed in approx. half a year :( So, I'm gonna give it a try here.
Here's the screenshot of it in Windows 10.
Well, the bug is with incorrectly disappearing taskbar - taskbar "hides" not in the bottom of the screen, but "taskbar height pixels" higher (see the images in onedrive folder below). It hides in such a way only when you go to start screen
with visible taskbar, wait until it disappears and return to desktop in any way (by pressing the win key, by selecting desktop on startscreen or by clicking the windows logo in the lower left corner); this bug only appears with two monitors setup and
heavily depends on monitors position - the secondary monitor bottom should be below primary monitor bottom (I mean not physical location, of course, but monitors' relative location in "Screen resolution" menu). The bug didn't appear before Update
1; I can't confirm whether it is reproduceable only on my PC at the moment.
I have reproduced the bug on windows 8.1 U1 across several computers with 100% success rate: two macbooks pro retina, lenovo laptop, two desktops (on one of them I reproduced the bug via teamviewer). I've reproduced it today in VMWare with windows 10 Technical
Preview.
This bug is really annoying - when it happens, you need "to cast some magic" - move the mouse to the bottom of the screen, activate/deactivate several applications, etc. in order for taskbar to reappear properly, let alone the fact that it looks
unaesthetic.
Skydrive folder with bug screenshot
Screen recording of the bug
Step-by-step guide with screenshots

Yeah, I already did it. I just wanted to open it here, because I've been trying to contact MS about this bug for almost half a year with no success, so I'm just trying to bring their attention to this thing in all ways possible. I could reproduce this bug
on all the systems I've tried so far, and I've managed to reproduce it even on VMWare in newly-installed windows 10 TP in a single try.
@rgggg
I can't understand what do you mean by weakness in graphics. It's a 100% functionality bug. Also, of course, I have nothing to do except reporting some non-existent bugs, making fake screenshots etc. I can't understand what do you mean about "intermediate
servers", and it's almost impossible to change every Windows iso distributive I've downloaded in such a way that this bug will appear there :D
C:\Users\Sfairat>fciv -both D:\Downloads\WindowsTechnicalPreview-x64-EN-US.iso
// File Checksum Integrity Verifier version 2.05.
MD5 SHA-1
9005dce26734bcde7f912c2c51ab1127 eb75a3d3c0f621f175b75dc65db036d0e00eac43 d:\dow
nloads\windowstechnicalpreview-x64-en-us.iso

IOS7 accessibility zoom conflict with multi app closing

I some times can't read small text or see small indicators so I turned on the zoom function from the accessibility settings. When I open the multitasking window, I usually need to close as much apps as possible in the least time so I flick three fingers up the screen to close three apps at a time. When the zoom is enabled from the settings (not the actual zoom (double tap three fingers)), I can only close two apps at a time, when it is disabled I can close three apps at a time. I believe this is a bug with iOS7, I wanted to tell apple but I didn't know how except through here. Please tell me if you have the same bug and that I'm not alone.

A Chrome extension is out which enable Bootcampers to swipe back/forth for pages. You can get it here:
https://chrome.google.com/webstore/detail/mgegfjnccpnkdppohmfgnjalkediapkc
Or search for it yourself:
Swipe Gesture
In google addon store.
All credits goes to antimatter15.com for creating this. It's still at an early stage, but very useful indeed. And as seeing that swiping back/forth is one of the most used multi touch features (at least to my experience) this addon is a godsend. Also has no problem with people running virtual machines, as the addon can simply be turned off.

Display Artifacts on MBPr Multi-Monitor Setup (+Solution)

Hey everyone,
I'm fortunate enough to have access to 3 MBPr in 3 different environments. I've confirmed that this bug is present on all MBPrs:
How to replicate:
- 2 1080p or higher monitors, one using a DVI -> DisplayPort adapter and the other using HDMI or HDMI -> DisplayPort (It doesn't matter)
- 2 external monitors arranged so that they are "Above" the internal display and the internal display is centered, below both monitors (I'm talking about the Displays Arrangement tool, not necessarily physically, FYI)
- Move your title bar so that the RIGHT external monitor has the menu bar.
- Your MBPr is setup to Scaled, "More Space" (1920x1200)
With this exact setup, you have now introduced display artifacts at the bottom of your retina display. Specifically near the bottom left. You can replicate this every time if you use mission control to display all spaces. (Swipe up with three fingers on trackpad).
The severeity of the artifacts changes from MBPr to MBPr and depending on how centered your retina display is. I believe this is a spaces / geometry bug when using scaling.
To work around this issue, simply move your menu bar to the LEFT monitor, or keep it on the internal display. You can also re-arrange the displays to make this go away. But I find having the menu on the left is the least impactful work around.
Can anyone confirm what I'm posting here?

Great information. I can confirm that fixes the problem... But unfortunately it isn't ideal, since my MBPr is below my two external monitors. I'd rather have the menu bar on one of the two monitors...
Sadly this issue is still present on OSX Mavericks. But since it has menu bars on every monitor, I might be able to get away with making the MBPr the primary monitor... Will test to confirm.

ATI card + OS driver + multi monitor

Hello everyone,
I'm stuck configuring the RadeonHD drivers for multi monitor setup. The system starts with both screens cloned; logging in is in clone mode too. After that the second display is being turned of (no signal). Using xrandr --auto will enable the second display to life and clones the sreen again. xrandr --output DVI-I_1/analog --left-of DVI-I_2/analog will create a big desktop only the second display can only be used for a half screen mouse will go further anything else will not.
I've started with a autogenerated, by xorg, xorg.conf file and tweaked to the one below
xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
EndSection
Section "Files"
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 "dri2"
# Load "extmod"
# Load "dri"
# Load "record"
EndSection
Section "Monitor"
Identifier "AL1916W"
VendorName "Acer"
ModelName "AL1916W"
DisplaySize 1440 900
EndSection
Section "Monitor"
Identifier "AL2016W"
VendorName "Acer"
ModelName "AL2016W"
Option "RightOf" "AL1926W"
DisplaySize 1680 1050
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "AccelMethod" # [<str>]
#Option "offscreensize" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "ignoreconnector" # [<str>]
#Option "forcereduced" # [<bool>]
#Option "forcedpi" # 
#Option "useconfiguredmonitor" # [<bool>]
#Option "HPD" # <str>
#Option "NoRandr" # [<bool>]
#Option "RROutputOrder" # [<str>]
#Option "DRI" # [<bool>]
#Option "TVMode" # [<str>]
#Option "ScaleType" # [<str>]
#Option "UseAtomBIOS" # [<bool>]
#Option "AtomBIOS" # [<str>]
#Option "UnverifiedFeatures" # [<bool>]
#Option "Audio" # [<bool>]
#Option "AudioStreamSilence" # [<str>]
#Option "HDMI" # [<str>]
#Option "COHERENT" # [<str>]
#Option "ForceLowPowerMode" # [<bool>]
#Option "LowPowerModeEngineClock" # 
Option "monitor-DVI-I_1/analog" "AL1916W"
Option "monitor-DVI-I_2/analog" "AL2016W"
Identifier "Card0"
Driver "radeonhd"
VendorName "ATI Technologies Inc"
BoardName "RV710 [Radeon HD 4350]"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
# Monitor "AL1916W"
SubSection "Display"
Depth 24
# Virtual 3840 1920
EndSubSection
EndSection
My Xorg.0.log shows the line (WW) RADEONHD(0): Option "monitor-DVI_I_2/analog" is not used wich puzzles me!
Information:
X.Org X Server 1.7.1.901 (1.7.2 RC 1)
xrandr program version 1.3.2
Server reports RandR version 1.3
xf86-video-radeonhd 1.3.0-1
If more information, from Xorg.0.log or anywhere else, is needed just ask....
Thanks in advance,
Arjan Gelderblom
Last edited by Bloged (2009-12-14 10:02:05)

Sorry for the delay, but I was away for the weekend!
Andrwe wrote:Please try setting the bigger one monitor right-of the small one.
xrandr --output DVI-I_2/analog --right-of DVI-I_1/analog
This doens't change much except that now the smaller monitor has the problems!
litemotiv wrote:try using xf86-video-ati instead of radeonhd. i tried to get xrandr working for over a week having exactly the same problem, ultimately switched drivers and had everything set up in ~10 minutes.
Changed to ati instead of the radeonhd drivers still gives the same error!
Eratosthenes wrote:
I think you need to set a valid virtual size in your xorg. I think the one you have commented out is too large.
Mine is:
Subsection "Display"
Virtual 3200 1200
EndSubsection
Changed see new xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
EndSection
Section "Files"
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 "dri2"
# Load "extmod"
# Load "dri"
# Load "record"
EndSection
Section "Monitor"
Identifier "AL1916W"
VendorName "Acer"
ModelName "AL1916W"
EndSection
Section "Monitor"
Identifier "AL2016W"
VendorName "Acer"
ModelName "AL2016W"
Option "RightOf" "AL1926W"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "AccelMethod" # [<str>]
#Option "offscreensize" # [<str>]
#Option "SWcursor" # [<bool>]
#Option "ignoreconnector" # [<str>]
#Option "forcereduced" # [<bool>]
#Option "forcedpi" # 
#Option "useconfiguredmonitor" # [<bool>]
#Option "HPD" # <str>
#Option "NoRandr" # [<bool>]
#Option "RROutputOrder" # [<str>]
#Option "DRI" # [<bool>]
#Option "TVMode" # [<str>]
#Option "ScaleType" # [<str>]
#Option "UseAtomBIOS" # [<bool>]
#Option "AtomBIOS" # [<str>]
#Option "UnverifiedFeatures" # [<bool>]
#Option "Audio" # [<bool>]
#Option "AudioStreamSilence" # [<str>]
#Option "HDMI" # [<str>]
#Option "COHERENT" # [<str>]
#Option "ForceLowPowerMode" # [<bool>]
#Option "LowPowerModeEngineClock" # 
Option "monitor-DVI-1" "AL1916W"
Option "monitor-DVI-0" "AL2016W"
Identifier "Card0"
Driver "ati"
VendorName "ATI Technologies Inc"
BoardName "RV710 [Radeon HD 4350]"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "AL1916W"
SubSection "Display"
Depth 24
Virtual 3120 1050
EndSubSection
EndSection
Andrwe wrote:BTW could you please sent teh log, maybe there is something you may have missed.
Because of the switch to ati from radeon the log is different now... but here it is: http://pastebin.com/m77d0ea0b
This one at least shows that my seccond monitor is connected which failed in radeonhd!
Thanks for all the help,
Arjan Gelderblom
Edit: changed topic title to have it apply better to it's content
Last edited by Bloged (2009-12-14 10:02:47)

Multi monitor issues with resolution(?)

At a customer I have got a really strange and annoying problem. The customer has got a Hyper-V VM with 2012 R2 Server as a RDS server aka Terminal Server.
One user has got issues with his multi monitor setup. The connection settings seems to be OK. It is set to full screen and the checkbox for the multi monitor configuration is enabled. Theoretically this works because the user sees a correct setup with one
primary display and one secondary display. The settings itself are correct.
1. Primary display: 1680*1050
2. Secondary display: 27" 1920*1080
The display settings on the client are nearly the same except that the numbers of the two monitors are different (those numbers you get when you click identify at the resolution change window). On the Windows 7 client the primary display
number 2 and the 27" has got the number 1. On the Terminal Server the primary display has got the number 1 and the 27" display has got the number 2. But the corresponding resolution at the display number is correct.
Now the problem. Everything seems fine, the desktop is expended. But when the user is "touching" the top or bottom edge of the screen the display is scrolling (in full screen) - like in a 3D game scrolling over a map. The user told me that
both screens are scrolling equally at the same time. I am not sure but the user told me that if he is going to the bottom the CLIENT task bar appears. Changing the task bar of the client to fixed the user told me that the task bar will always show up. - Strange
that CTRL + ALT + BREAK does not work.
I tried to press CTRL + ALT + BREAK twice, changing the resolution to a fixed value and back to full screen again, changing the primary display to the new 27" monitor, adding smart sizing:i:1 to rdp file and upgrading the Intel HD
4600 laptop graphic drivers (must be downloaded from Lenovo :/). NOTHING helped :(.
But this strange behavior does not exist on the client. Opening two programs (simple notepad e.g.) on each display and maximize them and moving the mouse the screen borders won't show this problem. It only exist on the remote session.
Now the "funny" part. If I connect with Team Viewer to the client the problem disappears as long as I am connected. If I disconnect the problem shows up again.

Hi,
This is most likely a problem with the local machine's graphics driver and monitor configuration. I would suggest trying different things like removing and re-installing the display adapter and its drivers, removing the second monitor/restarting/adding
the second monitor back, adjusting the multi-monitor settings in display properties (changing between extending the desktop to the second monitor and not), undocking/restarting/docking, changing between different modes using Fn key on laptop (if laptop), etc.
The behavior under Team Viewer is likely because the graphics configuration is different when the driver is active.
I wish I could give you more precise instructions on how to resolve the issue. I have seen this behavior (panning desktop, multi-monitor config not exactly right) probably 3 times over the last 5 years, always with a laptop, and I had to "play"
with the settings before it finally went back to normal. The instances I have seen it occur did not involve Remote Desktop specifically.
-TP

Multi-monitor application switching bug in Windows 8.1

In the latest 8.1 update, we got some better features here and there, but using metro apps seem to break multi-monitor setups.
In certain circumstances, the cursor will get "caught" between screen edges, as if the metro app-switcher or charms bar were open.
There's no one way to reproduce this bug, sometimes it happens and sometimes it doesn't, but it usually starts to happen when switching from a metro app to the desktop on the main display via the top-left hotcorner.
This may also happen in many other circumstances involving metro apps or the hotcorners or anything like that. I have not had a problem involving the start screen so far. Getting rid of it (temporarily) is just as finicky as reproducing the issue. I really
have no idea what makes it go away, but switching back and forth between apps using different methods (hotcorners, taskbar, metro minimize/close buttons) seems to get rid of it until you interact with apps again.
I have an AMD r9 280x and 2 1080p displays. I am not using eyefinity. I am running Win 8.1 Pro updated to the latest 8.1 update where there are metro apps on the taskbar.
Needless to say, this is very annoying. If I can't smoothly move my mouse cursor between screens, it really interferes with a dual/multi screen setup. With all the people with multiple screens, I'd expect more people to have run across this problem, so if
you need more information to identify whether this is a software/OS issue, let me know.

In certain circumstances, the cursor will get "caught" between screen edges, as if the metro app-switcher or charms bar were open.
That's not a bug. It's a feature. Unfortunately there is no GUI support for it. And evidently there needs to be a training dialog, in the same way that there is one for Flicks. Search for "Escape Velocity"...
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/issue-with-dual-monitors-after-windows-81-update/30431433-32a7-48e7-853e-f6f391f5fa3e?msgId=2139704d-c2d2-44e6-b466-452769e7fdbf
That's strange. They called it Escape speed? Implying direction doesn't matter? <eg>
Robert Aldwinckle

Financial Analyzer Web access after multi-node setup

hey guys
any idea on the follwoing
Financial Analyzer Web access after multi-node setup
any hints will be helpfull
fadi

Thank you Fadi for this quick idea.
I will try to apply it in our environment.
If we couldn't do it, I think that we have other two options; first options is to reinstall OFA in the Web Server Node where there is a Metalink note states how to move OFA from server to server. The second option is changing the configuration files of OFA to reference the Web Server in the new node.
I will update you with the results.
Regards,
M.Muhtadi

Multiple chrome windows on a multiple monitor, multi-desktop setup?

Dear all,
I'm having this huge headache because I have a dual monitor setup (imac 27" + second 24" monitor) and I have configured 6 different desktops in it (mountain lion here) where each desktop dual monitor scene has a chrome window (with several tabs each) on each monitor. I do this because i work 90% on SaaS's and as such I need this multi-desktop setup with chrome spread all over it.
Problem: Everytime i reboot the system, all those crhome windows get back to desktop 1 (on both monitors) and I have to painstakingly put each chrome window one by one back into each desktop again. Its really a PITA.
Solution: Anyone can tell me a workaround for this or if I am missing some OSX or chorme trick or tweak that will make the system "remember" where each chrome windows was in each desktop + monitor?
Thanks in advance!
//Ricardo

Peggy,
We have been running 3 separate Forte environments on one server (dev,
test, prod) for over a year now. The environments have been at
different Forte release levels at various times. Darrell is right on
target with the UNIX links and separate fortedef.sh files for each
environment. The links will help reduce disk space. Follow his
instructions and you should be good to go. We have each Forte
environment point to its own database instance also. You can set the
environment variables in each fortedef.sh file to do this. If you keep
multiple versions of Forte on a windows client machine, you will have to
switch the Forte.ini file before starting Forte.
As for security and auditing, I not sure what you are looking for here.
Our application has security and auditing but that it.
Keep in mind, that each Forte environment will be competiting for system
resources on the same server. When we have 3 environments running, we
notice a performance hit. Try to use as few resources as you can. For
example, our test and production environments do not require a
repository server, since we test deployed. So do not start these
processes.
Good luck.
Robert Crisafulli
AMISYS
301-838-7540
Long live Forte...

5-screen (multi-monitor) nVidia xorg.conf -- my setup

Hi. I would like to share my xorg.conf, since it took forever to get right.
There isn't a lot of information out there for folks using > 2 monitors, or several graphics cards, or esoteric setups including rotation etc. I hope this will be useful; I wouldn't mind contributing to the wiki if anybody thinks it might be useful.
So first up: hardware. I have
nVidia GeForce GTX 550 Ti connected to a 24" monitor (in the middle)
nVidia GeForce 210 connected to two 19" monitors, rotated into portrait (on either side of the 24")
nVidia GeForce GT 440 connected to two 15" monitors (above the 24")
here is a picture of the monitors, click for a bigger version
Drivers: I'm using the official nVidia drivers, I couldn't get nouveau to work. Since I am using Xinerama, the XRandR extension isn't loaded -- therefore my setup won't be suitable for people whose screen configuration changes dynamically. But I'd prefer not to use Xinerama, and even to use nouveau if possible; if anybody has a similar configuration working with nouveau, please share
Finally, the actual config itself. Here it is on pastebin.
Rotation
The correct way to rotate monitors in xorg.conf is through the metamodes option of the Screen section. On my Screen 2 and 4 (the two 19" monitors), you can see that
{ Rotation = left }
has been added at the end of the metamodes option. Contrary to some other guides floating around, it is not necessary to specify these options:
# Unnecessary
Option "RandRRotate" "on"
Option "Rotate" "right"
I believe these come from an earlier version of Xorg. They don't have any effect when I put them in my xorg.conf, using Xorg 1.12.4 and nVidia 304.43.
Even when I specified rotate in metamodes, my monitors didn't appear to rotate because I had originally written
Option "metamodes" "CRT-1: nvidia-auto-select +0+0 { Rotation = left} "
instead of
Option "metamodes" "DFP-1: nvidia-auto-select +0+0 { Rotation = left} "
This just made rotation fail silently, with no error message. Make sure to specify DFP if you're using a digital output (DVI, HDMI, DP) and CRT only if you're using a VGA output on your graphics board.
Tips
When you're testing out a new Xorg.conf, you can use
startx -- :1
to start a new X server without killing the current one. See if your configuration works, then switch back to your original X server by pressing Cmd-Alt-F7.
You should also keep a log of different configurations you have tried. You can use a version control system like git to track changes to your Xorg.conf; make sure you document every change you have made, and why, it can prove invaluable later on.
Feel free to ask about this setup. I would like to know something: what is the function of the Screen option in the Device section? On the four Device entries for my nVidia 210 and 440 cards, there is an option called Screen; when I take it out, the setup breaks. Why are they there? And why do they not map to the screen numbers in the Screen section? (They are numbered 0, 0, 1, 1 rather than 1, 2, 3, 4)

Thank you for the reply. I read the wiki page, but unfortunately I am still struggling with my two nvidia gpu, three monitor setup.
The red arrows show the pointer progression through the monitors (moving mouse left to right). When the cursor is on the top monitor, it becomes an X, and the screen is black.
Here is the matching xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 331.67 (buildmeister@swio-display-x86-rhel47-08) Fri Apr 4 12:26:05 PDT 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
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 "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Acer G236HL"
HorizSync 30.0 - 80.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor1"
VendorName "Unknown"
ModelName "Acer X223W"
HorizSync 31.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 9600 GT"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 610"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "CRT-1"
Option "metamodes" "VGA-0: nvidia-auto-select +0+0, DVI-I-1: nvidia-auto-select +1920+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "CRT-1"
Option "metamodes" "nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Based on this post on archlinux, I took a crack at matching the xorg.conf pattern above (monitor/device/screen sections) with my own. I took it as a victory that it actually didn't error (many xorg.conf experiments have in the last couple of days have). Here is my new xorg.conf with 3 screens/3 monitors/3 devices:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 331.67 (buildmeister@swio-display-x86-rhel47-08) Fri Apr 4 12:26:16 PDT 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" RightOf "Screen1"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "1"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
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 "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "leftAcer"
VendorName "Unknown"
ModelName "Acer G236HL"
HorizSync 30.0 - 80.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "rightAcer"
VendorName "Unknown"
ModelName "Acer G236HL"
HorizSync 30.0 - 80.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "topAcer"
VendorName "Unknown"
ModelName "Acer X223W"
HorizSync 31.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "geforce-9600-gt-0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 9600 GT"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "geforce-9600-gt-1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 9600 GT"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Device"
Identifier "geforce-gt-610"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 610"
BusID "PCI:2:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "geforce-9600-gt-0"
Monitor "leftAcer"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-0"
Option "MetaModes" "DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "geforce-9600-gt-1"
Monitor "rightAcer"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "DFP-1"
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "MetaModes" "DFP-1: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "geforce-gt-610"
Monitor "topAcer"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-0"
Option "MetaModes" "DFP-0: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
This what appears with the new xorg.conf:
"leftAcer" and "rightAcer" appear, but nothing appears on "topAcer" (it appears not to be getting a signal from the gpu). I can move the mouse pointer between "leftAcer" and "rightAcer".
Any help or advice would be greatly appreciated. Here are a few details about the hardware setup:
GeForce 9600 GT is in the PCI:1 slot. It's DVI out is going to "acerLeft", it's VGA out is going to "acerRight".
GeForce GT 610 is in PCI:2 slot. It's VGA out is going to "acerTop".
thanks!

Any 3rd party utilities that fix full screen mode for multi-monitor users?

I am a multi-monitor user. As multi-monitor users know, full screen mode is basically useless since if you try to go full screen on one monitor, it causes the other monitor to go blank and become unusable (at least with most programs). Are there any 3rd party utitilities or fixes for this?
Thanks

Spaces, which is what this functionality stems from, was limited in that it used your entire setup and switched all of the screens over; space to space. I never used spaces because I always had multiple monitors and I was always working with multiple apps simultaneously that I wanted to be able to reference while working on the others.
Now they call Spaces, "mission control" and changed the appearance of it, but the functionality remained the same, each workstation comprised all of your monitors, and would switch over all of them when switching to a new "Desktop".
Fullscreen apps wrongly assumes that it can take the functionality of the afformentioned MS/Spaces and use it for one app, negating the whole idea of why someone would have multiple screens (real estate to work with other applications).
If they stop considering multiple monitors as one Workspace, they can then make it so they are asynchronous "tablets" instead of one conjoined entity.
So, you say people have been asking about this for 2 years, I've been asking for this for 5!
The issue here is, the only answer is to not use it. Making Mission Control and Fullscreen apps completely ignored by people like us, where I could be using both functions to glide around my work station and three monitors, mixing and matching which apps I want to be viewed on each separate monitor, to perform one single task; together.
It would actually reward people who wanted to utilize Thunderbolt technology and have more then one monitor.
There is no telling why apple chose to push out something that would only support the casual user, with one display, but the only direct way to let apple know that we feel limited by the OS is to send feedback. Even though it seems that we are powerless in this situation, I hope that they do consider how to make this function better.
</rant>

Accessibility zoom unusable on multi-monitor setup

Similar Messages

Maybe you are looking for