[comp.protocols.tcp-ip.ibmpc] Cant start ka9q

JPHD@FRSAC11.BITNET (07/26/89)

Can some kind soul really help me ?

I am trying to install the "ka9q" networking software on my AT.
The outfit:

IBM PC AT3 with 640k and 30M
VEGA VGA card, with IBM monochrome vga display.
TOPS Fashcard. 2.1 (soft not yet installed, but card installed)

3com 3c503 card
3com 3c501 card
ka9q that I ftp'ed from clarkson.edu, beginning of this july.

I use the packet drivers, as the net.exe I have does not have the
3c501 internal driver option. (When I got TC 2.0 I will retry,
this will take probably too long...)

(Note 1: I tried the whole thing with only the 3c503 installed
(card & driver), and got the same results)

(Note 2: I tried to run NCSA with the same driver, for the 3c503 card
only, and the thing just freeze... ctrl-alt-del wont work... off/on
is the only realthing.... I have no luck with network or what?)

Here are the trace and content of all involved files.

=============================================================================
%%%%%% autoexec.bat
@echo off
path c:\;c:\dos;c:\bin;c:\word;c:\games;c:\turboc;c:\msc;c:\ka9q\bin;c:\ncsatn\d
keyb fr 850 c:\dos\keyboard.sys
prompt $p$g
set HACK=MonsterMagyc
set HACKDIR=c:\games\
set HACKLEVELS=c:\games\
set HACKSAVE=c:\games\hack.sav;noprompt
set INCLUDE=c:\include
set LIB=c:\lib
c:\bin\dosedit

%%%%%% config.sys
device = rambios.sys
device = vegaansi.sys
break=on
device=\games\nansi.sys
shell=command.com/p/e:1024
country=033,,\dos\country.sys
files=30
buffers=32

%%%%%% driver.bat
c:/ka9q/drivers/3c503 0x7c 3 0x300
c:/ka9q/drivers/3c501 0x7d 4 0x310

%%%%%% output from driver.bat
Packet driver for 3-Com 3C503, version 3.1
Portions Copyright 1989, Robert C. Clements, K1BC
Packet driver skeleton copyright 1988-89, Russell Nelson.
This program is free software; see the file COPYING for details.
NO WARRANTY; see the file COPYING for details.

Packet interrupt number 0x7C (124)
Interrupt number 0x3 (3)
I/O port 0x300 (768)
My Ethernet address is 02:60:8C:0D:A1:FF
Packet driver for the 3COM 3C501, version 3.0
Portions Copyright 1988 Phil Karn
Packet driver skeleton copyright 1988-89, Russell Nelson.
This program is free software; see the file COPYING for details.
NO WARRANTY; see the file COPYING for details.

Packet interrupt number 0x7D (125)
Interrupt number 0x4 (4)
I/O port 0x310 (784)
Using 80[123]86 I/O instructions.
My Ethernet address is 02:60:8C:47:17:35

%%%%%% autoexec.net (1)
hostname jasmin.cea.fr
#
ip address [128.1.65.3]
#
attach packet 0x310 0x7d arpa lan 5 1500
#
route add default lan
#
ip ttl 16
#
tcp mss 216
#
tcp window 432
#
log c:\net.log
#
start smtp
start ftp
start echo
start discard
start telnet

%%%%%% output from net.exe, with above autoexec.net (1)
KA9Q Internet Protocol Package, v890421.1 DS = 53f9
Copyright 1988 by Phil Karn, KA9Q
NET/ROM Support Copyright 1989 by Dan Frank, W9NK
No packet driver loaded at int 0x310
Could not attach packet driver
Interface "lan" unknown
net> exit

%%%%%% autoexec.net (2)
hostname jasmin.cea.fr
#
ip address [128.1.65.3]
#
attach packet 0x300 0x7c arpa lan 5 1500
#
route add default lan
#
ip ttl 16
#
tcp mss 216
#
tcp window 432
#
log c:\net.log
#
start smtp
start ftp
start echo
start discard
start telnet

%%%%%% output from net.exe, with above autoexec.net (2)
KA9Q Internet Protocol Package, v890421.1 DS = 53f9
Copyright 1988 by Phil Karn, KA9Q
NET/ROM Support Copyright 1989 by Dan Frank, W9NK
No packet driver loaded at int 0x300
Could not attach packet driver
Interface "lan" unknown
net> exit
==========================================================================

        +--------------------------------------------------+
        | Jean-Pierre H. Dumas                             |
        |                                                  |
        |    jphd@frsac11 (bitnet)                         |
        |    jphd%frsac11.bitnet@cunyvm.cuny.edu (arpanet) |
        |    dumas@sumex-aim.stanford.edu (arpanet)        |
        +--------------------------------------------------+

skl@van-bc.UUCP (Samuel Lam) (07/27/89)

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

hoffman@vax.cs.pittsburgh.edu (Bob Hoffman) (07/27/89)

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.

broehl@watdcsu.waterloo.edu (Bernie Roehl) (07/29/89)

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]