KVM switch + Windows 7 creates monitor switching nightmare

18 000 views, and still nothing

4 Port Starview DVI/VGA USB KVM Switch with audio when connected to a DVI monitor (HP 2709m) with DVI cables to the Windows 7 machine will work as intended. However, when a second computer is attached using VGA cables, the machines are never recognized.

I am a volunteer trouble shooter for our computer club, and I bought this device to allow for my Win7 machine and WinXP machine to remain connected and then when other computers which come in to be worked on, Win7, Win Vista or Win XP, I can easily connect the third and/or fourth computers. Each could be running virus scans, Disk Defragmenter, etc., while other work could be accomplished.

The time that it has taken to work on this issue has meant that I can no longer return the switch and the expensive cabling.

My old Airlink 101 2-port VGA switch works well for the monitor when I simply shut down the Win 7 machine which connected to the monitor and connect a spare keyboard and mouse to the Airlink switch. But this is far from ideal.

I have the same problem, but without the switch. Juan a 40'' LCD Toshiba connected to a ASUS EeeBox with an Nvidia ION.

When I turn off the monitor and/or the computer, I have like a 40% chance that the resolution changes from 1920x1080 to some other (1280 x 768 or 1024 x 768).

I NEED A SOLUTION!! PLEASE HELP

If I were Trendnet, and all the other KVM Manufacturers, I would be lobbying Microsoft to fix this (and definetely checking with their lawyers)..

If I were Trendnet, I wouldn't be wasting time trying to lobby Microsoft, I'd be putting my energy into developing a KVM switch that works.  You can't patent an idea, you can only patent the means in which you execute that idea (how the idea is brought to fruition).  Relating to KVM switches it's like this - If Avocent invented and patented the On Screen Display menu on their switches, that doesn't mean other companies can't develop an On Screen Display menu for their switches - it only means that other companies have to figure out their own way to do it, they can't just copy Avocent's engineering.

Joseph,

When I wrote "This USB DDM patented technology is the only solution for sharing among Windows 7 systems"  months ago,  I did mean that it was the over all the best switch technology I tested for sharing USB HID console devices among Windows 7 systems.  It's only my personal experience.  Of cause, technology itself will be advanced all the time, any one can release more advanced one to the existing one.   And the most important for me is that I should my right and freedom to express my opinions no matter what if someone just don't agree with me or not. 

It's not true we can create a monopolizing case here, but because we did truly spend thousands of our engineering time to test those issues bother Windows 7 users.  And we're just a small group of engineers who try to help and contribute good results.  We're simply too small and don't have the power to manipulate the market. 

The issue we're all talking about here is just the video HPD (Hot Plug Detect) issue.  To solve just the video HPD issue of Windows 7, it is very easy find a way to feed DDC/EDID communication to Windows 7 all the time.   Any KVM switches (not necessary be the ConnectPRO's UR+ serial) can solve this issue, if they find a way to feed the info to all connected Windows 7 systems.  Some KVM makers/OEM makers (as you listed) already having some models provide the solution.   It also can be solved by putting a so called "EDID ghost" "DDC/EDID emulator" between Windows 7 system and KVM switch (if the KVM switch can not provide the EDID communication feeding to all the connected Windows 7 systems). 

However, those EDID things just solve one of many HPD issues from Windows 7.   Because there are so many USB devices we connected to our systems now, the next big problem for HPD issue should be the USB HPD.   70~80% of most USB devices we plug-in to our systems are so called "USB HID" class devices (Human Interface Devices - such as keyboard, mouse, drawing tablet and touch screen ...etc.).  

There are three types of USB KVM switch which use different technology base to deal with the USB HPD. 

1. USB hub type KVM switch  (also called "Enumerated USB switch") - more than 90% of USB KVM switches currently in the market are based on this core.

Switching among connected systems is just like physically plug and unplug USB cables to/from the connected system. The result is each time you switch to different system, the target system have to do "USB enumeration" totally for each USB devices you want to share.  This earliest solution try to switch USB devices applied a relatively "hands off" approach.  It's both a good and bad thing.  The advantage is 100% transparent.  The disadvantage is that it takes time to do finish the enumeration procedures each time you "switch" and no hot-key commands can be issued. 

2. Emulated-type USB switches - just like their PS/2 ancestor, it emulates itself as a simple keyboard and/or mouse device to connected systems.  As results, just basic keyboard and mouse functions can be repackage and present to connected systems.  The good thing is that the enumeration process for the keyboard and/or mouse takes place only once.  
3. DDM (Dynamic Device Mapping) based USB switches -  it dynamically learns(copy) and represents the shared USB HID devices to each connected systems and keep alive of the communication among them.   Once the mapping is done, it eliminates the enumeration procedure when switch among connected systems.  And at the same time, it also preserve all the functions and characteristics of the shared USB HID devices.  This not only helps to make the switching/reconnecting faster, it also increases switching reliability. 

We can take other time to talk about how to solve other types of HPD (such as Audio devices...etc.).

Life is too short to mislead others.  The truth will be proofed.   We hope every one having a peace of mind in computing.