I have a Next Unit of Computing, or NUC.
I purchased a monitor for it, so my SightedMinions could see what it was doing in order to assist me.
A few weeks ago I disconnected the monitor from the mains because it really doesn't need to be plugged in unless I need to turn it on.
The NUC didn't care.
Two weeks ago I completely disconnected the video cable from the monitor, moved the monitor to my dresser, so people could get to the bedroom window & do some work there.
The NUC didn't seem to have any problem with this, so I didn't put the monitor back (nor plug it back in) after they were done.
Last week it started exhibiting issues every time I turned it on, with Jaws claiming the Video Intercept Driver hadn't loaded properly.
I'd reboot, it would load properly, and everything was fine.
I couldn't figure out why it was having difficulty with the driver, but since it fixed itself after a reboot, I didn't really care.
It did it again just a few minutes ago when I rebooted, and I got to wondering.
Move the monitor back, plug in the video cable (but not the power cable), and turn the NUC back on.
It started without a hitch.
Hmmmm...
Shut down, unplug the video cable, reboot.
Jaws claims the video intercept driver hadn't loaded properly.
Shut down, plug the monitor's video cable back in, & reboot.
No error.
Shut down, unplug, reboot, get error.
Shut down, plug it back in, reboot, no error...
The monitor isn't plugged into the mains, it has no power, thus any signal the NUC generates to query the device goes into a black hole.
But for some reason, if the video cable is plugged in, even to a device without power, Jaws thinks that's just fine & boots without a problem?
*FacePalmSigh*
Fine, I'll leave the monitor plugged in to the NUC, unplugged from the mains, and ignore it until/unless it's needed.
But seriously, someone cue the TZ theme.
=-)p
|
