SloStart Service Greyware SloStart lets you configure services to start after a delay on startup.
Download

SloStart Service Ranking & Summary

SloStart Service Tags

de microsoft word 2003 microsoft spider solitaire microsoft works free microsoft works calendar microsoft works task windows vista full microsoft freecell prn viewer microsoft office 2005 free task scanner u s weather first service

SloStart Service Description

Greyware SloStart lets you configure services to start after a delay on startup. Tame cranky services that only work when started by hand after the rest of the system has finished booting! Greyware SloStart Service lets you pick any services on your machine and configure a delay before the services start. This is often necessary for "cranky" services that just don't seem to work correctly if left on automatic start. Systems administrators are familiar with the routine of setting a service to manual start, rebooting, logging on, and starting the service by hand--all because if left on automatic, the service doesn't work correctly. The Greyware SloStart Service makes this an easy-to-manage task without having to rely on Batch files, AT job schedules or, worst of all, having to remember to log on and start the service after a reboot. SloStart will try to start a service (after the delay you have chosen expires) up to ten times. If you've ever had a service that works fine only after the second or third time you try to start it, you'll understand why this is so helpful. SloStart can write detailed information in the Event Viewer log about what services it is trying to start for you, what the results are, and how long until the next try. In Windows 2000/3 and Windows XP, Microsoft has finally added a service monitor that will (if you configure it) try to restart failed services. But the monitor only checks services that have started properly. Many services, especially on multi-processor and multi-homed servers, report that they've started correctly, and remain running, even though they don't work. Starting them slowly is almost always the solution. SQL Server and IIS are two very common culprits. Microsoft's monitor can restart them if they report a failure later on, but won't do anything at all about starting them initially.

SloStart Service Related Software