Discussion on:
View:
Show:
Could someone take a moment to explain why it is so important that your PC boot in as short a time as possible. I don't consider a one minute boot time to be a problem, but there are many that do, please tell us why?
a clean install of DOS 6 - hit switch to boot of OS - 25 seconds. Another twenty seconds to boot into Win 3.11
To boot my current P4 2.4 ghz to log on screen in SimplyMEPIS Linux 8 - is 40 seconds - OS and GUI, which is NOT really part of the OS, but seen as part of it now days.
So I voted 30 to 60 seconds.
Now, can anyone explain why most of the new versions of Windows take so much longer than the old ones, considering the machines are thousands of times faster in turning on and processing the code?
To boot my current P4 2.4 ghz to log on screen in SimplyMEPIS Linux 8 - is 40 seconds - OS and GUI, which is NOT really part of the OS, but seen as part of it now days.
So I voted 30 to 60 seconds.
Now, can anyone explain why most of the new versions of Windows take so much longer than the old ones, considering the machines are thousands of times faster in turning on and processing the code?
I don't really care how fast the computer boots, as long as it runs well, who cares if it boots up under 30 sec.
Back in the bad old days, before we manage to train users in the great concept of defraging a drive and developers in auto storage management within the OS - it was common for a system that had had a lot of use with applications being added, updated, and removed to take ten to thirty minutes to boot from turn on to I can now log in.
One place I was at the drives were five years old without having been defragged, when I started there. One Friday afternoon while the rest of the office were off at a technical conference of their type (mechanical and electrical engineers) I went around and defragged every computer - took three hours per system, but I set them all going at once.
Monday when they arrived and they booted while they were still taking their coats off, scared the hell out of most of them. It was quite funny watching their reactions.
One place I was at the drives were five years old without having been defragged, when I started there. One Friday afternoon while the rest of the office were off at a technical conference of their type (mechanical and electrical engineers) I went around and defragged every computer - took three hours per system, but I set them all going at once.
Monday when they arrived and they booted while they were still taking their coats off, scared the hell out of most of them. It was quite funny watching their reactions.
Take them away for a day to add program updates to tools they need, defrag and watch the amazement the next morning.
Still can't convince my IT people to get a real defrag utility scheduled in their tasks.
So I borrow the ol' defraggler, bad me, and run that.
Still can't convince my IT people to get a real defrag utility scheduled in their tasks.
So I borrow the ol' defraggler, bad me, and run that.
Run XP on a P3 with only 256 meg of RAM.
Slo-o-o-o-w. At least 10 minutes to boot to logon and another 10 to log on.
Slo-o-o-o-w. At least 10 minutes to boot to logon and another 10 to log on.
Like the infamous "boot accelerators" and a bloated anti-virus prog and whammo! 30 minute wait.
I have an old Dell Latitude CS, PIII 500 with 256MB. Boots up in less than 2 minutes to logon, about 2 more to load all background apps.
This is my netbook for lack of a better description, but it is pretty near bullet proof with the magnesium shell; and has survived off roading trips and a couple of accidental drop tests.
This is my netbook for lack of a better description, but it is pretty near bullet proof with the magnesium shell; and has survived off roading trips and a couple of accidental drop tests.
Boot, go get a coffee, go out for a smoke, come back and it's ready. I have a lot of programs that run when I boot up and don't feel like doing without any of them. The boot takes what it takes.
I've got dozens of computers on the factory floor. Employees clock in and out on them, and record the time they spend on each production work order. Boot time comes out of the work order. Five minutes to boot can be longer than some of our operations. Try explaining to a supervisor why his department's efficiency is down because of boot times. Be prepared to be handed your head.
I was giving my opinion as a retired man that... doesn't care how long it takes to boot.
I don't care much about how long my home system takes to boot. It's going to take several minutes to get the cat off the keyboard anyway.
I am sure you know the answer already, but here goes.
Boot up time on my Windows 7 PC takes 37 seconds, why? Because I have the latest and greatest hardware that supports all the added features that Win7 tries to employ; ie: 8gig ram, 1TBHD, Quad core AMD etc. and it is snappy no matter what.
Now, I am almost certain that "ALL" of those darn computer hardware/software companies all get together at some point and say; you know what, if MS comes out with that new OS this year, we will work with them to make sure that any PC over 2 years old won't be nearly as snappy as it should be just so that consumer has to say to themselves; man I have to upgrade my PC so it can be snappy and dandy with the new OS Microsoft has.
Hence, they either buy a new PC from Dell, Gateway, Acer etc. and/or they buy new hardware components from Best Buy and whatnot. See, that cycle of buying and upgrading is, and I swear to the CPU god, a darn conspiracy between the computer companies to keep that all powerful buy/sell cycle going. Hehe, anyhow my thoughts on that.
Boot up time on my Windows 7 PC takes 37 seconds, why? Because I have the latest and greatest hardware that supports all the added features that Win7 tries to employ; ie: 8gig ram, 1TBHD, Quad core AMD etc. and it is snappy no matter what.
Now, I am almost certain that "ALL" of those darn computer hardware/software companies all get together at some point and say; you know what, if MS comes out with that new OS this year, we will work with them to make sure that any PC over 2 years old won't be nearly as snappy as it should be just so that consumer has to say to themselves; man I have to upgrade my PC so it can be snappy and dandy with the new OS Microsoft has.
Hence, they either buy a new PC from Dell, Gateway, Acer etc. and/or they buy new hardware components from Best Buy and whatnot. See, that cycle of buying and upgrading is, and I swear to the CPU god, a darn conspiracy between the computer companies to keep that all powerful buy/sell cycle going. Hehe, anyhow my thoughts on that.
working on a brand new Toshiba with Win 7 Home Premium, initially it took over three minutes to boot to log in screen, then another minute after you log in. After I cleaned the Toshiba added crap out, I cut the initial boot down to two minutes. then I went in and shut off all the Windows set default crap the user doesn't need or use, set to auto log in - as client wanted, and got the final time down to two minutes from switch on to ready to use - included the auto log in.
My three to four year old 2nd hand Dell with SimplyMepis Linux 8 is much faster than that.
But, considering the modern systems use a CPU that's around the 2 to 3 ghz as against 25 mhz of twenty years ago, and the cpu design is said to be thousands of times faster and more capable than a 386 - well the modern cpus should be an order magnitude faster in the 5,000 plus range - the motherboards are said to be hundreds of times faster too. So modern systems should be booting in a fraction of the time of the old 386 systems, yet they don't - hmm. Enough said, I think
My three to four year old 2nd hand Dell with SimplyMepis Linux 8 is much faster than that.
But, considering the modern systems use a CPU that's around the 2 to 3 ghz as against 25 mhz of twenty years ago, and the cpu design is said to be thousands of times faster and more capable than a 386 - well the modern cpus should be an order magnitude faster in the 5,000 plus range - the motherboards are said to be hundreds of times faster too. So modern systems should be booting in a fraction of the time of the old 386 systems, yet they don't - hmm. Enough said, I think
Computers are like trucks in certain ways. As they get bigger and more powerful, we pile on more loads for them to carry. Revo uninstaller tells me that I have 159 installed applications on my harddrive. A certain number of these are more than 100 MB each. My old 66 Mhz computer with 540 Mhz harddrive would have choked to death L-O-N-G before it had any such load piled on it. (Forget the one before that with an 8086 processor and no harddrive at all.) The power and capacity of modern computers is really just keeping up with demand and this is why they are not hundreds and thousands of times faster. Would not Microsoft Edlin scream in comparison to Word 2010 if it were installed and configured to run on hardware capable of running Word 2010?
process. The boot to logged in should, at most be, the
Operating System
Graphics User Interface
Firewall
Anti-virus
and nothing else.
Operating System
Graphics User Interface
Firewall
Anti-virus
and nothing else.
MS should just have some seperate process for loading the critical files needed then the Firewall and Antivirus and nothing else. Then load the other stuff with a delay, ie; the added on application startup stuff.
I'm not talking about using a 3rd party app either, just having a default way to boot the critical files plus firewall/antivirus would be nice in Win7.
I'm not talking about using a 3rd party app either, just having a default way to boot the critical files plus firewall/antivirus would be nice in Win7.
You need to remember that a goodly portion of the boot process occurs BEFORE Windoz, or any other OS, starts to load.
& that may be where most of the problem lies.
I haven't personally researched it, but Maximum PC mag had an article that stated the BIOS was the main culprit for slow boot times.
I'm not sure I buy it, because as 1 post put it, there does seem to be some level of conspiracy to keep as steep as possible of an upgrade path going.
That really doesn't excuse Windoz (or others) of not designing a post and load sequence that would assign & execute boot priorities in a safe & reasonable order.
I guess its more profitable to ignore the way to speed boot times than to actually try to resolve such issues.
& that may be where most of the problem lies.
I haven't personally researched it, but Maximum PC mag had an article that stated the BIOS was the main culprit for slow boot times.
I'm not sure I buy it, because as 1 post put it, there does seem to be some level of conspiracy to keep as steep as possible of an upgrade path going.
That really doesn't excuse Windoz (or others) of not designing a post and load sequence that would assign & execute boot priorities in a safe & reasonable order.
I guess its more profitable to ignore the way to speed boot times than to actually try to resolve such issues.
what with checking for USB and different graphics sources and a lot more memory to check than it used to have. BUT, the system now works much faster and flies through them faster.
With many of the systems, you can set the BIOS to show what it's doing and time how long it takes from push button to when it has that little message it's starting to load Windows. Now, I've not timed that as such, but it seems that same as it used to. When I tried this with a 386 / 25 mhz and a P4 / 2.4 ghz, by pushing both buttons at once, the P4 got to the Windows loading stage faster than the 386, despite having a lot more to load in the BIOS. Yet, the 386 had Windows open and ready to rock and roll first, by a very noticeable margin.
The thing to do is to look at the huge list of 'services' that Windows has loading with the modern versions, most of which didn't exist or open in the older versions.
Hell, one way to shave time off the opening time is to disable the Windows services that it requires to enable their techs to hit your system from the outside - that makes a big difference, just there. Here's a list from another post I made recently - and it's not comprehensive:
'off the shelf' OEM Win 7 Home Premium set up - straight Microsoft defaults
1. Control Panel - Administrative Tool - Computer Management - Services
(all the following settings had a default of Automatic start - I think they should be either manual or disabled - unless your corporate set up requires you to use them)
Bluetooth Support service
Remote Desktop Configuration
Remote Desktop Services
Remote Registry
Routing and Remote Access
Windows Remote Management
2. Control Panel - Windows Firewall - Advanced Settings -
(these firewall settings are default set to allow - all now changed to block by me)
Inbound Rules
Remote Assistance - seven of them
Remote Event Log Management - six of them
Remote Volume Management - six of them
Windows Remote Firewall Management - four of them
Windows Remote Management - four of them
Outbound Rules
Remote Assistance - seven of them
..............
I'd also add to the list the wireless zero config, unless you use it.
With many of the systems, you can set the BIOS to show what it's doing and time how long it takes from push button to when it has that little message it's starting to load Windows. Now, I've not timed that as such, but it seems that same as it used to. When I tried this with a 386 / 25 mhz and a P4 / 2.4 ghz, by pushing both buttons at once, the P4 got to the Windows loading stage faster than the 386, despite having a lot more to load in the BIOS. Yet, the 386 had Windows open and ready to rock and roll first, by a very noticeable margin.
The thing to do is to look at the huge list of 'services' that Windows has loading with the modern versions, most of which didn't exist or open in the older versions.
Hell, one way to shave time off the opening time is to disable the Windows services that it requires to enable their techs to hit your system from the outside - that makes a big difference, just there. Here's a list from another post I made recently - and it's not comprehensive:
'off the shelf' OEM Win 7 Home Premium set up - straight Microsoft defaults
1. Control Panel - Administrative Tool - Computer Management - Services
(all the following settings had a default of Automatic start - I think they should be either manual or disabled - unless your corporate set up requires you to use them)
Bluetooth Support service
Remote Desktop Configuration
Remote Desktop Services
Remote Registry
Routing and Remote Access
Windows Remote Management
2. Control Panel - Windows Firewall - Advanced Settings -
(these firewall settings are default set to allow - all now changed to block by me)
Inbound Rules
Remote Assistance - seven of them
Remote Event Log Management - six of them
Remote Volume Management - six of them
Windows Remote Firewall Management - four of them
Windows Remote Management - four of them
Outbound Rules
Remote Assistance - seven of them
..............
I'd also add to the list the wireless zero config, unless you use it.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
