B
Bill P
Using win XP home sp3.
Is there an app that will time how long it takes for a machine to boot up.
Regards Bill
Is there an app that will time how long it takes for a machine to boot up.
Regards Bill
Bill said:Using win XP home sp3.
Is there an app that will time how long it takes for a machine to boot up.
Regards Bill
Bill said:No Good. How do you know when to stop the watch . SA
Alias said:Bill said:No Good. How do you know when to stop the watch . SA
I stop it when the little Internet screens appear in the systray. I doubt
an app in Windows will be able to time what happens before Windows loads.
Bill P said:Using win XP home sp3.
Is there an app that will time how long it takes for a
machine to boot up. Regards Bill
Bill P said:Using win XP home sp3.
Is there an app that will time how long it takes for a
machine to boot up. Regards Bill
Thanks Twayne. I tried Bootvis but it did nothing for my setup (XP SP3)
Bill
Snipped
"If you want to get smart about what happens when your system boots,
read this article:
http://technet.microsoft.com/en-us/library/bb457123.aspx
Stop guessing and just trying things that might work maybe and start
measuring and you will have better results.
Thanks Jose I will check out the article. I did start another thread
regarding hibernating rather than shutting down and that is what I am doing
at the moment. The resume time from hibernation is incredibly fast.
Regards Bill
Try the Bootlog XP tool too! If Bootvis won't run, fix
things so it does. It will show you may things that start
up h ow long they take, etc. when you boot and some
research will show you that you don't need many of them -
at all. Then you can remove them from your startup items.
This invalidates the trial and error advice you may also
read about.
InJose <[email protected]> typed:
...
Hmm, thanks Jose, for the Bootlog XP tool hint; if it does what it says it
does, that's going to be what I've been looking for for a long time.
Twayne
Jose said:What have you discovered, Twayne?
If Bootlog XP is not what you are looking for, describe
what it does not do and your requirements/needs - I may
have other things up my sleeve.
Are you able to run Bootvis as well?
Jose said:Bootvis works fine in SP3 unless your system is afflicted in some way
that prevents it from working.
If Bootvis doesn't work, you need to better define what "doesn't work"
means. I just ran Bootvis on my XP Pro SP3 and it works fine.
Another popular and revealing tool is Bootlog XP from Greatis:
http://www.greatis.com/
If you want to do a good job of figuring out timings and if
adjustments you make have some influence (in any direction), you need
to come up with something a little more scientific that looking at the
icons and deciding when you think Windows thinks it is "ready".
Remove subjective opinions and unmeasurable things from your analysis
completely. There should be no guessing about anything ever. You
need to know with 100% certainty when the boot cycle is complete with
tenth of a second granularity to be able to see if your adjustments
are helping or hurting things.
If you are getting paid or laid to fix some system that is slow to
boot, you need to be able to say: Before I started, it took exactly
this long to boot and now when I am done, it takes exactly this long
and here is what I did. You can see here after my repeatable tests
and mesurements that things have improved by this amount of time (down
to the tenth of a second).
Then it is easy to justify your $1 a second fee for speeding up
somebody's configuration issues because you can measure it exactly,
give a printed report, etc. Not bad for a usually 30 second system
analysis and "fix" of the slow boot phenomenon.
You could follow the "try a clean boot state and see if your system
boot faster" advice. Well, of course it will boot faster, but what do
you do next? You could also try to "check msconfig for things,
culprits and suspicious items and disabling them" or "try fiddling
with some things".
If you want to get smart about what happens when your system boots,
read this article:
http://technet.microsoft.com/en-us/library/bb457123.aspx
Stop guessing and just trying things that might work maybe and start
measuring and you will have better results.