Xref: utzoo comp.windows.misc:1802 comp.windows.ms:9123 comp.windows.ms.programmer:848
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!swrinde!dptspd!aas
From: aas@sat.datapoint.com (Adrienne Stipe)
Newsgroups: comp.windows.misc,comp.windows.ms,comp.windows.ms.programmer
Subject: Windows 3.0 question
Message-ID: <1991Feb8.214307.21361@sat.datapoint.com>
Date: 8 Feb 91 21:43:07 GMT
Sender: aas@sat.datapoint.com (Adrienne Stipe)
Organization: Datapoint Corporation, San Antonio, TX
Lines: 15


I'm posting this question for a friend. Hopefully I'm posting this
to the right place. Please send replies to me via mail, as I do not
normally read these newsgroups. My address is aas@sat.datapoint.com.

What is the easiest way for a protected-mode (386 enhanced) Windows
3.0 application to access a memory mapped device?

How do you make an entry in your virtual machine's Local Descriptor
Table (LDT) to reference a given physical memory location?

Can this be done without writing a Virtual Device Driver?

Thanks in advance for any information,
Adrienne