Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!ncar!noao!asuvax!hrc!gtephx!ellisond
From: ellisond@gtephx.UUCP (Dell Ellison)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Where does it all start: memory control blocks?
Summary: BIOS or DOS call
Message-ID: <43421c83.190fc@gtephx.UUCP>
Date: 16 May 89 16:02:54 GMT
References: <7495@spool.cs.wisc.edu>
Distribution: na
Organization: AG Communication Systems, Phoenix, Arizona
Lines: 13

In article <7495@spool.cs.wisc.edu>, rose@shorty.CS.WISC.EDU (Scott Rose) writes:
> ..., I wish to be able to follow
> the chain of memory control blocks.  I have a very lovely little program that
> does just that, and in a very informative fashion: mapmem, particularly
> useful in conjunction with its /v switch.  It works every time, which is
> evidence that if an entirely elegant technique is not available there is at
> least some repeatable way to find the head of the chain.  While I can
> find *some* of the MCBs- that associated with the PSP of my program and any
> that follow- these beasties are not doubly-linked, and no documentation that
> I have found describes how to find the root.

I understand that there is a DOS or BIOS call that will give you the address
of the head of the linked list.