Boot Times: Cold Start To Network Availability?

  • Thread starter Thread starter (PeteCresswell)
  • Start date Start date
P

(PeteCresswell)

The best I've been able to do from a cold start (i.e. computer
powered off) to being able to see a directory of my NAS box
shares is 1:30.

I see the Windows startup splash screen at about :31 and the
Windows desktop at about 1:00-1:15 depending.

But the NAS does not become available until 1:30-1:45
depending...

How does that measure up against others'?

NB: We're talking the ability to open a directory on some
network-attached device - NOT just the Windows desktop.
 
The best I've been able to do from a cold start (i.e. computer
powered off) to being able to see a directory of my NAS box
shares is 1:30.

I see the Windows startup splash screen at about :31 and the
Windows desktop at about 1:00-1:15 depending.

But the NAS does not become available until 1:30-1:45
depending...

How does that measure up against others'?

NB: We're talking the ability to open a directory on some
network-attached device - NOT just the Windows desktop.



I power on my computer when I get up in the morning, then go get my
coffee. When I come back, it's done booting. I don't know how long it
took to boot and I don't care.

My personal view is that the attention many people pay to how long it
takes to boot is unwarranted. Assuming that the computer's speed is
otherwise satisfactory, it is not generally worth worrying about.

Ken Blake, Microsoft MVP
 
The best I've been able to do from a cold start (i.e. computer
powered off) to being able to see a directory of my NAS box
shares is 1:30.

I see the Windows startup splash screen at about :31 and the
Windows desktop at about 1:00-1:15 depending.

But the NAS does not become available until 1:30-1:45
depending...

How does that measure up against others'?

NB: We're talking the ability to open a directory on some
network-attached device - NOT just the Windows desktop.

Used to see about that amount of time myself on XP and Windows 7,
anywhere between 1:30 to 3 minutes. There was a friend who had a serious
problem and used to not be able to use his computer until 8 minutes into
the boot process. That was fixed by doing an In-Place Upgrade Install of
of Win7 -- probably cleared out a bunch of useless drivers that were
still being loaded but not being used anymore.

Yousuf Khan
 
I power on my computer when I get up in the morning, then go get my
coffee. When I come back, it's done booting. I don't know how long it
took to boot and I don't care.

My personal view is that the attention many people pay to how long it
takes to boot is unwarranted. Assuming that the computer's speed is
otherwise satisfactory, it is not generally worth worrying about.

Ken Blake, Microsoft MVP

Considering that almost all Microsoft patches require a reboot of the
computer no matter what these days, the reboot time is a pretty
important feature to be aware of.

Yousuf Khan
 
Considering that almost all Microsoft patches require a reboot of the
computer no matter what these days, the reboot time is a pretty
important feature to be aware of.

Sooner or later, most of us have to get up and step away from the
computer, whether it's just to stretch our legs, get a drink or a bite
to eat, use the restroom, answer the front door, look out the window,
take a nap/sleep, etc. Take advantage of any of those breaks by using
it to complete the reboot process. It doesn't really matter how long
the reboot process takes because the break will almost certainly be
longer.
 
In
Yousuf said:
Considering that almost all Microsoft patches require a reboot of the
computer no matter what these days, the reboot time is a pretty
important feature to be aware of.

Yousuf Khan

I have found AV real time scanners to be far better at keeping your
computer(s) safe than depending on security updates anyway. It seems the
hackers gets around the new patches within 24 hours anyway.

And I reboot this computer for example like once every two months. And I
don't need to, but I do it, as it just seems to work better if you
reboot once in awhile.

And also people seem to be chatting, as everybody only owns one
computer. I think that idea is just nuts. True I usually only have one
computer running at a time. But if one is going to be tied up for
whatever reason, I'll fire up two or three of them.
 
In
Yousuf said:
Used to see about that amount of time myself on XP and Windows 7,
anywhere between 1:30 to 3 minutes. There was a friend who had a
serious problem and used to not be able to use his computer until 8
minutes into the boot process. That was fixed by doing an In-Place
Upgrade Install of of Win7 -- probably cleared out a bunch of useless
drivers that were still being loaded but not being used anymore.

Yousuf Khan

I have two Toshiba 2595XDVD 400MHz Celeron with 192MB of RAM (maxed
out). One has Windows 98SE and that one flies. The other one has Windows
2000 and that one takes 10 minutes to boot. I blame the 192MB of RAM, as
the disk activity just never seems to stop and that is a slow 4200rpm
6GB hard drive. I haven't used either one in years.

I do have Windows 2000 SP5 installed on an Asus EeePC 701 with 2GB of
RAM. And that one flies and boots in 40 seconds. XP SP2 on the same
machine takes 90 seconds.
 
In
Char said:
Sooner or later, most of us have to get up and step away from the
computer, whether it's just to stretch our legs, get a drink or a bite
to eat, use the restroom, answer the front door, look out the window,
take a nap/sleep, etc. Take advantage of any of those breaks by using
it to complete the reboot process. It doesn't really matter how long
the reboot process takes because the break will almost certainly be
longer.

That is so true Char. Although these Gateway M465 laptops (I have six of
them) this practice could be a problem. As you can't turn them on and
walk away. As if no key is pressed or no mouse movement, it thinks it
was turned on by mistake and shuts down. I never did find away to
override it. Although if AverMedia TV turned it on because of a
scheduled recording, it stays on.
 
Considering that almost all Microsoft patches require a reboot of the
computer no matter what these days, the reboot time is a pretty
important feature to be aware of.


"Almost all" is a big exaggeration. Yes, there are some that require
it, but far from almost all.

And when they do require it, they do *not* require that it be done
immediately. If you are concerned about the time it takes to reboot,
do the rebooting overnight.

Ken Blake, Microsoft MVP
 
Per Yousuf Khan:
Considering that almost all Microsoft patches require a reboot of the
computer no matter what these days, the reboot time is a pretty
important feature to be aware of.

Windows Update makes me crazy sometimes.

I need to reboot for some reason, forget to click on the fine
print, and then wind up with something like "Installing update 1
of 32....".
 
Per Yousuf Khan:

Windows Update makes me crazy sometimes.

I need to reboot for some reason, forget to click on the fine
print, and then wind up with something like "Installing update 1
of 32....".

One wonders why you update so infrequently that you get to a point
where you have 32 updates pending... ;-)
 
In
(PeteCresswell) said:
Per Char Jackson:

I think part of it is my inner control-freak plus a certain
amount of laziness.

To avoid the unexpected "Installing n updates....." when I need
to reboot in a hurry (as in I'm working on something and drinking
too much coffee....) I turn automatic updates off.

Then it becomes a matter of taking the trouble to apply them....

In the "32" case, I had been troubleshooting some boot-time
weirdnesses introduced when I installed a certain DVD transcoder
or/and a surveillance camera monitoring application.

In that case, I reverted to a known good image that was over a
year old - so the large number of updates should have been no
surprise.... but it was bc I had updates turned off and forgot to
click on the fine print.

I've devolved into applying other-than-security updates
one-by-one and checking the system after each.

Security updates, I'll apply as they come - but always have an
image of the "Before" system.

The motivation for that came from the IE 8 install that was part
of the 32. That one, I still have in the que bc it increases
boot time to almost five minutes. Yeah, that doesn't sound
right.... but it does and I'm too clueless to even guess why...
it just does... and I've replicated it several times, starting
with images that boots to NAS availability in 1:34-1:45.

Maybe I just have too much time on my hands....

Been there and done that. Ever noticed how those images with the fewest
number of updates are so rock solid? I too noticed that. And in 2008 I
bought an Asus EeePC 701 was a 4GB SSD on the motherboard that came with
XP SP2. There was no hope of getting SP3 installed or almost virtually
no other updates.

I thought for sure this machine would be a malware magnet and I made
backups all of the time just waiting. And after a year, nothing at all.
Of course you start thinking, how can that be? That is just impossible.
As that goes against everything we have been taught.

Something just isn't right and I have over 20 laptops here and I had
taken 6 of them and I quit updating them too. I figured many one I was
just lucky or something. But six more just waiting to be infected from
the lack of updates just can't be just being lucky anymore.

I ran them for four years and absolutely nothing. They were running
solid as a rock while the ones that were getting updates were having
stability problems. As every time you install an update, you had to
cross your fingers hoping it would work okay afterwards. Most of the
time, it did. But sometimes it didn't.

And Microsoft isn't helping by taking up to 7 years to plug some
security holes. And when they do patch a hole, hackers quickly find
holes in the new patch to use. This process doesn't work. Microsoft
works too slow and hackers work too fast.

What works so much better is AV real time scanners. Security holes? No
problem, as AV scanners are monitoring all of your ports anyway. And AV
doesn't take 7 years to stop new malware. As they are updated daily. And
if that isn't enough protection for you, there are also sandboxes. Which
even stops zero day malware dead in its tracks.
 
Per BillW50:
Been there and done that. Ever noticed how those images with the fewest
number of updates are so rock solid?

Yes.

I am even thinking about trying a new build from scratch: install
XP, and build it up from there one or two installs at a time with
an image at each step - just to measure/record the boot times at
each step of the build.

Now I'm thinking I *really* have too much time on my hands.....
-)
 
In
(PeteCresswell) said:
Per BillW50:

Yes.

I am even thinking about trying a new build from scratch: install
XP, and build it up from there one or two installs at a time with
an image at each step - just to measure/record the boot times at
each step of the build.

Now I'm thinking I *really* have too much time on my hands.....
-)

I wish I had the time. As I have been fighting for two days trying to
update a few utilities and removing software that refuses to uninstall.
And I haven't gotten anywhere. The utility updates screw up shutting the
computer down and it doesn't. Computers are no longer fun if you have to
fix everything that updates screws up. :-(
 
Back
Top