Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!pyramid!octopus!pete
From: pete@octopus.UUCP
Newsgroups: misc.wanted,comp.sys.ibm.pc,comp.sources.wanted
Subject: HELP! We're looking for Documentation of Undoc'd MSDOS Int 21H Functions
Message-ID: <246@octopus.UUCP>
Date: Mon, 30-Mar-87 03:46:00 EST
Article-I.D.: octopus.246
Posted: Mon Mar 30 03:46:00 1987
Date-Received: Tue, 31-Mar-87 05:09:47 EST
Reply-To: pete@octopus.UUCP (Pete Holzmann)
Followup-To: comp.sys.ibm.pc
Distribution: world
Organization: Octopus Enterprises, Cupertino, CA
Lines: 25
Xref: utgpu misc.wanted:698 comp.sys.ibm.pc:2624 comp.sources.wanted:816

I posted a query on this subject a week ago in comp.sys.ibm.pc. There seems
to be a lot of interest in the undocumented MSDOS functions from the 
responses I got... But nobody had any answers!

OK all you hackers out there! Here's a chance to do something useful!

If you have figured out any (part) of even one of the undocumented MSDOS
Int 21H (or other) functions, please mail me what you've got. I'll compile
a list and post it to the net (and gladly give all the credit to you!)

If you like to hack at obscure code and have the time to do it, why not
spend some time figuring out what DOS is doing in those extra functions?
They sure aren't NOPs! I've been looking at function 52H, which seems to
return a set of pointers to interesting internal lists related to devices:
Device driver linked list head, something similar to the current BPB for
all devices, etc etc. I'm not done yet, obviously.

Are there enough tidbits in the collected minds on the net to make a
reasonably complete list of what these functions do???

-- 
  OOO   __| ___      Peter Holzmann, Octopus Enterprises
 OOOOOOO___/ _______ USPS: 19611 La Mar Court, Cupertino, CA 95014
  OOOOO \___/        UUCP: {hplabs!hpdsd,pyramid}!octopus!pete
___| \_____          Phone: 408/996-7746