From: "Glenn Meadows" 

OK, working on it now, did a fresh install next to the existing install
(new Windows Directory), and that install boots fine, so I would PRESUME
that the MBR is OK.  When switching back to the original install though, I
still get 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
Windows on the same machine?

--

Glenn M.
"Glenn Meadows"  wrote in message
news:4237425d$1{at}w3.nls.net...
> Yea, that part I'm sure of (correct controller).  He first put the new
> DVDR drive in, on the secondary controller where the existing CDRom drive
> was installed, and got that right.
>
> Rich suggested upstream, that for some reason, the original disk MIGHT
> have been set as Slave, but from his description, the jumper was in the CS
> position, which he did for the second drive initially.  What I suspect
> might have happened, is when he did that, he changed the connectors
> (swapped Master for Slave position on the cable), and that's what's
> 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,
> as well as he did some poking around after the first crossed drive boot,
> 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.
> .
>
> --
>
> Glenn M.
> "Chris"  wrote in message
news:42371323{at}w3.nls.net...
>> This sounds suspiciously like he added the second drive incorrectly as
>> far as jumpers and which connectors he used.  Is he sure he got both
>> drives on the Primary IDE controller?  Now, having said this, he reverted
>> back to the single drive setup on the "old" drive. 
However, if the BIOS
>> booted off of the new drive, the damage is done and whoever suggested
>> using a "real" XP CD to run a recovery console and issue
the fdisk /mbr
>> command makes sense to me.
>>
>> /Chris
>>
>>
>> Glenn Meadows wrote:
>>> Correct, no error message, no BSOD.  Just goes to where the Welcome
>>> Screen would normally showup (the different peoples logon icons), but
>>> all you see is the small Windows Logo that normally appears to the left
>>> of the user logon icons.
>>>
>>> That's what I thought, (cabling/jumpers), but going back to ONE drive
>>> only, the original as the only physical drive powered, connected, and
>>> jumpered, gives that same screen, or if doing an F8 boot, and selecting
>>> 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).
>>>
>
>

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