Date: Wed, 30 Mar 2011 13:12:23 -0400 From: Jerry <freebsd.user@seibercom.net> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Easiest desktop BSD distro Message-ID: <20110330131223.07f13bb3@scorpio> In-Reply-To: <1892767898.53772.1301502751849.JavaMail.seven@ap4.trial.red.7sys.net> References: <1892767898.53772.1301502751849.JavaMail.seven@ap4.trial.red.7sys.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 30 Mar 2011 09:32:29 -0700 (PDT) four.harrisons@googlemail.com <four.harrisons@googlemail.com> articulated: > Once you've scaled the learning curve, you will appreciate how easy > it is to achieve things with FreeBSD compared to other OS which > attempt to make things 'easy' for you (wireless networking springs to > mind - in my experience if Windows can't do it 'automagically' then > you haven't a hope in hell of finding out what's wrong and fixing it). You have conveniently left out the part that if the OS does not have a driver for the wireless card, specifically "N" protocol cards, then you haven't any hope of getting it to work, period. In any case, the easiest way to get any wireless card to work in Windows, at least up to Win-7, was to deactivate the Windows wireless utility and use the one that accompanies the device, assuming that it does come with a configuration utility. I have not seen any of the top rated ones that did not. If for some reason that did not work, you could still manually enter any of the specific information manually, assuming that you actually took the time to learn (where did I here that term before) how to accomplish it. -- Jerry ✌ FreeBSD.user@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ In an orderly world, there's always a place for the disorderly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110330131223.07f13bb3>