Problem with WinXP repair install

I'm in mid-repair install on a PC (Windows XP Home SP2) and I've been stopped in my tracks by "Setup cannot copy the file clbcatq.dl_. Ensure the disk labeled Windows XP Home Edition Service Pack 2 is in the drive selected below, or provide the location where the file can be found." This particular error I've seen a few times in the past, only when trying to do repair installs, and have never been able to get around it. I've tried other XP install discs, and the error still comes up. On this PC, the beginning of the install went perfect (the blue screens with white letters), but once it got into the graphical section of the install, things slowed to a crawl. The PC sat at "34 minutes remaining" for about a half-hour; then it sat at "33 minutes remaining" for another 20 minutes. It eventually got past the "installing devices" section, and is now in the "copying files" part. But it has taken over an hour to get this far, and now I have the error. Anyone have any ideas? Should I skip file? Should I just back up the data, format, and reload? Should I abort the install and run some diagnostics on the HD and/or RAM???

Any ideas will be appreciated!

Thanks!

 

I think it's a diabolical ploy by Microsoft, they probably put a "slowly deteriorating metal film media virus" in all the CD's produced so you have to purchase a new copy or new O/S. ;>)

Seriously though, I've seen this more and more on the various help forums I visit. "Cannot find/copy filename.ext" on fresh or reinstalls. On the site where I "work", there's one guy who has invested in a new CDROM, and is now looking at a new hard disk to get by this problem. He's tried everything else. Maybe some of the suggestions there will help you. http://www.d-a-l.com/help/windows-xp-help/56570-missing-files-during-clean-install.html This is just one example. I've seen/helped with more. It's weird that this problem seems to be prevalent across several help forums/sites lately.

Sorry I don't have any answer for you.

 

Wow I didnt think that micrsoft would put an expiration date on their stuff---but who knows??? Did you try Daricks boot and nuke to try and solve the issue???