Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!hplabs!decwrl!decvax!tektronix!uw-beaver!uw-june!entropy!dataio!pilchuck!del
From: del@pilchuck.Data-IO.COM (Erik Lindberg)
Newsgroups: comp.sys.ibm.pc,misc.wanted
Subject: Re: Wanted: Memory block display for PC/MS-DOS
Message-ID: <575@pilchuck.Data-IO.COM>
Date: Mon, 17-Nov-86 23:12:45 EST
Article-I.D.: pilchuck.575
Posted: Mon Nov 17 23:12:45 1986
Date-Received: Tue, 18-Nov-86 21:36:36 EST
References: <2078@eagle.ukc.ac.uk>
Reply-To: del@pilchuck.UUCP (Erik Lindberg)
Organization: Data I/O - FutureNet Corp., Redmond, WA
Lines: 20
Xref: mnetor comp.sys.ibm.pc:136 misc.wanted:227


I have a PD program which displays the owner of the memory blocks, any
interrupts it may have redifined (allocated), the command line parameters
(if applicable) and the actual loading address of the program. It fails
to properly trace memory allocated by loadable device drivers (from
config.sys) but merely reports one large block for the whole lot of 'em.

There is also source, and programs which demonstrate how to follow the
DOS memory allocation chain to do other "illegal" things to DOS. If there
is a lot of demonstrated interest, I could post a shar file. Otherwise, I'll
just try to mail it to the UK.


del (Erik Lindberg)
uw-beaver!tikal!pilchuck!del
-- 
del (Erik Lindberg) aka Hugable
uw-beaver!tikal!pilchuck!del

Hugs: One of the few good things in life that are still free.