This is a long post, but please, bear with me for a while.
Yesterday, I probably made the worst computer mistake in my life.
I wanted to try what I thought was a live version of ReactOS, but as soon as it booted, I think it wiped out the MBR and maybe even the boot record that shows the location of the extended partition (I'm not 100% sure about this one).
I use Win98SE.
The HDD was originally partitioned with only one primary (C: ) and the rest was an extended containing 3 logicals (D: and E: on this drive and F: for the entire second HDD)).
If I try to boot from the CD or from the HDD, I now get this message:
What's weird is that if I choose F1, Win98SE seems to load normally, then right after the Windows starting screens (big flying Windows logo) appear, it tells me it is unable to find command.com (I tried all possible paths). I can use a:\command.com of course, but it's useless since it can't start Windows either.F1...DOS
F5...Disk 2
F1 Default
Type the name of the Command Interpreter (e.g., c:\windows\command.com)
C>_
If I choose F5, it tells me it's an invalid boot drive (I guess F5 is for my second HDD, which is an extended partition and therefore cannot be booted from).
When I boot from a startup floppy, I can't access any partition as if none was partitioned.
Not ready reading drive C
Abort, Retry, Fail?
I wonder how is the new MBR able to partially boot from c:, load the startup logo (located AFAIK in c:\windows\????.sys) and try to load the command line when I can't even access c: from the floppy?
Now my big question: is there any hope to solve this or have I lost any chance of ever getting all my data back?
Is there for example any data recovery software (free or commercial, but reliable) that could "manually" read the entire disk to find the boot records or the FATs for D: and E: and recover some files from there?
I'll be grateful to the kind souls who could help me out of this terrible mess.