Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!usc!orion.cf.uci.edu!mrichey From: mrichey@orion.cf.uci.edu (Mike Richey) Newsgroups: comp.sys.ibm.pc Subject: Re: Novell <===> DOS .......(Repost) Keywords: command.com Message-ID: <2601@orion.cf.uci.edu> Date: 1 Sep 89 18:42:54 GMT References: <9499@eerie.acsu.Buffalo.EDU> Reply-To: mrichey@orion.cf.uci.edu (Mike Richey) Distribution: usa Organization: University of California, Irvine Lines: 34 In article <9499@eerie.acsu.Buffalo.EDU> cook@sybil.UUCP (John M. Cook) writes: > > First to summarize I'm having two problems: > >1) Non-Dedict File Server has problem running application programs >that run fine on workstations. Giving File Server this Error message: >====> Invalid Command.com ... Cannot load Command, system halted. >Only when exiting the program. Two things to check. On the console/workstation, let DOS set the comspec. In other words, don't use the COMSPEC=S2:COMMAND.COM in the user or system login script. Keep a valid copy of command.com in the A: drive of the file server. Secondly, DO NOT set the DOS PROMPT command at the console/work- station. I know this is a bother, but that's what you get for using non ded- icated with Novell Netware. What version of Netware are you running? I would suggest, although this could be costly, buying another workstation and attaching it to your LAN, and keep the fileserver in the CONSOLE mode. >We have a BASIC software package causing weird crashes on the Network. >I wish we could get rid of the package but it the favorite from the 20 >other packages that have been reviewed and it was used 3 yrs prior to I've heard of some basic compiled applications causing problems. Generally because they are not Netware aware products, sorry not able to offer any more on this point. Michael S. Richey mrichey@orion.cf.uci.edu BITNET: mrichey@UCI Voice: (714) 856-8374 University of California, Irvine Network and Telecommunications Services 342 Computer Science Irvine, CA 92717