From:	Lars Erdmann <lars DOT erdmann AT arcor DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Windows NT: Writing to I/O port does nothing
Date:	Mon, 03 Jun 2002 21:35:12 +0200
Organization:	Arcor
Lines:	20
Message-ID:	<3CFBC4F0.EAD73B17@arcor.de>
NNTP-Posting-Host:	dialin-145-254-252-056.arcor-ip.net
Mime-Version:	1.0
X-Trace:	newsread1.arcor-online.net 23853 NG bGFycy5lcmRtYW5u
X-Complaints-To:	abuse AT arcor-online DOT net
NNTP-Posting-Date:	Mon, 3 Jun 2002 19:39:01 +0000 (UTC)
X-Priority:	1 (Highest)
X-Mailer:	Mozilla 4.61 [de] (OS/2; U)
X-Accept-Language:	de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,

I have written a small app that (in order to do its stuff) writes to the
parallel port I/O ports.
Unfortunately, it's not a printing app or so, so I have to access the
ports directly.
Using outp() does not give me an error or trap but under Windows NT it
appears to do nothing.
When I use the same app under Windows95, it works ok.

Does WindowsNT allow direct access to I/O ports for DOS apps (as OS/2
does for example) ?
If not, how does it virtualize the I/O ports ? To me it looks like it is
doing nothing at all.
Looking at the deassimbling window of the RHIDE debugger it appeared to
me that the code segment is running at IOPL 3 so I would hope that I am
able to access I/O ports directly even if WindowsNT normally catches the
I/O port accesses or am I wrong ?

Lars

- Raw text -