What the hell? I've never dealt with this, before, and now I've had two Windows installations (one XP Home and the other XP Embedded... yes, I built the damned thing myself...) go south and have to be fully reinstalled because of Winsock2 corruption. What is with that?
How do I know it's Ws2? Because when I open a command prompt and type in ipconfig /release I get "Windows IP Configuration - The operation failed since no adapter is in the state permissible for this operation."
Here's the documentation from Microsoft: support.microsoft.com/kb/811259
Anybody have any idea why this is happening? I'm more interested in getting the XPe installation fixed. With XP Home I just blew the partition and reinstalled. Shotgun therapy, I know, but I was in a hurry.
I'm currently recompiling my XPe image, again, to see if I accidentally configured a component that may be causing a resource conflict with the wireless card. Gah!
Love and light, dear ones.
Rev
How do I know it's Ws2? Because when I open a command prompt and type in ipconfig /release I get "Windows IP Configuration - The operation failed since no adapter is in the state permissible for this operation."
Here's the documentation from Microsoft: support.microsoft.com/kb/811259
Anybody have any idea why this is happening? I'm more interested in getting the XPe installation fixed. With XP Home I just blew the partition and reinstalled. Shotgun therapy, I know, but I was in a hurry.
I'm currently recompiling my XPe image, again, to see if I accidentally configured a component that may be causing a resource conflict with the wireless card. Gah!
Love and light, dear ones.
Rev
posted by:
|
Portland
|
