Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: motorollin on August 22, 2006, 09:31:19 PM
-
fx has kindly provided me with an AmiTCP boot disk. It has a cut down installation of AmiTCP/IP on it. I am trying to configure the interface so it uses FastEthernet.device, but I can't find which file to edit. The installer isn't included on the disk to configure it that way. Can anyone tell me where to find the correct config file? I've searched all the directories but can't find it anywhere.
Thanks
--
moto
-
Oooh think I found it in AmiTCP:db/
--
moto
-
Yes, it is in the db directory. If you want to change ip, it is changed in db/Provider.conf. There you also can change which interface you use, if you rename the interface in the interfaces file, but that would be unecessary.
/Patrik
-
I've edited the interfaces file to add the fastethernet.device, and changed Provider.conf to use the new interface and use the correct IP configuration. But when I run startnet it just hangs when trying to obtain the hostname. Any thoughts?
--
moto
-
Do you have all of the Mediator stuff (pci library, etc.) on the disk?
-
I've got pci.library in LIBS: and pciinfo in C:. I don't know what else I need. If I type pciinfo in to the shell then it lists the cards but not the names for some reason. (They show as unknown)
--
moto
-
Ok, I changed the local host's IP address in the hosts file to match the interface's IP address and it now goes online with no errors. However, I can't ping anything on my network (no replies). I can ping the machine's own IP address, but not the gateway. I know the IP configuration and cabling is ok as I can access the network when I boot in to OS3.9 :-(
--
moto
-
Yes, you need to add the right ip in the db/hosts file, so a hostname corresponds to the ip.
As you can ping your own ip-adress on the Amiga, it sounds like AmiTCP in itself works fine, but there is some issue with the device or something. Have you entered the device name as "FastEthernet.device" with a big F and E in the interfaces file? The case of the letters matter for devices.
Btw, if it is a 100Mbit card, I think Picasso96 needs to be running. Those cards need buffer data in vram, as that is the only place pci-cards (the network card) can dma to/from as the motherboard space is a no-no, and correct me if I am wrong, but I think I read somewhere that they need Picasso96 running to allocate that memory.
/Patrik
-
I'll check the capitalisation, though I suspect the problem is linked to not being able to see the names of the PCI devices in pciinfo. I'll have a look at the Mediator installer and see what it copies in case I missed something.
--
moto
-
Use your EasyNet archive to configure the TCP stack for FastEthernet.
-
@amigakit:
Does EasyNet work with AmiTCP 4.3?
/Patrik
-
Hmmm, I don't think EasyNet will fit on a floppy disk will it?
--
moto
-
@moto:
Did you read that P96 part I edited in just after posting earlier?
/Patrik
-
@Patrik
Just read your updated comment. If it does need P96 running then I'll have to use a boot CD instead of a floppy. I'll check the other bits first anyway.
--
moto
-
I've just checked and everything from the Mediator System FIles folder on the Elbox driver CD is on the floppy, but it still shows all the cards as "Unknown". Even without P96 running, my OS3.9 install recognises all the cards when I run pciinfo. Do you think that could be related to the problem with the network card?
--
moto
-
motorollin wrote:
I've just checked and everything from the Mediator System FIles folder on the Elbox driver CD is on the floppy, but it still shows all the cards as "Unknown". Even without P96 running, my OS3.9 install recognises all the cards when I run pciinfo. Do you think that could be related to the problem with the network card?
--
moto
I had the same problem with my Mediator PCI 1200. It didn't see any of my cards. They all came back in PCIInfo as 'Unknown Devices' :-? . I returned the board to the seller and he send me a new one which was working.
Here is what my Pciinfo showed me:
Pci Device 1:
VendorID: $ffff
VendorName: Unknown
DeviceID: $100f
DeviceName: Unknown
ClassCode: $100fff
RevisionID: $ff
InterruptPin: 0
SubsystemVendorID: $ffff
SubsystemID: $100f
Pci Device 2:
VendorID: $121a
VendorName: 3dfx Interactive Inc
DeviceID: $1007
DeviceName: Unknown
ClassCode: $120000
RevisionID: $1
InterruptPin: 2
SubsystemVendorID: $121a
SubsystemID: $1005
MemSpace0: $84000000 - $89ffffff
MemSpace1: $80000000 - $83ffffff
MemSpace3: $f0000000 - $dfffffff
MemSpace4: $f0000000 - $dfffffff
MemSpace5: $f0000000 - $dfffffff
RomSpace: $dfa20000 - $4f72ffff
Pci Device 3:
VendorID: $ffff
VendorName: Unknown
DeviceID: $100f
DeviceName: Unknown
ClassCode: $100fff
RevisionID: $ff
InterruptPin: 0
SubsystemVendorID: $ffff
SubsystemID: $100f
Pci Device 4:
VendorID: $ffff
VendorName: Unknown
DeviceID: $100f
DeviceName: Unknown
ClassCode: $100fff
RevisionID: $ff
InterruptPin: 0
SubsystemVendorID: $ffff
SubsystemID: $100f
It looks like your card is broken or not connected properly.
-
No, the Mediator works fine when I boot OS3.9. In the end I made a copy of a Workbench disk and installed the Mediator drivers on to it properly. Then PCIInfo correctly reported all of the cards. I then incorporated fx's network bootdisk in to the Workbench disk, booted from the disk, started AmiTCP, and hey presto I can map drives with smbfs to my MacBook from the floppy :-D
--
moto