a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
How to Reload Windows XP Without Removing Files
Deleting system files, modifying the registry and installing incompatible drivers to Windows XP can damage the integrity of the operating system, rendering it inoperable. Virus infections are often responsible for making the aforementioned changes to a system, but employees who have administrative access to the workstation can make deleterious modifications to the OS as well. Reinstalling Windows XP can repair the OS, but if work-related files are stored to the system partition, all of the data will be erased during the installation process. To reload Windows XP without losing files, you can perform an in-place upgrade, also known as a repair installation.
Step 1Insert the Windows XP CD into the optical drive and then press "Ctrl-Alt-Del" to restart the computer. Step 2Press any key when prompted to load the contents of the disc. Press "Enter" on the Welcome to Setup screen. Step 3Read the license agreement, pressing "PgDn" to scroll down the page. Press "F8" to agree to the terms. The CD will search for previous installations of Windows XP. Step 4 Press "R" to repair the selected operating system. The disc will begin reinstalling the operating system to the hard drive without affecting personal files. Follow the on-screen prompts to complete the repair installation. Step 5 Log in to Windows XP and sign on to the Internet when installation completes. Click "Start," "All Programs" and then "Windows Update." Step 6 Click "Scan for Updates" to search for applicable service packs and hotfixes to reinstall to the OS. Step 7 Click "Install Now" to bring the in-place upgrade up-to-date.
Windows XP CD
Make sure you have your Windows XP product key (found on the CD cover or on the computer case) available prior to reinstallation.
If possible, back up your files previous to the installation in case something goes awry during the process.
You will need to reinstall all non-native programs and removable devices after performing an in-place upgrade.
There's always the chance that the error Code 22 you're seeing on a device was caused by a temporary problem with the hardware. If so, a restart of your computer might be all you need to fix the Code 22 error.
Did you install a device or make a change in Device Manager just before the Code 22 error appeared? If so, it's highly likely that the change you made caused the Code 22 error.
Undo the change if you can, restart your PC, and then check again for the Code 22 error.
Depending on the changes you made, some solutions might include:
Important: If a USB device is generating the Code 22 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Correctly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
If updating the drivers does remove the Code 22 error, it means that the stored Windows drivers you reinstalled in the previous step were either damaged or were the wrong drivers.
Clear CMOS. If Windows had to disable the device, generating the Code 22 error due to a lack of system resources, clearing CMOS might fix the problem.
Update BIOS. Another possibility is that a newer BIOS version could better pass system resource handling to Windows, correcting the Code 22 error.
Move the device to a different expansion slot on the motherboard, assuming of course that the piece of hardware with the Code 22 error is an expansion card of some kind.
If the Code 22 error is due to a lack of system resources available for the card, moving it to a different slot on the motherboard could clear up the problem. This isn't as common a situation with newer hardware and Windows versions but it is possible and is an easy troubleshooting step to try.
Replace the hardware. A problem with the device itself might be the root cause of the Code 22 error, in which case replacing the hardware is the next logical step.
While not likely, another possibility is that the device is incompatible with your version of Windows. You can always check the Windows HCL to be sure.
Note: If you're positive that the hardware is working properly and is properly configured then you might consider a repair install of Windows. If that doesn't work, try a clean install of Windows. I don't recommend doing either before you replace the hardware, but you may have to give them a try if you're out of other options.
Please let me know if you've fixed a Code 22 error in a way I haven't mentioned above. I'd like to keep this page as accurate as possible.
See Get More Help for information about contacting me on social networks or via email, posting on tech support forums, and more.
Be sure to let me know that the exact error you're receiving is the Code 22 error in Device Manager. Also, please let us know what steps you've already taken to try to fix the problem.
Show Full Article
You could have a ghost device in the system. Remove the card and start the computer in safe mode. Look at the device manager to see if there are any sound devices detected. If so, delete them. Now install the card and let Windows detect it. You probably left the card in the machine when reinstalling the O/S. You shouldn't have any peripheral devices hooked up when doing a reinstall of Windows XP.
The best way to handle this is to completely reformat the drive again, to rid win 7 and the bad XP, and to then re-install XP from the DVD all anew. Any other way is just going to cause hassles trust me.
There are a couple of way to do this: Click on the start menu and then click on run, in the box type rstrui.exe and press enter. Or you should find system restore in All programs, accessories, system tools and system restore should be there.
Once you have the system restore window up click on restore my computer to an earlier time and take the computer back to a time before you deleted/uninstalled the programs.
I don't think there is such a version. It's probably either Windows 98 or Windows XP Professional.
If a reboot does not help, the simplest thing to try is to reinstall the device driver registry entries for the USB port.
Assuming you have Windows XP, right-click "My Computer" and select "Manage". Under "System Tools", select "Device Manager". If Windows is detecting problems with any of the device drivers, the Device Manager entry will be flagged with a exclamation point caution sign. Otherwise, you can try removing all of the entries under "Universal Serial Bus controllers". To remove the entry, right-click it and select "Uninstall". Remember, this only removes the entry from the registry. Unless the drivers are corrupted or missing, you will likely not need the install disk to reinstall the entry. Once you are done, reboot and Windows will detect the USB controller(s) does not have an entry and will prompt you to reinstall it. Take the option to let Windows find the drivers for you. If this procedure does not work, try uninstalling and reinstalling the drivers for the device. If that does not work, you likely have a hardware problem - bad cable, bad connection, etc.
If you do indeed have Windows 98, it's been a while, but the above procedure should be similar.