Windows Sockets Initialization Failed

[aligator79]

I am trying to fix my sister's computer. It is an emachines (I know) with XP on it. The bubble kept popping up saying they were dangerously low on memory. So they did what it told them to do and deleted the files it showed them. Needless to say they deleted some of the system files.

The error message we get is "Windows Sockets Initialization failed". We now want to reinstall windows to get back to the beginning. My problem now is that I have some pictures on the computer and need to get them off.

The computer has a CD-RW which doesn't work. We got a flash drive to save them to but when we try to use it the computer wants drivers to install. I tried using my digital camera and putting them on it and it wants drivers for it also. I was going to try emailing them to myself, but I cannot get onto the internet due to the error messages.

I was told that I could either reinstall windows over windows and it would only replace the system files but when I put in the disc and hit f12 it only gives me the option to overwrite everything. I was also told that I could network that computer to mine and pull the files that way. I'm leery about that due to the fact that it has no virus protection on it.

Any suggestions on what to do???

[tdbs]

tried the good old floppy?

if that doesnt work (although it will 99%), take the HDD out of that comp, set it to slave and hook it up to another working comp (with its own master HDD with windows installed). once it boots scan the slave drive for viruses (since you say it has no antivirus), and copy all the files you need

then be sure to reformat the drive before you install windows

good luck

[aligator79]

I've tried the floppy, but the files are too big to put onto it except one at a time and there are more than 300 to move.

Stupid questions: What's an HDD and how do you do what you proposed?

[tdbs]

hdd = hard disk drive = hard drive,

if you're not comfortable with this operation, dont do it; otherwise, here's what I had in mind:

- make sure you have another, separate, working comp (w/ windows installed)

- assuming its an IDE drive (wide grey ribbon cable connection); if its a SATA (narrow cable) - skip this section

- disconnect and take the hdd out of the messed up comp
- there should be a jumper on the back of the drive (little metal connection clip) - set it to Slave (marked SL or SLAVE) on the drive
- make sure the hdd in the other (working) comp is set to Master (MS or MASTER on the marker)
- connect the hdd from the messed up comp to the other IDE connector (on the same cable) on the good comp - so both the good and the messed up drives are connected to the same cable set as Master and Slave respectively
- boot it up (pray ot works...it should)
- since the messed up hdd had no virus protection, scan it immedeiately after boot using antivirus on the good hdd
- copy the files from the messed up hdd to the good one

if its a SATA drive - same thing, but no need to worry about Master/Slave setups, just make sure the messed up hdd is not connected to the very 1st SATA connector

good luck