I made a mistake.
The second identical copy of fdc.sys on my XP MCE 2005 installation, which has SP2 updates built into the first of two CDs and has been updated in Windows with SP3 updates, is in
so to correct the line, if you had / have that situation too....
copy C:\Windows\ServicePackFiles\i386\fdc.sys C:\Windows\System32\drivers\
copy C:\Windows\ServicePackFiles\i386\fdc.sys C:\Windows\System32\drivers
(on that computer fdc.sys in C:\Windows\System32\drivers and in C:\Windows\ServicePackFiles\i386 is the one included in the SP3 updates)
If SP3 updates are built into the XP Pro CD, you may not have a second identical copy of fdc.sys on the hard drive.
You could search C:\Windows (and subfolders, the default) for fdc.sys to see if you DO have an identical copy somewhere - same date and size as in C:\Windows\System32\drivers (unless it's damaged such that that's not correct), and modify that copy command line if you need to, if you do.
Mine is 27kb (rounded) in the search results, more specifically, RIGHT click on it, in it's Properties, 26.7kb, 27,392 bytes.
The date in the search results is the same as the Modified date in the Properties.
On two different installations, it's April 14 2008 on the MCE 2005 computer, April 13 2008 on an OEM XP Pro SP2 installation that has been updated with SP3 updates.
(Both those installations were installed from CDs that had SP2 updates originally. It doesn't matter if your date is different - it may be newer if it was built into the CD - but the size should probably be the same if your installation has SP3 updates installed.)
It's the driver for the floppy disk controller, by the way.
If you don't have an identical copy, or in any case, you could.try this.......
Boot into Safe mode.
Start - Run - type... cmd
Insert your XP CD in a drive.
Close the window if it auto starts.
Type.... extrac32 (CD drive drive letter):\i386\fdc.sy_ C:\Windows\System32\drivers (press Enter)
E.g. if the CD or DVD drive you have the CD in is E, type....
extrac32 E:\i386\fdc.sy_ C:\Windows\System32\drivers
You will be asked if you want to overwrite C:\Windows\System32\drivers\fdc.sys
(I tried that - you are allowed to overwrite the file because it's not being used by the system, unless you're using the floppy drive at the time).
You MAY need to Restart the computer after that to have your error go away.
extrac32 is XP's cab extraction utility
fdc.sy_ is the compressed version of fdc.sys on the CD
OEM XP MCE 2005 is OEM XP Pro SP2, with a few Pro features that most people don't use omitted, plus the major Media Center group of programs and additional multimedia support.
All versions of XP MCE are OEM.
I have the Microsoft OEM MCE 2005 2 CD set.
If replacing fdc.sys doesn't get rid of the error, it may be there is something else wrong but Windows can't tell you what that is directly.
You could test your hard drive, that Windows was installed on if you have more than one, to make sure your hard drive is not failing.
(If it is failing that is probably what caused your problem.)
Check your hard drive with the manufacturer's diagnostics.
See the latter part of response 1 in this:
If you don't have a floppy drive, you can get a CD image diagnostic utility from most hard drive manufacturer's web sites, but obviously you would need to make a burned CD, preferably a CD-R for best compatibility, on another computer if you need to.
Seagate's Seatools will test any brand of hard drive.
Do the long test.
The bootable Dos versions of SeaTools can be used even if Windows is not working properly.
If the hard drive itself tests okay, any data problems found can be fixed, one way or another.
It's also possible, but not likely, that malware has made a bogus fdc.sys file and placed it in C:\Windows\System32\drivers.
If fdc.sys is in C:\Windows\System32 other than in C:\Windows\System32\drivers, that probably IS malware .
It would probably NOT be, in it's Properties, 26.7kb, 27,392 bytes.
Your problem could also be caused by corruption that CHKDSK (Check Disk) can fix.
You could Run: cmd
CHKDSK /R C:
in Safe mode
(answer Y to the question)
that will test the whole partition with more tests than CHKDSK /F C:
does, including the free space
However, when you're checking the partition Windows was installed on, CHKDSK /R (or CHKDSK /F ) has to run just before Windows loads normally, and that may NOT work when Windows won't load normally or is producing an error, so you may NOT be able to do that until Windows will load normally.
OR - you can always run CHKDSK /R C: in the Recovery Console interface when you boot from the CD (there is no CHKDSK /F available there.)
I'm assuming your Windows installation has the C drive letter.
It's possible with XP (and 2000) that it hasn't been assigned C, depending on whether or not Setup detected other partitions on a hard drive that had already been assigned drive letters when it was run, which other devices have been or assigned drive letters or are assigned drive letters by Setup, and where and how the hard drive Windows was installed on is connected to the mboard when Setup was run.
E.g. I just re-installed OEM XP Pro on a friend's computer from scratch.
The DVD drive was on Primary IDE jumpered master, the hard drive on Primary IDE jumpered slave. It has a memory card reader that is assigned 4 drive letters for 4 types of memory cards.
Setup assigned H to the partition Windows was installed on, not C.
C, D, E,.F - memory card reader
G - DVD drive
I changed things - DVD drive to on Primary IDE jumpered slave, the hard drive to on Primary IDE jumpered master. I unplugged the USB connections to the front panel memory card reader.
I ran Setup from scratch again - the partition Windows is installed on was assigned C.
D - DVD drive.
I plugged in the USB to the memory card reader - E, F,G, H
(You can change any drive letter assignment, C to Z, except the one assigned to the partition Windows booted from, in Disk Management.)
When you go to Run , type.. cmd
The drive letter at the beginning of the resulting line is the same as the drive letter of your loaded Windows installation.