> The same time in safe mode, about 3 minutes. I just doublechecked it.
> Steve
[quoted text clipped - 34 lines]
>> >>
>> >> Ron Martell Duncan B.C. Canada
I am a stickler for having nothing in my startup list. However, I was amazed
at the amount of all the little processes and apps that started when I ran
the Startup List program. It's a cool little program. But I assume
everything there was required. I have nothing checked in the MSconfig
startup utility. The hard drive is intermittently active/inactive after the
desktop loads( for the 3 minutes while it waits to load the desktop icons).
Then the icons all of a sudden load within 5 seconds. The POST takes about
10-15 seconds and the HD light is flickering. I believe this is a software
problem in such that the system is searching/waiting for something before it
releases control to the desktop. There must be some setting or conflict
somewhere.
PS- I can copy/paste the starup list (long) if you need to see it.
> Given it occurs in Safe Mode also - still not sure if you have a HW or SW
> issue. Can you tell if the HD immediately boots after POST (for that matter
[quoted text clipped - 40 lines]
> >> >> Here is a link to a web page where a similar problem was solved
> >> >> (eventually).
http://forums.techguy.org/archive-windows-95-98-me/84233-resolved-start-up-log-d
elay.html
> >> >> Good luck
> >> >>
> >> >> Ron Martell Duncan B.C. Canada
mdp - 19 Feb 2006 16:46 GMT
I would expect BLA to capture the delay between two (multiple) events if
it's somewhere in the boot process. Have you tried Step-byStep booting to
see if anything in particular is taking very long (F8 during POST - select
Step by Step Confirmation)? Other boot options to experiment with can be
found here:
http://www.winguides.com/registry/display.php/1268/
Focusing on HW you could:
* Disconnect CDROMs, other HDs, any other non-essential HW
* Use partial memory, e.g. take out stick(s)
Time consuming options include:
* Image partition to a different drive - try the different drive
* Fresh reinstall OS
Troubleshooting can be somewhat open-ended until you can repeat or isolate
the problem or until you have enough clues to formulate a reasonable
hypothesis one can test. If you find the problem, I for one am curious as
to what it is.
>I am a stickler for having nothing in my startup list. However, I was
>amazed
[quoted text clipped - 69 lines]
>> >> >>
>> >> >> Ron Martell Duncan B.C. Canada