From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_05F2_01C5298C.A6D84A00
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   You can use REGEDIT File/Load Hive to attach a registry file on disk. =
 This is only allowed at some locations.  HKEY_LOCAL_MACHINE is one.

Rich

  "Glenn Meadows"  wrote in message =
news:42378efb{at}w3.nls.net...
  OK, working on it now, did a fresh install next to the existing =
install (new=20
  Windows Directory), and that install boots fine, so I would PRESUME =
that the=20
  MBR is OK.  When switching back to the original install though, I =
still get=20
  the same hang at the Welcome screen (as in no welcome screen).

  Thoughts?

  How do you edit the registry of a machine booted to a different =
install of=20
  Windows on the same machine?

  --=20

  Glenn M.
  "Glenn Meadows"  wrote in message=20
  news:4237425d$1{at}w3.nls.net...
  > Yea, that part I'm sure of (correct controller).  He first put the =
new=20
  > DVDR drive in, on the secondary controller where the existing CDRom =
drive=20
  > was installed, and got that right.
  >
  > Rich suggested upstream, that for some reason, the original disk =
MIGHT=20
  > have been set as Slave, but from his description, the jumper was in =
the CS=20
  > position, which he did for the second drive initially.  What I =
suspect=20
  > might have happened, is when he did that, he changed the connectors=20
  > (swapped Master for Slave position on the cable), and that's what's=20
  > screwed things up.
  >
  > I'm going to go back over with my full XPPro install disk, and get a =

  > recovery console up, and try the /fixmbr and go from there.  At this =

  > point, being brought in after the fact, and not knowing the full =
sequence,=20
  > as well as he did some poking around after the first crossed drive =
boot,=20
  > there's no telling how things were.  Right now, it's screwed up, and =

  > trying to go back will be an interesting exercise, to say the least. =

  > .
  >
  > --=20
  >
  > Glenn M.
  > "Chris"  wrote in message =
news:42371323{at}w3.nls.net...
  >> This sounds suspiciously like he added the second drive incorrectly =
as=20
  >> far as jumpers and which connectors he used.  Is he sure he got =
both=20
  >> drives on the Primary IDE controller?  Now, having said this, he =
reverted=20
  >> back to the single drive setup on the "old" drive. 
However, if the =
BIOS=20
  >> booted off of the new drive, the damage is done and whoever =
suggested=20
  >> using a "real" XP CD to run a recovery console and
issue the fdisk =
/mbr=20
  >> command makes sense to me.
  >>
  >> /Chris
  >>
  >>
  >> Glenn Meadows wrote:
  >>> Correct, no error message, no BSOD.  Just goes to where the =
Welcome=20
  >>> Screen would normally showup (the different peoples logon icons), =
but=20
  >>> all you see is the small Windows Logo that normally appears to the =
left=20
  >>> of the user logon icons.
  >>>
  >>> That's what I thought, (cabling/jumpers), but going back to ONE =
drive=20
  >>> only, the original as the only physical drive powered, connected, =
and=20
  >>> jumpered, gives that same screen, or if doing an F8 boot, and =
selecting=20
  >>> Command Prompt, then you get a BSOD with IRQ equal to or less than =

  >>> error. (memory serves me well, I think that's what the error was).
  >>>
  >
  >=20


------=_NextPart_000_05F2_01C5298C.A6D84A00
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   You can
use REGEDIT =
File/Load Hive to=20
attach a registry file on disk.  This is only allowed at some=20
locations.  HKEY_LOCAL_MACHINE is one.
 
Rich
 

  "Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:42378efb{at}w3.nls.net...OK=
,=20
  working on it now, did a fresh install next to the existing install =
(new=20
  Windows Directory), and that install boots fine, so I would =
PRESUME that=20
  the MBR is OK.  When switching back to the original install =
though, I=20
  still get the same hang at the Welcome screen (as in no welcome=20
  screen).Thoughts?How do you edit
the registry of a =
machine=20
  booted to a different install of Windows on the same =
machine?--=20
  Glenn M."Glenn Meadows" <gmeadow{at}comcast.net>">mailto:gmeadow{at}comcast.net">gmeadow{at}comcast.net>
wrote =
in message=20
  news:4237425d$1{at}w3.nls.net...=
>=20
  Yea, that part I'm sure of (correct controller).  He first put =
the new=20
  > DVDR drive in, on the secondary controller where the existing =
CDRom=20
  drive > was installed, and got that
right.>> Rich =

  suggested upstream, that for some reason, the original disk MIGHT =
>=20
  have been set as Slave, but from his description, the jumper was in =
the CS=20
  > position, which he did for the second drive
initially.  =
What I=20
  suspect > might have happened, is when he did that, he changed =
the=20
  connectors > (swapped Master for Slave position on the cable), =
and=20
  that's what's > screwed things
up.>> I'm going to =
go back=20
  over with my full XPPro install disk, and get a > recovery =
console up,=20
  and try the /fixmbr and go from there.  At this
> point, =
being=20
  brought in after the fact, and not knowing the full sequence, > =
as well=20
  as he did some poking around after the first crossed drive boot, =
>=20
  there's no telling how things were.  Right now, it's screwed up, =
and=20
  > trying to go back will be an interesting exercise, to say the =
least.=20
  >
<sigh>.>> --
>> Glenn =
M.>=20
  "Chris" <nospam{at}noemail>">mailto:nospam{at}noemail">nospam{at}noemail>
=
wrote in=20
  message news:42371323{at}w3.nls.net...>=
>=20
  This sounds suspiciously like he added the second drive incorrectly as =

  >> far as jumpers and which connectors he
used.  Is he =
sure he=20
  got both >> drives on the Primary IDE
controller?  Now, =
having=20
  said this, he reverted >> back to the single
drive setup on =
the=20
  "old" drive.  However, if the BIOS
>> booted off of the =
new=20
  drive, the damage is done and whoever suggested
>> using a =
"real" XP=20
  CD to run a recovery console and issue the fdisk /mbr >> =
command=20
  makes sense to me.>>>>=20
 
/Chris>>>>>>
Glenn Meadows=20
  wrote:>>> Correct, no error message, no
BSOD.  Just =
goes to=20
  where the Welcome >>> Screen would
normally showup (the =
different=20
  peoples logon icons), but >>> all you see
is the small =
Windows=20
  Logo that normally appears to the left >>>
of the user =
logon=20
 
icons.>>>>>>
That's what I thought,=20
  (cabling/jumpers), but going back to ONE drive
>>> only, =
the=20
  original as the only physical drive powered, connected, and =
>>>=20
  jumpered, gives that same screen, or if doing an F8 boot, and =
selecting=20
  >>> Command Prompt, then you get a BSOD
with IRQ equal to =
or less=20
  than >>> error. (memory serves me well, I
think that's =
what the=20
  error was).>>>>> =


------=_NextPart_000_05F2_01C5298C.A6D84A00--

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