Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!vax.cs.pittsburgh.edu!hoffman
From: hoffman@vax.cs.pittsburgh.edu (Bob Hoffman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Cant start ka9q
Message-ID: <CMM.0.88.617555335.hoffman@vax.cs.pittsburgh.edu>
Date: 27 Jul 89 15:08:55 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

The relevant lines from the original message are:

> %%%%%% autoexec.net (1)
> attach packet 0x310 0x7d arpa lan 5 1500
>
> %%%%%% output from net.exe, with above autoexec.net (1)
> No packet driver loaded at int 0x310

> %%%%%% autoexec.net (2)
> attach packet 0x300 0x7c arpa lan 5 1500
>
> %%%%%% output from net.exe, with above autoexec.net (2)
> No packet driver loaded at int 0x300

The problem is improperly-formed "attach" lines.  The hardware address
of the interface is only used when starting the packet driver itself.
NET needs to know only the software interrupt number.  Also, the keyword
"arpa" is redundant and should not be used.  Therefore, in autoexec.net (1)
the line should read:

attach packet 0x7d lan 5 1500

and in autoexec.net (2) the line should read:

attach packet 0x7c lan 5 1500

	---Bob.