topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Saturday April 27, 2024, 7:02 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - offie999 [ switch to compact view ]

Pages: [1]
1
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.

2
Admitting that I probably have more little utility programs lurking in my Windows XP boot-up than I should, I find that I often start using the system without knowing that the boot-up process has not yet finished.  As a result, the first few actions taken - opening applications or whatever - often hang up briefly while the boot-up finishes its work.

A simple solution would be a small pop-up window (or whatever equivalent a good programmer can develop) to show a message on the screen simply saying something to the effect:  "BOOT PROCESS HAS COMPLETED" or "YOUR SYSTEM IS NOW READY FOR USE" --- you get the idea.

In addition, a bit more complicated perhaps, would be to expand on it and provide a simple alert - very simple - should any of the start-up processes or applications fail to properly boot-up.  Something like "BOOT PROCESS HAS COMPLETED - No Errors" or "BOOT PROCESS HAS COMPLETED - Avira Anti-Virus Failed to Load Properly" would provide notice that perhaps I should consider rebooting the system.

Perhaps something in a simplified format already exists - but I think a simple utility of this type would be very useful to those of us who keep a fairly complex system with many start-up processes or applications slowing down the boot-up process.

Thanks in advance to all your ideas and efforts.

Pages: [1]