Workstation NT - Windows NT Workstation Services
workstation

 Services


All of the following services were set to start up automatically by default (except Remote Access Connection Manager, which was set to Manual startup). For stand-alones, this is a huge waste of resources. I suggest you go through your Services applet in the Control Panel and set the unnecessary services to manual (or maybe disabled in some cases).

necessary services startup automatic

    Event Log runs in services.exe; provides event logging.

    Plug and Play runs in services.exe; for RAS (unimodem modems, in particular).

    RPC Service runs as rpcss.exe. It stands for Remote Procedure Call Sub System, but it means DCOM (Distruted Common Object Model) -- it's internal name is dcomss.exe -- and this is a basic NT service.

    Spooler runs as spoolss.exe; for printing.

services to set to manual or disable startup manual

    Computer Browser (services.exe) will never start if you set it to manual.

    Messenger (services.exe) set it to manual, and it will start when needed (ie, via Alerter, for example, which is already set to manual).

    Remote Access Autodial Manager (rasman.exe) should be set to manual... if you have settings otherwise, it will start when called upon.

    Remote Access Connection Manager (rasman.exe) is already properly set at manual.

    Server (services.exe) is unnecessary, and can be disabled, but at least set it to manual.

    TCP/IP Netbios Helper (services.exe); used for LMHosts lookup (names resolution). Set to manual and it'll never come on (unless you use LMHosts).

    Telephony (tapisrv.exe) is necessary for unimodem modems, and will start when needed. Set to manual. Note that this is one of those few services that, once started, can't be stopped.

    Workstation runs in services.exe, and will start automatically (even if set to manual) unless you disable it.

Looking Up Services in the Registry

    In the Services applet in the Control Panel, the names you are viewing are "Display Names". It is sometimes confoundedly (that is a word... now!) difficult to dig up information about these services: what are they, where did they come from, will my machine work if I turn them off, etc.

    If you check out the Registry entries under:

      HKLM\System\CurrentControlSet\Services\

    you'll be able to glean some information about all your services (and devices, drivers, etc). There are a lot of them, and you may have to do some hunting and pecking, but this is where NT stores information for all your services, including the executable ("Image Path"). All of which should help you find out about any service in question.

    The service's "Display Name" is a parameter in the subkey, so you have to click through the subkeys and look over (into the data pane) to see if one of the subkeys has a matching "Display Name".

      An alternate means of searching the Registry is using regedit.exe in c:\winnt. After you open the program, select the "directory" (hive/subkey) you want to search, then select [menu item] Edit\Find.

    In the snapshot below, I have Alerter selected, and the data pane shows the Display Name as being "Alerter":


NT Services

excerpted from my 9/29/98 article at Suite101.com.

Protected Storage Service

Last week I engaged in a few interesting email exchanges regarding NT services. In one exchange, which referred back to last year's November 11, 1997 article, Internet Explorer 4 on NT, the user found that the Protected Storage service (pstores.exe), which installs with Internet Explorer 4 and takes up a good chunk of RAM, but which appears relatively useless in IE4 (unless you use the MS Wallet application), is required running for Outlook Express 98.

Indeed, and right on que, nt.zdnet.com's Russ Cooper wrote a rather in-depth article, "Service Pack 4: No Browser Required?", regarding the Protected Storage service. (In effect, you didn't need to install IE4 to use SP3 or the Option -- you just needed the Protected Storage service which is installed with IE4)

Running an Application as a Service

The other relevant email exhange dealt with NTVDM running the CPU up to nearly 100% when running certain 16-bit applications some of the time.

The user had installed SP3 (a common answer to the NTVDM problem), to no avail. Finally, he ended up making the application (Word 2.0) a service, and now it seems to runs fine all the time (except he has to remember to turn the "service" off manually when he's finished with the application).

srvany.exe, available in the Resource Kit, allows you to easily add an application as a service. While the Resource Kit Help file indicates that not all 16-bit applications may function well as services, it certainly might be worth a shot if you're having similar CPU-hogging problems. The usage is as follows:

    instsrv {AnyName} {drive}:\{path}\srvany.exe

You can run any number of applications this way, as long as each has a different service name ("AnyName" in the above example).

Services are applications that launch at startup (either on boot or when called by another program), without need for intervention from the user. They can run without anyone logged on.

Services can be managed through the Control Panel applet Services. From this applet, you can view all registered services, their current running status, and their startup type (ie, System, Automatic, Manual, or Disabled). Furthermore, you can start and stop services from this applet.

You can also start and stop services using the console's net start and net stop commands. If you do this, you can call a service by its "display name" (see below... it's the name of the service as it appears in the Services applet), as long as you put the name in quotes, like:

    net stop "Protected Storage"

You can read the remainder of this article here.

Registry snapshot