»

[BenShep]

Been having a spot of trouble setting up Amitcp 4.22 with a 3com Etherlink III 3c589d PCMCIA network card on an Amiga 600.

This is from a fresh install of workbench 2.1.

I downloaded the 3c589.device driver from aminet, ran the installer and everything worked ok. The driver is located in :devs\network as it should be.

Then I used the 2 AmiTCP disks to install AmiTCP - this went ok also, up to the point when I had to select an Ethernet driver. The 3c589 didn't show up in the list of drivers to select. Startnet just bombs out with "AmiTCP couldnt be started".

Also additionally, the link light on the 3c589d is on from the moment I plug it it - is this normal? I've tried a few different cards (of the same type) and the light is on for all of them - hopefully this isn't a sign of some fault with the pcmcia slot.

So this is basically the point I'm up to - do I need to edit a file or do something differently? Anyone have any hints/tips/pointers?

[dawiper]

Dont know much about AmiTCP. Did the pccard.library end up in LIBS:?
Regarding the 3c589d light.
Yes it should be on from the moment you insert the card.
I have the exact same card myself, and the driver worked without a hassle for me.
Btw, If the card is connected to a switch/hub, the "connected" light on that side will not be lit until Amitcp/Miami/Genesis are online.

[Piru]

Then I used the 2 AmiTCP disks to install AmiTCP - this went ok also, up to the point when I had to select an Ethernet driver. The 3c589 didn't show up in the list of drivers to select.

That's quite understandable since the 3c659 driver is 3rd party one, how the installer is supposed to know about it?

You need to manually configure AmiTCP to use it.

[BenShep]

Good that the link light thing is normal, yes pccard.library is in :LIBS. You're right about the link light on the hub not being up also.

Piru: I was thinking it used a script to scan the :devs\network folder - or it retrieved the info about the card from something the 3c589.device installer installed.

So if this what I need to do - how do I manually configure AmiTCP to become aware of the 3c589 device?

[dawiper]

Doesn't Amitcp find them by itself like genesis/miami?

[BenShep]

dawiper: I would have thought so.. but apparently not.

I'd consider using miami, but I'm using an a600 - so need all the memory I can get (don't want to install MUI, etc). No PCMCIA memory to use as yet either.

[dawiper]

When I think some more about it, with miami/genesis you have to select the right driver thru a file requester...

[fragment]

This is what I have in my amitcp:db/interface file (just add the line in the bottom)

3c589 dev=devs:networks/3c589.device unit=0

and in amitcp:bin/startnet edit at least this:

.def IFACE 3c589

[BenShep]

Yep fixed this, but no good result.

Might downgrade to an earlier version of amitcp and see if that works.

[ncafferkey]

BenShep wrote:
Yep fixed this, but no good result.

What happens when you try to start it? What's in your startnet script?

[arven-pl]

i've got the same problem:

Under Miami32b everything works fine.. i can login online, ping, use irc..

But i wanted to save some precious RAM so i decided to try AmiTCP.. i have 2 versions (AmiTCP3.0b2 and 4.2) and one problem.. i can't login online.. i can only ping my router and computer's in my network.

My config file's look like this:

----------
Interfaces
----------

eth0 DEV=DEVS:networks/3c589.device UNIT=0
and i tryed name it:
eth DEV=DEVS:networks/3c589.device UNIT=0
--------
startnet
--------

run AmiTCP:AmiTCP
WaitForPort AMITCP
; configure loop-back device
AmiTCP:bin/ifconfig lo0 127.0.0.1
; Configure Devs:Networks/3c589.device unit 0
AmiTCP:bin/ifconfig eth0 inet 192.168.0.156 192.168.0.1 netmask 255.255.255.0
; Add route to this host
AmiTCP:bin/route -v add ami.dom localhost
; Add route to the default gateway
AmiTCP:bin/route -v add default 192.168.0.1
Assign TCP: Exists > NIL:
IF Warn
Mount TCP: from AmiTCP:devs/Inet-Mountlist
EndIf
; Start the internet `super server'
run AmiTCP:bin/inetd

my other combinations:

AmiTCP:bin/ifconfig lo0 localhost
AmiTCP:bin/ifconfig eth0 192.168.0.156 192.168.0.1 netmask 255.255.255.0
AmiTCP:bin/ifconfig DEVS:networks/3c589.device 192.168.0.156 192.168.0.1 netmask 255.255.255.0
--------------------------
user-startup (AmiTCP part)
--------------------------

;BEGIN AmiTCP/IP
assign AmiTCP: System:AmiTCP
path AmiTCP:bin add
AmiTCP:bin/login -f root >"con:*/*/*/200/AmiTCP-IP Login/AUTO/CLOSE/WAIT"
AmiTCP:bin/umask 022
;END AmiTCP/IP

so what is wrong :-?

[Argus]

@arven-pl
@BenShep

Have you tried using Miami without the mui interface, it uses gadtools.library instead. I believe it uses a lot less memory. Worth a shot.

[patrik]

@arven-pl:

Try:
AmiTCP:bin/ifconfig eth0 inet 192.168.0.156 netmask 255.255.255.0

instead of the current:
AmiTCP:bin/ifconfig eth0 inet 192.168.0.156 192.168.0.1 netmask 255.255.255.0

As mentioned in the other thread, AmiTCP might get confused as an ethernet interface is not of point-to-point type and should thus not have a destination ip specified. So if you havent tried this - try it .

You could also try to remove the line:
AmiTCP:bin/route -v add ami.dom localhost

as it should not be needed and might cause issues if ami.dom isn't in the hosts file.


/Patrik