From: "Glenn Meadows" 

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).

--

Glenn M.
"John Beckett"  wrote
in message news:4236bb6e.9929537{at}216.144.1.254...
> "Glenn Meadows"  wrote in message
> news::
>> If you remove the second HD, and try to boot the system, it starts to
>> boot,
>> then ends up at a Blue Screen (not the BSOD, but a graphical screen with
>> the
>> Windows Logo) and never boots.
>
> Do you literally mean that there is no error message ... the system just
> never finishes whatever it was trying to do?
>
> That sounds like a cabling or jumper problem. I would not expect  Windows
> to go to sleep when trying to boot. If it couldn't find what it wanted, it
> would report an error.
>
> One thing you might try would be edit *one* boot.ini file (whichever is on
> the partitiion that you think the BIOS is booting) and put any
> recognisable text in the menu. Like "XXX". On booting, do you see this
> text? Uh oh ... I've forgotten if you see the boot.ini menu when you press
> F8 during boot. I was going to say to press F8 and see if the boot text
> contains the XXX. If it did, you would removing some confusion about which
> drive was being used to boot.
>
> John
>

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