From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10010012015.AA14631@clio.rice.edu>
Subject:	Re: Beta Testers Needed
To:	eliz AT is DOT elta DOT co DOT il
Date:	Sun, 1 Oct 2000 15:15:08 -0500 (CDT)
Cc:	Martin DOT Stromberg AT lu DOT erisoft DOT se, djgpp-workers AT delorie DOT com
In-Reply-To:	<7263-Sun01Oct2000211741+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Oct 01, 2000 09:17:41 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > (I also discovered an interesting bug-feature of the system() command 
> > during testing - I had an invalid directory in my path and system quit ...)
> 
> I'd appreciate the details of this problem, like the exact invocation
> sequence, the situation with PATH, and what exactly happened (I'm not
> sure what does ``system quit'' mean--did it wedge the machine or
> what?).

Exactly what happened is not reproducible.  In all cases it just didn't
do anything useful, but didn't wedge or anything.

Originally system() was failing, but I wasn't checking the return status.
I changed the path, then system() worked.  Then I changed the path to a
simple failure example, and system() failed.  It continued to fail when 
I put the path back to just c:\DOS

I changed the system("command") to i = system("command.com") so I could 
check the return status, and it started working again.

Since my whole goal was to be able to look at the DOS memory layout and
contents under new stubs when an image is active - I've moved on ...

- Raw text -