KVM switch + Windows 7 creates monitor switching nightmare

I just thought that if all 77 of us hadn't yet lodged support calls that doing so might focus additional attention on the fact that many are affected, and unhappy.

The problem as I see it is that it isn't just a question of new, unplanned expenditure to fix it (which, BTW, I have absolutely NO intention of doing - if it's a question of buying new hardware or returning the software, the software's going back), because it happens with single monitors as well .  It seems to me that only disabling the computer searching for monitors (that it doesn't find) will fix this issue.

Well, you got me there, Higgy. 77 support calls in one day, all refering to the same social.answers thread might get some attention.

Then again, didn't I read MS averaged over 10,000 calls an hour (all languages, all countries)? Maybe I need to troll MSDN to see if there's a thread over there on this, multi-monitor & KVM arrangements are sure to be more common in the development world.

Apologies extended if my previous response seemed dismissive or offensive in any way - that was not my intent. Frustration seeping through perhaps

Then again, didn't I read MS averaged over 10,000 calls an hour (all languages, all countries)? 

Apologies extended if my previous response seemed dismissive or offensive in any way - that was not my intent. Frustration seeping through perhaps

1.  That's what I thought when the guy said they hadn't heard about it (but I kept civil and didn't snap :D).  With however many zillion support people they've got, they wouldn't necessarily know what other calls had been lodged.  Any calls might not have been logged properly in the computer for them to come up (assuming that's how it works).  I would assume that they must have some sort of quality assurance procedures as to what things are fixed, how long it takes, etc., because I got an email saying they were going to close it as fixed (!!!!!)  (I promptly emailed back not to close it.)

2.  No, I didn't take it that way.  I hope my reply to you didn't make you think that I did.  I am equally annoyed and frustrated.  It's hard not to start a tirade every time I post.

I think this is a non-auto-detect issue.  (I do not use a kvm switch. But I do use remote desktop for these computers.)

A couple of weeks ago I installed w7 on a wV computer.

I do not power-on the monitors when the computers are started. (Not all computers are used every-day.)

When I do power-on the monitors I find stupidity:

One system (Clean installation) has the monitors set to default resolution and the shortcuts are moved.

The other system (upgrade) has the monitors reversed, number one on the right, and default resolution, and the shortcuts are moved.

I right-click, click screen resolution, click detect and all becomes as it should: display is moved to the correct monitors and resolutions are restored. But the shortcuts are not placed as there were.

At the very least the monitors should be auto detected when powered-on, and the settings should be restored.

YEA to all the new windows candy, but this issue, and the windows explorer idiocies, are fundamental functions, they should have been fixed immediately.

J

I've now received a reply from technical support and been told that there is no intention of fixing the fault.

I was serarching for the answer as well and i think i got the real solution

 

I am using a software called powerstrip. It let you not only fix the resolution but let you customize the resolution. Give it a shot.

 

 

Good day

 I had already posted about this back in February. It lets you control refresh rates and create custom resolutions... but it didn't fix my original problem (windows resized and icons moved).