Tweaking boot time (classpnp.sys?)

or there are too many processes running at startup.

Now wait! What's to say "too many"? And what's to say a lot is "bad"? Many folks have cameras, card readers, external drives, printers, email programs, PDA devices, various security programs including AV, AS, FW programs, HW monitors, special mouse and keyboard programs, dual monitors, networked/mapped drives, etc. that start at boot. I say again, as long as the system is running fine once it is fully booted, then a long (3 - 4 minutes) boot time does not indicate a "problem". Some XP systems can take 5 - 6 minutes to boot, then run great all day long.

There is no harm in having many processes run at startup as long as you have the resources (namely RAM) to support them after the boot is complete.

I'm new here and am puzzled why someone would want to wait up to 4 minutes for their system to boot. FYI - my normal boot time 23 seconds as timed by program boottimer.exe. And no it is not an ssd. It's a 5400 RPM HDD (WD2500BEVS).

I'll admit though, I am not well versed with Raid configurations. I just can't imagine troubleshooting program or driver issues with that long of a boot time. I'd pull my hair out. Wait, can't I'm already bald. LOL.

How much time does this add to a single system hdd setup?

logic - sorry I didn't make my question clearer. When comparing single hdd to multi-hdd setup (Raid), how much time does the Raid configuration add?

I'm new here and am puzzled why someone would want to wait up to 4 minutes for their system to boot.

Nobody said that! But what I did say, and what I am saying again is that boot times is NOT an indication of performance.

Originally Posted by Digerati
Nobody said that! But what I did say, and what I am saying again is that boot times is NOT an indication of performance.

Digerati - please don't take offence but my question of why someone would want to wait up to 4 minutes for their system to boot was taken from your quote.

"Many systems take 3 or 4 minutes or longer to fully boot and load up everything at start."

Did I misunderstand your meaning? Again I have little experience with RAID set ups but am posing questions to have a better understanding. Does a raid set up add significant time to the booting of an Win7 OS? If so how much time... 10, 30, 60 seconds?

I am having a hard time getting around the aggravation that even a 2+ minute reboot would pose while troubleshooting a system let alone your mentioned 3-4 minutes.

Laker said:

Originally Posted by Digerati
Nobody said that! But what I did say, and what I am saying again is that boot times is NOT an indication of performance.

Digerati - please don't take offence but my question of why someone would want to wait up to 4 minutes for their system to boot was taken from your quote.

"Many systems take 3 or 4 minutes or longer to fully boot and load up everything at start."

Did I misunderstand your meaning?

No offense taken but you did, and still are twisting the meaning of my words around. You say you took it from my quote but I NEVER said or implied that anyone wants to wait for anything! The fact is, most computer users would prefer instant on, if possible, and would rather not wait at all.

So again, I am not speaking about desires. I am merely stating, again, that long boot times is not an indication of performance.

Yes, you have stated your point several times now. I did not nor am I attempting to "twist the meaning of your words".

I am attempting to understand whether a raid set up add significant time to the booting of a Windows 7 OS? If so how much time... 10, 30, 60 seconds? Would you be willing to provide an answer?