Bernie said:
I have all the most important data backed up. But I have a huge number
of downloads (utilities and lots of other stuff) that would take a long
time to replace. It is worth it to me to spend some hours and even some
money not to have to replace those things. So...
I had four partitions; XP, Vista, Linux and a Linux swap. The XP
partition is the important one.
So I can see there are sites promising partition recovery software for a
fee. I don't mind a smallish fee but I want to know what works and what
doesn't first.
So anyone out there good at data recovery?
More data: I have another drive in the machine with a lot of free space
but it is also my data drive. It is okay but doesn't have an O/S on it.
There isn't a working O/S on the main drive and it is the main drive
that I want to recover. So the ideal solution is something that can
work from a bootable CD.
Bernie:
Following your posts today it seem that your problems really began after
you installed osl2000. Although it did not seem to boot the OS's
correctly (for some reason) I would think that it still knows where the
partitions are (or were).
I don't know about osl2000, but I think the way these boot managers work
is that they install themselves to a small partition, and then change
the IPL code in the MBR to transfer control to this partition, rather
than to the boot sector of the active primary partition (which is what
the "Standard IPL" code does). On first installation it also copies the
partition table in the MBR into its own internal partition table,
sometimes called the extended MBR (EMBR). Now when you reboot, the
machine boots to the boot manager (which is a kind of mini-OS). The boot
manager then displays a list of the bootable partitions in its EMBR,
from which you choose one.
When the boot manager boots (or tries to boot) to the selected OS, it
may hide the partitions of the other OS's. To do this, it rewrites the
MBR to include only the partition of that OS (which it makes the active
partition), and removes the others. However, its EMBR still knows where
all the partitions are.
When you want to install a new OS, the boot manager makes a new
partition for it, and makes it the active partition in the MBR (probably
hiding the other OS partitions). You then boot with the CD of the new
OS, and install to the created partition. The installation typically
rewrites the MBR IPL code to transfer control to the boot sector of the
new partition. So now the machine boots only to the new OS. To fix this,
you have to do a "repair install" of the boot manager, so that the IPL
code in the MBR again points to the boot manager partition, so the
machine will boot to the boot manager again.
What you did, I think, was run fixmbr from the XP disk, thereby losing
the boot manager. You probably should not have done this. But if you are
able to do a repair install of the boot manager (as after installing a
new OS), its EMBR should still have a record of where all the partitions
are. The important thing is to do this "repair install" rather than a
fresh installation, because the latter will copy the current MBR into
the EMBR. One you have done the repair install, the boot manager should
have some mechanism for putting all the EMBR information back into the
MBR, and your partitions will be restored.
I don't know if this will help you at all. My understanding of these
things has come from playing with the Ranish Partition Manager, and it
may not apply to osl2000. But I think these boot managers generally
operate in a similar manner.
HTH,
David Wilkinson