Path: utzoo!attcan!utgpu!watmath!maytag!watdcsu!broehl
From: broehl@watdcsu.waterloo.edu (Bernie Roehl)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Cant start ka9q
Message-ID: <6155@watdcsu.waterloo.edu>
Date: 28 Jul 89 18:13:24 GMT
References: <8907261031.aa05467@louie.udel.edu>
Reply-To: broehl@watdcsu.waterloo.edu (Bernie Roehl)
Organization: U. of Waterloo, Ontario
Lines: 28

In article <8907261031.aa05467@louie.udel.edu> JPHD@FRSAC11.BITNET writes:
>Can some kind soul really help me ?
>
>c:/ka9q/drivers/3c503 0x7c 3 0x300
...
>Packet interrupt number 0x7C (124)
>Interrupt number 0x3 (3)
>I/O port 0x300 (768)
...
>attach packet 0x310 0x7d arpa lan 5 1500

The correct syntax for this line should be:

attach packet 0x7c lan 5 1500

You can find this by typing "attach packet ?".  Note that the <int#> is
the *packet* interrupt number, not the hardware interrupt number (i.e.
is 0x7C, not 0x3).  Since you're going through the packet driver interface,
the higher-level software doesn't need to (and therefore shouldn't) know
anything about the hardware address or hardware interrupt number.

Hope this helps...

-- 
	Bernie Roehl, University of Waterloo Electrical Engineering Dept
	Mail: broehl@watdcsu.UWaterloo{.edu,.csnet,.cdn}
	BangPath: {allegra,decvax,utzoo,clyde}!watmath!watdcsu!broehl
	Voice:  (519) 745-4419 [home]  (519) 885-1211 x 2607 [work]