Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!usc!ginosko!uunet!iconsys!caeco!jose!jim
From: jim@jose.uucp (Jim)
Newsgroups: comp.sys.ibm.pc
Subject: Re: problem with Novell ELS II...
Keywords: shell problems(command.com & net3.com)
Message-ID: <1989Sep13.152802.7213@jose.uucp>
Date: 13 Sep 89 15:28:02 GMT
References: <836@xroads.UUCP> <2674@orion.cf.uci.edu> <[250c7428:5420.3]comp.ibmpc;1@ddsw1.MCS.COM>
Organization: Price Savers, Salt Lake City, UT
Lines: 20

Sorry to post, but I am having problems mailing right now.

You mention that your programs are not finding command.com and crash after
running.  I had similar problems running a novell network.  Something that
actually worked for me was to force the comspec.
set comspec = f:\somewhere\command.com
Put it in the users login script if evenyone might be running different
versions of dos, or put it in the system login script if and only if 
everyone is running the EXACT same version of dos.  Not just a 3.3 or
whatever, but it must be the same MAKE of the version.  Also, just a note:
I had some problems, actually alot of problems on the network with
IBM's MS-DOS ver 3.2 first release.  

Another things to watch for.  You can do stuff to loose a drive mapping.
Example.  If you have your comspec set for f:\dos\command.com, and then
in your activities you change to another drive, lets say g:  If you then
logout from g:, that will be your prompt.  It will not see an f:  Remember
this, because it then will not be able to reach your f:\anything, and 
command.com will be inaccessable.  (Of corse, if you logout of novell, 
you can not get at anything except login, so just watch for those ideas).