Xref: utzoo comp.dcom.lans:7190 comp.protocols.tcp-ip.ibmpc:4858 comp.sys.ibm.pc.hardware:5238 comp.unix.xenix.misc:99 comp.unix.xenix.sco:1634
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!klefstad
From: klefstad@ux1.cso.uiuc.edu (Sue Klefstad)
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc.hardware,comp.unix.xenix.misc,comp.unix.xenix.sco
Subject: Re: 3c503 etherus interruptus
Message-ID: <1991Feb7.144231.1699@ux1.cso.uiuc.edu>
Date: 7 Feb 91 14:42:31 GMT
References: <1991Feb3.225956.28698@m2xenix.psg.com>
Organization: University of Illinois at Urbana
Lines: 20

news@m2xenix.psg.com (Randy Bush) writes:

>I am having problems with 3c503s interfering with serial ports, both in Xenix
>and MS-DOS.  I believe it has to do with interrupts. 
>....
>If I use NCSA ftp or telnet with CONFIG.TEL saying to use Int-2, both of the
>serial ports (COM1: and COM2:) are useless (by my interrupt-driven FOSSIL
>software) until I power cycle the box (no reset button available).

>The same software with a 3c501 jumpered for Int-2 causes no problems.

The 3C503 defaults to interrupt 3.  If you're using a DEVICE=ETH503.SYS
in your config.sys, you'll need to specify interrupt 2 there:
DEVICE=ETH503.SYS /I:2

-- 
-- Sue
--
=========================================================================
Sue Klefstad    Ill. Natural History Survey    klefstad@uiuc.edu