Newsgroups: comp.protocols.tcp-ip.ibmpc
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!clarkson!grape.ecs.clarkson.edu!nelson
From: nelson@sun.soe.clarkson.edu (Russ Nelson)
Subject: Re: Help with NET_PC and Clarkson Packet Drivers
Reply-To: nelson@clutx.clarkson.edu (aka NELSON@CLUTX.BITNET)
Organization: Clarkson University, Potsdam NY
Date: 10 Apr 91 23:17:41
Message-ID: <NELSON.91Apr10231741@sun.clarkson.edu>
In-Reply-To: eeh@Dixie.Com's message of 9 Apr 91 22:18:24 GMT
References: <9385@rsiatl.Dixie.Com> <9436@rsiatl.Dixie.Com>
Sender: usenet@grape.ecs.clarkson.edu

In article <9436@rsiatl.Dixie.Com> eeh@Dixie.Com (Ed Howland) writes:

   After some experimentation I found out that my NCSA software had config.tel
   interrupt=5. But when I call ubnicps2.com with:
   ubnicps2 0x60 5 or with all parameters  0x60 5 0x1550 0xD000
   it comes back with interrupt = 3. What gives. The .asm has some mysterious
   thing about it always is 3??? The NCSA stuff works fine.

The technical documentation says that it always uses interrupt 3.  Perhaps
NCSA Telnet is ignoring the interrupt= parameter for the nic-ps/2 because
it doesn't make any sense for that adapter?

--
--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.