From: labtek@cs.yale.edu (Tom Griest)
Subject: Re: GNAT: WIN95 - System.Address Question...
Date: 1996/09/19
Date: 1996-09-19T00:00:00+00:00 [thread overview]
Message-ID: <51rgc1INNbvp@RA.DEPT.CS.YALE.EDU> (raw)
In-Reply-To: 3240134A.7877@ab.com
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
next prev parent reply other threads:[~1996-09-19 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-18 0:00 GNAT: WIN95 - System.Address Question Mike Gardner
1996-09-19 0:00 ` Tom Griest [this message]
1996-09-19 0:00 ` David C. Hoos, Sr.
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox