The only consistant fix I've seen for that error is using the windows command line "netsh winsock reset"
Use that, then reboot. AFter that, it seems to be a crap-shoot. Gotta say, I'm sorry that you got that bug. You wouldnt happen to have another computer would you? Even a roomies just to test.
__________________
You bore me.... next.
|