Although not a KVM issue I wanted to add my problem (which i believe is related) to the growing list:
I have dual displays running off an ATI HD4200, one's an epson tw-3000 projector, the other a 1080p acer monitor. Often I like to just have the monitor on if i'm listening to music and will then turn the projector on later if i'm going to watch something.
I never had a problem with this with XP but noticed when I "upgraded" to win 7 that often upon turning the projector on it would not display, and no matter how many times i'd try to force detection I would need to restart the computer to get windows to detect
the projector.
For a few reasons I reinstalled 7 the other day and made sure the only monitor hooked up was the projector. To cut a long story short if the computer boots with the projector on then it'll display, i can turn the projector on and off and it'll still work,
the problem arises if I start the computer up without the projector on, it won't get detected and this is frustrating. Since I've plugged the acer LCD back in, the acer LCD does not behave like this, it can be off when the computer boots but i can switch it
on later and it works.
The acer is running off VGA and the Projector DVI.
I've tried xenubite's fix but it doesn't work. I've also disabled TMM and ATI's servcie monitor. In looking closer at the EDID stuff in the registry i've noticed some things though: Firstly with just the projector hooked up there was no "default monitor"
listed, so i guess windows recognises the EDID just fine. Strangely the epson registry entry actually has 2 EDID entries - not sure why that is. When i hooked the ACER up it reads the edid fine too but then also adds a default monitor entry for the acer, in
addition to the EDID entry, perhaps this explains why the acer always works fine but not the epson - of course win 7 doesn't let you add further default monitors. Not sure how related it all is but I really wish this could get solved - at present i simply
have to leave the computer running (i can't put it into sleep for other reasons) so not very environmentally friendly on microsofts part!
Sean