Lucent silver to gold

Configuration and other hardware related information

Postby CrackerStealth » Sat Jul 05, 2003 6:28 pm

Worked great for me. I had to use legacy support and it took two tries. First try resulted in an error. Thinkpad 760el with Orinoco Silver card.

Here's what I did exactly:
flash -5v -legacy -pd card.pda
edit card.pda
[Change two characters]
[alt+f] [save]
flash -5v -legacy -p card.pda

I used notepad in windows the first time which resulted in the error. The second time I just used the DOS edit command. Also did this with a Windows 98SE startup disk, but the flash files were on the C: drive.
CrackerStealth
Mini Stumbler
 
Posts: 23
Joined: Tue Feb 25, 2003 9:54 pm

Postby peekitty » Sat Jul 05, 2003 7:44 pm

Maybe I'm just imagining things, but it looks like the price of silver cards on eBay has just jumped up a bit...
User avatar
peekitty
 
Posts: 1054
Joined: Wed Sep 04, 2002 6:14 am
Location: S. Florida

Postby norm » Sun Jul 06, 2003 12:23 am

why boot to 'real dos mode'

surely then you wouldnt be able to communicate with the PCMCIA device?

whats also interesting is the ability to change one's MAC address with this utility.
norm
Mini Stumbler
 
Posts: 69
Joined: Fri May 17, 2002 9:02 am
Location: UK

Postby lincomatic » Sun Jul 06, 2003 8:46 am

ok i tried a few more different laptops and i got the same error as before (command 322 never signaled status). this was using my lucent-branded orinoco silver.

just as a test, i tried reading the pda from an IBM-branded gold card and then writing it back unchanged, and it works fine.

next, i tried read/writing the pda from my silver card unchanged,
and it still fails w/ the above error.

so it appears that my lucent silver is somehow "locked." has anyone else noticed this prb?
~lincomatic
User avatar
lincomatic
Mini Stumbler
 
Posts: 1682
Joined: Tue Apr 16, 2002 12:53 am
Location: Tinsel Town

Postby peekitty » Sun Jul 06, 2003 11:29 am

Don't know if it will be helpful, but here's the output of flash.exe run on an Avaya with -5v -log log.txt -vb -legacy -pd avaya.pda arguments:

# Logging enabled. Timestamp: 2003-07-06 14:44:21 #
PCIC: 82365SL compatible - B step (possibly 5V only)
Using Legacy Mode
(COR reset) Startup... Read 25 records from card. Current PDA
5) [ 1] 3041 3531 3832 4130 (A015280A)
5) [ 2] 4131 3034 3238 3637
7) [ 3] 3130 4755 3034 3134 3332 3532 (01UG40412325)
3d) [ 4] 0 0 67fb 40a3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
6) [ 5] 0 6 1 2 2
6) [ 6] 0 1 1 3 3
6) [ 7] 0 2 1 5 6
5) [ 8] 1 1 4 2
f) [ 10] 9d11 97ee 9922 9833 9b44 9e55 9f66 9d77 9b88 9a99 9aaa 99bb 9bcc 98dd
f) [ 20] 7a11 95ee 7422 6f33 6b44 6855 6766 6777 6888 6a99 6daa 70bb 76cc 7cdd
f) [ 30] 5011 5022 5033 5044 5055 5066 5077 5088 5099 50aa 50bb 50cc 50dd 50ee
3) [ 40] 800 800
4) [101] 200 3e2d 362 (00-02-2d-3e-62-03)
5) [102] 0 0 0 0
7) [103] 6 2010 3130 4132 0 0
2) [104] 7ff
2) [105] a
2) [106] 0
2) [107] 1
3) [108] 69d1 d29e
6) [109] 3 3 2b 0 0
f) [110] 139d 1399 1398 139b 139e 139f 139d 139b 139a 139a 1399 139b 1398 1397
f) [120] 127a 1274 126f 126b 1268 1267 1267 1268 126a 126d 1270 1276 127c 1295
f) [130] 4450 4450 4450 4450 4450 4450 4450 4450 4450 4450 4450 4450 4450 4450
3) [140] 4208 4308
End Record. New CRC: 5123
- okay
PDA written to avaya.pda
User avatar
peekitty
 
Posts: 1054
Joined: Wed Sep 04, 2002 6:14 am
Location: S. Florida

Postby pulz » Sun Jul 06, 2003 12:42 pm

Originally posted by peekitty
Don't know if it will be helpful, but here's the output of flash.exe run on an Avaya with [b]-5v -log log.txt -vb -legacy -pd avaya.pda arguments:

[/B]


You wouldnt mind pasting what it says when you have rewritten your pda ?

The dumping part works fine here, but im not able to write the new pda
pulz
Mini Stumbler
 
Posts: 8
Joined: Sun Jun 29, 2003 8:00 am

Postby peekitty » Sun Jul 06, 2003 1:05 pm

The output from the write process is:

(COR reset) Startup... Loaded PDA file "card.pda" successfully. Previous PDA will be replaced.
Writing this PDA:

<body of the PDA>

Writing PDA...
Download buffer: page 60; offset 0; size 2000; timeout 5000 ms
Download buffer written to NV RAM
User avatar
peekitty
 
Posts: 1054
Joined: Wed Sep 04, 2002 6:14 am
Location: S. Florida

Postby norm » Sun Jul 06, 2003 2:19 pm

just to confirm, this alchemy trick worked no problem on an orinoco silver (OEM).

using dos version 6.2

--

just a thought, but does anybody have any knowledge surrounding the cisco aironet 350 cards and the output TX limits imposed on them.

wondering whether it'd be possible to alter this ETSI (50mw) card to allow the 100mw TX allowed by FCC.

using this utility I was only able to call up the 'CIS' (Card Information Structure, contains information relating to card type/voltage). not sure whether its relevant but maybe if somebody else has an FCC rated card we could compare findings?
norm
Mini Stumbler
 
Posts: 69
Joined: Fri May 17, 2002 9:02 am
Location: UK

Postby JimmyPopAli » Sun Jul 06, 2003 9:13 pm

It's no go here, I'm using a Lucent Technologies Wavelan Silver (orinoco silver), I get the Command 332 never signaled status error. What cards have worked for everyone?
User avatar
JimmyPopAli
Mini Stumbler
 
Posts: 242
Joined: Sun Apr 14, 2002 9:55 am
Location: Washington the state

Postby lincomatic » Sun Jul 06, 2003 9:25 pm

now i've tried both an Lucent ORiNOCO and WaveLan Silver cards both w/ error on command 322 (which is the download command, btw). only my ibm card lets me write the PDA. i wonder if the firmware that's currently in the card matters. can everyone post their card/primary/secondary firmware for the cards that worked and failed? you can view them via the Client Manager from the Help/Version Info menu.

here are mine that fail:
Orinoco Silver:
card: variant 1, 4.00
primary: variant 1, 4.04
station: variant 2, 8.10

Wavelan Silver:
card: variant 1, 4.00
primary: variant 1, 4.00
station: variant 2, 8.10

works:
IBM:
card: variant 1, 4.02
primary: variant 1, 4.04
station: variant 2, 8.10

the only thing that's different about the one that worked for me is the card is v4.02
~lincomatic
User avatar
lincomatic
Mini Stumbler
 
Posts: 1682
Joined: Tue Apr 16, 2002 12:53 am
Location: Tinsel Town

Postby norm » Sun Jul 06, 2003 9:41 pm

Variant 1, Version 4.04 of Primary Functions firmware

Variant 1, Version 8.72 of Station Functions firmware

Variant 3, Version 4.02 of PC Card Type-II Extended
Agere Systems Gold Card
Enhanced WEP encryption allowed
IEEE high-speed data rates
norm
Mini Stumbler
 
Posts: 69
Joined: Fri May 17, 2002 9:02 am
Location: UK

Postby lincomatic » Sun Jul 06, 2003 9:57 pm

Originally posted by norm
Variant 1, Version 4.04 of Primary Functions firmware

Variant 1, Version 8.72 of Station Functions firmware

Variant 3, Version 4.02 of PC Card Type-II Extended
Agere Systems Gold Card
Enhanced WEP encryption allowed
IEEE high-speed data rates


thanks norm. hmm. so you have card v4.02, which is the only ver that worked for me. new we gotta figure out if there's a way to chg the card version. i hope it's not because the PDA is not writable in card v4.02...

i wonder what the variant means...
yours is Variant 3 and mine is Variant 1.
~lincomatic
User avatar
lincomatic
Mini Stumbler
 
Posts: 1682
Joined: Tue Apr 16, 2002 12:53 am
Location: Tinsel Town

Postby lincomatic » Sun Jul 06, 2003 11:33 pm

Originally posted by norm
[Bjust a thought, but does anybody have any knowledge surrounding the cisco aironet 350 cards and the output TX limits imposed on them.

wondering whether it'd be possible to alter this ETSI (50mw) card to allow the 100mw TX allowed by FCC.

using this utility I was only able to call up the 'CIS' (Card Information Structure, contains information relating to card type/voltage). not sure whether its relevant but maybe if somebody else has an FCC rated card we could compare findings? [/B]


there is some info about the PDR's here:
http://www.cawnet.org/pipermail/rfmon/2001-December/000207.html

here is the pertinent info:
> * ID 0x0103: Regulatory Domain List
> * ID 0x0104: Allowed Channel Set (either 0x07FF for US 1-11 or
> 0x1fff for ETSI)

there's nothing about power settings but maybe changing the regulatory domain list or the allowed channel set will work? if you want to see the US settings from orinoco's take a look at peekitty's dump above.
~lincomatic
User avatar
lincomatic
Mini Stumbler
 
Posts: 1682
Joined: Tue Apr 16, 2002 12:53 am
Location: Tinsel Town

Postby norm » Mon Jul 07, 2003 12:15 am

thanks for looking out the info, i'll try matching up any of the values to the CIS.

btw, the card i flashed was pulled from a silver lucent/orinoco USB adapter. may explain the different variant.
norm
Mini Stumbler
 
Posts: 69
Joined: Fri May 17, 2002 9:02 am
Location: UK

Postby norm » Mon Jul 07, 2003 1:30 am

well been playing a bit more and managed to switch the card to the japanese regulatory domain as a test, with all 14 channels.

also tried accessing my dell truemobile 1150 series card but that failed.

Variant 1, Version 2.42 of Client Manager
Variant 2, Version 7.42 of NDIS 5 Miniport driver
Variant 4, Version 5.00 of PC Card Type-II Extended
Dell Gold Card
Enhanced WEP encryption allowed
IEEE high-speed data rates
IO base:FF40
IRQ number:7
Variant 1, Version 4.04 of Primary Functions firmware
Variant 2, Version 8.10 of Station Functions firmware


# Logging enabled. Timestamp: 2003-07-07 09:46:16 #
PCIC: 82365SL DF compatible - C step (3.3V / 5V capable)
Using Legacy Mode
(COR reset) Startup... Invalid record encountered. PDA is invalid.

Checking CIS.
Vcc = 5 volts
CIS String: Version 5.0 Dell TrueMobile 1150 Series PC Card Version 01.01
Firmware loaded:
P1040400.HEX S1081000.HEX


It is however a similar sort of read error to that on the cisco card, which reported Version 4.1, so maybe an incompatibility with the flash utility rather than some form of write protection?

# Logging enabled. Timestamp: 2003-07-06 23:41:21 #
PCIC: 82365SL DF compatible - C step (3.3V / 5V capable)
Using Legacy Mode
(COR reset) Startup... Bad status 0 auxEnable failed!

Checking CIS.
CIS String: Version 4.1 Cisco Systems 350 Series Wireless LAN Adapter
Error - Command 0 never signaled status!
norm
Mini Stumbler
 
Posts: 69
Joined: Fri May 17, 2002 9:02 am
Location: UK

PreviousNext

Return to Hardware

Who is online

Users browsing this forum: No registered users and 6 guests

cron