Path: utzoo!yunexus!maccs!cs4g6ag From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) Newsgroups: comp.sys.ibm.pc Subject: Re: problem with Novell ELS II... Summary: happens occasionally in SFT 2.15 Keywords: shell problems(command.com & net3.com) Message-ID: <251071C5.18135@maccs.dcss.mcmaster.ca> Date: 15 Sep 89 03:51:32 GMT Article-I.D.: maccs.251071C5.18135 References: <836@xroads.UUCP> <2674@orion.cf.uci.edu> <[250c7428:5420.3]comp.ibmpc;1@ddsw1.MCS.COM> <1670@bucket.UUCP> Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) Organization: McMaster University, Hamilton, Ontario Lines: 21 In article <1670@bucket.UUCP> leonard@bucket.UUCP (Leonard Erickson) writes: >Please note that these problems are with *non-dedicated* servers. There >aren't any problems with dedicated servers. >We use Advanced Netware and haven't had any of these problems. And in my >opinion, a non-dedicated server should only be considered in cases of >*extreme* poverty. You don't dare have anybody but the "expert" users >using a machine that is a non-dedicated server. We used SFT Netware 286 V2.15 where I worked this past summer. There was only ever one program I ever had problems with. Originally, it was because my COMSPEC didn't point to a valid COMMAND.COM (this had nothing to do with the network); however, even after I put a COMSPEC= into the AUTOEXEC, I would very occasionally get an INVALID COMMAND.COM; SYSTEM HALTED error even though COMSPEC pointed to the very same copy of COMMAND.COM which was used at boot- time. I never figured this one out. -- Stephen M. Dunn cs4g6ag@maccs.McMaster.CA ********************************************************************** = "\nI'm only an undergraduate!!!\n"; "VM is like an orgasm: the less you have to fake, the better." - S.C.