UPS Warning Message

[Guest]

I have a UPS connected via COM2 to my PC. The UPS signals a power failure and
battery low. Also it can be shutdown via the PC. If there is a power failure
a screen message pos up and informs the user. This works well under XP with
SP1. Either XP Pro or XP Embedded.

But if I switch to SP2 the message is gone. The event manager shows the
power failure. But for the user the screen message is necessary. Is there any
known bug in SP2 that prevents the screen message to pop up? How can I fix
that?

 

[Brad Combs]

Hello,

I believe that the UPS service uses the Messenger service to broadcast a
power event. This is disabled by default in XP SP2 (alos XP Embedded SP2).
You can enable the Messenger service through the Services control panel
(services.msc) or using the SC.exe command line utility.

Of course since this is XP Embedded you also need to actually have the
Messenger component in your image. ;-)

The component is named "Messenger Service (Net Send)".

HTH,
Brad

 

[Guest]

I tried it with the messenger service enabled. But there is no warning
message. The event manager shows the event of power failure correct.
Therefore the UPS works fine. But no warning messages on screen. There must
be other services needed additionally to the messenger service. I have tried
it and enabled all services but it does not work. There must be another trick
to solve this. What has MS done in XP2?

 

[Brad Combs]

Hello,

Take a look at these registry entries on your device:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UPS\Config]
"Upgrade"=dword:00000000
"Vendor"="American Power Conversion"
"Model"="Basic signaling to any APC UPS"
"ServiceProviderDLL"=""
"NotifyEnable"=dword:00000001
"ShutdownOnBatteryEnable"=dword:00000001
"ShutdownOnBatteryWait"=dword:00000004
"RunTaskEnable"=dword:00000000
"TaskName"="UPS System Shutdown Program"
"TurnUPSOffEnable"=dword:00000001
"CustomOptions"=dword:0000007f
"CriticalPowerAction"=dword:00000000
"TurnUPSOffWait"=dword:000000b4


Specifically were looking at the "NotifyEnable" value. Possibly it's set to
0?

HTH,
Brad