home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!news.udel.edu!bach.udel.edu!radel
- From: radel@bach.udel.edu (Todd Radel)
- Newsgroups: comp.os.ms-windows.programmer.misc
- Subject: Help using DPMI "Allocate DOS Memory Block"
- Message-ID: <BrwrI5.FGG@news.udel.edu>
- Date: 24 Jul 92 19:30:05 GMT
- Sender: usenet@news.udel.edu
- Organization: University of Delaware
- Lines: 30
- Nntp-Posting-Host: bach.udel.edu
-
- Well, it's time for another installment of "Help Todd get his stuff
- to work under Windows." :-) :-)
-
- I'm trying to use the DPMI services in Windows 3.1 to communicate with
- a DOS program running in a window. The DOS program is a server which
- communicates with a couple of transputer boards installed in the system.
- The transputers support DMA transfers, but only as long as the server
- is running. Thus, if I want to bring data into my Windows program,
- I have to start the server, allocate some memory, tell the server
- where to find it, and wait for data to come in.
-
- Of course, giving the server the value of a pointer won't work
- because of the way Windows handles virtual memory in VDM's. The
- DPMI function "Allocate DOS Memory Block" (AX= 0100h) seems to be
- what I need. But what is a "selector", and how do I use it? I
- know I can pass the transputer server the real-mode segment of the
- allocated block (or can I?), but how do I access the allocated
- memory from within my program?
-
- Oh yeah, this is 386Enh mode, of course.
-
- Thanks in advance for any help...
-
- -- Todd
-
- --
- Todd Radel | "I obscenity in the milk of all," Agustin said,
- CIS/English undergrad | "if it does not seem like a lunatic asylum in
- University of Delaware | here." -- Hemingway, _For Whom the Bell Tolls_
- A.I. duPont Institute, 1600 Rockland Road, Wilmington, DE 19899
-