1
Post New Requests Here / Re: IDEA: Simple Pop-Up to Advise When XP Boot Process Has Finished
« on: March 08, 2011, 03:43 PM »
Thanks for those early responses.
@skwire: This is a classic example of the dangers of giving a layperson like myself a little bit of information !!! I have always assumed the between the boot files (boot.ini and all the others, I guess), the initial set of processes and services and the user-defined start-up applications that the system knew exactly what it was doing each time it started up. And, if it knew exactly what it was doing to start its self up it should know when those actions have been completed.
Always amazing how we can assume something is so basic and simple and it turns out be just the opposite.
@PaulKeith: Thanks for the suggestion of Soluto. Will load it up to learn more about it but it seems not to apply as I already know what I want my system to do - that is to complete the "boot" and then tell me in some simple message that it has actually done that - completed the boot and its now ready for me to do my thing.
@Cranioscopial: I'll look more closely at Idlerun on the theory that if the CPU is idle enough to run my user-defined message then it must have completed what I would call the "boot" --- I assume the first "idle" period would be immediately after the so-called "boot" so Idlerun could then kick in displaying my user-defined message. That wouldn't tell me if there had been a minor problem in loading something (such as a given application waiting in the start-up), but it would at least tell me it has completed the "boot".
Haven't had my morning coffee yet so will take a closer look once the caffeine kicks in.
Again, thanks to all three of you. Look forward to any other suggestions.
@skwire: This is a classic example of the dangers of giving a layperson like myself a little bit of information !!! I have always assumed the between the boot files (boot.ini and all the others, I guess), the initial set of processes and services and the user-defined start-up applications that the system knew exactly what it was doing each time it started up. And, if it knew exactly what it was doing to start its self up it should know when those actions have been completed.
Always amazing how we can assume something is so basic and simple and it turns out be just the opposite.
@PaulKeith: Thanks for the suggestion of Soluto. Will load it up to learn more about it but it seems not to apply as I already know what I want my system to do - that is to complete the "boot" and then tell me in some simple message that it has actually done that - completed the boot and its now ready for me to do my thing.
@Cranioscopial: I'll look more closely at Idlerun on the theory that if the CPU is idle enough to run my user-defined message then it must have completed what I would call the "boot" --- I assume the first "idle" period would be immediately after the so-called "boot" so Idlerun could then kick in displaying my user-defined message. That wouldn't tell me if there had been a minor problem in loading something (such as a given application waiting in the start-up), but it would at least tell me it has completed the "boot".
Haven't had my morning coffee yet so will take a closer look once the caffeine kicks in.
Again, thanks to all three of you. Look forward to any other suggestions.