David wrote:
> squelch41@hotmail.com wrote:
>> OK - thanks. So it is basically the fact that the drivers are extremely
>> difficult to find/make.
>> That would certainly fit with my experience where, under windows,
>> things are reasonably easy as you just install the manufacturer's
>> driver, but for linux, you have to hunt around for chipset type, then
>> try the driver which often doesnt work, etc.
>>
>> Thanks again,
>> squelch41
>>
>
> Well you could just try using NDISwrapper and the native windows driver.

The downside of that approach is that no kernel developer will even look at any oops that you have
as long as that Windows binary "taints" your system.

Once you solve the driver problem, and I'm part of the group working on the bcm43xx driver, using
NetworkManager to connect is even easier then Windows. When you try to connect with a new, encrypted
AP, up pops a box asking for your encryption key, which is then stored in your KDE wallet.

Larry