Welcome, Guest. Please
login
or
register
.
Forums
Forums
Board
Topic
Home
Today's Posts
Gallery
Login
Register
Amiga.org
»
Amiga computer related discussion
»
Amiga Hardware Issues and discussion
»
prism2.device and Netgear MA401
« previous
next »
Print
Pages: [
1
]
Go Down
Author
Topic: prism2.device and Netgear MA401 (Read 3487 times)
Description:
0 Members and 1 Guest are viewing this topic.
x56h34
Hero Member
Join Date: Sep 2003
Posts: 2921
Re: prism2.device and Netgear MA401
«
on:
April 20, 2005, 07:08:50 PM »
This is probably due to the PCMCIA A1200 reset bug.
You can fix this with BlizKick as well, by downloading CardReset and CardPatch from Aminet. Those are modules for BlizKick which you will need to put in your BlizKick line.
That's an easy way to fix the PCMCIA problem. Another solution is the hardware mod. :-)
Logged
x56h34
Hero Member
Join Date: Sep 2003
Posts: 2921
Re: prism2.device and Netgear MA401
«
Reply #1 on:
April 20, 2005, 07:47:55 PM »
DjBase's suggestion works too. :-)
Since you are already using BlizKick, I guess it's kind of neater to insert an extra module or two into your BlizKick line, other than to run separate little programs as well as your BlizKick line. :-)
Logged
x56h34
Hero Member
Join Date: Sep 2003
Posts: 2921
Re: prism2.device and Netgear MA401
«
Reply #2 on:
April 20, 2005, 08:33:30 PM »
Is the WiFi card worth getting? I'd assume that speed would be about the same as a regular PCI/Zorro ethernet card.
I think that we definitely need some better wireless support for Amiga in the PCI card form (Elbox) or Zorro (Jens/Individual Computers).
I wish only that if Elbox releases such a card that they will not pull a "Spider" with it, e.g. force a propriatery product on Mediator users which should actually be free of such things as the whole point is to be able to buy cheap ($10-$20 range) off the shelf cards.
Logged
Print
Pages: [
1
]
Go Up
« previous
next »
Amiga.org
»
Amiga computer related discussion
»
Amiga Hardware Issues and discussion
»
prism2.device and Netgear MA401
There was an error while thanking
Thanking...