On Sun, 16 Dec 2001 21:46:42 -0800, Derek Blazer wrote: > Thanks for the replies. I have tried to provide additional info below: > > ----- Original Message ----- > From: "Anita Lewis" <[EMAIL PROTECTED]> >> >> You might try running the cdrom as a rescue disk to see what is > happening. >> I know you can do that with the RH disk. Boot it and then do 'linux > rescue' >> That will start linux in ram. Then do >> 'fdisk -l /dev/hda' and write down what that looks like. > > I don't understand how I can use a linux disk as a rescue disk for > windows.
Actually, you should be able to do this and see what the hard drive looks like from linux. I misunderstood and thought you had installed, but when you booted you got that message. You are getting it when you attempt to install. My hope is that by running the linux rescue and then that fdisk command, you will see what the hard drive looks like. It may not be accessible or there may not be any unpartitioned space. I'm not sure what kind of message that would give, but I thought a look at it while using a linux kernel in RAM would be helpful information. If you get that error when you run 'linux rescue' then the problem is with loading a root filesystem into RAM. I may have the terminology wrong, but that's the general idea. I just finished installing slackware on a laptop with 4Mb RAM and using floppies. First there was the boot floppy with the kernel and then a root floppy which put a filesystem into RAM. I think that is what happens with the install from cdrom too. You have plenty of RAM; so I'm interested to see what happens with trying to run the cdrom as a rescue disk. RH does this and perhaps other distros do too. Anita _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
