- October 13, 2008
- 97
- 5
- Home Country
- Netherlands
The same as running devcon rescan. This thread has more details about it.
If it works. Then put the bat cmd in ur startup folder.
Usually this works in those cases.
My setup is like this:
Desktop PC with a main display and a secondary display which is the LCD TV, connected through an Onkyo AVR by (of course) HDMI.
I always had a hard time getting it all to function properly. Seems like turning off the Onkyo AVR makes the GPU think the HDMI-cable is completely disconnected. Which results in all windows incl MePo being moved to the primary display.
I had high hopes for the PIN19 trick. After getting it right I thought I nailed it, but noooo . The GPU does not detect if the AVR is turned off, which is good, but now I have to make sure the AVR is in the same on/off state as it was before my system entered standby mode. If not, Windows will somehow still detect it has turned off and all kind of problems arise. Most of the times MePo will force close as well. To get it fixed I first need to open Catalyst Control Center which will force detect connected devices and then restart MePo (major WAF killer!).
Now my question to you gibman, which of the following solutions do you think will work for me? Since you seem to have tried them all and have a similar setup, I think you would know
1. The devcon trick. I guess this works the same way as forced detection by CCC. So I guess it will only work if the AVR is turned on first? Still not ideal… System might wake unattended now and then.
2. Dr. HDMI or HDMI Detective. Should fix all issues, but should be the last resort.
3. I’ve read on some AV forums that a cheap but powered HDMI splitter could also keep the AVR signal alive? Have you (or anyone else) tried this?
4. Your soldering trick. Seems golden! But do you think it would work in my situation?
Thank you in advance!