| View previous topic :: View next topic |
|
|
| Author |
Message |
wbs Guest
|
Posted: Mon Jul 16, 2007 4:06 am Post subject: startup monitor |
|
|
| In win 95 and win98 there was a small program "bootAnalyzer" that monitored the start up time sequence___I know there are many small appz out there that do this like MS bootvis __but this startup monitor must monitor the time in millisecs or {near enough} that each appz and service takes to boot up showing where there is a lag in the boot up With Kind Regards From OZ |
|
| Back to top |
|
 |
wbs Guest
|
Posted: Tue Jul 17, 2007 1:27 am Post subject: Re: startup monitor |
|
|
trouble with bootyis is that I cannot understand it!!!!!!!!!!!!!!!
"wbs" <nooneere@noware.net> wrote in message
news:469b26f2@news.comindico.com.au...
| Quote: |
| In win 95 and win98 there was a small program "bootAnalyzer" that monitored the start up time sequence___I know there are many small appz out there that do this like MS bootvis __but this startup monitor must monitor the time in millisecs or {near enough} that each appz and service takes to boot up showing where there is a lag in the boot up With Kind Regards From OZ |
|
|
| Back to top |
|
 |
Guest
|
|
| Back to top |
|
 |
wbs Guest
|
Posted: Thu Jul 19, 2007 11:43 pm Post subject: Re: startup monitor |
|
|
"Franklin ." <frank.says@no.mail> wrote in message news:Xns996F91464399578D91A@127.0.0.1...
| Quote: |
On 16 Jul 2007, wbs <nooneere@noware.net> wrote:
| Quote: |
| In win 95 and win98 there was a small program "bootAnalyzer" that monitored the start up time sequence___I know there are many small appz out there that do this like MS bootvis __but this startup monitor must monitor the time in millisecs or {near enough} that each appz and service takes to boot up showing where there is a lag in the boot up With Kind Regards From OZ |
XP's Bootvis should show the time info you seek.
Are you seeing the half a dozen graphs Bootvis can create? |
yes ! but they do not give me details of where the boot up lag is happening |
|
| Back to top |
|
 |
jcmatt
Joined: 17 Jul 2007 Posts: 514
|
Posted: Fri Jul 20, 2007 6:49 am Post subject: Re: startup monitor |
|
|
On Jul 20, 11:43 am, "wbs" <noone...@noware.net> wrote:
| Quote: |
| yes ! but they do not give me details of where the boot up lag is happening |
How much memory do you have?
What operating system?
Are you networking? |
|
| Back to top |
|
 |
Franklin Guest
|
Posted: Fri Jul 20, 2007 7:09 am Post subject: Re: startup monitor |
|
|
On 20 Jul 2007, wbs <nooneere@noware.net> wrote:
| Quote: |
"Franklin ." <frank.says@no.mail> wrote in message news:Xns996F91464399578D91A@127.0.0.1...
| Quote: |
On 16 Jul 2007, wbs <nooneere@noware.net> wrote:
| Quote: |
| In win 95 and win98 there was a small program "bootAnalyzer" that monitored the start up time sequence___I know there are many small appz out there that do this like MS bootvis __but this startup monitor must monitor the time in millisecs or {near enough} that each appz and service takes to boot up showing where there is a lag in the boot up With Kind Regards From OZ |
XP's Bootvis should show the time info you seek.
Are you seeing the half a dozen graphs Bootvis can create? |
yes ! but they do not give me details of where the boot up lag is happening |
System tuning is too big a topic to go into but here are some key steps.
You're looking on the graphs for modules which get loaded and are then followed by no further modules loading up for a period. This is the sort of delay you are looking for.
Unless the "lockout module" is using all available system resources (cpu, disk I/O or virtual memory) then other modules could have been loaded to run concurrently. In other words, at that moment of delay more than one module could have been running but wasn't.
Unfortunately there is not a lot of user control even once you have seen what is causing a delay. You could run that app at some other time than at startup. You might be able to tweak an app's settings to make it run less intensively. Defragging and error checking the file system should be regular tasks on a slow booting system.
As for OS components which cause the lockout, there are lots of myths about what XP does or does not do. Check out prefetch and Layout.ini in Google and believe the guys who say do not delete them. FOr example:
<http://www.populartechnology.net/2005/10/ccleaner-cripples- application-load.html>
Also make sure EnablePrefetcher is not disabled in the registry. If it is disabled then Bootvis's optimization will actually seem to work rather well! Howeverit should not be disabled and Bootvis's optimization would then do only a little. |
|
| Back to top |
|
 |
|