Re: TightVNC Shows black screen after Win 10 updates
Mark Foley <[email protected]> Tue, 29 May 2018 09:46:55 -0400
| Newsgroups | gmane.network.tight-vnc.general |
|---|---|
| Organization | Novatec Software Engineering, LLC |
| Message-ID | <[email protected]> |
The DVI emulator is probably a better idea than the KVM switch. It's designed to do exactly what you want. Post your results. I'm curious. Re. BIOS settings, I was thinking of the one to ignore any video errors, but there might not be such a setting and that still might not work. --Mark -----Original Message----- From: Ed Meadows Tom Perkins <[email protected]> To: Mark Foley <[email protected]> Subject: Re: TightVNC Shows black screen after Win 10 updates Date: Mon, 28 May 2018 14:02:47 +0000 Hi Mark, Thanks. I don't have a KVM switch handy and there are no BIOS settings for this. Someone else suggested using an EDID emulator, so I'm going to try this: https://www.amazon.com/1920x1200-DVI-D-Emulator-Dummy-Headless/dp/B01EISICO0/ref=sr_1_10/140-3476651-2228763?ie=UTF8&qid=1527515656&sr=8-10&keywords=DVI-D+emulator There's probably a non-hardware solution/setting somewhere, but for $18, why not? Thanks, Ed On 5/27/2018 7:30 PM, Mark Foley wrote: Maybe the new Win 10 update is "smart" enough to detect no monitor as shut down the video memory. The VNC server maps the actual video memory. I tried something like this on purpose to turn off the real monitor video (not the monitor itself) and still see the screen on the VNC client. No go. Try attaching a KVM switch or seeing if there is a BIOS setting to ignore the monitor. --Mark Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- From: MossyRock <[email protected]><mailto:[email protected]> Date: 5/27/18 8:01 PM (GMT-05:00) To: [email protected]<mailto:[email protected]> Subject: TightVNC Shows black screen after Win 10 updates Hello, Suddenly, after applying the latest Windows 10 updates to a headless machine used for BOINC crunching, I am getting a black screen when I try to remote into it from another machine using TightVNC. I've tried completely uninstalling and re-installing TightVNC server on it so it's at it's most current release. I've also tried fiddling with a lot of its options and with the Win 10 desktop "personalizations" as well (including the resolution) and none of it has any effect. Here's the strange thing - when I attach a real monitor to it, I can remote into it and I can see the desktop just fine. When I remove the real monitor, the remote session goes black. I don't know what's changed and I don't know what else to do. Any ideas? If you need any specifics about my machine or TightVNC's settings, just let me know. Thanks. -- Sent from: http://tightvnc.10971.n7.nabble.com/VNC-Tight-List-f3.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___________________________________________________________ TightVNC mailing list, [email protected]<mailto:[email protected]> To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list -- Det angår också dig när det brinner i grannens vägg. (gammalt svenskt ordspråk) It concerns you, too, when your neighbor's wall is on fire. (old Swedish proverb) Meaning: We're all in this together. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___________________________________________________________ TightVNC mailing list, [email protected] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list