From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ca147c487910c1d8
X-Google-Attributes: gid103376,public
From: labtek@cs.yale.edu (Tom Griest)
Subject: Re: GNAT: WIN95 - System.Address Question...
Date: 1996/09/19
Message-ID: <51rgc1INNbvp@RA.DEPT.CS.YALE.EDU>#1/1
X-Deja-AN: 183928440
distribution: inet
references: <3240134A.7877@ab.com>
organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
newsgroups: comp.lang.ada
Date: 1996-09-19T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <3240134A.7877@ab.com> mike.gardner@ab.com writes:

>I'm writing an interface to an EISA card which sits in a Gateway
>computer running WIN95.  I need to write a 0x0001 to a real-mode address
>of CC00H:0804H.  Since WIN95 is running in protected-mode, I assume that
>I need to buy/write a package for peeking and poking values to real-mode
>addresses...  My question is this...  Will the GNAT for WIN95 system
>allow me to directly write to a real-mode address and it handles the
>nasties of the protected-mode interface?  My hunch is that I cannot just
>simply use the System.Address stuff on this platform and must buy/write
>an interface package to give me a porthole from protected-mode to
>real-mode.  What do you think?

I think you should write a device driver.  This is the proper "model" to
follow when interfacing with hardware.  Probably the best way is to
get the MS Device Driver Kit (DDK).  I believe some companies sell
something like what you want "a porthole", but I can't recall their
names.  There may also be some sample drivers on the net (I know there
are many samples in the DDK).

-Tom