comp.lang.ada
 help / color / mirror / Atom feed
From: dmitry@elros.cbb-automation.de (Dmitry A. Kazakov)
Subject: Re: Accessing I/O Ports in Windows NT/2000
Date: Fri, 18 Jan 2002 08:29:40 GMT
Date: 2002-01-18T08:29:40+00:00	[thread overview]
Message-ID: <3c47dae5.155431437@News.CIS.DFN.DE> (raw)
In-Reply-To: 3C474180.8060306@mail1.monmouth.army.mil

On Thu, 17 Jan 2002 16:26:24 -0500, Jeffrey Glenn
<jeffrey.glenn@mail1.monmouth.army.mil> wrote:

>
>Ted Dennison wrote:
>
>> Jeffrey Glenn <jeffrey.glenn@mail1.monmouth.army.mil> wrote in message news:<3C45FC6C.2030208@mail1.monmouth.army.mil>...
>> 
>>>I've found that accessing the I/O ports on Windows 9x is rather easy, 
>>>but with Windows NT/2000 input and output instructions are privileged 
>> 
>> That's right. NT doesn't allow direct access to the hardware from a
>> user-mode program. If you want to do that, you have to write a Windows
>> device driver.
>> 
>>>Does anyone know of an Ada solution to accessing I/O ports on Windows 
>>>NT/2000?
>> 
>> This isn't a language issue, its an OS issue. What you need to figure
>> out is how to write a device driver for NT-class OS's. Anything you
>> learn about that can be translated into Ada quite easily.
>> 
>> Good places to get started are the Microsoft DDK website
>> (http://www.microsoft.com/ddk/ ) , and the newsgroups
>> comp.os.ms-windows.programmer.drivers
>> (http://groups.google.com/groups?group=comp.os.ms-windows.programmer.drivers)
>> and comp.os.ms-windows-programmer.nt.kernel-mode
>> (http://groups.google.com/groups?group=comp.os.ms-windows.programmer.nt.kernel-mode
>> ).
>
>I was (am) hoping that I would not have to learn about writing device 
>drivers for Windows NT. I realize that Ada doesn't provide these 
>facilities, but I hoped to find that someone had already written such an 
>interface/wrapper package. Ada also doesn't support ODBC, TCP/IP, nor 
>Windows for that matter, but a lot has been written to bind with them.

There was a product by Blue Wave, I believe, called WinRT. It
contained a primitive Windows driver, which allowed you to read/write
arbitrary physical memory locations [= your I/O ports]. I think all
that you will need then is standard Win32 bindings and here you are.

Regards,
Dmitry Kazakov



  parent reply	other threads:[~2002-01-18  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16 22:19 Accessing I/O Ports in Windows NT/2000 Jeffrey Glenn
2002-01-17  3:41 ` Steve Doiel
2002-01-17 15:35 ` Ted Dennison
2002-01-17 21:26   ` Jeffrey Glenn
2002-01-18  7:09     ` Michael Bode
2002-01-18  8:29     ` Dmitry A. Kazakov [this message]
2002-01-18 17:22       ` Stephen Leake
2002-01-18 15:03     ` Ted Dennison
2002-01-22  7:47   ` Mats Karlssohn
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox