Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!princeton!phoenix
From: greg@phoenix (greg Nowak)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Yet another 4DOS quirk
Message-ID: <13856@phoenix.Princeton.EDU>
Date: 14 Feb 90 22:16:37 GMT
References: <1513@krafla.rhi.hi.is> <AUSTIN.90Feb13152915@bucsf.bu.edu> <1990Feb14.140213.10488@uwasa.fi>
Sender: greg@phoenix.Princeton.EDU
Reply-To: greg@phoenix (greg Nowak)
Organization: Cabal of Fools; Phoenix Gang
Lines: 18
In-reply-to: ts@uwasa.fi (Timo Salmi LASK)


I'm having a problem with 4DOS 2.0 -- it doesn't recognize the b:
drive.
When I type b:  , it reponds with a stream of "No path" errors.
The "path" command also has several interesting responses : 
sometimes it will merely hang the machine, sometimes it spews out
gibberish (it looks like the same sector over and over again.) I use
the format "set path = ..." in my autoexec.bat, because using path as
a command caused the above errors. while this allows me to use files
in a:\bin, the command "path" without arguments claims there is "no
path". Is this the result of some conflict between path, the command,
and PATH, the environment variable? Is there any way I can fix it?

thanks,

...!rutgers!phoenix.princeton.edu!greg

                           Greg Nowak/Phoenix Gang/Princeton NJ 08540