From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0593_01C528DA.0403B2E0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   The BIOS is responsible for the identity of the drives.  What is =
unclear is the order of events here.

   Did the second drive get added them removed from a Windows =
installation that occured when there was only one drive?

   Was the configuration of the one drive identical before the second =
drive was added and after the second drive was removed?

Rich

  "Glenn Meadows"  wrote in message =
news:42364da5{at}w3.nls.net...
  OK, WHY does this happen, I've seen it before, don't understand what=20
  actually causes this to happen.

  A friends child (14) decided to add a second HD to his XPPro install, =
from=20
  an old computer that they had.

  Somehow, he got the jumpers/connectors bolloxed up, and when the =
system came=20
  up and booted, but the drive letters were now swapped.  Even though =
the=20
  original disk was still Primary master, and the second drive was =
Primary=20
  Slave, the C drive, was actually the slave drive, and the original =
drive was=20
  now listed as drive F. (D and E are CD and DVD-R drive).

  If you remove the second HD, and try to boot the system, it starts to =
boot,=20
  then ends up at a Blue Screen (not the BSOD, but a graphical screen =
with the=20
  Windows Logo) and never boots.  Both drives have to be connected for =
the=20
  system to boot, but of course, anything that is in the registry as =
needing=20
  to start from C, won't start, since it's really on F.

  And, of course, the eMachine ONLY provides a Restore/Nuke CD=20
  (format/re-install is the only option).

  I believe that the solution is to remove the second HD, boot from a =
real=20
  WindowsXP CD, go to the Recovery Console, and do a FIXMBR command, in =
that=20
  the MBR on the primary HD is now farkled.

  But WHY does this happen?  Boot.ini looks correct (there's a boot.ini =
on=20
  both HD's, btw, from the old computer, which was an XPHome install).

  --=20

  Glenn M.=20


------=_NextPart_000_0593_01C528DA.0403B2E0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   The BIOS
is responsible =
for the=20
identity of the drives.  What is unclear is the order of events=20
here.
 
   Did the
second drive get =
added them=20
removed from a Windows installation that occured when there was only one =

drive?
 
   Was the
configuration of =
the one drive=20
identical before the second drive was added and after the second drive = was=20
removed?
 
Rich
 

  "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:42364da5{at}w3.nls.net...OK=
,=20
  WHY does this happen, I've seen it before, don't understand what =
actually=20
  causes this to happen.A friends child (14) decided to add a =
second HD=20
  to his XPPro install, from an old computer that they =
had.Somehow,=20
  he got the jumpers/connectors bolloxed up, and when the system came =
up and=20
  booted, but the drive letters were now swapped.  Even though the=20
  original disk was still Primary master, and the second drive was =
Primary=20
  Slave, the C drive, was actually the slave drive, and the original =
drive=20
  was now listed as drive F. (D and E are CD and DVD-R =
drive).If you=20
  remove the second HD, and try to boot the system, it starts to boot, =
then=20
  ends up at a Blue Screen (not the BSOD, but a graphical screen with =
the=20
  Windows Logo) and never boots.  Both drives have to be =
connected for=20
  the system to boot, but of course, anything that is in the =
registry as=20
  needing to start from C, won't start, since it's really on =
F.And,=20
  of course, the eMachine ONLY provides a Restore/Nuke CD =
(format/re-install=20
  is the only option).I believe that the solution is to remove =
the=20
  second HD, boot from a real WindowsXP CD, go to the Recovery =
Console, and=20
  do a FIXMBR command, in that the MBR on the primary HD is now=20
  farkled.But WHY does this happen?  Boot.ini
looks correct =

  (there's a boot.ini on both HD's, btw, from the old computer, =
which was an=20
  XPHome install).-- Glenn M. =


------=_NextPart_000_0593_01C528DA.0403B2E0--

--- BBBS/NT v4.01 Flag-5