"Long Stall" in Boot Process for WinXp on Shuttle Computer

[Bill VanDatta]

Hello,
I have just assembled a new XPC Shuttle SK41G case with an AMD 2400+ CPU
w/512 MB RAM and a WD 120GB HD. All new parts. I'm using onboard
graphics, sound, network hardware.
I've yet to load any applications or done any other configuration.
When I turn on the computer it goes through the POST fine, but then the
Black Screen "logo" of the Windows comes on with the little bar with the
three scrolling "dots" horizontally and then it "stalls" in that mode
for more than 30 seconds. The HD shows no "activity" at all during that
time and finally after the long delay, it finally starts to see some HD
activity and then it quickly then boots to the Windows desktop. I've
checked the BIOS and looking for a clue why it seems to "stall" at this
point, but am out of Ideas. I don't have a floppy drive and have it
"off" in BIOS for seek. It seems to be timing out somewhere but can't
figure out what is going on. This 30+ seconds at initiation is way too
long when compared to my other computers and I find unacceptable. I've
not loaded any programs (except WinXP Pro and the Shuttle drivers from
their CD) on it yet and want to get this problem resolved before I go on
using it. I've not gone into MSCONFIG and fooled with that yet but feel
something is in the post BOOT process that is "hanging it up". Since it
is a "clean" installation I'm puzzled why the secondary "boot" stalls
and takes so long? Shut down is fine.
Does anyone have any ideas on this I'd love to know.
Regards,
Bill Van Datta

 

[Richard Urban]

Disable everything in the bios that you are not using. Ex: if you have 2
built in NIC connections, but only use one of the, turn the other one off.
If you don't, the computer will search for these items on every boot -
adding considerable time to the boot process. Look for others!

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard

 

[Bill VanDatta]

I went back in and discovered I had the CD-RW set up as a "Slave" when
it was the only IDE device in the secondary interface. Reset to "Master".

Bingo! It now takes only 3 seconds in that mode.

Got my problem solved.
Thanks for the help.

Bill