This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C27B97.84C13D50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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 -----=20
From: Cleve Allison=20
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
------=_NextPart_000_0008_01C27B97.84C13D50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'm not sure if I can be any help at =
all, but I'm=20
curious, in your /etc/fstab what hard drive does it say that your boot =
partition=20
is on? /dev/hda, /dev/hdc, etc.?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Is it possible that the IDE chain that =
your hard=20
drive is connected to changes the naming of the hard drive, and =
linux=20
isn't looking in the right place when you switch it to the next=20
chain?</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A [EMAIL PROTECTED] href=3D"mailto:[EMAIL PROTECTED]">Cleve =
Allison</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
[EMAIL PROTECTED]
href=3D"mailto:[email protected]";>[email protected]</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, October 24, =
2002 6:38=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [brlug-general] dual =
booting=20
issues</DIV>
<DIV><BR></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>Ok....here's the deal.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have an Asus A7V motherboard. =
It runs a=20
Duron 700 chip with the 100/200 bus.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The way this motherboard was =
implemented is that=20
there are two onboard IDE controllers.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>One is a 33/66 and the other is a =
33/66/100, I=20
think.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>What happens is the upon booting up, =
it first=20
looks at the ata66 controllers...then scans the ata100=20
controllers.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I have had to plug my hd cables into =
the ata33/66=20
controller to actually install the OS or OS's.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>So....last night I received my new WD =
100 Gig HD=20
with the 8mb buffer..pretty sweet.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>had to plug it into the slower ide =
controller to=20
install first WinXP and then MDK 9.0</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Everything is cool so far. Took =
everyones=20
advice and I have a huge partition that both OS's can see...its=20
great.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Here is the problem. When I =
moved the=20
cables to the ata100 controller....and rebooted....I can boot into =
WinXP=20
fine...but I cannot boot into MDK9</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If I move the cables back to the =
ata66 controller=20
then I can boot into either.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>So there must be something like the =
boot.ini file=20
in Linux.......so I'm guessing I need to edit it to do something=20
different.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>But if that is the case then why =
didn't I have to=20
do the same for boot.ini under WinXP?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Or am I barking up the wrong tree=20
altogether? I really want to use the faster controller since my =
new=20
harddrive was designed to make use of it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>TIA for any help you can =
provide,</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>Cleve</FONT></DIV></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0008_01C27B97.84C13D50--
