Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!ubc-cs!van-bc!skl
From: skl@van-bc.UUCP (Samuel Lam)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Cant start ka9q
Summary: The "attach" command for different drivers take different parameters.
Keywords: KA9Q, NET.EXE, Packet Driver
Message-ID: <201@van-bc.UUCP>
Date: 27 Jul 89 10:14:38 GMT
References: <8907261031.aa05467@louie.udel.edu>
Organization: Balliffe International, Vancouver, B.C., Canada
Lines: 17

In article <8907261031.aa05467@louie.udel.edu>, JPHD@FRSAC11.BITNET wrote:
>attach packet 0x310 0x7d arpa lan 5 1500

In net.exe, if you just type "attach packet", it will give the
usage syntax as something like:

	attach packet <int#> <label> <buffers> <mtu>

which means what you really want in your autoexec.net file is probably:

	attach packet 0x7d lan 5 1500

I don't know if this is all the problems, but at least it's one of them.

...Sam
-- 
Samuel Lam     {alberta,watmath,uw-beaver,cs.ubc.ca}!ubc-cs!van-bc!skl