Message-ID:	<3914BEA3.11769667@home.com>
From:	Robin Johnson <robbat2 AT home DOT com>
Organization:	Orbit Computers
X-Mailer:	Mozilla 4.7 [en] (Win98; U)
X-Accept-Language:	en,af,es
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Dos MEM Command
References:	<3912DA26 DOT FEED14AE AT home DOT com> <8euosi$rcm$1 AT antares DOT lu DOT erisoft DOT se> <3913BE7A DOT AB729B95 AT home DOT com> <200005062120 DOT RAA07126 AT indy DOT delorie DOT com>
Lines:	30
Date:	Sun, 07 May 2000 00:53:51 GMT
NNTP-Posting-Host:	24.113.36.103
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news1.rdc1.bc.home.com 957660831 24.113.36.103 (Sat, 06 May 2000 17:53:51 PDT)
NNTP-Posting-Date:	Sat, 06 May 2000 17:53:51 PDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

If you boot off a boot disk, you cannot be sure that it is there. Because it 
isn't in most bootdisks.

Eli Zaretskii wrote:
> 
> > From: Robin Johnson <robbat2 AT home DOT com>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Sat, 06 May 2000 06:40:53 GMT
> >
> > i need my code to be able to work without having to call mem.exe
> > unfortenetly.  because i can't be guarenteed that it will be on
> > every system.
> 
> MEM is a standard program on any DOS/Windows system.  There's no need
> to assume that it might be absent, exactly like you have no reason to
> assume that COMMAND.COM will be absent.
> 
> If you want to write your own program that reports programs loaded
> into memory, you can do that too.  You will need to trace the DOS
> memory chain; the excellent book "Undocumented DOS", 2nd edition by
> Andrew Schullman includes a chapter on how to do that.

-- 
Robin Hugh Johnson
"Robbat2"
QTOD: "I used to be an idealist, but I got mugged by reality."
E-Mail     : robbat2 AT orbis-terrarum DOT net
ICQ#       : 30269588 or 41961639
Home Page  : http://www.orbis-terrarum.net
Time Zone  : Pacific Daylight (GMT - 8)

- Raw text -