It says this:
/dev/hda6 / ext3 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hda10 /home ext3 defaults 1 2 none /mnt/cdrom supermount dev=/dev/scd0,fs=auto,ro,--,umask=0,codepage=850,iocharset=iso8859-1 0 0 none /mnt/cdrom2 supermount dev=/dev/hdd,fs=auto,ro,--,umask=0,codepage=850,iocharset=iso8859-1 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,umask=0,codepage=850,iocharset=iso8859-1,sync 0 0 /dev/hda1 /mnt/nt ntfs ro,umask=0,iocharset=iso8859-1 0 0 /dev/hda5 /mnt/nt2 ntfs ro,umask=0,iocharset=iso8859-1 0 0 /dev/hda11 /mnt/windows vfat umask=0,codepage=850,iocharset=iso8859-1 0 0 none /mnt/zip supermount dev=/dev/sda4,fs=auto,--,umask=0,codepage=850,iocharset=iso8859-1,sync 0 0 none /proc proc defaults 0 0 /dev/hda8 /usr ext3 defaults 1 2 /dev/hda9 /var ext3 defaults 1 2 /dev/hda7 swap swap defaults 0 0 Wow! Cleve On Thu, 2002-10-24 at 19:57, Douglas Adams wrote: > I'm not sure if I can be any help at all, but I'm curious, in your /etc/fstab > what hard drive does it say that your boot partition is on? /dev/hda, > /dev/hdc, etc.? > > Is it possible that the IDE chain that your hard drive is connected to > changes the naming of the hard drive, and linux isn't looking in the right > place when you switch it to the next chain? > ----- Original Message ----- > From: Cleve Allison > To: [email protected] > Sent: Thursday, October 24, 2002 6:38 PM > Subject: [brlug-general] dual booting issues > > > Ok....here's the deal. > I have an Asus A7V motherboard. It runs a Duron 700 chip with the 100/200 > bus. > The way this motherboard was implemented is that there are two onboard IDE > controllers. > One is a 33/66 and the other is a 33/66/100, I think. > What happens is the upon booting up, it first looks at the ata66 > controllers...then scans the ata100 controllers. > I have had to plug my hd cables into the ata33/66 controller to actually > install the OS or OS's. > > So....last night I received my new WD 100 Gig HD with the 8mb > buffer..pretty sweet. > had to plug it into the slower ide controller to install first WinXP and > then MDK 9.0 > Everything is cool so far. Took everyones advice and I have a huge > partition that both OS's can see...its great. > > Here is the problem. When I moved the cables to the ata100 > controller....and rebooted....I can boot into WinXP fine...but I cannot boot > into MDK9 > If I move the cables back to the ata66 controller then I can boot into > either. > > So there must be something like the boot.ini file in Linux.......so I'm > guessing I need to edit it to do something different. > But if that is the case then why didn't I have to do the same for boot.ini > under WinXP? > > Or am I barking up the wrong tree altogether? I really want to use the > faster controller since my new harddrive was designed to make use of it. > > TIA for any help you can provide, > Cleve
