Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline Matt_HTopic starter

Another wireless PCMCIA success story
« on: June 14, 2006, 01:55:20 AM »
Just got my 1200 online with a Proxim Orinoco Silver (8420-WD - a rebranded Agere 0110).

Make sure to install the HermesII chipset firmware. I thought I didn't need it; several headaches later, I realized I did.
 

Offline AmiBiL0

  • Newbie
  • *
  • Join Date: May 2006
  • Posts: 31
    • Show only replies by AmiBiL0
Re: Another wireless PCMCIA success story
« Reply #1 on: June 14, 2006, 08:31:00 AM »
Matt_H
do you think I need the same driver for my orinoco gold?
do you have a normal A1200 or you#re using some accell on it?
My version of miamidx wont install as it check for a 020 at least.
Do you have a demo copy that works with a normal 1200?

thanx for your help on my post as well

BiL0
 

Offline patrik

Re: Another wireless PCMCIA success story
« Reply #2 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 Matt_HTopic starter

Re: Another wireless PCMCIA success story
« Reply #3 on: June 14, 2006, 04:10:54 PM »
@ patrik

Miami has the advantage, however, of being about 25 times easier to configure :-)

@ AmiBiL0

Contrary to what I may have said earlier, it may be possible that 2MB of RAM just isn't enough. I've been trying to get my 2MB A600 online, and it just isn't working. Low memory is my best working theory.
 

Offline patrik

Re: Another wireless PCMCIA success story
« Reply #4 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 Matt_HTopic starter

Re: Another wireless PCMCIA success story
« Reply #5 on: June 14, 2006, 05:49:54 PM »
@ patrik

Heh. I do have AmiTCP installed,but it's the 4.3 commercial version (significantly different configuration method). Maybe I'll give it a shot :-)
 

Offline patrik

Re: Another wireless PCMCIA success story
« Reply #6 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
 

Offline scap61

  • Newbie
  • *
  • Join Date: Jun 2006
  • Posts: 5
    • Show only replies by scap61
Re: Another wireless PCMCIA success story
« Reply #7 on: June 17, 2006, 04:31:36 PM »
hello world  i'm from italia and
i'm testing a compaq wl110 16bit pcmcia card on my a1200
the card work well on pc
i have inserted the line
Run >NIL: C:CardPatch" to your S:Startup-Sequence file, just after the C:SetPatch line.
but when i test the device with this command
sanautil device prism2.device status
i take this error:
can't open device networks/prism2.device unit
error: device open failure
sanautil: sanautil failed with code 10
can you tell me how i can use card reset ??

thanks
 

Offline scap61

  • Newbie
  • *
  • Join Date: Jun 2006
  • Posts: 5
    • Show only replies by scap61
Re: Another wireless PCMCIA success story
« Reply #8 on: June 17, 2006, 04:37:57 PM »
excuse me but i have missed my configuration
a1200 with 3.1 rom (hardware)
o.s. 3.1
blizzard 1240t with 32mb of fast ram
four ide card with idefix with 3 hd and a cdrom
the pcmcia slot i think work well because i have burned a cd with a surfsquirrel and an yamaha scsi burner 8x4x24x

thanks
 

Offline Matt_HTopic starter

Re: Another wireless PCMCIA success story
« Reply #9 on: June 17, 2006, 04:43:57 PM »
@ Patrik

Yep. With a little trial and error (and a bugfixed version of the device from Neil Cafferkey), I got 4.3 configured and online.

@ scap61

Do the same thing for CardReset that you did for CardPatch. Just add another line in the startup-sequence:
Run >NIL: C:CardReset
 

Offline scap61

  • Newbie
  • *
  • Join Date: Jun 2006
  • Posts: 5
    • Show only replies by scap61
Re: Another wireless PCMCIA success story
« Reply #10 on: June 17, 2006, 05:56:16 PM »
damn... i have added the line for cardreset but i take the same error :(
 

Offline ncafferkey

  • Sr. Member
  • ****
  • Join Date: Feb 2003
  • Posts: 370
    • Show only replies by ncafferkey
Re: Another wireless PCMCIA success story
« Reply #11 on: June 17, 2006, 06:31:22 PM »
I got a report of someone successfully using a WL110 with prism2.device before. Does the card look like this? I'd recommend just inserting the card after boot while you're figuring out the problem, and only using CardReset after you've got the card working.

I've read that the Squirrel software takes over the PCMCIA port and stops other PCMCIA drivers working, so you should make sure you don't have it running.
 

Offline scap61

  • Newbie
  • *
  • Join Date: Jun 2006
  • Posts: 5
    • Show only replies by scap61
Re: Another wireless PCMCIA success story
« Reply #12 on: June 18, 2006, 12:00:38 AM »
Quote

 Does the card look like this?

yes the card is the same

I've read that the Squirrel software takes over the PCMCIA port and stops other PCMCIA drivers working, so you should make sure you don't have it running.


i have disabled 2 items under devs/dosdrivers that use  squirrelscsi.device and now i can read the status of the card and the power led is on

many thanks

now i must configure miami :)

ciao