From: Lars Erdmann <lars DOT erdmann AT arcor DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: farpeekw under Windows NT
Date: Wed, 29 May 2002 17:47:26 +0200
Organization: Arcor
Lines: 27
Message-ID: <3CF4F80E.52456363@arcor.de>
References: <3CF4EE40 DOT 19E44519 AT arcor DOT de> <200205281523 DOT g4SFNZw26739 AT envy DOT delorie DOT com>
NNTP-Posting-Host: dialin-145-254-251-081.arcor-ip.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: newsread1.arcor-online.net 4558 NG bGFycy5lcmRtYW5u
X-Complaints-To: abuse AT arcor-online DOT net
NNTP-Posting-Date: Tue, 28 May 2002 15:50:50 +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,

ok, I can see them. Unfortunately, writing to port 0x3BC (at 0x408 in
bios data area -> LPT1) will block my PC. This is not astonishing since
my "real" LPT1 is on 0x378 (which shows up at 0x40C in bios data area,
and 0x278 will show up at 0x40E).

I wonder if NT messes around with the bios data segment (for whatever
reason) ?
On Windows95, this all works perfectly well (that is I find value 0x378
at bios data area 0x408 and 0 at bios data areas 0x40C and 0x40E).

Will the bios function via int 0x17 (_bios_printer) handle this
differently ? Then, I will use that one.

Lars

DJ Delorie schrieb:
> 
> The IBM PC spec defines three parallel ports:
> 
> 3BC - on monochrome card
> 378 - primary on mainboard
> 278 - secondary on mainboard
> 
> NT emulates all three, so you see three addresses in your DOS
> emulation window.