Dual Boot Problems...big problems

wdhart · 06-21-2003, 07:17 AM

Just as your Linux cannot read NTFS, Micros**t XP cannot read the Linux hard disk format. So XP is now saying what you are calling drive D is drive C. Not sure if someone else has made this point -- there are so many replies! But when you said the system could not find drive D, that was true.
...........Bill

jarib · 06-21-2003, 12:08 PM

Looks like when you created d: it was an extended partition. Then you removed the primary partition :c and left the extended dos partition. Is that possible. Probably not a recomended configuration. Don't know if you can boot an extended partition?

anyone?

wdhart · 06-21-2003, 03:07 PM

No, sorry! I have two drives, hd0 and hd1. If both were FAT format they would be (and were once) respectively C: and D:. But I moved my Windows system from C: to D:, then gave over the whole hd0 drive to Linux. Guess it comes to much the same thing, though.

After much exploration, I have managed to work out how to get Lilo to double-boot this combination satisfactorily. Let me know if you want the command set!

...........Bill

pstpup · 12-09-2006, 02:30 PM

go get yourself a copy of system commander, the latest version. or download from a p2p which ever. you'll like it

saikee · 12-09-2006, 04:44 PM

This lines in Post #1

Code:

 booting dos...
rootnoverify(hd0,4)
chainloader +1

confirms XP is in the first logical partition hda5.

It is evident XP was booted by the NTLDR resideing in the original C drive. The 3 needed files are now gone as the space has been used up (or half of that) for Red Hat Linux.

As far as I am aware XP will not boot without the boot.ini, NTLDR and NTDETECCT.com.

All the data in inside the XP partition is pertfectly save unless the owner destroys it himself. All modern Linux can read a NTFS partition, don't need to have its partition declared and and then write the content on any other partition, say a Fat32 for importing back to a MS system. Red Hat is not modern. It is ancient. THus using a Live CD will be able to salvage all the files inside hda5.

BY the way the partition number of XP of drive D will be "1" as partition "0" would be the original C-drive. As Red Hat most likely need two partitions minimum to install (one for itself another for Swap) and so the current partition of the XP will not match the old record. It is however possible to edit boot.ini to reflect the new position but the internal part of XP also has records of its original partition position. It does look like a losing battle to me to rescue XP now with Red Hat in the way.

If XP is important (not just the data) it may be simpler to go back to the original setting of "C" and "D" drives.