Sorry. I can't help editing myself. Especially when the morning coffee
finally wakes up my internal editor.
Anyway, I believe that if you alreay have WOSB.exe running, then you
MUST add the "/ami" arg to the schedule wakeup command. I.E.
Code:
--------------------
Schedule Wakeup Command: c:\windows\system32\cmd.exe /C start /B
P:\SYSTEM~2\POWERT~1\WAKEUP~1\wosb.exe /ami /run /systray /screenon dt=%f tm=%t
--------------------
Without the /ami arg, the 2nd instance of WOSB.exe never ran. That's
why your server didn't wakeup at the 3 minutes before alarm time. It
was your other instance of WOSB.exe that performed the waking up.
>From the WOSB user manual:
-/ami - normally WakeupOnStandby does not allow more than one instance
of itself to run at the same time. If specified this option will allow
multiple instances of WakeupOnStandby to run at the same time, i.e.
will make it run in a Multi-Session Mode (see above for more info).
Maximum allowed number of simultaneously running instances is 15. (Use
this option to link one job in WakeupOnStandby to another, or to apply
multiple scheduling);-
--
gharris999
------------------------------------------------------------------------
gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115
View this thread: http://forums.slimdevices.com/showthread.php?t=62029
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
