Measure XP & Vista Boot-up/Re-boot Times

I don't know if there has been a thread on all this or not, and I am a bad Googler, and I didn't find anything except this....

Alright, 2 ways to measure the times....

I. Re-boot Time

Open up a text editor, i.e. Notepad, and paste the code below and save it as ReBoot .VBS anywhere on the HDD, preferably the desktop.

Code:

Option Explicit
On Error Resume Next
Dim Wsh, Time1, Time2, Result, PathFile, MsgResult, MsgA, AppName, KeyA, KeyB, TimeDiff
MsgA = "Please close all running applications and click on OK."
KeyA = "HKEY_CURRENT_USER\Software\RestartTime\"
KeyB = "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\RestartTime"
AppName = "ReBoot-Time"
Set Wsh = CreateObject("WScript.Shell")
PathFile = """" & WScript.ScriptFullName & """"
Result = wsh.RegRead(KeyA & "Times")
if Result = "" then
MsgResult = Msgbox (MsgA, vbOKCancel, AppName)
If MsgResult = vbcancel then WScript.Quit
Wsh.RegWrite KeyA & "Times", left(Time,8), "REG_SZ"
Wsh.RegWrite KeyB, PathFile, "REG_SZ"
Wsh.Run "cmd /c Shutdown -r -t 00", false, 0
else
Wsh.RegDelete KeyA & "Times"
Wsh.RegDelete KeyA
Wsh.RegDelete KeyB
TimeDiff = DateDiff("s",Result,left(Time,8))
MsgBox "Your computer reboots in " & TimeDiff & " seconds", VbInformation, AppName
end if
wscript.Quit

You can also Download this script and run it.

Use of the Script:

• Double click on the script icon if it is on your desktop or on the file if you saved it in a particular folder.
• Close all the running applications and click the OK button in the dialog box.
• The computer will reboot and when Windows will be ready to be used, a new dialog box will open displaying the time your computer took to reboot.

My Times

Vista Ultimate SP1 x64



XP Pro SP3 x86-32



Original Thread/Link

II. Boot-up Time

This procedure is fairly simple. Just download it at PlanetSoft ( BootTimer) and double click on the executable file. On the next restart cycle, the timer will start counting from the time it boots up till the OS loading and display it correctly on the pop up window.

The tiny software utility has the capability to measure the boot time starting from the bootloader until the handling get passed to the OS to move on with proper applications loading. It only consumes around 130kB, which is quite suitable to be used for any Windows PC. Only one drawback, it is said not to work for Linux or other fastboot OSs that takes less than 5 seconds for total boot up time to OS.

Currently it is only compatible with Windows OS such as NT and XP. And for me, it works in Vista as well.

Using this App:

Download and Double-click the .exe file to Reboot....



After the OS reboots, and you login....



After clicking on OK, all temporary files are cleaned up, and a link comes up..





Also, the .exe creates a startup entry as well, so if you want to, you can disable it in MSConfig from preventing BootTimer to calculate the Boot-Up time, each time you start your system (OS).



PlanetSoft

My Times

Vista Ultimate SP1 x64



XP Pro SP3 x86-32





Not the most useful app one'll find, but comes in handy after one follows a Tweaking Guide, after cleaning up, testing single-core||multi-core boot-ups etc

 

Cool, +1 rep

 

Cool stuff, I am going to try it out.
But after my finals are over, so that I dont screw anything up

K-TRON

 

CeleronM 1.4Ghz 512MB RAM 40GB Fujitsu 5400rpm - XP PRO SP3=89sec.
T7500 2.2Ghz 2GB RAM 120GB WD 5400rpm - Vista Basic=63sec

Cool stuff Andy.

Question: I have to type a password to login on both laptops..so does the time I spend to type usr/pass counts?
Question: When the test is over this script "stays" in the registry right?

 

Thanks, I'll try this out later! BTW, what theme are you using on Vista?

 

Yeah, the login time counts. For the vbs script tool, everything counts -- POST time, bootloader loading and selection time, etc.
For BootTimer, the time taken from the Boot-loader to the point you login into windows, counts.

And the registry keys created by the script are removed. I'm not a programmer, but I think that's what these commands do:

Code:

Wsh.RegDelete KeyA & "Times"
Wsh.RegDelete KeyA
Wsh.RegDelete KeyB

Project X2 (Deviantart)

 

Cool script but be careful with the "On Error Resume Next" statement since it just continues even if a runtime error does occur and can cause unpredictable results .

Here's some code from one of my scripts that uses On Error to catch runtime errors:

Code:

On Error Resume Next         ' Error catching on
   Set LogFile = oFs.CreateTextFile(VBSROOT & "\\" & "Backup.log", True)
   If (Err.Number <> 0) Then
      oShell.Run "net send " & COMPUTERNAME & " Fatal error!!! " & "Error: " & Err.Number & " " & Err.Description
      Err.Clear
      WScript.Quit 0
   End If
On Error Goto 0                  ' Error catching off

On Error Resume Next = Continue even if a runtime error does occur
Err.Number = the error number (zero if no error)
Err.Description = the error message (for example: could not create file)
Err.Clear = Clear the last runtime error so you can catch the next error
On Error Goto 0 = Do not continue if a runtime error occur (error message box popup and script stops)

 

99 seconds.
I am on Vista Home Premium SP1.
This is insane.
Why do most people have much lower boot times?
I cleaned out the OS as much as I could, optimized it as well .. and still I get so high boot times.

 

You can try and enable Multi-Core Boot support, which dropped my boot times by 10 seconds.

The VBS script gives the reboot time, and is not the best way to measure the boot-up time. (I posted it just just for fun, and because most people don't trust software)

BootTimer gives a much more credible result.

 

Nice this should help

 

Don't even need to run anything to know mine's over 120 secs - way over.

 

I voted for all the options. I mean -

My system is 20-29 fast.

I tried to make sense of "(I)", maybe this might be an indication, or a hint, of the unit, but I couldn't make anything of it.

 

Re-Boot Time and (I) refers to the VB script, the 1^st method shown in the OP, on how to measure the system's re-boot time.

Now, the VB script uses seconds as a unit for measuring the time taken to re-boot, it is obvious that, if a user's system has a reboot time that falls within 20 and 29 seconds, may check 20-29.

And the reason, why I made a multiple-choice poll is that most users have multiple systems, and are dual/tri/quad booting their systems.

I hope that makes it more clear for you.

 

How could you improve your boot time? i had disabled a lot of services and startup programs, defragment disk, clean up the disk. And still getting almost 110 seconds.

I got cpu ntel dual core 2.0 ghz, vista premium 64bits, gpu 9600m GT, 4GB ram :/

 

Have you used BootTimer to measure the bootup time ?

The VB Script counts the time your system wastes while shutting down, and then restarting all over again ( Re-boot time)

You can try and enable the multi-core boot option in msconfig, but I would advise not to modify any crucial system settings to get a lower boot time.

 

Hm, I might try this later. Thanks.

 

This has been posted before, the script counts shut down time...so it's not very accurate to a "boot time".

 

Meh! Thats what I posted before. VB Script: Re-Boot Time. Even the poll says Re-Boot Time. (And I couldn't find anything on this here)

BootTimer: Boot-Up Time

(Since most users don't trust never-heard-before software, I made a poll for the VB Script thing)

 

Here's mine with BootTimer:



Vista Home Premium x64
T7500
3gb RAM
Western Digital Scorpio 160GB 8MB cache 5400 RPM

 

Weird, boot timer doesn't do anything for me...Vista 32 premium. Oh well, just hope it didn't crap in my registry

 

Did you run it as administrator, I had to do this on mine to get it to work,

 

I have the .exe on my desktop, run it, restart and it works, always.
Its a clean software, else it wouldn't have been posted here..

It is not officially supported by .Vista, but it hasn't choked a single time on my system.

@bangert: Man, your system is fast !!

 

Lol, I don't have many startup programs, just what I need, hate waiting for things not needed to load!!!!

 

Reboot time 48 seconds
Windows xp pro sp-3
32Gb Samsung ssd
BootTimer all over the place
25.718sec to 42.277


Alex

 

Reboot time: 70 seconds
Boot time: 48.89 seconds

 

BootTimer: 45 seconds
RebootTimer: 92 seconds

HP Protecttools using tpm for logon steals about 15-20 sec so i guess disabling the tpm and protecttools the boot and reboot times would be 30-35 seconds / 60-70 seconds.

I'd like to modify the reboot script as follows:

Code:

Option Explicit
Dim Wsh, Time1, Time2, Result, PathFile, MsgResult, MsgA, AppName, KeyA, KeyB, TimeDiff
MsgA = "Please close all running applications and click on OK."
KeyA = "HKEY_CURRENT_USER\Software\RestartTime\\"
KeyB = "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\RestartTime"
AppName = "ReBoot-Time"
Set Wsh = CreateObject("WScript.Shell")
PathFile = """" & WScript.ScriptFullName & """"
On Error Resume Next
   Result = wsh.RegRead(KeyA & "Times")
On Error Goto 0
if Result = "" then
MsgResult = Msgbox (MsgA, vbOKCancel, AppName)
If MsgResult = vbcancel then WScript.Quit
Wsh.RegWrite KeyA & "Times", left(Time,8), "REG_SZ"
Wsh.RegWrite KeyB, PathFile, "REG_SZ"
Wsh.Run "cmd /c Shutdown -r -t 00", false, 0
else
Wsh.RegDelete KeyA & "Times"
Wsh.RegDelete KeyA
Wsh.RegDelete KeyB
TimeDiff = DateDiff("s",Result,left(Time,8))
MsgBox "Your computer reboots in " & TimeDiff & " seconds", VbInformation, AppName
end if
wscript.Quit

I moved the "On Error ..." statement from the start of the script to the only line that actually needs it. So if a runtime error (like registry key could not be created or deleted) should occur the user gets an error popup.

 

ReBoot time: 43 seconds
First time I ran it, it was 46, and I was shocked (that it was so fast) so I ran again, and get 43.
This is the laptop in my sig, with a HDD.
I'll make a video if you don't believe me.

 

No need of a video really. Have you tried running BootTimer, that'll be insanely low, I guess .

 

Why do some of us get nearly 100 seconds on the boot up time even with fully optimized OS's?
This really makes little sense.

 

http://www.youtube.com/watch?v=lnMVsBzvfZM

 

If you get nearly 100 seconds, your system is either messed up rather than optimized or Windows is doing something special on that particular boot. It always boots quite a bit slower after installing drivers or certain updates.

Also, keep in mind that in this thread, Vista is being compared to XP which results in a very wide variety of times.

I get 69 seconds for the reboot time. This includes the second or so that it takes me to react to grub's choice between Vista and Linux.

 

My old boot times were:

BootTimer: 45 seconds
RebootTimer: 92 seconds

Then i disabled the tpm chip and hp protecttools and got

BootTimer: 31 seconds
RebootTimer: 64 seconds

TIP! running boottimer under Vista:

set compatibility to xp sp2 and run as administrator
after reboot you will get a windows has blocked a startup program - just start it manually from the taskbar as fast as possible

 

I ran that Boot timer program, and although every boot was nearly identical, the times varied ALOT. The fastest I got was about 28 and slowest about 42, and both of those boots seemed the same.

Also, my results are probably a little unfair, because this Xp is partially nlited (the actual install with pagefile disabled was 900mb) and the only programs installed are Firefox, Xvid, X264, CCleaner and ffdshow.
Though I do have about 10Gb of media on the boot drive.

This helps though
"Rundll32.exe advapi32.dll,ProcessIdleTasks"

 

Yeah, but 97 seconds for booting up is really long, even for Vista.
Well, I'm using Vista Home premium that came pre-installed.
Boot times were virtually identical (perhaps a bit lower) when I first got the laptop (even after cleaning out all the garbage programs that came with it along with shutting down various processes using Black Viper's website, defragmentation and all).

Either Acer messed up the OS somehow upon the install itself or I dunno what.
I'll probably have to re-format my boot partition and re-install the OS (was planning on doing that anyway).
This is exactly why I detest pre-installed OS's.

 

With a few more programs installed:
http://i158.photobucket.com/albums/t100/duksandfish/boot.jpg

I'm gonna stop now before I get obsessed lol (unless I already am )

 

That did the trick. Boot up time of 62s is vista home premium 32bit. My time probably isn't helped much since I run objectdock and rainmeter at startup.

T61p, 2.4ghz, 3gb RAM, Hitachi 7k30, Quadro FX570M

 

I run Rocketdock, rainmeter, launchy, and avira at startup. still under 30s

 

How many of you have disabled Vista's ReadyBoost service, and thereby disabled ReadyBooT optimization?

36 seconds to boot with wireless connection established - UNTWEAKED and loading sidebar with 4 gadgets and objectdock.

Disabling services may do more harm than good but can only be worth a few seconds of boot time.

See: http://forum.notebookreview.com/showthread.php?t=328787

 

how r these times possible? i want this

 

I think some of you guys are taking boot times way too <s>seriously</s> religiously. Maybe manufacturers should post the 0-to-logon-screen time like the 0-60 mph time for cars.

 

I race my friends all the time. We all press the power button at the same time and glue our eyes to each others screen.

/sarcasm

 

I wouldn't be surprised if some people actually do that.

 

LOL. Uber nerds. Jk. <3 you all for people who do, do that.

 

McGrady, it's not nice to talk about Andy that way.

 

Haha good idea!

 

I'm sitting at ~36secs untweaked XP SP3 with ObjectDock, AIM 6.8 and Norton 2008 all starting at boot.

Specs in sig.

 

Me..Nerdus Maximus ??

Whoever said that is..

 

Well, on a Vista clean install, with quite a few programs installed, I still get 57 secs reboot

 

26 seconds. Not bad for a 3 and a half year old Asus laptop with 1.6 Ghz Dothan

It's a Samsung HM160HC and I tweaked it a bit though.