Date: Sun, 16 Apr 2000 10:45:25 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Robin Johnson <robbat2 AT home DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP and Win2K
In-Reply-To: <38F80615.77AAB41D@home.com>
Message-ID: <Pine.SUN.3.91.1000416104345.2482i-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 15 Apr 2000, Robin Johnson wrote:

> Just a thought on this, from something I ran into while trying to compile an 
> old Turbo Pascal v7.0 program on Win2K, part of the code involved calling
> command.com to do some stuff, and then spawning a child process for a few
> other things, but I traced the crash to the moment that any child
> process tried to do any file access, it died. So just an idea to look at 
> the code of SetEdit or anything, and see where it calls spawn(), or
> maybe just try something that you know will write a file.

Any DJGPP program that can run other programs *will* call spawn at some 
point.  So there's no need to look at the sources to know that.

But I'm unsure what exactly are you trying to say.  Why is it important 
to know whether spawn is or isn't called?  Could you please elaborate?