dgeesaman@gmail.com hath wroth:

>On Dec 12, 1:03 pm, Jeff Liebermann <j...@comix.santa-cruz.ca.us>
>wrote:
>> dgeesa...@gmail.com hath wroth:
>
>Jeff, I did update the drivers with the latest software from dell, and
>the wireless connectivity dropped to zero.
>
>So then I uninstalled it, and was left with only the windows wireless
>support. (It was using a slightly more featureful utility from
>Dell/Broadcom). Voila, everything works now on all wireless networks.

Cool. I just went through that exercise on an HP laptop for a
customer. Broadcom wireless card. (I forgot the model numbers). It
had some early version of the driver and client utility. I updated
the driver but not the client utility when everything started working
weird. For example, the wireless on/off button would allow me to turn
off the wireless, but not on. I eventually realized that the driver
and client utility (or whatever it's called) had to go together with
the same version. I downloaded version 4.x of the driver and the
Broadcom utilities, and everything worked just fine. Kinda nifty
looking interface.

In addition, I found that in the properties for the driver, were a
bunch of settings that I thought were only in Cisco and Intel Proset.
I can now control how aggressively the client sticks to a single
access point (for roaming), and SNR thresholds. Unfortunately, I
didn't have time to explore, tinker, and test.


--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558