Ok, I've got an incredible screamer of a system here: super-high-end Asus workstation 
mobo, dual-core 3.0GHz Intel processor, 8 GB RAM, 3 TB of attached hard disk space. 
It finishes some tasks so fast I sometimes doubt whether it did anything at all (it 
always has).

So why does it take 11 MINUTES to boot?

Oh, the system and disk adapter BIOS pages zip by fast enough, and the desktop picture 
shows up quickly enough, but then TEN WHOLE MINUTES pass before I can actually DO 
anything!

The desktop icons don't show up for 6 of those minutes (i.e., the desktop background 
picture ONLY shows for 6 of those first ten minutes after the BIOS pages go by)!

And once the icons show up, it's still FOUR MINUTES before I can double-click anything 
or open the start menu!

I need detailed instructions on exactly how to find out what's taking all this time. 
 There's absolutely nothing unusual or fancy or at all tricky in my setup.  I know 
there's a Microsoft tool for monitoring processes and the like, but that was more 
of a hassle than it was worth (too MUCH data!)  What I'm looking for instead is something 
that sits and watches and accumulates the total time each process took from point 
a to point b (and not, like the MS tool, a huge, highly repetitive list of every 
single process and every single millisecond it spent!)

Can anyone help me out on this?

[Reply or follow-up to this message]

I do know that 32 bit version of XP supports a maximum of 4GB of memory..64 bit goes to 128 though...

[Reply or follow-up to this message]

Curious.

What happens if you take out some of the RAM ? XP 32 will USE a maximum of 2Gb - 
anything more is a complete waste - and I have no idea what will happen at boot time 
with such a vast amount installed.

More likely, though, is something to do with your 3Tb of disk space - any sort of 
disk checking that is happening at boot time could easily take 11 minutes, indeed 
11 hours or 11 days !

So I'd start by disabling some of this storage and seeing if the boot time reduces 
- that will provide useful clues.

[Reply or follow-up to this message]

Yeah, sorry, I was mistaken about how much RAM was present.  It's 4GB, not 8.

Still doesn't help me isolate the problem, though...

[Reply or follow-up to this message]

Martin Bush wrote: ...accumulates the total time each process took from point 
a to point b (and not, like the MS tool, a huge, highly repetitive list of every 
single process and every single millisecond it spent!)


Dunno which M$ tool you used (there's no such thing as the M$ tool), but did 
you already try this?

1) run eventvwr.msc and delete all entries
2) restart your computer
3) run eventvwr.msc and look for errors (highlighted with scary red icons) 
and unusually long gaps between events.

A virus scanner that runs a full check before letting you in will make your system 
startup routine take forever. Having lots of files encrypt/decrypt during shutdown 
and bootup will also force you to take a coffee break.

______________

make windows xp behave

[Reply or follow-up to this message]

I would turn off all file and network sharing and see what that gets you. If your 
system is trying to make sure the network is all up and good before you get the prompt, 
you could wait a long time as you describe.



Wayne A Wehrspann




On Monday, March 31, 2008 at 5:12 pm, 666 wrote:

>


>Martin Bush wrote: ...accumulates the total time each process took from point 

>a to point b (and not, like the MS tool, a huge, highly repetitive list of every 

>single process and every single millisecond it spent!)

>

>

>Dunno which M$ tool you used (there's no such thing as the M$ tool), but 
did 

>you already try this?

>

>1) run eventvwr.msc and delete all entries

>2) restart your computer

>3) run eventvwr.msc and look for errors (highlighted with scary red icons) 

>and unusually long gaps between events.

>

>A virus scanner that runs a full check before letting you in will make your system 

>startup routine take forever. Having lots of files encrypt/decrypt during shutdown 

>and bootup will also force you to take a coffee break.

>


>______________

>

>make windows xp behave 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum