I'm hoping to recover a hard drive messed up by a mate of a wayward offspring. I bought identical machines for both her and me, knowing there would be problems and hoping that we could get over some problems by looking at identical systems. Problem started when mate tried to mess with BIOS to get better performance. His report was the mouse went bad, but I found the machine would boot to diskette and had no MBR, but data on disk still good and accessable. I said I would bring some backup and copy files but before that happened, his "EXPERT" brother ran something from SuperFDISK that clobbered the drive geometry. Below is the report I get now from FDISK and SFDISK. I've never worked with anything down to this low level of hard drive problem and don't know where to start. Could someone help me with a good tool or writeup on how to beging recovery? Any guesses about if the Granddaughter photos that were still on the drive before the SuperFDISK running could still be recovered? Although the machine is 2000 miles away, I now have the hard drive and the like configured machine in my hands for testing and repair.
BAD DRIVE
CYL 2442384
HEAD 16
SEC 2
PART ACTIVE SYSTEM LABEL START SPACE(MB)
C H S
NO FREE] 1 1 1 37173
1 NO HIDDEN/FAT32 IBM_SERVICE 2379126 0 1 988
NO FREE} 2442382 0 1 0
WORKING DRIVE ON ANOTHER MACHINE -
BAD DRIVE WOULD HAVE LOOKED LIKE THIS BEFORE THEY BROKE IT
CYL 4865
HEAD 255
SEC 63
PART ACTIVE SYSTEM LABEL START SPACE(MB)
C H S
1 YES HPFS/NTFS IBM _PRELOAD 0 1 1 37173
NO HIDDEN/FAT32 IBM_SERVICE 4793 0 1 988
BAD DRIVE
CYL 2442384
HEAD 16
SEC 2
PART ACTIVE SYSTEM LABEL START SPACE(MB)
C H S
NO FREE] 1 1 1 37173
1 NO HIDDEN/FAT32 IBM_SERVICE 2379126 0 1 988
NO FREE} 2442382 0 1 0
WORKING DRIVE ON ANOTHER MACHINE -
BAD DRIVE WOULD HAVE LOOKED LIKE THIS BEFORE THEY BROKE IT
CYL 4865
HEAD 255
SEC 63
PART ACTIVE SYSTEM LABEL START SPACE(MB)
C H S
1 YES HPFS/NTFS IBM _PRELOAD 0 1 1 37173
NO HIDDEN/FAT32 IBM_SERVICE 4793 0 1 988