Problems with WIN/TCP for 386 Streams on AT&T V/386 3.2.2
Conor P. Cahill
cpcahil at virtech.uucp
Tue Mar 20 12:41:58 AEST 1990
In article <3642 at infmx.UUCP> aland at 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
More information about the Comp.unix.i386
mailing list