[DUG] Has Windows finished??

[Jolyon Smith]

... this is still "vulnerable" to a "false dawn" scenario (where system CPU
load drops for a period due to a stalled process/processes during startup).

 

So extend 3 seconds to 10 seconds.  If that's not enough, try 15, 30 or 60
seconds....

 

Now you're making the user wait longer than they have to start using their
PC, when presumably the intention was originally to let them know when the
system was "usable" so that they could get on with some work as quickly and
efficiently as possible.

 

This is the sort of problem where a bit of common sense thinking and some
modification of working practices is likely to work far better than any
software solution....

 

1)      do not shutdown at the end of every day.  If you must switch off the
computer, set it up to hibernate rather than shutdown.

 

2)      A full shutdown would be recommended once a week.  Friday would make
sense in an office environment.  Then Monday mornings you have to wait for a
complete system startup - a good time to catch up with colleagues and
discuss weekend R&R.  This should more than occupy even the longest Windows
startup process.

 

That 2nd suggestion isn't entirely serious, but the principle of using
wetware - i.e. brain power - rather than silicon should apply I think.  A
user that can't get their head around "wait" and in time "learn how long you
need to wait and wait that long" is probably not the sort of user you
could/should safely trust to operate a computer in the first place!

 

J

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20090914/42e5f8e7/attachment.html