Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.i386
Subject: Re: Problems with WIN/TCP for 386 Streams on AT&T V/386 3.2.2
Message-ID: <1990Mar20.024158.28195@virtech.uucp>
Date: 20 Mar 90 02:41:58 GMT
References: <3642@infmx.UUCP>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 21

In article <3642@infmx.UUCP> aland@infmx.UUCP (alan denney) writes:
>   WIN/TCP installed fine with no error messages.  Installed using 
>   interrupt 2 (instead of the default of 3) because interrupt 3 is
>   in use by COM2.  There were no references to interrupt 2 in mdevice.

Leave the card configured as is, but configure it as interrupt 9 in UNIX.

There is no interrupt 2 on an AT bus because that interrupt line is used
to cascade the second interrupt controller onto the first controller.
If you configure a card to use interrupt 2, it actually appears as interrupt
9 to the system.

MS-DOS software knows about this and does the remapping as appropriate. 

In UNIX you have to say it like it is.  


-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170