This was originally posted by Isegrimm DaGrimm on 18 Nov., 2004
""Although this is a rather old topic, I thought it might be handy to
post the solution I found for this problem.
- SALDM.EXE is a service used to control an LCD or LED at the front of
a Windows-based storageserver.
- It's part of the Microsoft Server Appliance Kit.
- In Services it's called "Local Display Manager".
- When running, it frequently uses up 100% of your CPU. One CPU in the
case of a multi-processor system.
- When you try to stop it, or it tries to stop itself at the absence of
an LCD or LED, it hangs.
- You can disable it however, so the next time your server is booted
the service won't start.
- When rebooting the server is an issue (as it was in my case) you can
kill the running/hanging process (saldm.exe) using pskill (part of
pstools, which can be found at
www.sysinternals.com) or any other
utility that is able to forcibly kill a process.
Regards,
Isegrimm ""
Posted by Keith on 4-15-2005
""saldm.exe is the Server Appliance Local Display Manager, and is a
service
that is part of the Microsoft Server Appliance SDK. It is there to allow
server appliances to display information on small local displays (e.g. an
LCD on the front panel).
Server Appliances that do not have these displays seem to still have this
service installed and running. The service tries to talk to the
non-existant
display and goes a bit wrong. It is ok to disable the service "Local
Display
manager" and reboot (you cannot stop the service otherwise). This prevents
the problem occuring in the future.""
Hope these help,
