MO> Wednesday November 12 1997 21:07, Michael Kristensen 
 MO> wrote to Michael Oliver:
 MO>> Make the PC's more reliable...
 MK> It is difficult, when about 300 different users including 200 LAMERS
 MK> are connecting and installing a lot of "shit" on the PCīs. Then itīs
 MK> impossible to prevent some "halts" once in a while...  :-)
 MO> Then either take away their ability to install the 
 MO> software, or pull a new image from the server on the 
 MO> 1st boot every morning.
Crap, some system nerd trys taking away my ability to install new software is 
going to get his ass fired. I don't work for him, he works for me and I'm the 
one that allows him on the system . The cure rests in the Novell 
Server setup, not keeping people from installing software from thier 
workstations or improperly logging off the system when the big red switch has 
to be pressed.
The real cure is to either setup Novell to close bad sockets, which is what 
all other decent NOS systems do or change a NOS that is smart enough to do 
so. Not detected and closing bad sockets/connections has been one of Novell's 
mindless nuances/problems ever since ELS v 2.10. I always thought Novell Left 
that "feature" in, so that thier customers would be more inclined to buy more 
liscenses.
I don't know what the cure is with a Novell Server setup but the problem of 
bad connections has always been inherent in Novell's design and it is not 
just limited to Windows 95 clients. It's been around for ever w/DOS and 
perhaps even with CPM novell. Hopefully Novell, other than to recommend 
buying more liscenses than you need has come up with a better solution.
--- Maximus/NT 3.01b1
---------------