I work in a bank, and losing data even once-in-a-blue-moon is not acceptable. Tantalizingly, our Windows XP machines fail in a range of recoverable ways.
Today, I have a machine with a 20GB IDE HDD that has 2 partitions: 0 is FAT32 (1GB, for holding the source files for drivers, etc.), and 1 is NTFS (all the remaining space, for the running OS).
This particular machine crashed on the user, claiming that the XP loader couldn't find PCI.SYS. In cases similar to this previously, I'd run the Windows XP Setup disks (WinXP_EN_PRO_BF.EXE if you can find it), copied over the necessary file from thumbdrive, and restored the system's ability to boot. In contrast, for simple data recovery, I had put the HDD into another XP machine machine and then inspected the added NTFS partition for files.
Not this time, however. XP thinks there is a partition, but considers it unformatted. Hence, I have a damaged NTFS partition.
Well, I'm currently running ZAR32 (Zero Access Recovery) version 7.3.0, and it's taking a gawd-awfully long time to process. I suspect that ZAR32 is going to fail to recover the partition.
What would you do in this case to attempt to repair the NTFS partition? Given the state of the damage, even a lossy repair is much, much better than nothing.
Today, I have a machine with a 20GB IDE HDD that has 2 partitions: 0 is FAT32 (1GB, for holding the source files for drivers, etc.), and 1 is NTFS (all the remaining space, for the running OS).
This particular machine crashed on the user, claiming that the XP loader couldn't find PCI.SYS. In cases similar to this previously, I'd run the Windows XP Setup disks (WinXP_EN_PRO_BF.EXE if you can find it), copied over the necessary file from thumbdrive, and restored the system's ability to boot. In contrast, for simple data recovery, I had put the HDD into another XP machine machine and then inspected the added NTFS partition for files.
Not this time, however. XP thinks there is a partition, but considers it unformatted. Hence, I have a damaged NTFS partition.
Well, I'm currently running ZAR32 (Zero Access Recovery) version 7.3.0, and it's taking a gawd-awfully long time to process. I suspect that ZAR32 is going to fail to recover the partition.
What would you do in this case to attempt to repair the NTFS partition? Given the state of the damage, even a lossy repair is much, much better than nothing.