Welcome, Guest. Please login or register.

Author Topic: Another wireless PCMCIA success story  (Read 3371 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline patrik

Re: Another wireless PCMCIA success story
« on: June 14, 2006, 10:15:32 AM »
@AmiBiL0:

The A1200 has a 020, so if MiamiDX is checking for atleast an 020, it should be able to install.

However, AmiTCP is faster, consumes less memory (which is at premium in a stock A1200) and has no time-limit. The only downside to using AmiTCP is if you absolutely _must_ use DHCP for automatic assigning of the A1200s ip address. But it is only in a situation where you don't have your A1200 on your own local network where there is a possibility that you can't use a static ip address.

If you follow this guide to the letter, you will have a working AmiTCP installation.

For the prism2.device to work properly, you just need to put pccard.library in LIBS: , prism2.device in DEVS:Networks/ , CardReset in C: and add the line "Run >NIL: C:CardPatch" to your S:Startup-Sequence file, just after the C:SetPatch line.


/Patrik
 

Offline patrik

Re: Another wireless PCMCIA success story
« Reply #1 on: June 14, 2006, 04:52:41 PM »
@Matt_H:

I dare you to try the guide I linked to earlier! :-D It might not be foolproof, but it makes it quite easy.

Why not give the guide a shot and install AmiTCP on your A600 - I guarantee you it will leave you with a large part of the memory free :-).


/Patrik
 

Offline patrik

Re: Another wireless PCMCIA success story
« Reply #2 on: June 14, 2006, 06:05:15 PM »
@Matt_H:

Aah, 4.3 is actually really nice/easy to install if you have one of the presupported cards.

If not, I usually just install it and select I have a A2065 card and when the install is done, just change the a2065 line in AmiTCP:db/interfaces to point to the right device.

The deluxe-version would be to change the interface name by also editing the AmiTCP:db/Provider.conf file :-D.

A tad bit less work than 3.0b2!


/Patrik