Cyclic reduncdancy check errors

[gutted]

I'm running Win2k (sp3, plus a bunch of hotfixes) on my work laptop.

I'm trying to copy a VMWare image to a 'safe' network location, but part way through the file copy it bombs out and gives me an error about cyclic redundancy checks.

I'm getting a bit anxious This is a temporary laptop, since my last one got stolen... I've only just managed to recover what I could from several week's worth of lost data. (It turns out that in the current office location, Veritas runs but doesn't actually back up anything. It's a long story, but let's just say I was not pleased when I found out I had lost so much data).

So anyway - I've got a sinking feeling that this temporary (old) laptop is on it's way out. I've got our IT guys on the case and they are looking at getting me a new hard-drive.

Meantime, is there anything else that could be causing this?

Cheers!
Dan.

[NEPATEC]

Hi Dan,

The problem here is most likely the result of an NTVDM error. Assuming that your IT guys are going to copy your existing configuration over to the new hard drive, this approach will not solve the problem. What will solve it should take less than 5 minutes. All you need to do is replace a few files on your machine + delete a few others.

You mentioned that you are running Windows 2000 (SP3) . . .

In order to correct the problem, refer to Q305521 of the Microsoft Knowledge Base [ http://support.microsoft.com/default...b;en-us;305521 ]

By replacing the existing versions of config.nt, autoexec.nt, and command.com with the "stock" versions that ship with Windows 2000, you should note that the error(s) no longer occur(s).

An additional step in assuring that things return to normal is to do a search on your drive(s) and rename all files with the extension *.prf to something other than prf (I usually use *.pr!)

This should knock it out for ya.

Mike

[gutted]

Thanks Mike.

I didn't see your reply 'till this morning, so in the meantime I ran several defrags plus a startup checkdisk (chkdsk /f /r). Checkdisk found a couple of bad clusters which it replaced, and that sems to have solved the problem for the moment. I can now take a safe backup of my VM image. The VM image still seems to work ok too (thankfully!)

Thanks for the info - I'll have a look at the MS article and will most likely also apply the config changes you suggested.

Excellent stuff - this forum rocks

Dan.