Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!uwm.edu!csd4.csd.uwm.edu!chad
From: chad@csd4.csd.uwm.edu (D. Chadwick Gibbons)
Newsgroups: comp.sys.ibm.pc
Subject: DOS 3.3/Novell 2.15SFT bug
Keywords: network, dos, bug
Message-ID: <1608@uwm.edu>
Date: 21 Dec 89 19:47:53 GMT
Sender: news@uwm.edu
Reply-To: chad@csd4.csd.uwm.edu (D. Chadwick Gibbons)
Distribution: na
Organization: University of Wisconsin-Milwaukee
Lines: 23


	I have run into an interesting problem/bug/oversight with
the path setting mechanism of DOS V3.3, and Novell NetWare 2.15.
Take, for example, an autoexec file containing the following PATH
statement:

path c:\bin;c:\dos

When logging onto the network, the system automatically will include
the two path directories as search drives.  However, if the path
statement is structured as:

set path=c:\bin;c:\dos

The search drive mappings will _not_ take place.

	We have just received an update to our Novell NetWare, so
it should be interesting to see if the new version suffers from
this problem.  I'd like to say "problem with Novell" but I have a
feeling it's more a problem with DOS, since path c:\bin and set
path=c:\bin should be indentical, as far as I know.

	Anyone with similiar experiences?