In case you didn't know, Windows XP will look for a new wireless connection every 3 minutes, which usually doesn't cause any problems, but when you don't want to roam, there isn't any way to turn it off, until now.
Just run the batch file, which starts and stops the service for you! If you stop it, it will automaitically start when you re-boot. This has kept my laptop connected all day in a rainstorm, while it kickedme off 3 times in two hours before I wrote the batch files. (Actually, I did it by hand this afternoon, and wrote the batch files to automate it tonight)
There's gotta be a better way of doing it than that.
I also suffer from that, but apparently if you update the drivers for your wireless adapter, it will fix it. Due to the fact that for the Centrino, you can't get them from Intel directly and my OEM seems to have made a stuff up, I can't update mine, so I just use the ProSet utility.
I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
I have the most recent drivers, and when the connection is good, then it is good. The problem is when conditions are less than perfect. I don't need Windows searching for a new connection every 3 minutes.
If there is a better way than simply turning off the service, then I'd like to know it. This method is foolproof, and keeps me connected even under the worst of conditions. If you know a better way, then please post it.
This is the only thing that has worked for me, and I've been trying different methods and settings for over a year.
I did mention it, I use the Intel ProSet utility, it disables the Windows one. Though I need to find out how to get non-administrators to use it. It locks up for users when they try to run it.
I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
No, Intel ProSet only works with Intel NIC chipsets. So if you don't have one, you can't use it. Mine's really touchy too, I can't seem to update the drivers otherwise it doesn't detect it anymore, PITA.
I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
Reply With Quote
