Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!hellgate.utah.edu!dog.ee.lbl.gov!nosc!baron!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.protocols.nfs
Subject: Re: When NFS fails
Message-ID: <1991May06.174006.3166@jadpc.cts.com>
Date: 6 May 91 17:40:06 GMT
References: <1991Apr30.165109.23950@jadpc.cts.com> <1991Apr30.221106.8559@usasoc.soc.mil> <578@rc6.urc.tue.nl>
Organization: Network Engineering Technologies, San Diego, CA.
Lines: 19

In article <578@rc6.urc.tue.nl> rcstack@urc.tue.nl writes:
>In article <1991Apr30.221106.8559@usasoc.soc.mil> ted@usasoc.soc.mil (Ted Nolan) writes:
>>We have used this from time to time, and it seems to work. 
>
>Or: use: shell=command.com /p /e:1024 /f in your config.sys.
>                                      ^^
>This is an undocumented switch which, at least in dos 3.30 and 4.01 causes
>dos to generate a Fail on any critical error. We use this on our BBS and it
>works just fine.
>

It does work, but I need to return an error to the process.  Does this
do that?

Jim
-- 
ARPANET:    jadpc!jdeitch@nosc.mil
INTERNET:   jdeitch@jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch