Path: utzoo!attcan!uunet!snorkelwacker!tut.cis.ohio-state.edu!ucbvax!ulysses!lee
From: lee@ulysses.att.com (Lee Begeja[cwc])
Newsgroups: comp.unix.i386
Subject: Re: Problems with WIN/TCP for 386 Streams on AT&T V/386 3.2.2
Summary: interrupt 2 may be suspect
Message-ID: <12706@ulysses.att.com>
Date: 20 Mar 90 20:27:30 GMT
References: <3642@infmx.UUCP>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 14


I am not familiar with the WIN/TCP software but your use of interrupt
2 raises a flag with me.  Since the interrupt 2 slot is actually wired to
interrupt 9 on the bus the software must correctly identify the interrupt...

Here is where I get hazy and maybe someone with more familiarity could
explain the whole situation better...

So check the mdevice file and see if the software is set to use interrupt 2
and if it is change that to interrupt 9 .

At worst it couldn't hurt...

Lee Begeja  AT&T Bell Labs  ulysses!lee