mvordeme;620383 Wrote: > Thanks a lot. It just went from nothing works at all to perfect. What > about the srvrpowerctrl setwakealarm CLI command? Is that what sets the > wake timer in case there is an alarm? Could it be that a wake timer is > also set if there aren't any alarms, or is that the spurious bug you > fixed? > > Those SCPowerTool.exe instances seem to interfere with smooth > operations. I upgraded my SBS to 7.5.4 (because it kept up- and > downgrading my SBR software) and witnessed how the SBS service kept > crashing until I stopped all SCPowerTool processes. It was a bug that was causing SCPowerTool to be executed twice for each alarm. You can go ahead and add the setwakealarm cli command back in now and just a single instance of SCPowerTool will get started. Also, take a look at the SysInternals PSKill.exe utility. You might want to execute that as part of a custom on-wakeup command and have it kill off any ScPowerTool instances that are still hanging around. I should really update SCPowerTool so that only a single instance can run. Interprocess communications isn't that easy to program in Windows though, so I've been avoiding it.
-- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=48521 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
