Pc Compaq Deskpro - Celeron A 495mHz - 128mb SDRAM.

Partitioned and formatted an 8Gb hdd (C:=3gb D:=remainder) and installed Win.2k Pro. No problems noted. System ran ok, installed AVG and Zone Alarm then rebooted. Immediately after the splash screen displayed, a notification was posted that drive D: was being checked then a further message that the Master File Table was corrupt and CHKDSK was aborted.

Immediate thought was that the hdd had failed but it passed the manufacturer's diagnostics. Drive D: was SHOWN in the My Computer window but could not be accessed.

Reformatted the partition (used Disk Management) and continued USING it until another reboot when the above problems repeated. No problems with C:

Installed a different hdd, partitioned/formatted - no problems with W2k install. Installed PROGRAMS, rebooted, repeat of above error

Second thought was that the W2k cd was defective so used it to install on another pc without problems. Installed programs and rebooted several times without error.

Installed Win XP Home on the Deskpro using the original hdd which W2k picked as being defective, no errors.

Both the W2k and XP cd's are genuine with coa's.

Current thought is that there is 'something' in the Deskpro hardware which causes the problem with W2k.

Any ideas please?"Current thought is that there is 'something' in the Deskpro hardware which causes the problem with W2k."

I have had this happen with the modem or sound card not working
with the install.They did not play WELL together.

My solution was to remove the modem and sound card,install the
operating system,then add the parts back to the computer,one
at a time after install.

This happened to me with a Compaq Deskpro EN so, give it a try.Thank you Street1. I tried your cure but the error still came up.

However, today I did things just a LITTLE differently.

When SP.4 completes, the option to reboot 'now' or not reboot is available. I have been opting not to reboot at that point and proceeding to install all the hotfixes which were produced after SP.4 then reboot when all were installed.

Today I rebooted after SP.4 and the error did not appear. So, it seems that a reboot is necessary after SP.4 despite the option not to reboot being available.

Still baffled as to why not rebooting would cause a corrupt MFT but I'll quit while I'm ahead.

Thanks again.Good for you.Smart thinking.Glad you got it fixed
friend.