A recent question here was for a workstation that stopped booting when a software install created some 6500+ temporary files in the root of their boot hard drive. While Recovery Console has the DEL command, it does not without pre-planning on your part allow the use of wildcards; e.g. DEL *.tmp is not permitted. ( While FAT32 volumes have a limit of 512 entries in the root of a vlume, and long files names count for 4 entries if they are used, I assumed it was this issue that was responsible. But the drive was NTFS. Hmmm.....
Then I remembered this KB article:
And its XP version:
My guess was that the process of file creation, and file deletion, had so defragmented the MTF that poor old NTLDR was getting lost in the shuffle.
Do not wait for an error to happen to you. Once a year or so run the MFT defragmentation tool on your NTFS volumes.
Now Why, you might ask, are the utilies named BCUpdate2.exe? Because the most likely symptom of excessive MFT fragmentation is a blinking cursor at top left when starting XP. "BC = Blinking Cursor"
HOWTO: Use the BCUpdate2 Utility on NTFS Volumes
[ul]
[li]You must create an XP Boot disk, and boot from it. Since the MTF is locked while XP is active, you have to access XP in this indirect fashion.
[/li]
[li]To create an XP Boot disk for an NTFS Partition:
[/li]
[li]You have to use a fairly specific command line:
bcupdate2.exe drive_letter: /f
[/li]
[li]You can ask for the file from Microsoft Support. See my second link above.[/li]
[/ul]
Best wishes,
Bill Castner
Then I remembered this KB article:
And its XP version:
My guess was that the process of file creation, and file deletion, had so defragmented the MTF that poor old NTLDR was getting lost in the shuffle.
Even in situations without a lot of file activity in the root of your boot volume, over time an issue of MFT fragmentation can lead to a surprise boot message that NTLDR is missing. Since the MFT is not defragmented by the native XP utility, nor by others except as a boot-time scheduled task, it made sense for Microsoft to release utilities to do the job.
Do not wait for an error to happen to you. Once a year or so run the MFT defragmentation tool on your NTFS volumes.
Now Why, you might ask, are the utilies named BCUpdate2.exe? Because the most likely symptom of excessive MFT fragmentation is a blinking cursor at top left when starting XP. "BC = Blinking Cursor"
HOWTO: Use the BCUpdate2 Utility on NTFS Volumes
[ul]
[li]You must create an XP Boot disk, and boot from it. Since the MTF is locked while XP is active, you have to access XP in this indirect fashion.
[/li]
[li]To create an XP Boot disk for an NTFS Partition:
[/li]
[li]You have to use a fairly specific command line:
bcupdate2.exe drive_letter: /f
[/li]
[li]You can ask for the file from Microsoft Support. See my second link above.[/li]
[/ul]
Best wishes,
Bill Castner