Date:	Sat, 6 May 2000 17:20:11 -0400 (EDT)
Message-Id:	<200005062120.RAA07126@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	Robin Johnson <robbat2 AT home DOT com>
CC:	djgpp AT delorie DOT com
In-reply-to:	<3913BE7A.AB729B95@home.com> (message from Robin Johnson on Sat,
	06 May 2000 06:40:53 GMT)
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>
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

> 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.

- Raw text -