Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!sun.soe.clarkson.edu!nelson From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: NCSA and Novell Message-ID: Date: 25 Apr 89 02:32:37 GMT References: <8904190744.aa29039@louie.udel.edu> Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu Organization: Clarkson University, Postdam NY Lines: 19 In-reply-to: DOBEIRNE@IRLEARN.BITNET's message of 18 Apr 89 16:56:51 GMT In article <8904190744.aa29039@louie.udel.edu> DOBEIRNE@IRLEARN.BITNET (Dermot O'Beirne) writes: I have a 3c501.COM from Phil Karn originally. Give Phil the credit, but blame me for the bugs. I run 3c501 with 0x60 3 0x300 as the parameters. That sounds good to me, but you might try it with values other than 0x60, as some of the interrupts between 0x60 and 0x80 are used by other software. I am not sure if I am giving the right parameters to the 3c501.com. Is there any documentation explaining how to invoke the packet driver. Each of the packet drivers will emit a usage: line if invoked without any parameters. If invoked with one parameter (the software interrupt used to communicate with it), then the interrupt, I/O port, etc. default to the manufacturers defaults. In other words, there is no documentation. Given the amount of trouble people have, I need to write some. -- --russ (nelson@clutx [.bitnet | .clarkson.edu]) America -- Socialism for the rich people, Capitalism for the rest of us. -- Michael Harrington, Co-Chair, Democratic Socialists of America