Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!daccess!eric
From: eric@daccess (Eric Ashley)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Help with BYU Novell shell and packet driver
Message-ID: <9105291357.AA07230@miavax.ir.miami.edu>
Date: 28 May 91 21:33:15 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The Internet
Lines: 11

What you are experiencing here is a nasty little problem that DOS has.  A
secondary command proccess (shelling out to DOS) gets its own UNIQUE environ-
ment.  When you login or logout from your Novell server in a DOS shell, the
environment of that secondary shell gets the path correctly updated.  But
once that process terminates, you again have the environment (including the 
path) that you had before starting your program in the primary command process.

DOS does not define an easy way of determining where the parents environment is
located, so a secondary command process won't alter it.  In short, only alter 
your environment in the primary command process (command line) if that change
will be needed after you exit any app you may be running.