Intel ProWireless or Windows?

[jjfcpa]

Just trying to get a feel for who uses Intel's system for managing their wirelss connections versus Windows XP built in system?

Is there a reason Intel's is better, albeit slower?

[kyrotech]

right now am using microsofts wireless management instead of Access Connections softwarez.

[kaplanfx]

I am continuing to use Access Connections. It is far superior to the others as far as features, the negatives being that its a memory hog, and that it inexplicably fails to connect sometimes and requires either a restart of the program or a restart of the system. The fail to connect issue is almost always after sleeping or hibernating the laptop, but sometimes happens when the radio is turned off and then back on.

[aabram]

Just trying to get a feel for who uses Intel's system for managing their wirelss connections versus Windows XP built in system?

Is there a reason Intel's is better, albeit slower?

If you don't need additional configuration options Access Connections can give you, there is no reason to use it, really. If you just use mainly few access points or have everything automatically configured you might just be fine with Windows' own management.

However, if you need to force specific settings for different networks you use the AC is godsent tool. I used to have around 9-10 profiles, each with different settings (fixed IP, DNS etc) and it would've been a nightmare to keep it all tidy and tucked tight without AC.

For some reason AC seems to be great deal slower when it comes preinstalled with Windows and other IBM tools. I have two machines I've been debugging which both are way slower to connect to wireless networks than my own system. I myself have hand picked configuration and I can't complain about AC being slow to find network or to apply profile settings. It usually takes up to 10 seconds on my machine whereas it takes forever (up to couple of minutes) on those other mentioned laptops.

But yea, if everywhere you go you rely on automatic configuration you may as well let Windows manage it.

[christopher_wolf]

I agree with aabram here; if you need it, it is an Excellent Tool to use...if what you do is simple, then Windows might work out well for you.

Personally, I use Access Connections quite a bit and I haven't noticed ay situations where it took longer than 1 minute to connect. I also like the level of feedback and control it gives you over the hardware; Windows Wireless doesn't come anywhere near that level of feedback. If it doesn't have a profile for a certain area, it doesn't get in the way. Having multiple Profile though, is a good feature.

[jjfcpa]

Thanks for the excellent replies. I think I may use Windows since I don't have any special requirements.

[GomJabbar]

Everyone replying on this thread has been talking about Access Connections vs Windows networking. The title of the thread however concerns the Intel PRO/Wireless software. This is third way to manage your wireless connection. I use Access Connections, but I did try the Intel PRO/Wireless software briefly, and it seemed to work pretty good. If you don't want Access Connections, you still might want to try the Intel PRO/Wireless software. If you don't like it, just uninstall it.

[DIGITALgimpus]

I personally like AC. Well designed, and very useful.

It may be overcomplicated for many... but when you need it, I've yet to see something beat it.

[kaplanfx]

I tried the PROwireless as well. It did a fine job of handling connections to access points, however I found the interface to be non-intuitive, and most of the features are not presented, or are hidden where they are difficult to find.

[Roy_W]

I have used both Windows and AC and am often connected to many different client Wifi networks throughout the week. I used AC for at least six months, but then eventually went back to using Windows Wireless as it kept me in tow with what my clients were using. Also, by sticking to Windows Wireless it removed any doubt ( or not ) I had about the whether or not any wireless problems were Windows,AC or otherwise related.

I think it would be safe enough to assume that the same rule would apply to the Intel Software. By remaining with the MS solution as least you have an extremely large user-base which you can consult in case of problems.

[bill bolton]

> By remaining with the MS solution as least you have an extremely
> large user-base which you can consult in case of problems.

When it comes to information connection manangement using wirless links, few serious wireless mobility users find that relying on the low information functionality wireless link management provided as standard in Windows XP is practically workable.

So the preceived "large user base" usually dones't have a clue about sorting out many of the practical problems with managing real information connectivity (as distinct from the 802.11x link connectivity) to in a highly mobile environment.

Cheers,

Bill

[Roy_W]

When it comes to information connection manangement using wirless links, few serious wireless mobility users find that relying on the low information functionality wireless link management provided as standard in Windows XP is practically workable.

I agree with what you are saying, but in the case of a problematic wireless connection none of the aforementioned solutions would suffice. There are are utilitys which would be far more usefull. In any event, the majority of cases that I come across I do not have the opportunity of changing the clients software and I am forced to using whatever is available on the clients machine. which is usually the MS solution.

As for the userbase, I have to disagree. Consider how many techno geeks know the XP interface by heart, this forums is already full of them, against the number of technogeeks that know the AC or the Intel solution by heart.

(No offence to any who considers themselves a TechoGeek, I admittedly am one).

I am sure that you will agree though that the MS Solution is not so bad and that it does indeed work, although for once MS does not offer any bells or whistles. On top of that the MS solution does not require any System Hogging drivers to be loaded.

All in good heart, Roy

[christopher_wolf]

True, quite True

But when I could *not* connect to a Wireless network for over half an hour using the MS Wireless Utility...I was forced to use Access Connections, which diagnosed exactly what the problem was, created a log of all the attempts, and enabled me to extract certain infomation which was supposed to be static on my Thinkpad for the Network to actually work; the MS Manager did squat-all in trying to help there; all I would get is the "limited connectivity" message. I travel alot, so adapting to different networks is important. It seems as though Access Connections does an extraordinarily good job of this as I can attest to how many Wireless Networks I have connected to without knowing anything at all about their setup; it really did seem as though AC actually changed options to sync with the Network all by itself; as if it were "learning." Plus, it connects when coming back from suspend instantly. All i can say is use what you like.

[bill bolton]

> that it does indeed work

It works only as a simple link manager, but it doesn't work at all as a connection manager.

Cheers,

Bill