Xref: utzoo comp.lang.c:32529 comp.os.msdos.programmer:1285
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!haven!umbc3!gmuvax2!2113av
From: 2113av@gmuvax2.gmu.edu (John Porter)
Newsgroups: comp.lang.c,comp.os.msdos.programmer
Subject: Re: Child processes in Mess-Dos
Message-ID: <2503@gmuvax2.gmu.edu>
Date: 3 Oct 90 22:06:23 GMT
References: <1990Sep28.234836.17868@gpu.utcs.utoronto.ca>
Reply-To: 2113av@gmuvax2.UUCP (John Porter)
Followup-To: comp.lang.c
Organization: George Mason Univ. Fairfax, Va.
Lines: 12

In article <1990Sep28.234836.17868@gpu.utcs.utoronto.ca> sarathy@gpu.utcs.utoronto.ca (Rajiv Sarathy) writes:
>Others were under the impression that spawn and exec load an additional
>copy of COMMAND.COM.  I didn't test to see if this is true, but I doubt it.


The MS-DOS programming references are rather explicit on this point.
I have written programs to test these hypotheses, and it is quite true
(at least for ver.3.30) that spawn and exec do NOT load COMMAND.COM.
Both of these system calls are handled by a load/exec routine located in
the resident portion of DOS.

-- john.porter