Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: flaviosr on March 04, 2007, 06:54:12 PM
-
Hello to everybody,
I've been told that the NetGear MA-401 can work with my A1200, so that I can connect her to my Zyxel router and from there to internet and to my PCs (using Amiga explorer)... true? :-?
If so, where can I download the drivers and docs? :-?
Another problem... I still have OS3.1... is it enough? :oops:
Right now I cannot install OS3.9 since I do not have a CD-ROM yet... :-(
Thank you and ciao to everybody
-
Yes, as long as you install and setup driver and TCP/IP stack properly.
Look for prism2.device on aminet.
Here is the latest aminet (http://aminet.net/hard/drivr/prism2.lha)
-
Thanx!!! :-D
Downloaded!!!
Now I have to find a card but...
do you have a link to a site where there is a help to configure the A1200 for TCP-IP (remember... OS3.1...)?
Ciao and thank you again
-
I never got mine to work, even with the latest drivers.
Machine locks up when trying to get online with Miami :(
Check topic here:
http://www.amiga.org/forums/showthread.php?t=20912
Good luck!
-
I'm using a NetGear MA401 card on my A1200 and it works great with Miami for me.
-
do you have a link to a site where there is a help to configure the A1200 for TCP-IP (remember... OS3.1...)?
search: amitcp installation guide (http://www.amiga.org/search.php?query=amitcp+installation+guide&action=results)
-
fryguy wrote:
I'm using a NetGear MA401 card on my A1200 and it works great with Miami for me.
Seconded. The only issue I have is only having WEP support while my home wireless is WPA. So I have a WAP11 for the 1200, and a WAP54G for everything else, each on non-overlapping channels.
-
Just add - yeah it does work fine for me also with wep.
Just make sure and follow readme instructions. if you run into problems google - this issue has been beaten too death... :-D
-
terminator4 wrote:
Just make sure and follow readme instructions. if you run into problems google - this issue has been beaten too death... :-D
And that's really the key -- follow the instructions with prism2.device.