Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!ncar!mephisto!uflorida!haven!umbc3!gmuvax2!2113av
From: 2113av@gmuvax2.gmu.edu (John Porter)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Child processes in Mess-Dos
Message-ID: <2530@gmuvax2.gmu.edu>
Date: 4 Oct 90 19:36:22 GMT
References: <15651@yunexus.YorkU.CA> <626@demott.COM>
Reply-To: 2113av@gmuvax2.UUCP (John Porter)
Organization: George Mason Univ. Fairfax, Va.
Lines: 10

In article <626@demott.COM> kdq@demott.COM (Kevin D. Quitt) writes:
>    Sure wish I had your system.  When I do that, I see command.com clear
>as day.

Not to be picky or skeptical, but: are you saying you saw *another* copy of
command.com *between* your parent and your child, the memory mapper?
Because, as you know, the original command.com is always around, but it 
is below any transient user processes.

-- john.porter