Xref: utzoo comp.dcom.lans:1923 comp.dcom.modems:2663 comp.protocols.tcp-ip.ibmpc:841 comp.sys.ibm.pc:20153
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!ames!vsi1!altnet!uunet!lupine!klein
From: klein@lupine.UUCP (Doug Klein )
Newsgroups: comp.dcom.lans,comp.dcom.modems,comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc
Subject: Re: Communication problems involving PC-Interface and Procomm / Kermit
Summary: Changing int with PC-I
Message-ID: <147@lupine.UUCP>
Date: 11 Oct 88 13:33:05 GMT
References: <1053@rivm05.UUCP> <13035@cisunx.UUCP> <956@asylum.UUCP>
Organization: Network Computing Devices, Palo Alto, CA
Lines: 21

In article <956@asylum.UUCP>, romkey@asylum.UUCP (John Romkey) writes:
> 
> For the people who are having problems with Kermit and 3C501's: make
> sure that the 3C501 is not using the same interrupt vectors as your
> COM ports. COM1 uses interrupt 4; COM2 uses interrupt 3. Make sure the
> 3C501 isn't using 3 or 4 then. Interrupt 5 or 2 is probably safe,
> depending on what other hardware you've got installed.

To change the int on the 3C501, move the jumper on the the card. (See the 
manual). But if you do, you have to tell PC-Interface that you did this with
a run-string switch, '-x'. For example, changing the int to 5 means you should
change the cmd line for PCI to:

	pciinit -x13 -iAA.BB.CC.DD

(13 = 8 + 5).
-- 

Doug Klein
Network Computing Devices
uunet!lupine!klein