Wireless hardware guru out there?

For what I can determine your Proxim card uses a Prism chipset and the
others use Atheros chipsets. So that's the main difference.

I just went through a similar problem with a Proxim Gold 802.11 b/g card in
an older laptop with an O2Micro OZ6812 PCMCIA controller. I'd get an
excellent radio link but all received packets were reported as having frame
errors. Turned out to be a general problem in the Atheros reference driver.
It wasn't properly recognizing and configuring for the O2Micro controller.
Proxim, Netgear and SMC cards based on the same Atheros chipset (and
presumably that ship with renamed versions of the same reference driver)
failed in the same way.

Proxim customer support eventually was able to supply me with a variant of
the Atheros AR5211.sys driver file that could be forced to detect my O2Micro
controller when coupled with a manually-entered Windows registry key. For
grins I also tried it with the other cards that showed problems; the
modified driver worked fine for all of them once renamed to match the
driver file name used by the respective OEMs. Atheros is aware of issues
with the O2Micro OZ6812. It is quite possible a similar issue exists with
your O2Micro controller chipset. You might try pursuing the problem via the
wireless NIC customer support avenues available to you. In my case it took
nearly a month to get a response but things worked out in the end.

Good luck.

"Noozer" wrote in message
news:j_y3c.757493$X%5.609931@pd7tw2no...
Can anyone tell me what may be different between the following cards?

- Proxim Harmony 8432 802.11b 3.3v cardbus card
- SMC 2335W 802.11a&b
- SMC 2735W 802.11a 3.3v cardbus card
- DLink DWL-AB650 80211a&b 3.3v cardbus card

- Only the Proxim will connect to my Netgear MR814v2 802.11b router
- DLink randomly sees my Netger 802.11b router, as well as a couple others
in the neighbourhood, but NEVER connects to anything.
- Nothing will even see my SMC 2755W 802.11a WAP
-All cards are 3.3v PCMCIA type 2 cards
- Laptop is an HP N5495 running a fresh install of Windows XP Pro SP1
(also
tried in Windows ME)
- PCMCIA controllers are O2Micro OZ6933 chips.
- Proxim card is not identified by Windows as a wireless card. All
configuration done through their utility.
- Other cards are Windows Wireless compatible, but using Windows OR their
utilities to configure makes not difference.

Only thing I can see is that any wireless card compatible with Windows
Wireless Zero Configuration does not work on my machine.

Any PCMCIA tricks or quirks that might identify issues with my cardbus
slots???

Very helpful stuff!

Thank you VERY much!!!

Going to knock of a email to all the companies involved and see who responds
first. : )


"JohnM" wrote in message
...
For what I can determine your Proxim card uses a Prism chipset and the
others use Atheros chipsets. So that's the main difference.

I just went through a similar problem with a Proxim Gold 802.11 b/g card
in
an older laptop with an O2Micro OZ6812 PCMCIA controller. I'd get an
excellent radio link but all received packets were reported as having
frame
errors. Turned out to be a general problem in the Atheros reference
driver.
It wasn't properly recognizing and configuring for the O2Micro controller.
Proxim, Netgear and SMC cards based on the same Atheros chipset (and
presumably that ship with renamed versions of the same reference driver)
failed in the same way.

Proxim customer support eventually was able to supply me with a variant of
the Atheros AR5211.sys driver file that could be forced to detect my
O2Micro
controller when coupled with a manually-entered Windows registry key. For
grins I also tried it with the other cards that showed problems; the
modified driver worked fine for all of them once renamed to match the
driver file name used by the respective OEMs. Atheros is aware of issues
with the O2Micro OZ6812. It is quite possible a similar issue exists with
your O2Micro controller chipset. You might try pursuing the problem via
the
wireless NIC customer support avenues available to you. In my case it took
nearly a month to get a response but things worked out in the end.

Good luck.

"Noozer" wrote in message
news:j_y3c.757493$X%5.609931@pd7tw2no...
Can anyone tell me what may be different between the following cards?

- Proxim Harmony 8432 802.11b 3.3v cardbus card
- SMC 2335W 802.11a&b
- SMC 2735W 802.11a 3.3v cardbus card
- DLink DWL-AB650 80211a&b 3.3v cardbus card

- Only the Proxim will connect to my Netgear MR814v2 802.11b router
- DLink randomly sees my Netger 802.11b router, as well as a couple
others
in the neighbourhood, but NEVER connects to anything.
- Nothing will even see my SMC 2755W 802.11a WAP
-All cards are 3.3v PCMCIA type 2 cards
- Laptop is an HP N5495 running a fresh install of Windows XP Pro SP1
(also
tried in Windows ME)
- PCMCIA controllers are O2Micro OZ6933 chips.
- Proxim card is not identified by Windows as a wireless card. All
configuration done through their utility.
- Other cards are Windows Wireless compatible, but using Windows OR
their
utilities to configure makes not difference.

Only thing I can see is that any wireless card compatible with Windows
Wireless Zero Configuration does not work on my machine.

Any PCMCIA tricks or quirks that might identify issues with my cardbus
slots???

So far the only response I've gotten was some moron at HP asking questions
that were already answered in my message...

Talk about lame customer support.

....so far what I've been able to find out for myself...

All my cards exept the Proxim are using an Atheros chipset. The Proxim uses
a Prism chipset.

My SMC2735W 802.11a card just freezes the laptop whenever inserted and
drivers installed. Yank the card and the latop just runs like nothing had
happened.

*sigh* If I can find Atheros' website/support I'm going to try them next.



"Noozer" wrote in message
news:VBK3c.764247$ts4.182377@pd7tw3no...
Very helpful stuff!

Thank you VERY much!!!

Going to knock of a email to all the companies involved and see who
responds
first. : )


"JohnM" wrote in message
...
For what I can determine your Proxim card uses a Prism chipset and the
others use Atheros chipsets. So that's the main difference.

I just went through a similar problem with a Proxim Gold 802.11 b/g card
in
an older laptop with an O2Micro OZ6812 PCMCIA controller. I'd get an
excellent radio link but all received packets were reported as having
frame
errors. Turned out to be a general problem in the Atheros reference
driver.
It wasn't properly recognizing and configuring for the O2Micro
controller.
Proxim, Netgear and SMC cards based on the same Atheros chipset (and
presumably that ship with renamed versions of the same reference driver)
failed in the same way.

Proxim customer support eventually was able to supply me with a variant
of
the Atheros AR5211.sys driver file that could be forced to detect my
O2Micro
controller when coupled with a manually-entered Windows registry key.
For
grins I also tried it with the other cards that showed problems; the
modified driver worked fine for all of them once renamed to match the
driver file name used by the respective OEMs. Atheros is aware of issues
with the O2Micro OZ6812. It is quite possible a similar issue exists
with
your O2Micro controller chipset. You might try pursuing the problem via
the
wireless NIC customer support avenues available to you. In my case it
took
nearly a month to get a response but things worked out in the end.

Good luck.

"Noozer" wrote in message
news:j_y3c.757493$X%5.609931@pd7tw2no...
Can anyone tell me what may be different between the following cards?

- Proxim Harmony 8432 802.11b 3.3v cardbus card
- SMC 2335W 802.11a&b
- SMC 2735W 802.11a 3.3v cardbus card
- DLink DWL-AB650 80211a&b 3.3v cardbus card

- Only the Proxim will connect to my Netgear MR814v2 802.11b router
- DLink randomly sees my Netger 802.11b router, as well as a couple
others
in the neighbourhood, but NEVER connects to anything.
- Nothing will even see my SMC 2755W 802.11a WAP
-All cards are 3.3v PCMCIA type 2 cards
- Laptop is an HP N5495 running a fresh install of Windows XP Pro SP1
(also
tried in Windows ME)
- PCMCIA controllers are O2Micro OZ6933 chips.
- Proxim card is not identified by Windows as a wireless card. All
configuration done through their utility.
- Other cards are Windows Wireless compatible, but using Windows OR
their
utilities to configure makes not difference.

Only thing I can see is that any wireless card compatible with Windows
Wireless Zero Configuration does not work on my machine.

Any PCMCIA tricks or quirks that might identify issues with my cardbus
slots???

WooHoo!

Atheros came through (PLEASE DON'T BOMBARD THEM WITH QUESTIONS)

Sent me a new driver and I can see and connect to my "A" network... I don't
see the "B" network though, so there is still work to do.


"Noozer" wrote in message
news:zzb6c.96987$Up2.80424@pd7tw1no...
So far the only response I've gotten was some moron at HP asking questions
that were already answered in my message...

Talk about lame customer support.

...so far what I've been able to find out for myself...

All my cards exept the Proxim are using an Atheros chipset. The Proxim
uses
a Prism chipset.

My SMC2735W 802.11a card just freezes the laptop whenever inserted and
drivers installed. Yank the card and the latop just runs like nothing had
happened.

*sigh* If I can find Atheros' website/support I'm going to try them next.



"Noozer" wrote in message
news:VBK3c.764247$ts4.182377@pd7tw3no...
Very helpful stuff!

Thank you VERY much!!!

Going to knock of a email to all the companies involved and see who
responds
first. : )


"JohnM" wrote in message
...
For what I can determine your Proxim card uses a Prism chipset and the
others use Atheros chipsets. So that's the main difference.

I just went through a similar problem with a Proxim Gold 802.11 b/g
card
in
an older laptop with an O2Micro OZ6812 PCMCIA controller. I'd get an
excellent radio link but all received packets were reported as having
frame
errors. Turned out to be a general problem in the Atheros reference
driver.
It wasn't properly recognizing and configuring for the O2Micro
controller.
Proxim, Netgear and SMC cards based on the same Atheros chipset (and
presumably that ship with renamed versions of the same reference
driver)
failed in the same way.

Proxim customer support eventually was able to supply me with a
variant
of
the Atheros AR5211.sys driver file that could be forced to detect my
O2Micro
controller when coupled with a manually-entered Windows registry key.
For
grins I also tried it with the other cards that showed problems; the
modified driver worked fine for all of them once renamed to match the
driver file name used by the respective OEMs. Atheros is aware of
issues
with the O2Micro OZ6812. It is quite possible a similar issue exists
with
your O2Micro controller chipset. You might try pursuing the problem
via
the
wireless NIC customer support avenues available to you. In my case it
took
nearly a month to get a response but things worked out in the end.

Good luck.

"Noozer" wrote in message
news:j_y3c.757493$X%5.609931@pd7tw2no...
Can anyone tell me what may be different between the following
cards?

- Proxim Harmony 8432 802.11b 3.3v cardbus card
- SMC 2335W 802.11a&b
- SMC 2735W 802.11a 3.3v cardbus card
- DLink DWL-AB650 80211a&b 3.3v cardbus card

- Only the Proxim will connect to my Netgear MR814v2 802.11b router
- DLink randomly sees my Netger 802.11b router, as well as a couple
others
in the neighbourhood, but NEVER connects to anything.
- Nothing will even see my SMC 2755W 802.11a WAP
-All cards are 3.3v PCMCIA type 2 cards
- Laptop is an HP N5495 running a fresh install of Windows XP Pro
SP1
(also
tried in Windows ME)
- PCMCIA controllers are O2Micro OZ6933 chips.
- Proxim card is not identified by Windows as a wireless card. All
configuration done through their utility.
- Other cards are Windows Wireless compatible, but using Windows OR
their
utilities to configure makes not difference.

Only thing I can see is that any wireless card compatible with
Windows
Wireless Zero Configuration does not work on my machine.

Any PCMCIA tricks or quirks that might identify issues with my
cardbus
slots???

OK... I'm an idiot. Big correction here...

It was O2MICRO that sent the reply to me, not Atheros... I need to check my
headers a bit more closely.

At this point I can see and connect to my "A" network with my DLink card.
Turbo mode even works. The "B" network doesn't show up at all. The SMC card
still locks the machine solid.

"Noozer" wrote in message
news:C4I6c.108833$Up2.75366@pd7tw1no...
Atheros came through (PLEASE DON'T BOMBARD THEM WITH QUESTIONS)

Sent me a new driver and I can see and connect to my "A" network... I
don't
see the "B" network though, so there is still work to do.

"Noozer" wrote in message
news:zzb6c.96987$Up2.80424@pd7tw1no...
So far the only response I've gotten was some moron at HP asking
questions
that were already answered in my message...

Talk about lame customer support.

...so far what I've been able to find out for myself...

All my cards exept the Proxim are using an Atheros chipset. The Proxim
uses
a Prism chipset.

My SMC2735W 802.11a card just freezes the laptop whenever inserted and
drivers installed. Yank the card and the latop just runs like nothing
had
happened.

*sigh* If I can find Atheros' website/support I'm going to try them
next.



"Noozer" wrote in message
news:VBK3c.764247$ts4.182377@pd7tw3no...
Very helpful stuff!

Thank you VERY much!!!

Going to knock of a email to all the companies involved and see who
responds
first. : )


"JohnM" wrote in message
...
For what I can determine your Proxim card uses a Prism chipset and
the
others use Atheros chipsets. So that's the main difference.

I just went through a similar problem with a Proxim Gold 802.11 b/g
card
in
an older laptop with an O2Micro OZ6812 PCMCIA controller. I'd get an
excellent radio link but all received packets were reported as
having
frame
errors. Turned out to be a general problem in the Atheros reference
driver.
It wasn't properly recognizing and configuring for the O2Micro
controller.
Proxim, Netgear and SMC cards based on the same Atheros chipset (and
presumably that ship with renamed versions of the same reference
driver)
failed in the same way.

Proxim customer support eventually was able to supply me with a
variant
of
the Atheros AR5211.sys driver file that could be forced to detect my
O2Micro
controller when coupled with a manually-entered Windows registry
key.
For
grins I also tried it with the other cards that showed problems; the
modified driver worked fine for all of them once renamed to match
the
driver file name used by the respective OEMs. Atheros is aware of
issues
with the O2Micro OZ6812. It is quite possible a similar issue exists
with
your O2Micro controller chipset. You might try pursuing the problem
via
the
wireless NIC customer support avenues available to you. In my case
it
took
nearly a month to get a response but things worked out in the end.

Good luck.

"Noozer" wrote in message
news:j_y3c.757493$X%5.609931@pd7tw2no...
Can anyone tell me what may be different between the following
cards?

- Proxim Harmony 8432 802.11b 3.3v cardbus card
- SMC 2335W 802.11a&b
- SMC 2735W 802.11a 3.3v cardbus card
- DLink DWL-AB650 80211a&b 3.3v cardbus card

- Only the Proxim will connect to my Netgear MR814v2 802.11b
router
- DLink randomly sees my Netger 802.11b router, as well as a
couple
others
in the neighbourhood, but NEVER connects to anything.
- Nothing will even see my SMC 2755W 802.11a WAP
-All cards are 3.3v PCMCIA type 2 cards
- Laptop is an HP N5495 running a fresh install of Windows XP Pro
SP1
(also
tried in Windows ME)
- PCMCIA controllers are O2Micro OZ6933 chips.
- Proxim card is not identified by Windows as a wireless card. All
configuration done through their utility.
- Other cards are Windows Wireless compatible, but using Windows
OR
their
utilities to configure makes not difference.

Only thing I can see is that any wireless card compatible with
Windows
Wireless Zero Configuration does not work on my machine.

Any PCMCIA tricks or quirks that might identify issues with my
cardbus
slots???

O2Micro came through...

With the new Atheros driver they sent me I can now use my DLink DWL-AB650
802.11ab card with my laptop. Not sure where the fault lies, but obviously
something going on with the controller chip and the Atheros chipset.

I will post the modified Dlink drivers/software if someone gives me
someplace to FTP it (via FTP or webpage interface)

The SMC 2735W card on the other hand still pauses the laptop indefinately
when the drivers start. I've tried three different driver versions in both
Windows XP SP1 and Win ME. This card uses a different Atheros chipset than
the DLink and I haven't been able to find anything to help with this card.

SMC has sent some pretty generic stuff to try... I'm just waiting for my
latest info to them to get processed.

Short version of issue for those interested...

HP Pavilion laptop, model N5495, works fine on my wireless network with a
Proxim Harmony 8432 802.11b card. Dlink DWL-AB650 802.11ab and SMC 2335W
802.11ab cards did not work but did not affect operation of the laptop. SMC
2735W 802.11a card stops the laptop whenever the drivers have been installed
and card inserted into laptop. Laptop continues normally when card is
removed. This last card was RMA'd once so it is most likely not broken.

Proxim uses a Prism chipset. Dlink and SMC cards use Atheros chipsets.
Laptop has O2Micro controller for the card slots.

At this point O2Micro's support staff was able to get my DLink working, but
they can't reproduce the issue with the SMC 2735W card so can't do much with
it.

I purchased 2 of these cards and they both exhibit the same behaviour
you mention. I can't remember exactly what I did, but I have them
semi-working now. Try uninstalling the card & drivers and then
turning WEP off on the card and access point, then reinstall the
drivers. Once you have this baseline working, try renabling WEP etc.
Also, there is a driver update on the SMC@Work web site. I still have
problems with the card freezing at certain times... if the laptop goes
into standby or hibernation, at power down, or if I alter the card's
network settings. Let me know if you have any success. FYI, my
laptop has both the O2Micro OZ6812 Cardbuz controller and the TI
PCI1410 PC card controller... which is funny considering I only have
one slot?

"Noozer" wrote in message news:usibc.13990$Ig.8117@pd7tw2no...
O2Micro came through...

With the new Atheros driver they sent me I can now use my DLink DWL-AB650
802.11ab card with my laptop. Not sure where the fault lies, but obviously
something going on with the controller chip and the Atheros chipset.

I will post the modified Dlink drivers/software if someone gives me
someplace to FTP it (via FTP or webpage interface)

The SMC 2735W card on the other hand still pauses the laptop indefinately
when the drivers start. I've tried three different driver versions in both
Windows XP SP1 and Win ME. This card uses a different Atheros chipset than
the DLink and I haven't been able to find anything to help with this card.

SMC has sent some pretty generic stuff to try... I'm just waiting for my
latest info to them to get processed.

Short version of issue for those interested...

HP Pavilion laptop, model N5495, works fine on my wireless network with a
Proxim Harmony 8432 802.11b card. Dlink DWL-AB650 802.11ab and SMC 2335W
802.11ab cards did not work but did not affect operation of the laptop. SMC
2735W 802.11a card stops the laptop whenever the drivers have been installed
and card inserted into laptop. Laptop continues normally when card is
removed. This last card was RMA'd once so it is most likely not broken.

Proxim uses a Prism chipset. Dlink and SMC cards use Atheros chipsets.
Laptop has O2Micro controller for the card slots.

At this point O2Micro's support staff was able to get my DLink working, but
they can't reproduce the issue with the SMC 2735W card so can't do much with
it.