This appears to have done the trick for me.
What did? The DVI pin removal? If so, which pin did you take out? Both of them?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a problem with Windows 7 and my KVM switch (Iogear model# gcs1764) which is makes switching via KVM an absolute nightmare. The iogear KVM does not use drivers nor are any available on their website.
Here's what happens:
I switch from Win 7 (2 monitors) to XP (1 monitor) via KVM. When I switch back to Win 7 (2 monitors) sometimes Win 7 will throw my desktop to the 2nd monitor (1st monitor goes blank) and opening up display settings only shows the 2nd monitor as existing. It's as if the 1st monitor is now unplugged which it isn't. At this point I have to go into display settings, click Detect, and then it re-detects my 1st monitor and "extends" my desktop back out over 2 monitors. All windows have now been thrown to my 1st monitor and i have to rearrange all my work back across 2 monitors. This is why KVM switching in Win 7 makes my work life a living nightmare. This isn't all of it either...
When everything gets thrown to my first monitor, it takes any windows that were maximized and resizes them to about 1/4 my screen size. Due to compatibility issues between Win 7 and SQL Server Management Studio, Management Studio has a redraw bug that doesn't "re-size" the query window correctly. So even though I maximize the app, when I start typing in the query window my text disappears about 1/4 the way across the whole window. The only way to fix this is to save all my work, close the app, and then re-open the app with all my work. So basically every time I switch computers there's about a 1/5 chance I have rinse and repeat everything I just typed above. Fun times.
So are there any future fixes planned for this? I have tried everything and nothing fixes this problem. I have all the latest Nvidia drivers (my card: Nvidia GTS 250).
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This appears to have done the trick for me.
What did? The DVI pin removal? If so, which pin did you take out? Both of them?
UPDATE: thepcguy suggestion of Disabling the AMD/ATI External Events Utility service appears to help but it's not a complete solution.
This appears to have done the trick for me. I had assumed it was something to do with the new ATI card as the 8800GTS it replaced had no such issue with W7 and my cheapo TrendNet KVM.
At one point i thought switching to using the digital to dsub bender had fixed the issue but no luck.
As per your request, and being the right thing to do, I have marked that this needs answered.. .. ..
Originally I read the DVI was Pin #6, then in another post I read pin #6 & #7 (reference links above)
If you look at the Wikipedia pin out you can see that #6=DDC Clock[SCL] #7=DDC Data[SCA]
http://en.wikipedia.org/wiki/Display_Data_Channel (used to transport edid information)
http://www.interfacebus.com/Design_Connector_I2C.html (SCL vs SCA)
I am on the road for the next 2 weeks, so I can't modify any cables to verify which or if it works as desired :(
If anyone else has any cables laying around and wants to try I would like to hear the results.
about a $4 experiment . . .
Best Wishes
Mike
At first I was very skeptical about this solution... but if DDC signaling is really done using a dedicated wire, I might as well try this out and see what is does. I'll order two DVI cables from Monoprice and see what I can do.
Still, I can't believe that I need to physically damage some hardware so that my operating system starts working like it should. I thought I was accustomed to MS messing up by now... but this tops it all. I wonder who's brilliant idea it was to incorporate this new "bug"... [clears throat] ...sorry, feature. Do they keep the same staff on hand just so they can keep messing things that had previously worked fine for years... or do they hire new "bug guys" each time a new OS is about to hit the shelves? After all, it seems like they introduced this at the last minute... almost like they thought their product was a bit too perfect! :+.
As per your request, and being the right thing to do, I have marked that this needs answered.. .. ..
Originally I read the DVI was Pin #6, then in another post I read pin #6 & #7 (reference links above)
If you look at the Wikipedia pin out you can see that #6=DDC Clock[SCL] #7=DDC Data[SCA]
http://en.wikipedia.org/wiki/Display_Data_Channel (used to transport edid information)
http://www.interfacebus.com/Design_Connector_I2C.html (SCL vs SCA)
I am on the road for the next 2 weeks, so I can't modify any cables to verify which or if it works as desired :(
If anyone else has any cables laying around and wants to try I would like to hear the results.
about a $4 experiment . . .
http://www.monoprice.com/products/subdepartment.asp?c_id=102&cp_id=10209
Best Wishes
Mike
I'm hoping that MS is working on this - and that it will be in an upcoming patch or SP-1.
However - I see that there have been 8,046 views, and 173 (now 174) replies to this thread - yet only 52 people have taken the time to mark it as they need an answer.
PLEASE MARK THAT YOU NEED THIS ANSWERED. The more votes that are put towards this - the better the chances that MS will do something about it.
I am also interested in verifying what pin for DVI needs to be removed. I wouldn't mind trying it if it solves the problems...
Joseph W. Leathlean