Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!bellcore-2!bellcore!cellar.bae.bellcore.com!louie
From: louie@cellar.bae.bellcore.com (Paul Louie)
Newsgroups: comp.dcom.lans
Subject: 3com ethernetcard + SCO TCP/IP
Message-ID: <27886@bellcore.bellcore.com>
Date: 15 Oct 90 18:35:31 GMT
Sender: news@bellcore.bellcore.com
Reply-To: louie@cellar.bae.bellcore.com (Paul Louie)
Organization: Bell Communications Research
Lines: 29

In article <7947@star.cs.vu.nl> vdp@cs.vu.nl (=Ronald van der Pol) writes:

>I have some problems with a 3COM 503 Ethernet card. It only
>seems to work with SCO UNIX 3.2.0 TCP/IP (Lachmann) when I
>use the default IRQ vector of 2. When I try to set the IRQ 
>to 5 it doesn't work (e.g. when I install the Unix e3B driver). 
>Should I use some additional (MS-DOS??) setup software? 
>(there is no interrupt conflict!)

Ron,

	By setting the IRQ5 you've conflicted with the floppy controller.
Each machine can use IRQs differently, but the industry's practice has
been:
	IRQ1 - timer
	IRQ2 - Whatever, according to the manufacturer
	IRQ3 - COM2
	IRQ4 - COM1
	IRQ5 - Floppy
	IRQ6 - LPT2
	IRQ7 - LPT1
	IRQ9-13 - Whatever, according to the manufacturer
	IRQ14 - HD Controller
	IRQ15 - Again, whatever.

You can make it easy for yourself by picking the "well known" interrupts
or you can buy programs, such as Checkit, to find out if an IRQ is in use.
If it's up to me, I'll use one of the well known ones even if it means
that I have to remove one of the ports.