bootvis made my startup longer

  • Thread starter Thread starter Alistair
  • Start date Start date
A

Alistair

My winXP Home was taking almost 3 mins to startup (measured from power on,
to the point of no disk activity), so after seeing bootvis recommended all
over the web I tried it.

Now my startup is almost up to 3 and a half minutes! Anyone else hear of
this happening?
 
Alistair

Have you looked for clues in Event Viewer?

1. To open Event Viewer, click Start, click Control Panel, double-click Administrative Tools, double-click Event Viewer and select System for system errors or Application for application errors. Look for Error in the Type column and double click on Error to reveal a Description of the error. This can be copied by using Clipboard Viewer (see later).

2. Part of the Description of the error will include a link, which you should double click for further information and you can copy using copy and paste.
http://go.microsoft.com/fw.link/events.asp
(Please note the hyperlink above is for illustration purposes only)

3. For some errors you will find "+ Related Knowledge Base Article", which if double clicked takes you to the Knowledge Base Article containing a suggested solution.

There always seems to be a step 2 but not always a step 3.

A tip for posting copies of Error Reports (Step 1). Run Event Viewer and double click on the error you want to copy. In the window which appears is a button resembling two pages. Double click the button and close Event Viewer. Now start your message ( email )and do a paste into the body of the message. This will paste the info from the Event Viewer Error Report complete with links into the message. Make sure this is the first paste after exiting from Event Viewer. It can be helpful to place a shortcut to Event Viewer on your Desktop.

Check what is loading at start up?

~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
(e-mail address removed)
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.

~~~~~~~~~~~~~~~~~~~~~~~~
 
Peter said:
Did you use BootVis according to instructions? There is an effective and
ineffective way to apply it, i believe..
Click to expand...

Mine was apparantly the ineffective way :o(

Trace>Next Boot (1)
Trace>Optimise
 
That's the purpose of bootvis. To allow system mfg to optimise boot times.

You can use bootvis the same way. If you thought optimise would help you then NO. Windows does the optimisation automatically. Bootvis just does it on command so it measures an optimised system.

Bootvis is a troubleshooting tool. Use it as such.
 
Bootvis measures boot times for computer manufacturers to make sure their hardware/drivers isn't holding things up (to get the XP logo it has to boot in X seconds).

So it can measure the real world time (over a few minutes rather than an unknown amount of time) it has to tune the OS now rather than waiting for the third boot (when windows will do it) after the computer has been idle for a while. Windows redoes it every third day (if you're idle).

So it makes an API call ProcessIdleTasks which does all the idle processing now so one can experiment with drivers etc without waiting three days to do the next step. You can do this by hand by typing in Start - Run

rundll32.exe advapi32.dll,ProcessIdleTasks

It does some System restore stuff as well. For the defragging stuff typing in Start Run
defrag c: /b
will just run the defragger in it's boot/app speedup mode only (won't defrag document files or anything).
 
Back
Top