pssshutdown options

In alt.comp.os.windows-10, on Sat, 17 Feb 2018 19:12:26 -0500, Paul
wrote:

micky wrote:
In alt.comp.os.windows-10, on Sat, 17 Feb 2018 16:20:40 -0500, micky
wrote:

https://www.howtogeek.com/119028/how...automatically/
I had as my Action c:\bat\PrintFile but this page seems to make
clear that I should have cmd.exe
with the argument C:\Bat\PrintFile.bat

Right?

I"m narrowing in on one of the 2 main problems using the Task Scheduler
in windows10.

The url above shows for the program cmd.exe
and optional arguments. He uses /c "exit" .

In the Scheduler I has as the argument C:\Bat\PrintFile.bat
and what happened is the cmd window opened but it didn't do anything
and it didn't thave anyhting to the right of c:\windowss\system32

Then I added /K and that didn't change things.

So I looked up how to pass an argument to cmd and it seems to say that
this is the right way to do it.

For example https://ss64.com/nt/cmd.html

How can I fix this?

Their example here didn't even use cmd.exe.

http://www.thewindowsclub.com/how-to...ally-windows-7

Paul

Last night I made a point to turn off the computer 10 minutes before a
task was scheduled to start, to see if it wold wake the computer up.

It didn't. In fact even after I started the computer myself, the task,
which still should have been running if it had started, didn't start --
that's some other setting in the Scheduler, I guess.

So today I looked in the BIOS -- Didn't you mention the BIOS? -- and
found Low Power something, and it was ON. And the text said that if it
was On the computer could not be wakened from Off or Hibernate. So I
turned it OFF, and I'll test again soon. The default was OFF and I
don't know if I changed it or the second hand store I bought it from
changed it, or the previous owner. Probably not me. I think it said
in ON/Lower Power mode, the NIC wasn't running. Network Interface
Controller.

The next setting, Remote WAkeup, or something similar, was about remote
wakeup, but its text also referred to Low Power and it said that switch
had to off for what one might call local wakeup.

This is a Dell computer, and I forget who wrote the BIOS, but the exact
words might be different in another brand of computer and certainly with
a BIOS written by someone else.

micky wrote:
In alt.comp.os.windows-10, on Sat, 17 Feb 2018 19:12:26 -0500, Paul
wrote:

micky wrote:
In alt.comp.os.windows-10, on Sat, 17 Feb 2018 16:20:40 -0500, micky
wrote:

https://www.howtogeek.com/119028/how...automatically/
I had as my Action c:\bat\PrintFile but this page seems to make
clear that I should have cmd.exe
with the argument C:\Bat\PrintFile.bat

Right?
I"m narrowing in on one of the 2 main problems using the Task Scheduler
in windows10.

The url above shows for the program cmd.exe
and optional arguments. He uses /c "exit" .

In the Scheduler I has as the argument C:\Bat\PrintFile.bat
and what happened is the cmd window opened but it didn't do anything
and it didn't thave anyhting to the right of c:\windowss\system32

Then I added /K and that didn't change things.

So I looked up how to pass an argument to cmd and it seems to say that
this is the right way to do it.

For example https://ss64.com/nt/cmd.html

How can I fix this?
Their example here didn't even use cmd.exe.

http://www.thewindowsclub.com/how-to...ally-windows-7

Paul

Last night I made a point to turn off the computer 10 minutes before a
task was scheduled to start, to see if it wold wake the computer up.

It didn't. In fact even after I started the computer myself, the task,
which still should have been running if it had started, didn't start --
that's some other setting in the Scheduler, I guess.

So today I looked in the BIOS -- Didn't you mention the BIOS? -- and
found Low Power something, and it was ON. And the text said that if it
was On the computer could not be wakened from Off or Hibernate. So I
turned it OFF, and I'll test again soon. The default was OFF and I
don't know if I changed it or the second hand store I bought it from
changed it, or the previous owner. Probably not me. I think it said
in ON/Lower Power mode, the NIC wasn't running. Network Interface
Controller.

The next setting, Remote WAkeup, or something similar, was about remote
wakeup, but its text also referred to Low Power and it said that switch
had to off for what one might call local wakeup.

This is a Dell computer, and I forget who wrote the BIOS, but the exact
words might be different in another brand of computer and certainly with
a BIOS written by someone else.

I think that's ErP. There is more than one acronym for this, and
I typically look for the word "Ready" in the motherboard manual
to find it, as I can never be sure about the TLA used. This is
from my newest machine.

ErP Ready [Disabled]

This item allows user to switch off some power at S5 to get the
system ready for ErP requirement. When set to Enabled, all other
PME options will be switched off.

Configuration options: [Disabled] [Enabled]

PME is basically "anything that wakes the computer". Like Wake
On LAN, whether it's Wake On LAN on a PCI card or a PCI Express card.
PME is also used by the USB control block, for when a USB device
that still has power, sends an event to the motherboard.

The intention as described there, is to reduce power wastage below
1 watt or so, when the computer is in S5 "Soft Off". The hibernate
state is S4, which is only slightly different. Even in "Soft Off"
state, the front Power button should always work. It works as
long as the rear switch on the supply is on (making +5VSB full time).

So for ErP, the machine may be making +5VSB, but the motherboard
has turned off the NIC chip power, and the USB port power, to save
on wastage. I think I actually measured 1 watt dissipation here
once just in passing, so the real power component can be pretty
low. The power supply, even ones with Active Power Factor Correction,
they don't necessarily do PFC when the machine is sleeping, so that
1 watt of thermal wastage, doesn't show the 6 or 7 watts of
reactive power sloshing between the computer and the power
company. You're only billed for the real power (the 1 watt).

The computer still isn't necessarily a "perfect citizen",
but getting down to the 1 watt level for a vampire situation
is pretty good in my book. Lots of your wall warts aren't
necessarily that good. Even your old transformer based warts
are warm to the touch, and right away that tells you there's
more than 1 watt of eddy current waste.

By disabling that setting, the computer is more likely to wake up :-)

Only if some clever person tied a waking event into the Power
Button circuit, might you convince it to do otherwise. If it is
turning off PME for that one, lots of automation is disabled.

Paul

In alt.comp.os.windows-10, on Mon, 19 Feb 2018 13:03:09 -0500, Paul
wrote:


So for ErP, the machine may be making +5VSB, but the motherboard
has turned off the NIC chip power, and the USB port power, to save
on wastage

This makes me think. Now that I turned that Power Saving off so it's
always slightly awake, will that mean that the USB port has power when
it's shut down?

I can check next time I turn the computer off, but that wont' be for a a
day or more, and by then I'll forget. And this question will help other
people think about the possibilty.

In alt.comp.os.windows-10, on Sat, 17 Feb 2018 17:48:13 -0500, Paul
wrote:
.....



I tried to put more than one task in an Action in the Win10 Scheduler
and I get the message box "Multiple actions in a single task are
supported only on Windows Vista or later. To use multiple actions, you
must upgrade this task to a Windows Vista task or later."

What does this mean? It's windows 10.

What makes a task a "Vista task or later"? (googling on this question
got no hits.)


The first step is RadioMaximus, 64 bit, which runs fine under win10,
though I'll admit I've only tested once but have not yet gotten it to
start automatically from the scheduler, but I've never gotten a message
about Vista or later.

The second step that I'm trying to add when I get this message is as
simple as can be. It's called C:\bat\shutdown.bat and it's only this:

echo on
Time /T
Pause [for testing only, but the words in brackets are not there]
rem #### C:\Downloads\pstools\psshutdown.exe -t 18000


In what way are these 4 lines earlier than Vista? Or not a Vista task
or later?

Or what does the message mean?