Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!usc!srhqla!demott!kdq
From: kdq@demott.COM (Kevin D. Quitt)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Child processes in Mess-Dos
Message-ID: <685@demott.COM>
Date: 6 Oct 90 00:13:49 GMT
References: <2530@gmuvax2.gmu.edu>
Reply-To: kdq@demott.COM (Kevin D. Quitt)
Organization: DeMott Electronics Co., Van Nuys CA
Lines: 21

In article <2530@gmuvax2.gmu.edu> 2113av@gmuvax2.gmu.edu (John Porter) writes:
>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.

    No, I see the non-resident portion of command com taking up space
above me, and my BIOS trace reports the reads from the sectors occupied
by COMMAND.COM.  (Quite right to be picky and skeptical - extraordinary
claims and all that).
-- 
 _
Kevin D. Quitt         demott!kdq   kdq@demott.com
DeMott Electronics Co. 14707 Keswick St.   Van Nuys, CA 91405-1266
VOICE (818) 988-4975   FAX (818) 997-1190  MODEM (818) 997-4496 PEP last

                96.37% of all statistics are made up.