Hello again, There was a recent change to the beta that requires the Telephony (TapiSrv) be running before Salive will start. If you startup Salive manually this is usually not an issue because Telephony will be running by the time you login.
On bootup with Salive setup as an autostart service, Salive wants to run before the Telephony service has started. This causes Salive to fail to start. I've gotten around this by manually editing the registry and adding the Telephony (TapiSrv) service as a dependency to the Salive service. (details here: http://support.microsoft.com/kb/193888 ) Perhaps this should be added the Salive install? Trevor MacDougall To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
