Welcome, Guest. Please login or register.

Author Topic: AmiTCP  (Read 2225 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline HodgkinsonTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2006
  • Posts: 1080
    • Show only replies by Hodgkinson
    • http://www.myspace.com/em_radiation *****and ***** www.booni.info
AmiTCP
« on: April 05, 2006, 03:32:25 PM »
Can anyone out there please give me a idea where to go with AmiTCP, after installing it to HD, in order to get it to work with a 3COM PCMCIA network card?

I figure that there is probably a file that needs modifiying to make the program configurable, and there is somthing to do with ifconfig I believe.

I already have the 3COM drivers for the card (From AmiNet) installed, as well as SMBFS.
The card is already wired up to a network (Via a hub) consisting of Windows PC's.

Any help much appreciated.
Main A1200D: WB3.0, 3.1 ROMs, 2GB HDD, Blizzard 1230IV (64MB RAM + FPU) and a whole load of custom heatsinks... :flame:
 

Offline Thomas

Re: AmiTCP
« Reply #1 on: April 05, 2006, 03:53:56 PM »

Reading the docs may help, I guess.

Bye,
Thomas

Offline leofoe

  • Sr. Member
  • ****
  • Join Date: Jun 2005
  • Posts: 499
    • Show only replies by leofoe
Re: AmiTCP
« Reply #2 on: April 05, 2006, 04:21:52 PM »
If you have the 4.0 demo version:
1. Install 3c589.device in DEVS:networks/
2. Install pccard.library in LIBS:
3. Install AmiTCP
4. Run AMitTCP config
5. Add in Amitcp:db/interfaces:
"3c589 DEVS=DEVS:networks/3c589.device"
5. Alter in AmiTCP:bin/startnet the installed/configured interfacename in:
"3c589 " i.e. "3c589 192.168.1.10"
6. Try to ping your router or any other machine in your network. From the CLI: "ping " i.e. "ping 192.168.1.1"

If you have the commercial 4.2 version, then change line 5 in: Alter in AmiTCP:bin/startnet the installed/configured interface behind .def IFACE in "3c589"

Come back here if that works. And also if it doesn't. And tell us what you did and what your Amiga says.
We're going to use smbfs only if this worked!
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: AmiTCP
« Reply #3 on: April 05, 2006, 05:12:37 PM »
News: Software : AmiTCP 3.0b2 Installation guide

This guide applies to the GPL AmiTCP/IP v3.0b2.
 

Offline HodgkinsonTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2006
  • Posts: 1080
    • Show only replies by Hodgkinson
    • http://www.myspace.com/em_radiation *****and ***** www.booni.info
Re: AmiTCP
« Reply #4 on: April 06, 2006, 11:34:07 AM »
Yep, im trying to set up AmiTCP 3.0b2.

There is some screens in the setup guide that I havent seen before - Think i'll re-install it in exactly the same way that he has done just to see if they will appear.

PS. I also had problems with the installer script as mentioned in the guide, couple of file addresses had a / (I think) in front of them, causing errors; and some of the files required were in the DISK2.DMS file.

 :getmad:  Is it just me or do most thinks need tweaking before they'll work ??? !
Main A1200D: WB3.0, 3.1 ROMs, 2GB HDD, Blizzard 1230IV (64MB RAM + FPU) and a whole load of custom heatsinks... :flame:
 

Offline Ilwrath

Re: AmiTCP
« Reply #5 on: April 06, 2006, 12:13:32 PM »
Quote
Is it just me or do most thinks need tweaking before they'll work ??? !


Well, especially when the thing in question is an ancient port of a GPL clone of a BSD stack.  ;-)

Actually, it works remarkably well when you take that into consideration.  :-)  Combined with ppp.device, it gave me stable dial-up access for a good 6 years or so before cablemodem became available.  Take a look at the dates in AmiTCP 3.0b2 and tell me of any computer back in that era that was EASIER to connect to the internet.  ;-)

 

Offline patrik

Re: AmiTCP
« Reply #6 on: April 27, 2006, 06:44:27 PM »
@Hodgkinson:

The guide does not use or depend on anything in a disk archive with the name DISK2.DMS.

Just download AmiTCP3.0b2 from the top of the guide and follow it from the beginning to the end.


/Patrik
 

Offline HodgkinsonTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2006
  • Posts: 1080
    • Show only replies by Hodgkinson
    • http://www.myspace.com/em_radiation *****and ***** www.booni.info
Re: AmiTCP
« Reply #7 on: April 27, 2006, 08:24:50 PM »
Slight problem...
The HDD in the A1200 Desktop machine that I have been attempting to set the 3COM card and AmiTCP up on has died  :boohoo:
(P.S. HDD tried in a different A1200 desktop machine - Still appears dead...)

Fortunately, I also have a A1200 Tower with the files that I have been using backed up on; but this machine can't be used with the 3COM card since the internal PCMCIA port also appears to be duff - Seems to be due to an iron filing that somehow landed across the PCMCIA port pins (Any ideas how to fix it or how to acquire a PCMCIA port & buffer schematic???)

Seems I’ll have to get round to dismantling the both the A1200 tower and desktop machine and interchanging the main boards (!!!), or if someone could point me to a source of A2065 boards that would be much appreciated.

Sorry folks to all of you who were watching this space in the hope of some success - It might just take some time now.
Main A1200D: WB3.0, 3.1 ROMs, 2GB HDD, Blizzard 1230IV (64MB RAM + FPU) and a whole load of custom heatsinks... :flame:
 

Offline HodgkinsonTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2006
  • Posts: 1080
    • Show only replies by Hodgkinson
    • http://www.myspace.com/em_radiation *****and ***** www.booni.info
Re: AmiTCP
« Reply #8 on: August 25, 2006, 05:04:57 PM »
I DONT BELIEVE IT!!!

Anyway, for those of you who might of bookmarked this page, I've just got the 3c589 3COM network card, AmiTCP3.0b2, and SMBFS to work cross-amiga-PC.

The AmiTCP install guide helped a LOT, and I should note that in order to get SMBFS to recoginse the host names, they need to be entered in the AmiTCP:db/hosts file before they'll work. I know that the SMBFS documentation implies that host names should just work, but with this configuration that just doesn't seem to be the case.

Thanks all,
Hodgkinson.
Main A1200D: WB3.0, 3.1 ROMs, 2GB HDD, Blizzard 1230IV (64MB RAM + FPU) and a whole load of custom heatsinks... :flame: