>When I start up Windows NT I get the message that a Service has failed to start. I get the following message in the Event Viewer:
>
>"The Server service terminated with the following error:
>Not enough server storage is available to process this command."
>
>There are also a number of cascaded failures, that is other services which failed to operate because of the failure of Server to load. "Service Control Manager", "Computer Browser" and others.
>
>I cannot manually start the server service. It fails with the same "Not enough server storage is available to process this command" mesasage.
>
>What storage are we talking about here. Memory (computer has 64mB), harddisk (computer has more than enough).
>
>The event viewer is nice but what are we suppose to do with the information. NT help is no use. Server help is not availible when the Server Control Manager is not running.
>
>The current version of NT is newly loaded (yesterday). I could not load IE 4.0 on NT. The setup failed with out copying any files. MicroSoft advised me to load a new version of NT and to try loading IE4.0 as soon as possible (after loading Service Pack 3). It worked but I have had this problem since.
>
>What does this service do beyond the oblvious of allowing others to access my computer over the network. Since I have had this problem I have had trouble logging on to my Netware 4.0 directory tree.

Essentially, everything that relies on your system to provide services externally relies on the Server service. A nasty side effect is that many things that would otherwise work will stop working if you enable the Server service and it fails to start, including SCM and the network browser facility. It's not surprising that you're having numerous problems with Server not starting properly.

I've not run into this specific problem, but I'd guess that it's a problem with the system swapfile (fairly likely if you created a minimal FATpartition to install NT on, and there isn't adequate space available for the swap file. Fixable using Control Panel/System/Performance, and then changing the Virtual Memory settings to allocate some swapfile space on another partition aw well), the amount of disk space allocated for registry entries (fixed in the same screen) or the network configuration done while installing NT is badly hosed. I can't help much with Netware 4 NDS support, but I'd look at CSNW configuration; I know it's been a headache for some of our clients.

I'd recommend starting completely fresh, and if you allocated a boot partition of less than ~500MB, increase that significantly. Both of the boxes here running NT (one NT Server, one NT Workstation, both build 1381 with SP3 and Option Pack 4, with IE 4.01) are using over 400MB on the boot drive, with virtually no apps installed to that partition. I preallocate swap files to ~10%> than actual installed DRAM, and have my maximum registry sizes set to ~25MB.

hth,

Ed