I had a strange Zenith Data System machine that had a EISA bus with an
on-board SCSI controller (Adaptec 7700 I think). for performance reasons we
had installed another Adaptec card and disabled the on-board controller.
This worked when we ran SCO and then when we put WfWG it still worked ok.
When I put NT3.51 on the machine I thought I had a hardware problem. It
would take 9.5 minutes for the blue screen to start displaying dots!!! It
was caused by the "extra" scsi controller with 2 channels and nothing on it.
we had disabled it in the EISA config file, but of course, once NT went to
the bluescreen it not longer relied on the Cmos/bios/eisa config. I only
realized that it was going to work when I went looking for a DOS diskette to
try andrecover the machine, when I returned to my station it was sitting at
the ctl-alt-del prompt. Once it came up, I was able to go to the scsi
controller applet in control panel and remove the offending controller, then
it would boot normally.
My ultimate solution was to trash the ZDS machine and get something that was
>I don't have the resource kit myself but am told that the delay is caused
>poor detection algorithm used by MS to detect a SCSI card when there is an
>controller in there as well.
>I have both and so I experence this delay as well and it's realy not fun.
>delay for me happens after the blue screen comes on but before the dots
>start. There isn't any/much HD activity during this time and it just seems
>sit there and timeout on some detection thingy. (Note it's even worse when
>SCSI fails to start because you're doing something to it and it takes about
>3-4min and still doesn't load the SCSI).
>Aparently MS is trying to fix this...
>> Hi Andy,
>> This is very normal and you should not do anything to try to stop it.
>> When you see these screens, NT is setting itself up. i.e. when you
>> see the dots, NTLDR is loading the Kernel and hal.dll into memory,
>> then loads low level drivers...
>> When you see the blue screen specifying memory, processors, etc.,
>> drivers & services are being initialized, page file is created,
>> subsystems are started....
>> If you're interested in more-comprehensive answers, you'd probably
>> want to get the NT Workstation Resource Kit (book with CD) and/or the
>> MCSE study Guide by Perkins, Strebe, and Chellis. Both are available
>> at many PC stores.
>> >I am a complete Windows NT newbie. I searched through
>> >lots of newsgroups withouth finding an answer to this:
>> >When I startup NT I pretty soon see a blue screen with information
>> >about the amount of RAM and the number of processors in the first
>> >two lines.
>> >Then nothing happens for about 30 seconds. Finally then it continues
>> >with a couple dots .......
>> >Is that the normal way or did I misconfigure anything?
>> >If this is normal, what's going on during that time? And is there
>> >a way to turn it off, somehow?
>> >Thanks a lot in advance for any hint,
>> > Andy.