Win XP Loading Operating System

[kerneldebugger]

On my new PC (GA 790XTA UD4) after POST the Windows screen appears, with the
blue things swiping across the screen about 20 times. Then all is well. On
my old PC there were only about 5 'swipes' of the blue dots before loading
completed. I'm wondering what's going on during that time that takes so
much longer on my new super speed (?) PC.

TIA

 

[Paul]

On my new PC (GA 790XTA UD4) after POST the Windows screen appears, with the
blue things swiping across the screen about 20 times. Then all is well. On
my old PC there were only about 5 'swipes' of the blue dots before loading
completed. I'm wondering what's going on during that time that takes so
much longer on my new super speed (?) PC.

TIA

What mode is the disk interface in ? AHCI perhaps ?
Some disks don't support NCQ (Native Command Queueing),
which is a part of AHCI. Presumably they should be telling
the driver that fact, so NCQ can be disabled. NCQ allows
completing disk commands out of order, so that the disk controller
on the hard drive can reorder them. But a downside, is sometimes
the boot time is longer when using AHCI.

In Safe Mode, there is an option to turn on "Boot Logging", but
it sadly lacks timestamps for when the drivers are loading.

I found this, Bootvis, which gives a graphical trace of startup
activity. But in reading the description, apparently it can
"hose" a system (it wasn't stated exactly how it managed to
achieve that - you'd think just tracing system activity wouldn't
be that dangerous, especially if the instrumentation capability
was already built into the system).

http://www.tweakhound.com/xp/bootvis/

http://articles.techrepublic.com.com/5100-10878_11-5034622.html

http://en.wikipedia.org/wiki/BootVis

(Where to get a copy of Bootvis)

http://majorgeeks.com/BootVis_d664.html

(Sample user experience with disk operating modes or driver choices)

http://www.motherboardpoint.com/boot-delay-xp-startup-screen-k8n-neo2-t56773.html

As long as you've got a backup of C: , what could go wrong ?

Paul

 

[kerneldebugger]

I ran bootlog and it shows a 24 second blank period before anything starts,
then all the .exe's appear to run normally in a few seconds. When i ran
bootlog on my old PC, the blank period was only 5 seconds before the exe's
started. That pretty much shows the problem, apparently nothing is
happening, Windows must be just waiting for some event before it starts the
executables. Another identical computer does the same thing. I've tried
AHCI and didn't see any change; I'll investigate it further.

Thanks