How to impede W10 from hibernating automatically?

Char Jackson replied ( to me ):
1. Move the computer out of the bedroom. or
2. Move the bed out of the computer room.

Now you're just being silly.

Laying on your back is the only way to mouse.

Char Jackson replied ( to me ):
Paul was suggesting that you use a VGA card to fake out the computer.
He didn't suggest that you actually run the monitor from VGA.

I might end up dropping another grand on another monitor.

Maybe next year; the boom is busting, I think.

I wonder how this will affect the upcoming elections.

I might end up on the streets, with very little privacy.

Carlos E.R. wrote:
15 seconds after the monitor is put to sleep
{ possibly from a RANDOM awakening },
as I'm starting to relax, "No Signal" flashes up,
annoying the crap out of me.

I don't have that issue.
But that is a bug between the operating system and the monitor.
They don't usually document bugs, you know.

It's a DisplayPort "feature", I think.
I wonder if DisplayPort 1.4 or HDMI v2.0 is different.

I wrote:
15 seconds after the monitor is put to sleep
{ possibly from a RANDOM awakening },
as I'm starting to relax, "No Signal" flashes up,
annoying the crap out of me.

Switching to a HDMI v2.0 cable should
solve my "No Signal" problem, I think.

I bought a 6' cable from Walmart for 12$, after shipping+taxes;
Amazon wanted 20$, after shipping+taxes.

https://www.walmart.com/ip/2-0-HDMI-...-6ft/329154783

On Sun, 14 Jul 2019 17:07:24 -0700 (Seattle), Jeff-Relf.Me @. wrote:

Char Jackson replied ( to me ):
1. Move the computer out of the bedroom. or
2. Move the bed out of the computer room.

Now you're just being silly.

Laying on your back is the only way to mouse.

Hmmm, please tell me more. Maybe I'm missing out on a good thing. I
don't have the sensitive eyes thing, but I'm not opposed to mousing
while laying in bed, if it's really the way to go.

On Sun, 14 Jul 2019 18:33:45 -0700 (Seattle), Jeff-Relf.Me @. wrote:

I bought a 6' cable from Walmart for 12$, after shipping+taxes;
Amazon wanted 20$, after shipping+taxes.

I presume, bought online, delivered to your door, where someone else
brought the item inside. To go outside, you'd probably have to wear a
welder's mask, right? Sensitive eyes wouldn't be much fun, except in
very limited circumstances.

Char Jackson replied ( to me ):
Laying on your back is the only way to mouse.

Hmmm, please tell me more.

Maybe I'm missing out on a good thing.
I'm not opposed to mousing while laying in bed.

My mouse-arm rests on my "twin" bed, so my hand hangs over,
onto the side-table, where this mouse (+pad) is:

http://Jeff-Relf.Me/MouseKeyboardLayout.PNG

Note: There's no physical keyboard.
My virtual keyboard is extremely custom;
it might be too hard for you to create.

My 40' 4k monitor swings on a long+high monitor arm;
it's super-difficult to find a proper monitor arm, one that
can handle a 25 lb, 40' monitor... you may have to improvise.
I use the Amazon Basics monitor arm, along with an extension.

Also, my table had to be reinforced with plywood and
attached to it is a 25 lb counter-weight, using glue and clamps.

A large monitor is good for viewing (bright) videos, farther away.

When viewing text, up close, smaller monitors are better;
otherwise, the edges are too far from the center.
I'm not sure what the best compromise is.

DisplayPort is buggy ( sleep mode is effectively
the same thing as pulling the cord ); use HDMI v2 instead.

Char Jackson replied ( to me ):
I bought a 6' cable from Walmart for 12$ total;
Amazon wanted 20$, after shipping+taxes.

Bought online, I presume.

Yes, because I don't have a car, and I hate riding buses,
and Walmart is too far away from (deep) Seattle.

To go outside, you'd probably have
to wear a welder's mask, right ?

I just squint a lot, when walking into the sun,
and I put my hand over my eyes.

Sensitive eyes wouldn't be much fun,
except in very limited circumstances.

It's great right now, in my dark room.
I look+act like a prototypical hacker/beard.

Jeff-Relf.Me wrote:
Owl,

No one knows how to stop the mouse
from accidentally waking the monitor;
apparently, it can't be done.

I don't know if this has been mentioned in the umpteen responses, but
AFAIK, the 'powercfg' command can solve your problem.

Do "powercfg /devicequery wake_armed" in a Command Prompt window. For
subsequent commands, you need to open the Command Prompt windows to 'Run
as administrator'.

powercfg will say something like:

C:\home\frankspowercfg /devicequery wake_armed
Standard PS/2 Keyboard
Synaptics SMBus TouchPad

I.e. it will note some type of keyboard and some kind of pointing
device ('mouse'), in my (laptop) case, a touchpad.

Now do

C:\home\frankspowercfg /devicedisablewake "Synaptics SMBus TouchPad"

where "Synaptics SMBus TouchPad" is replaced by the string for *your*
'mouse'.

Check with:

C:\home\frankspowercfg /devicequery wake_armed
Standard PS/2 Keyboard

From now on, a keypress should wake the computer and in your case the
monitor, but a mouse movement should no longer wake the computer/
monitor.

[...]

Frank replied ( to me ):
No one knows how to stop the mouse
from accidentally waking the monitor;
apparently, it can't be done.

AFAIK, the 'powercfg' command can solve your problem.
" powercfg /devicequery wake_armed "

"wake_armed" returns just: " HID Keyboard Device (001) ";
i.e. hitting the keyboard will wake my computer.

a mouse movement should no longer wake the computer/monitor.

It's become apparent to me that waking the monitor
is not the same thing as waking the computer;
there are settings for the latter, but not the former.

A mouse button toggles my monitor "off/on" (sleep/wake);
when a random bump wakes my monitor, my code turns it off again.

But, with DisplayPort, "sleep" is no different than "unplugged";
so I get blasted by a bright "no signal" message,
right when I'm trying to relax.

Hopefully, switching to a HDMI v2 cable will solve my problem;
I'll know later this week, when it arrives.

My iGPU, the Core-i7-5775c, stops at HDMI v1.4;
so I might have to upgrade my CPU+motherboard.

On Mon, 15 Jul 2019 06:20:17 -0700 (Seattle), Jeff-Relf.Me @. wrote:

Frank replied ( to me ):
No one knows how to stop the mouse
from accidentally waking the monitor;
apparently, it can't be done.

AFAIK, the 'powercfg' command can solve your problem.
" powercfg /devicequery wake_armed "

"wake_armed" returns just: " HID Keyboard Device (001) ";
i.e. hitting the keyboard will wake my computer.

a mouse movement should no longer wake the computer/monitor.

It's become apparent to me that waking the monitor
is not the same thing as waking the computer;
there are settings for the latter, but not the former.

A mouse button toggles my monitor "off/on" (sleep/wake);
when a random bump wakes my monitor, my code turns it off again.

But, with DisplayPort, "sleep" is no different than "unplugged";
so I get blasted by a bright "no signal" message,
right when I'm trying to relax.

Hopefully, switching to a HDMI v2 cable will solve my problem;
I'll know later this week, when it arrives.

My iGPU, the Core-i7-5775c, stops at HDMI v1.4;
so I might have to upgrade my CPU+motherboard.

My motherboard BIOS has settings for standby and while software can
put it in standby, I have to press the power button once to go active,
or I can press the power button to put it in standby (press and hold
switches it off)

Check your BIOS and see if it has choices like that.

On 7/14/19 11:22 AM, Jeff-Relf.Me@. wrote:

[snip]

I don't want to be blinded by an advertisement, first thing,
after waking up, in a pitch black room.

Why are you turning the monitor on in a dark room?

--
"We're here on your account." - a bank in Tyler

On 15/07/2019 01.47, Carlos E.R. wrote:
On 14/07/2019 14.27, Carlos E.R. wrote:
On 13/07/2019 20.41, Paul wrote:
Carlos E.R. wrote:
On 13/07/2019 19.30, Paul wrote:
Carlos E.R. wrote:
On 12/07/2019 20.57, Paul wrote:
Carlos E.R. wrote:

...


I tried this batch script:

echo off
runas /user:Carlos powercfg /hibernate off
pause

...

It finally worked with this line:

runas /user:Minas-Morgul\Carlos "powercfg /hibernate off"

Well, no, it doesn't work. At least, "/hibernate on" doesn't, the
machine did not hibernate for hours, and the entry for hibernate
disappeared from the start menu! I had to issue the command from the
powershell as administrator to reestablish hibernation.

I might live with that, for now... I will investigate other methods with
calm, but at least I have one.

A funny thing happened: the machine came out of hibernation on its own,
at 1:20AM, but of course, it booted to Linux, not Windows (and on
battery; when I found out battery was down to 60% already). I guess
Windows programmed and automatic wakeup, to see for updates, perhaps,
but what would have happened if the laptop was inside a bag? It could
catch fire!

And of course, it is the wrong assumption to think that Windows is the
only system in the machine, and that it will boot first.

Bad, M$, very bad form.


--
Cheers, Carlos.

On 15/07/2019 17.25, default wrote:
On Mon, 15 Jul 2019 06:20:17 -0700 (Seattle), Jeff-Relf.Me @. wrote:

Frank replied ( to me ):
No one knows how to stop the mouse
from accidentally waking the monitor;
apparently, it can't be done.

AFAIK, the 'powercfg' command can solve your problem.
" powercfg /devicequery wake_armed "

"wake_armed" returns just: " HID Keyboard Device (001) ";
i.e. hitting the keyboard will wake my computer.

a mouse movement should no longer wake the computer/monitor.

It's become apparent to me that waking the monitor
is not the same thing as waking the computer;
there are settings for the latter, but not the former.

A mouse button toggles my monitor "off/on" (sleep/wake);
when a random bump wakes my monitor, my code turns it off again.

But, with DisplayPort, "sleep" is no different than "unplugged";
so I get blasted by a bright "no signal" message,
right when I'm trying to relax.

Hopefully, switching to a HDMI v2 cable will solve my problem;
I'll know later this week, when it arrives.

My iGPU, the Core-i7-5775c, stops at HDMI v1.4;
so I might have to upgrade my CPU+motherboard.

My motherboard BIOS has settings for standby and while software can
put it in standby, I have to press the power button once to go active,
or I can press the power button to put it in standby (press and hold
switches it off)

Check your BIOS and see if it has choices like that.

It is not that kind of sleep. It is controlled by the operating system,
because it is running, not by the BIOS.


--
Cheers, Carlos.

On Tue, 16 Jul 2019 11:10:13 +0200, "Carlos E.R."
wrote:

On 15/07/2019 17.25, default wrote:
On Mon, 15 Jul 2019 06:20:17 -0700 (Seattle), Jeff-Relf.Me @. wrote:

Frank replied ( to me ):
No one knows how to stop the mouse
from accidentally waking the monitor;
apparently, it can't be done.

AFAIK, the 'powercfg' command can solve your problem.
" powercfg /devicequery wake_armed "

"wake_armed" returns just: " HID Keyboard Device (001) ";
i.e. hitting the keyboard will wake my computer.

a mouse movement should no longer wake the computer/monitor.

It's become apparent to me that waking the monitor
is not the same thing as waking the computer;
there are settings for the latter, but not the former.

A mouse button toggles my monitor "off/on" (sleep/wake);
when a random bump wakes my monitor, my code turns it off again.

But, with DisplayPort, "sleep" is no different than "unplugged";
so I get blasted by a bright "no signal" message,
right when I'm trying to relax.

Hopefully, switching to a HDMI v2 cable will solve my problem;
I'll know later this week, when it arrives.

My iGPU, the Core-i7-5775c, stops at HDMI v1.4;
so I might have to upgrade my CPU+motherboard.

My motherboard BIOS has settings for standby and while software can
put it in standby, I have to press the power button once to go active,
or I can press the power button to put it in standby (press and hold
switches it off)

Check your BIOS and see if it has choices like that.

It is not that kind of sleep. It is controlled by the operating system,
because it is running, not by the BIOS.

Windows and Linux can both initiate a standby mode from software, but
only the power switch can wake it not the keyboard or mouse. ("wake
on LAN" is a choice, but I've never used it)