Using MSCONFIG to Disable a Startup ProcessIf you are using an IBM 11a/b/g Wireless CardBus – PCMCIA – on a machine running Windows XP with Service Pack 2, you've probably noticed conflicts between XP's Network Connection utitlity (XPNCU) and the IBM Client Utility (IBMCU), as they both attempt to control your wireless connections.
The main symptom of this conflict appears shortly after starting the computer. First, the IBMCU connects to to the wireless hot spot. Then, a moment later, the XPNCU attempts to connect to the hot spot, disconnecting any connection the IBMCU had already established. After this disconnection, the XPNCU refuses to connect to the hot spot, apparently sulking because it is not set up as the primary networking utility.
The manual (read: annoying) work around for this problem involved waiting for the conflict to occur, and then clicking through the advanced settings of the XPNCU, effectively putting it back in control of wireless connections.
I realized that one of the two utilities needs to be disabled. And since it's probably easier to disable third-party software than an integral part of Windows XP, I set my sights on disabling or removing the IBMCU. This proved more difficult than I had anticipated.
If you have found any errors, omissions, or grounds for legal action, please contact me at "troy" at this domain name. (textheavy.com)