Slashdot Mirror


Windows 8 To Feature 'Fast Startup Mode'

New story submitter CSHARP123 writes "Microsoft has posted details about a Windows 8 feature that is a hybrid between cold booting and waking up from a hibernated state. This feature is called fast startup mode. Gabe Aul, director of program management in Windows, explains: '[A]s in Windows 7, we close the user sessions, but instead of closing the kernel session, we hibernate it. Compared to a full hibernate, which includes a lot of memory pages in use by apps, session 0 hibernation data is much smaller, which takes substantially less time to write to disk. If you’re not familiar with hibernation, we’re effectively saving the system state and memory contents to a file on disk (hiberfil.sys) and then reading that back in on resume and restoring contents back to memory. Using this technique with boot gives us a significant advantage for boot times, since reading the hiberfile in and reinitializing drivers is much faster on most systems (30-70% faster on most systems we’ve tested).' The post contains a video as well, which shows Windows starting up in less than 10 seconds."

287 comments

  1. Time to Usable by Scutter · · Score: 4, Insightful

    Can we start talking about "Time to a Usable Desktop"? My laptop boots to a login prompt in 15 seconds, but after login it's another 2-5 minutes before it's done thrashing the hard drive. There are precious few (useful) tools available to track down everything the system is doing, and even fewer to help you improve the situation.

    --

    "Tell me doctor, with all of your defenses, are there any provisions for an attack by killer bees?"
    1. Re:Time to Usable by drinkypoo · · Score: 1

      There are precious few (useful) tools available to track down everything the system is doing, and even fewer to help you improve the situation.

      Soluto does both, for Windows Vista and better, anyway.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Time to Usable by UnknowingFool · · Score: 1

      Yep same here. Now if you are part of an enterprise domain, it seemingly takes even longer.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    3. Re:Time to Usable by Anonymous Coward · · Score: 1

      You're still using XP I'm guessing? I hate Vista/7 with a passion, but this is one thing that MS actually fixed. I have 3 Windows 7 machines, all are "usable" within seconds of the desktop appearing.

    4. Re:Time to Usable by Anonymous Coward · · Score: 2, Insightful

      Doesn't really matter yet.
      There is a sweet spot between when you push the power on button to when the computer is usable.
      If it is about 5s or less then the user will stay at the computer during boot. If it is in the 10s or more the user will go and do something else that probably takes several minutes while the computer is booting and in that range it doesn't really matter if the boot time is 30s or 3 minutes.
      A 5s boot time will still make the user reluctant to use the computer while in a hurry and will cause stress and heart problems for simple things like looking up at time-table for the train and similiar things.
      Below 1s and there is not really any need to optimize it further. (Unless it is a server that gets its power on signal from the router when there is incoming communication.)

    5. Re:Time to Usable by Anonymous Coward · · Score: 5, Funny

      There are precious few (useful) tools available to track down everything the system is doing, and even fewer to help you improve the situation.

      Soluto does both, for Windows Vista and better, anyway.

      So... that means Windows 7, XP, 2000, 98, 95, 3.1, but not ME?

    6. Re:Time to Usable by Wowsers · · Score: 1

      In Linux it appears most the loading takes place before the login screen, then what remains is the users desktop after login, but it appears usable as soon as it appears. Certainly on my distro the only thing that slows down the desktop loading in using Superkaramba apps because there are no decent KDE4 widget replacements.

      My Win7 install is frustrating, just like other version of Win, where the desktop looks like it's loaded, but you don't really know how long it will take until the OS releases control to the user. Microsoft seem to have gone for the "show something is happening" to make it look fast, rather than actually being fast.

      --
      Take Nobody's Word For It.
    7. Re:Time to Usable by Hatta · · Score: 0

      Indeed. They're closing user sessions here to get a shorter boot, that's essentially curing the disease by killing the patient. If I have a long boot time from hibernate, I can go do something else for 5-10 minutes. But if I've lost my user sessions, I have to sit there and reopen all my windows before I have a usable desktop. They might technically have a shorter boot time with this strategy, but it will end up wasting more of the user's time.

      --
      Give me Classic Slashdot or give me death!
    8. Re:Time to Usable by JanneM · · Score: 2, Insightful

      Here's an idea for Ubuntu to beat Windows: Take a screenshot of the desktop when the user selects shutdown. Throw up that screenshot as the boot splash screen. Presto - Ubuntu "booting" in just a second.

      About as honest.

      --
      Trust the Computer. The Computer is your friend.
    9. Re:Time to Usable by Anonymous Coward · · Score: 0

      I highly doubt they are going to kill the original Hibernate feature.

    10. Re:Time to Usable by andrewbaldwin · · Score: 3, Informative

      Now if you are part of an enterprise domain, it seemingly takes even longer.

      And if you have a corporate standard image with policies etc pushed out on each boot....

      On a cold boot, I can wander off, make a cup of tea, come back and it may just be ready. On a request for a reboot after a system update (and why it has to reboot after a change is yet another gripe) I could walk into town, go to the supermarket, buy a box of biscuits, queue up at the checkout, walk back and still be waiting for a usable system.

      Strange that all that downtime x the number of users never really appears in TCO calculations -- I guess that's what meetings were invented for (so we'd have something to do without access to the IT infrastructure

      ...and people ask me why I prefer Linux !

    11. Re:Time to Usable by couchslug · · Score: 2

      That much thrashing indicates something is wrong and/or you have too little RAM.
      The first solution for any old Windows install is to nuke-and-pave (format and reinstall). It takes less time than troubleshooting. Update, add apps, and see if the behaviour recurs.

      --
      "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
    12. Re:Time to Usable by GIL_Dude · · Score: 1

      The tool you want to trouble shoot this is xperf (specifically xbootmgr.exe) from the Windows Performance Toolkit. That is part of the Windows SDK. This tool will give you a look into exactly what is going on during boot and what is hogging disk, CPU, and everything. It is very detailed. Our Windows 7 boot is about 35 seconds from "starting Windows" to being at the desktop with the network icon showing an internet connection and being usable. xperf helped us to get to that state. The Windows SDK is here: http://www.microsoft.com/download/en/details.aspx?id=8279. With their web installer you can select the components you want and not have to download the rest - for xperf you just need the "Windows Performance Toolkit".

    13. Re:Time to Usable by Pope · · Score: 1

      No kidding. Back when classic Mac OS was around, it booted to a usable desktop faster than Windows did. So one of the big "improvements" for XP was to get the desktop open faster. Great, but it sure as hell wasn't usable for 20 to 60 seconds afterwards.

      --
      It doesn't mean much now, it's built for the future.
    14. Re:Time to Usable by agentgonzo · · Score: 1

      This is not about 'time to usable desktop'. It's about shortening the existing boot process (I agree that Windows is far from usable the first half-minute or so after it gets you to the desktop).

      This image sums it all up nicely, without the waffle, video or text.

    15. Re:Time to Usable by Pope · · Score: 1

      I think you just invented iOS :D

      --
      It doesn't mean much now, it's built for the future.
    16. Re:Time to Usable by Anonymous Coward · · Score: 0

      I have noticed that Windows is by far the worst offender in this.

    17. Re:Time to Usable by Anonymous Coward · · Score: 0

      And yet it happens on my parents Win7 machine with 4gbs of ram and a core 2 duo. It's unfortunately too hard to get them to switch to anything.

    18. Re:Time to Usable by EdZ · · Score: 1

      There are precious few (useful) tools available to track down everything the system is doing, and even fewer to help you improve the situation.

      Assuming you're running windows, MSCONFIG handles things that run at startup. It's pretty easy to look through the list and disable anything you don't want.

    19. Re:Time to Usable by neokushan · · Score: 2

      They're not killing hibernate, they're not REMOVING anything, they're simply making the computer start up and shut down operate differently by default. They've actually increased hybernate's resume speed as well because of this, so everyone benefits.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    20. Re:Time to Usable by ByOhTek · · Score: 1

      I think the problem there is more due to your IT mismanagement. I lose about 10 mins a month due to patches. Maybe another minute or two due to the network security software starting up, allowing me to access our network.

      Even with EVERYONE in this situation, we'd still lose much more time to restroom or cigarette breaks (and in the later case, most people here don't even smoke).

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    21. Re:Time to Usable by doobydoobydoo · · Score: 2

      There are precious few (useful) tools available to track down everything the system is doing, and even fewer to help you improve the situation.

      Soluto does both, for Windows Vista and better, anyway.

      I tried Soluto on my old laptop and was not impressed. I had lots of things in Startup that it either wouldn't disable or that I couldn't disable (lots of system processes, sound driver, etc. - basic stuff I'd need). I disabled tons of stuff but it didn't really seem to be any better (and, in addition, Soluto itself needs to start up, which slows things down quite a bit. I tried the "Delayed load" option, but that didn't seem to improve matters much, to be honest. Whilst being quite aggressive in what I turned off, there seemed to be marginal improvement at best. I think instead there's something fairly fundamentally wrong with a lot of Windows services, etc., and maybe the Windows scheduling, that just take an age to load.

    22. Re:Time to Usable by Anonymous Coward · · Score: 0

      Ubuntu like the Linux systems seem ready when they present themselves. And it's common for an HDD to boot around 10 seconds without hibernation. With all the updates that OSes get vs how rare reboots are, hibernation tricks won't help many.

    23. Re:Time to Usable by Anonymous Coward · · Score: 0

      Oh, you mean like my Mac?

    24. Re:Time to Usable by jader3rd · · Score: 1

      There are precious few (useful) tools available to track down everything the system is doing.

      That's because Process Monitor does all you need to do. There's no need for another tool beyond that one. The primary reason why are because so many applications start as part of start up (iTunes and Quicktime being the worst offenders). You can disable them using msconfig. Windows 7 did make things better by causing application which run as part of start up to run as low priority, which as upset many developers who chose to run as part of startup to make their application "appear" to have a fast startup.

    25. Re:Time to Usable by omnichad · · Score: 1

      I think MS decided to "speed up" the boot process in previous versions by showing the logon prompt sooner (before a larger percentage of windows components had loaded). It still took the same amount of time, but you log in earlier in the process with the supposed apparent effect of a faster boot.
       
      This might at least tighten up that same delay a little.

    26. Re:Time to Usable by omnichad · · Score: 1

      On a temporary basis, anyway. It tells you where the settings are and lets you "disable" them, but the settings can come back if you want to change it from "Selective Startup" back to "Normal Startup," meaning you still have to go into regedit or the start menu itself to clear the entries out.

    27. Re:Time to Usable by RebelWithoutAClue · · Score: 1

      You're right, it does work for XP.

      --
      "However beautiful the strategy, you should occasionally look at the results" - Winston Churchill
    28. Re:Time to Usable by Anonymous Coward · · Score: 0

      What's the problem in thrashing the hard drive? As long as your system responds quickly it's not an issue. Prefetch does that but it doesn't hang your pc. Besides it will make your applications start more quickly.

    29. Re:Time to Usable by Reverand+Dave · · Score: 1

      That's why we do all our patching at night or on the weekends. In the case of some updates you may have delay when you boot up, but that is the price of keeping your environment up to date and secure.

      --
      I got here through a series of tubes
    30. Re:Time to Usable by grimmjeeper · · Score: 1, Insightful

      for Windows Vista and better, anyway.

      ... so it works on OS X?

      ...and Linux?

    31. Re:Time to Usable by ByOhTek · · Score: 1

      That's reasonable. Prior to using disk encryption where I had to be at the console to log in, I restarted my system when I left for the evening, and had no downtime (that affected me) from updates.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    32. Re:Time to Usable by bertok · · Score: 2

      Get an SSD.

      No amount of software tuning or tweaking is ever going to make 5ms random seek times magically disappear. Eliminating the last moving part still used to perform computation will.

    33. Re:Time to Usable by antdude · · Score: 1

      How about for XP SP3? Bootvis didn't give me much.

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    34. Re:Time to Usable by ArsonSmith · · Score: 1

      why not? Cant we align all the boot files so they isn't a random seek time and everything is streamed straight off the disk linearly? Of course this would have to be changed whenever a boot option changes, but that shouldn't be to bad.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    35. Re:Time to Usable by Anonymous Coward · · Score: 0

      If he is using vista he could be seeing that behavior. I had a laptop with 8 gig of memory and a decent 7200rpm drive. Time to usuable desktop 10-15 mins.

      Finaly figured it out. It was the system cache loader. It was hosing down the disk for 10 mins straight while it filled up the memory for any file I had sorta touched... Well ever. That ISO you downloaded last year and opened once SURE load that bad boy up into memory. Every picture you ever took load em up. Every mp3 you own load it up. It wasnt even loading the whole file but large portions of them. Turned it off finaly and could get a usuable desktop in 1-2 mins.

      Win 7 is better about it with time to usuable desktop in the 1-2 min range on the same hardware. Dont bother turning that service off anymore.

      Also 'readyboost' was a waste of time. It blows away the file on the usb drive on every reboot. So during normal usage it was somewhat faster (not much). But during boot when I could have used it the most it was taking 2-5 mins just to copy files to the USB drive. Making time to desktop even worse.

      I *RARELY* have to scratch out an OS install. If you have to do that 'on an regular basis' you are doing something wrong. As a scratch out rebuild takes 2-5 hours (depending on network). Plus all the time reinstalling all of your applications again.

      Win7 the 'speed' everyone was talking about was them fixing that preloader and the sytem indexer. The rest was really service pack sort of changes.

    36. Re:Time to Usable by Sniper98G · · Score: 1

      My current PC, with optimized 4th gen SSD on an SATA3 controller and windows 7, boots in 20sec. That is from pushing the power button to having a totaly usable machine. I am very happy with it and honestly don't think I would care if it was an faster. I push the button before I sit down and by the time I am seated and have my monitors turned on, it's ready.

    37. Re:Time to Usable by Miffe · · Score: 3, Interesting

      Take a look at e4rat. It reorders the files loaded at startup to be sequentially on disk.

    38. Re:Time to Usable by Anonymous Coward · · Score: 0

      Did you watch the demo? This is talking about time to a usable desktop.

    39. Re:Time to Usable by Colonel+Korn · · Score: 1

      And yet it happens on my parents Win7 machine with 4gbs of ram and a core 2 duo. It's unfortunately too hard to get them to switch to anything.

      Yet doesn't happen on my Atom + 2GB RAM netbook, which is fully useable 20 seconds after pushing the power button. In the ~20 Win7 boxes I use, not one has sluggishness after the desktop appears. Half of those even have junkware like Symantec Endpoint Protection, too.

      --
      "I zero-index my hamsters" - Willtor (147206)
    40. Re:Time to Usable by Anonymous Coward · · Score: 0

      But what does "solid state" have to do with moving parts? Solid state, at least when I was in school, simply refers to electrical conduction in a solid, as opposed to a vacuum, gas, plasma or liquid. Since hard drives are solid, and don't conduct electricity in a vacuum, gas, plasma or liquid, hard drives are solid state. That's why they're hard, you see. If "solid state" now means no moving parts, where are the moving parts in a vacuum tube? Do I need to make new labels for my vacuum tube circuits?

      Odd. No one calls those USB dongles "solid state drives", they just call them memory sticks or fobs. Why not just call it silicon storage, or chip drives? Why take a perfectly valid technical and overload it?

    41. Re:Time to Usable by rikkards · · Score: 2

      Yep and they even admitted that. That was one of the big complaints of Vista is that everything was slow so now they give you dribs and drabs to make you think it is faster

    42. Re:Time to Usable by woboyle · · Score: 2

      For any Windows system, the time to usable is (IMO) just about infinite...

      --
      Sometimes, real fast is almost as good as real-time.
    43. Re:Time to Usable by lobiusmoop · · Score: 1

      Heh, reminds me of the ending of Sales Guy vs Web Dude

      --
      "I bless every day that I continue to live, for every day is pure profit."
    44. Re:Time to Usable by JasterBobaMereel · · Score: 1

      The only measure that is wanted is time to a usable system...Time to login screen, unusable desktop etc is pointless

      But the real problem is that you are booting the system at all, if you are rebooting, it's because the driver model is poor and requires a rebbot, or your system is unstable, Windows is better than it was but still insists on reboots far too often, and many users still power cycle to solve problems

      If you are turning the system on then why is it not in hibernate/suspend rather than shut down?

      Most Linux systems, and Laptops simply don't care about this (although they are quite fast) since the solution it not to boot/reboot them ...

      --
      Puteulanus fenestra mortis
    45. Re:Time to Usable by PJ6 · · Score: 1

      Can we start talking about "Time to a Usable Desktop"? My laptop boots to a login prompt in 15 seconds, but after login it's another 2-5 minutes before it's done thrashing the hard drive. There are precious few (useful) tools available to track down everything the system is doing, and even fewer to help you improve the situation.

      Stop running McAffee.

    46. Re:Time to Usable by couchslug · · Score: 1

      "I *RARELY* have to scratch out an OS install. If you have to do that 'on an regular basis' you are doing something wrong. As a scratch out rebuild takes 2-5 hours (depending on network). Plus all the time reinstalling all of your applications again."

      I'm used to Ghosting my clean installs and saving images. No problem. Clonezilla works nicely too, and of course there's old-school dd. When I load a PC for someone else I either keep the clone or leave restore media inside the (desktop) case so I won't have to hunt it down. That makes a restore mostly "blue bar time" while I go do something else.

      There are so many imaging and offline update solutions now that it's easy to find one to suit your needs.

      I don't have to nuke my personal installs often, but most of those are snapshotted in Virtualbox (Ubuntu host) so that's REALLY painless! 8-P

      I don't reload Vista. I consider it my duty to replace it with something less annoying.

      --
      "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
    47. Re:Time to Usable by Anonymous Coward · · Score: 0

      That's what OS X does when you pull it out of hibernate. It takes a screenshot and applies a blur to it, and you get to stare at that while it pulls itself up.

    48. Re:Time to Usable by Anonymous Coward · · Score: 0

      The iOS boot spash screen is a silver apple, you nimrod.

    49. Re:Time to Usable by nabsltd · · Score: 1

      But the real problem is that you are booting the system at all, if you are rebooting, it's because the driver model is poor and requires a rebbot

      Every time I upgrade 90% of hardware drivers on my Linux system, it requires a reboot, since the new drivers are part of a new kernel. The next 7-9% only require me to log out (graphics drivers, etc.), but the effect on a desktop user is pretty much the same as a reboot...save everything and start over.

      Sure, there are ways like ksplice that allow in-memory kernel changes, but the reality is that driver changes mostly require a reboot, regardless of the OS.

      Now, if you want to complain about why patching a web browser, word processor, or some obscure shared library that isn't in use often requires a reboot on Windows, I'll be more than happy to agree with you.

    50. Re:Time to Usable by Anonymous Coward · · Score: 0

      Now if you are part of an enterprise domain, it seemingly takes even longer.

      And if you have a corporate standard image with policies etc pushed out on each boot....

      On a cold boot, I can wander off, make a cup of tea, come back and it may just be ready. On a request for a reboot after a system update (and why it has to reboot after a change is yet another gripe) I could walk into town, go to the supermarket, buy a box of biscuits, queue up at the checkout, walk back and still be waiting for a usable system.

      Strange that all that downtime x the number of users never really appears in TCO calculations -- I guess that's what meetings were invented for (so we'd have something to do without access to the IT infrastructure

      ...and people ask me why I prefer Linux !

      I would prefer an IT department that knew what they were doing, or they do the same crap if they switch you to Linux. This is clearly not well set up (speaking as a user of a 50.000+ PC corporate network with the full set of AD based management, policies and managed security - boot up and restart of Win7 laptop is pretty fast)

    51. Re:Time to Usable by PRMan · · Score: 1

      XP and higher already do this while your system is idling... And most defrag programs do it even better.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
    52. Re:Time to Usable by EdZ · · Score: 1

      Wait, are you seriously complaining that it turns off Selective Startup when you deselect Selective Startup? Just leave it on!

    53. Re:Time to Usable by perryizgr8 · · Score: 1

      this used to be a problem in win xp. but now, in win7, i can start working the second the desktop appears. and this is a low end machine (core i3, 2gb ram).

      --
      Wealth is the gift that keeps on giving.
    54. Re:Time to Usable by Anonymous Coward · · Score: 0

      Use xPerf, which is part of the Windows Performance Toolkit (found in the Windows SDK). GIS 'xPerf', and you will find plenty of blog articles outlining how to use the tool to measure boot performance.

      Most of the time, when the performance hit is after the logon prompt, it is either group policy, or bloated apps like anti-virus that are killing performance.

      A good tool to help optimize your boot time is autoruns by Sysinternals (now owned by Microsoft). This tool will show you all of the crap that automatically starts at boot, and allow you to disable them.

    55. Re:Time to Usable by the_B0fh · · Score: 1

      YOU LIE!

      Heh.

    56. Re:Time to Usable by firewrought · · Score: 2

      Take a screenshot of the desktop when the user selects shutdown. Throw up that screenshot as the boot splash screen. Presto - "booting" in just a second.

      I think you just invented iOS

      He just invented the Canon Cat. It was basically a 17 pound text editor that showed a screenshot of your current document about 1-2 seconds after turning it on (if I'm remembering Raskin's description correctly). Most users never noticed that it took about 10 seconds for the boot to finish and the screen to "unfreeze".

      --
      -1, Too Many Layers Of Abstraction
    57. Re:Time to Usable by fast+turtle · · Score: 2

      and I don't shut down at all. Yes my system goes into standby (s5 mode) using the hybrid Sleep/Hibernate feature so I never have to reboot the system. Of course I've also got a UPS connected with 30+mins of runtime for the occaisional outage. If it's longer then that, the system goes to sleep and uses the hybrid hybernate.

      What I like about the S5 sleep mode is the total power consumption of the system is no greater then when it's off. Yes there is a small parasitic demand but it is no greater then when the system is powered down because of the manner the PSU shuts down. That problem is related to the ATX 1.3 + specification that results in both the 12 & 5 volt rails always being powered.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    58. Re:Time to Usable by Spiridios · · Score: 1

      Yet doesn't happen on my Atom + 2GB RAM netbook, which is fully useable 20 seconds after pushing the power button. In the ~20 Win7 boxes I use, not one has sluggishness after the desktop appears. Half of those even have junkware like Symantec Endpoint Protection, too.

      And yet it happens on my 6 core 16 GB Win7 machine. Likely in my case it has to do with the many boot-time utils for all those tray icons. Unfortunately at this time I haven't bothered to figure out which can be gotten rid off without losing functionality that I actually use (synergy, gaming keyboard/mouse/gamepad software, etc). Doesn't stop me from cursing at Windows every time I have to wait 5 minutes from log-in to actually accomplish anything.

    59. Re:Time to Usable by omnichad · · Score: 1

      No, I'm saying that it's a band-aid. And it warns you on every boot that you're in Selective Startup last I knew.

    60. Re:Time to Usable by antdude · · Score: 1

      FYI for its details and results if anyone is interested on my super long startup:

      I used MS' old Bootvis v1.3.37.0 (is that the latest?). I am still confused what is pausing the long disk access and wait. I also notice this long disk access at XP's login screen before logging in so it is not the startup programs. If I am reading this analysis correctly, there are unknown drivers too. I also noticed if I wait a minute or more before logging in, then my desktop starts up fast. It's like prebuffering (prefetching?) or something?

      http://i.imgur.com/EEWXh.gif for the screen shot (had to hide Boot and Resume Activities since they showed nothing).

      Thank you in advance. :)

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    61. Re:Time to Usable by cerberusss · · Score: 1

      On a cold boot, I can wander off, make a cup of tea, come back and it may just be ready

      That's nothing! When I leave work, I reboot and when I show up the next morning, the hard drive LED is still warm!

      Of course, this leaves my login wide open, so I have resorted to various Dungeons&Dragons-like maze full of traps to get into my office.

      The dwarf from the helpdesk already got skewered by an animated skeleton. But that's the price you pay for security.

      --
      8 of 13 people found this answer helpful. Did you?
    62. Re:Time to Usable by Anonymous Coward · · Score: 0

      I love how Windows 7 tells me that all the trashing going on my HDD during boot is done by something called "System". So very useless.

    63. Re:Time to Usable by adisakp · · Score: 1

      Get an SSD.

      No amount of software tuning or tweaking is ever going to make 5ms random seek times magically disappear. Eliminating the last moving part still used to perform computation will.

      Yup... the biggest speedup I've experienced recently is an SSD. It provides and enormous bang-for-the-buck as long as you already have a decent CPU and memory. SSD's actually allow things like a virus scan to run in the backgroun without your computer turning as slow as molasses in January.

    64. Re:Time to Usable by Anonymous Coward · · Score: 0

      5ms is extremely low for large HDDs. It's more like 9-15ms.

    65. Re:Time to Usable by Man+Eating+Duck · · Score: 1

      we'd still lose much more time to restroom or cigarette breaks (and in the later case, most people here don't even smoke).

      Somewhat OT, but short and relatively frequent breaks are good whether you smoke or not. Where I work most employees and managers, including the non-smokers, join in on "smoking" breaks about every 90 minutes. Actually, in my country the law gives you the right to a five minute break per hour if your main working tool is a computer or if your work is very repetititive.

      With breaks you are less prone to fatigue which increases productivity towards the end of the day. It leads to a better work environment when employees can chat and get to know each other better. Employees don't feel dogged, and are happier. In my experience, if your work involves problem solving (like coding) a short break can take your mind off a tricky problem for a while and lets your subconscious work on it, I frequently have Eureka moments when on a break and not actively thinking about whatever issue I'm tackling. We'll often discuss work on the breaks, effectively having a mini-meeting, and often get valuable input from others who isn't directly involved with our particular project. Win all around.

      Of course, if you only allow explicit smoking breaks for smokers you are an idiot, it makes no sense to punish someone for not smoking.

      As for productivity it varies hugely between employees anyway, a good moment was when a somewhat grumpy (incidentally a non-smoker) co-worker complained at lunch that us bastards (which included a lot of non-smoking bastards) "were outside half the time" leaving him to "do all the work". My boss' reply? "They actually carry *your* load since they get a lot more done on an individual basis (this was no secret to anyone). Maybe you need to put in that little extra time. Or you could shut up and join us".

      If I was informed at a workplace that short breaks were not allowed I'd be sceptical to their ability to treat employees in general.

      --
      Are you a grammar Nazi? I'm trying to improve my English; please correct my errors! :)
    66. Re:Time to Usable by Man+Eating+Duck · · Score: 1

      repetititive

      Oh goddamnit.

      --
      Are you a grammar Nazi? I'm trying to improve my English; please correct my errors! :)
    67. Re:Time to Usable by Man+Eating+Duck · · Score: 1

      This tool will give you a look into exactly what is going on during boot and what is hogging disk, CPU, and everything. It is very detailed.

      That seems interesting, thanks for the link. Mailed to myself to check out at work come Monday :)

      On a side note we've found that a very efficient way of reviving a somewhat slow computer (boot and in general) is to throw in a small, cheap SSD for the OS. The increase in speed and responsiveness is amazing. You don't even need to reinstall, just dd the system partitions to the new disk.

      --
      Are you a grammar Nazi? I'm trying to improve my English; please correct my errors! :)
    68. Re:Time to Usable by Anonymous Coward · · Score: 0

      I don't know. My usable desktop boots in about 17 seconds... But I'm not a Microsoft Windows fanatic...nor Mac OS x.

    69. Re:Time to Usable by EdZ · · Score: 1

      There's a checkbox to suppress the dialogue box for subsequent boots. And said 'band-aid' has been my default mode of booting for the last few years without issue. I can't see any argument against using it other than that it isn't labelled "Other Normal Startup".

    70. Re:Time to Usable by Dails · · Score: 1

      I'm a naval officer, so my workplace is a ship integrated with all the relevant networks and systems of the US military. Stuff takes forever on the machines on the ship, but it's a different network environment than a typical corporate setup, I imagine. Our networks are under constant surveillance and attack all the time, so there are frequent patches (some which can't afford to be put off until a scheduled time), virtual machines, bootloaders, logins, logins within logins, lots of cross-system connections, etc. Add on top of all that the fact that at sea all of the bandwidth is satcom and a good chunk of it is encrypted and you have a giant tangle of a network to work with. This is something all modern navies deal with, so while I empathize with the general populace and agree that it's silly, it could be worse.

      Oh, also, if it is an IT mismanagement you probably have the option of firing your IT staff and/or switching to another architecture. The good ol' US of A no longer has that option: http://www.wired.com/dangerroom/2010/08/hp-holds-navy-network-hostage/

    71. Re:Time to Usable by lsatenstein · · Score: 1

      In the older IBM mainframe days, particularly with MVS, MFT and with development under VM (Circa 1980), we could boot an operating system, have an address stop set by the virtual machine, and when the opsys hit the address and gave control to the human (system programmer), he did a savesys. Which is essentially a hibernate.

      Instead of taking 10 minutes to boot a system, it could be done in less than two. So, what we need in good old linux is a savesys concept. A concept we used in 1978+ until IBM sold the company on abandoning VM because it did not sell hardware and VM would stop having support.

      --
      Leslie Satenstein Montreal Quebec Canada
    72. Re:Time to Usable by Zorpheus · · Score: 1

      On my systems only the virus scanner is causing this. With virus scanner it takes ages until the system is finished booting up, without it is done short after logging in.

  2. so I can make a comment by lecheiron · · Score: 1

    in the 11 seconds or less

    1. Re:so I can make a comment by Anonymous Coward · · Score: 0

      If you really had it, maybe you'd have made first post.

  3. will they have a real reboot by mikeabbott420 · · Score: 1

    will they have a real reboot for when I inevitably need it

    having the same bolixed kernel coming back after a necessary reboot seems like it would be an pleasant experience

    --
    This program was made possible by a grant from the Ultra-Humanite, and viewers like you.
    1. Re:will they have a real reboot by clownface · · Score: 1

      RTFA: shutdown /s /full

    2. Re:will they have a real reboot by adonoman · · Score: 3, Informative

      RTFA and find out..

      Hint... The answer is yes. But note that they do re-intialize drivers even in the hybrid boot, so that takes care of a majority of kernel level issues

    3. Re:will they have a real reboot by CSHARP123 · · Score: 1

      They do have "Real reboot" option similar to Windows 7 cold boot using the UI or you can also do so from the command prompt shutdown /s /full / t 0 to effect an immediate full shutdown.

    4. Re:will they have a real reboot by mikeabbott420 · · Score: 1

      who has time to RTFA, complain and make excuses?
      not me so I picked my favorite two.

      --
      This program was made possible by a grant from the Ultra-Humanite, and viewers like you.
    5. Re:will they have a real reboot by neokushan · · Score: 1

      Shutdown/Startup are hybrid methods.
      Reboot works like it does today (i.e. is a FULL Shutdown/Restart).
      Hibernate works as it does today, only faster.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    6. Re:will they have a real reboot by Ex+Machina · · Score: 1

      If you need to actually reboot your machine, you can always run Windows Update.

  4. so the rootkit stays alive by Gunstick · · Score: 0

    best to have the rootkit reside inside the kernel so it's there forever. Clever system.

    --
    Atari rules... ermm... ruled.
    1. Re:so the rootkit stays alive by Haedrian · · Score: 1

      Didn't think about that. The hibernate file doesn't have any special permissions or encryptions or something does it?

    2. Re:so the rootkit stays alive by Thornburg · · Score: 3, Interesting

      Didn't think about that. The hibernate file doesn't have any special permissions or encryptions or something does it?

      It doesn't matter if the file is protected. If you can breach the kernel, and store your malware/rootkit/etc as part of the "session 0" data mentioned in the summary, then the OS will automatically save it all for you. No need to crack the file.

      However, the file does provide another vector for attack.

    3. Re:so the rootkit stays alive by Haedrian · · Score: 1

      Was more thinking of a program when asked to shutdown (not sure how windows works, but I assume there's a sigterm of some sort), writing the executable code into the file so it boots up on next load.

    4. Re:so the rootkit stays alive by neokushan · · Score: 2

      If you've got THAT much access to the system, you probably don't need to do anything fancy to keep it there. Besides, if the user does a restart, it'll wipe the hibernate file anyway.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    5. Re:so the rootkit stays alive by Wingman+5 · · Score: 1

      The file is erased and rewritten after everything outside of ring 0 has been terminated. So the only way to infect the hyberfil.sys would be have ring 0 write the infected file.

    6. Re:so the rootkit stays alive by Tarlus · · Score: 1

      A well-made rootkit will be there after a cold reboot as well.

      --
      /* No Comment */
    7. Re:so the rootkit stays alive by the_B0fh · · Score: 1

      Not really, think about penetration tests or bad guy walking by while your laptop is "hibernating". "boot to USB", infect hibernate file, walk away.

      And depending on how you restart, it won't wipe the hibernate file.

      or worse yet, it writes to some sectors of the hidden partition that is not in use... and then just hook to it in the hibernate image.

    8. Re:so the rootkit stays alive by Anonymous Coward · · Score: 0

      "Session 0" may not be the same as "Ring 0".

      This might mean basic services and whatnot that usually sit idle / get paged out anyway.

  5. Who cares about the technical details by jefferies · · Score: 1

    As usual the computer scientist spends about 95% of the time talking about the technical details of how this feature is achieved, and 5% talking about why the user would actually want to use it. Seems like waiting 4 minutes and 15 second for your computer to start are two pretty different options. There is definitely room for a middle ground, 30-70% less than the maximum.

    1. Re:Who cares about the technical details by reashlin · · Score: 1

      you must be new here

    2. Re:Who cares about the technical details by Anonymous Coward · · Score: 0

      I'm so sorry it hurts your brain thinking about technical issues. But its OK. There are plenty of stupid people like you in the world.

    3. Re:Who cares about the technical details by Anonymous Coward · · Score: 0

      This *is* the middle ground. Suspend to ram is the fast one.

  6. Mac by Anonymous Coward · · Score: 0

    So,, they are actually thinking of imitating MAC

    Should not be a feature they advertise but implement, who would chose between 10 second boot vs 35.

    Another feature looking a lot like the boost feature on old 486 tower when it had the boost option, who was stupid enough to leave it at slow?

    1. Re:Mac by Bobakitoo · · Score: 1

      Another feature looking a lot like the boost feature on old 486 tower when it had the boost option, who was stupid enough to leave it at slow?

      DOS didn't have gettimeofday(), games timing was base on cpu speed. I remember taking 'turbo' off to slow down a older games that was running too fast, or slow down a difficult game...

      But the same question can be asked today. If your cpu is know to be overclockable and stable, who is stupid enough to leave it at slow? Even today, there is reason to leave it at slow. More speed is not always the solution, sometime less speed is better and some other time less heat is better...

    2. Re:Mac by larry+bagina · · Score: 1

      Turning off the turbo button was for the sake of games that expected to run on a slower cpu.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    3. Re:Mac by BitZtream · · Score: 1

      So,, they are actually thinking of imitating MAC

      No, OSX doesnt' do anything like this. It just boots fast. No need to save the last boot and resume like this.

      And for reference, a full resume from hibernate on my Mac takes about 8 seconds, faster than a windows quick boot.

      Another feature looking a lot like the boost feature on old 486 tower when it had the boost option, who was stupid enough to leave it at slow?

      Anyone who had a reason to? So basically anyone who used an app that expected a specific CPU speed rather than looking at a real time clock or something like that to figure out how to do things at the proper speed. During that time, most things ran on bear hardware and assumed they had full CPU, so they could do things based on CPU timing. When the CPU timing suddenly changed, everything that had any sort of video or audio was horribly broken.

      The turbo button turned that off so things would run slower, more like the program was expecting. LOTS of people used it, you were just too busy putting your hands down your diapers to notice or remember.

      Way to totally not have any clue what you're talking about, go back to middle school and shut your pie hole.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    4. Re:Mac by mla_anderson · · Score: 1

      DOS didn't have gettimeofday(), games timing was base on cpu speed. I remember taking 'turbo' off to slow down a older games that was running too fast, or slow down a difficult game...

      I can't speak to the specific function (after all it's been 16 years already), but there were certainly more specific timers to be had in DOS than the CPU speed. The turbo button was primarily on the XTs running at 8 MHz to reduce them to the IBM standard of 4.77 MHz. When IBM XTs all ran at 4.77 MHz the use of loop based timing was common, Frogger comes to mind. By the time AT computers were common place loop based timing was mostly going the way of the dinosaur as it became evident that programs would be run on different speed machines.

      However, one place I worked had to keep buying pallets of 386 motherboards whenever they could even after 2000 because they ran their older data capture platform with loop based timers. Fortunately for the platform I worked on they hired some real programmers who knew better.

      --
      Sig is on vacation
    5. Re:Mac by Waffle+Iron · · Score: 1

      DOS didn't have gettimeofday()

      You didn't need gettimeofday() in DOS, because you could just use "in al, 40h" to directly read the (14.31818 / 12) MHz timer.

  7. This is fine and all... by Anonymous Coward · · Score: 0

    When are they going to come up with the technology that boots before I press the power button?

    1. Re:This is fine and all... by Anonymous Coward · · Score: 0

      In Soviet Russia......

  8. Fast Boot by mfh · · Score: 1

    Skip the loading of anything unimportant, full of bloated crapware? Sounds familiar...

    --
    The dangers of knowledge trigger emotional distress in human beings.
    1. Re:Fast Boot by Mashiki · · Score: 1

      Now all you need to do is get system builders like acer, hp, sony, etc, to stop piling their crapware in. Or you can build your own. To be honest my PC boots up into a ready state in about 18 seconds after post. A SSD helps a lot with that.

      --
      Om, nomnomnom...
  9. Relevant? by Grizzley9 · · Score: 1

    While a welcomed improvement to the 60 seconds or so that my current machine reboots in (I don't even know really), I'm not sure this even matters. Booting has never been one of the slow downs in my computer and shaving a few seconds off a boot, which is rarely done as my machine is hardly ever turned off, is not something I even care about them improving.

    But will this give corporate IT directors a reason to upgrade since they can count those few seconds as "saved" x the number of workers = profit! Even though in reality it won't make any difference.

    1. Re:Relevant? by Anonymous Coward · · Score: 0

      I use Arch Linux with 60GB Vertex2 SSD (gen1)
      and my boot time to login is 5 seconds. Time to full desktop so everything is booted is under 12 seconds. And I use KDE 4.7 and plain cold start without any hibernation or hybrid booting or sleep. With hybrid my boot time to same situation is 5 seconds.

      So windows has much to improve itself.

    2. Re:Relevant? by perryizgr8 · · Score: 1

      it infuriates me when most of my friends don't use sleep or hibernate. instead they shut down _every_ time. and then wait ~2min next time they need to use their system. this approach will unknowingly force these people to hibernate, not shut down.

      --
      Wealth is the gift that keeps on giving.
    3. Re:Relevant? by UltraZelda64 · · Score: 1

      Hey, when I shut down my system, I also *shut down* my system. Sleep and hibernate both take too long, and I've given up on sleep years ago because it was so damn buggy. Aside from the bugginess, lost data (refusal to successfully leave sleep mode and get back up and running), etc., even when sleep mode *did* work, I got tired of things like the wireless card taking an additional 20-40 seconds to get up and running every time I wanted to use the machine. Hibernate has its own set of problems; it wastes massive amounts of hard drive space on machines with a good amount of memory, and these bits don't exactly get dumped back into memory in no time. Add to this the fact that you're not starting from scratch in either case, and as a result bugs and stability problems can occur.

      You also won't see me waiting for my system to boot to be able to use it, because it's left on 24/7. Only the monitor has been allowed to go to standby when the system is not in use for the last decade-plus. Other than that, I just keep the system locked.

      Bottom line, sleep mode and hibernation suck. I'll take a plain old reboot and shutdown any day. Maybe I'm old-fashioned, but hey... they work.

  10. BTDT by tibit · · Score: 2

    So they have done what LISP systems have been doing for two decades or more? It's a standard thing for a LISP environment to initialize the environment and store a core image of it to speed up startup. Same thing can be done for LISP applications, effectively giving you hibernation of individual apps in a clean state.

    --
    A successful API design takes a mixture of software design and pedagogy.
    1. Re:BTDT by AmberBlackCat · · Score: 1

      Or better yet, they're creating the same effect as people who log off before hibernating their computers.

  11. It's all about perception by Infiniti2000 · · Score: 1

    Some of you are missing the point. It's all about perception, not a usable desktop. If the user thinks or feels like his computer boots up in 10 seconds, then he's happier. Happier customers tends to mean more $. But, yeah, I'd like to know what exactly is available to do after 10 seconds. For example, how much longer to launch a browser and see the latest feed on /.?

    1. Re:It's all about perception by Sockatume · · Score: 1

      They tried "thinks or feels like his computer boots up in 10 seconds" in XP, what you got was people whining about how slow and chuggy Windows is (because it chugs like hell after you log in while it really finishes booting). I'm not sure that's a mistake they want to repeat.

      --
      No kidding!!! What do you say at this point?
    2. Re:It's all about perception by Cimexus · · Score: 2

      My Windows 7 already starts up in under 10 seconds anyway (SSD for the win). That's from the end of the BIOS to a fully responsive and usable desktop, too.

      Needless to say I don't use hibernate (or even sleep). I just power off and back on. It's stupidly quick on SSDs and will get faster in the future. I think once rotating platter HDDs start going the way of the dodo on all PCs rather than just enthusiasts' ones (which will be quite a while yet, admittedly, as they still lag in price/GB and some would also argue reliability stakes), the whole 'slow booting' problem (and need to use things like hibernation) will go along with it.

    3. Re:It's all about perception by JasterBobaMereel · · Score: 1

      SSD's are quoted now as $1 per GB
      1TB rotating metal drive ~ $60 That's $16 per GB

      At that price I will be adding more memory, and using the SSD as a pure boot drive, not for storage - That will stay as rotating metal for a while

      --
      Puteulanus fenestra mortis
    4. Re:It's all about perception by perryizgr8 · · Score: 1

      there's something wrong with your figures...

      --
      Wealth is the gift that keeps on giving.
    5. Re:It's all about perception by rollingcalf · · Score: 1

      "SSD's are quoted now as $1 per GB
      1TB rotating metal drive ~ $60 That's $16 per GB"

      $60 for a terabyte is 6 cents per GB.

      --
      ---------
      There is inferior bacteria on the interior of your posterior.
  12. Rebootinate proposed on Matthew Garrett's blog by Sits · · Score: 1
    1. Re:Rebootinate proposed on Matthew Garrett's blog by dirtyhippie · · Score: 1

      Doing a full reboot followed immediately by a suspend is nothing like this approach. What are you on about?

    2. Re:Rebootinate proposed on Matthew Garrett's blog by Anonymous Coward · · Score: 0

      Except for the part where is exactly the same on the other side of that operation. Stop focusing on the front end of the operation and realize the back end is exactly what MS is doing. Its the same but different.

    3. Re:Rebootinate proposed on Matthew Garrett's blog by dirtyhippie · · Score: 1

      citation needed.

  13. Re:Really? by Anonymous Coward · · Score: 0

    You Linux homosexuals really do my head in. Any post about Windows and you're all over it dribbling bile.

  14. I don't "get" it... by Anonymous Coward · · Score: 0

    Why would you switch your computer off in the first place, in the middle of the day?
    I mean yeah, when you go to bed, then the workstation can be switched off.
    But in the morning when you switch it on, you won't sit in front of it anyway, until you have said good morning to others and gotten yourself something to drink. (Or showered, eaten, etc for home computers.) Which is never less than 1-2 minutes, is it?
    And during the day, logging out and shutting it down would be stupid since you have your whole work session open, and closing and restoring that is just making yourself additional work.

    So why all that virtual wanking over boot times?
    Monkey see, monkey do? Imitation-mania again?

    If you want to save power, get yourself a very fast SSD or other non-volatile storage the size of your RAM, and let it save its hibernation file in there while powered off. Done.

  15. Nice, in theory... by Anonymous Coward · · Score: 0

    But the reality is that whenever you swap a hardware device resume from hibernation fails. Since I swap hardware quite often I have to instead select reboot and hit the power button when the system resets. The vast majority of users will never see this problem, or see it so infrequently that it will be a non-issue, but not having the option to disable this feature sucks.

  16. SSD by Anonymous Coward · · Score: 0

    Or, you could get yourself an SSD boot drive. I did so, and Windows boots in 14 seconds for me, and is usable immediately upon login, no waiting for everything to finish loading. I'll never go back!

  17. SSDs are a better overall solution by davros74 · · Score: 1

    My current Windows7 boots to login screen in about 8 seconds, and after logging in, it's about 2 seconds to useable desktop. Of course, this is on a new SF-2281 SSD, that pumps out about 511MB/sec read rate on SATA-III controller. If you want fast boot times, people these days should consider an SSD OS drive (120-240GB), and a spinning disk for everything else (data, games, photos, movies, etc). The SSD improves a lot of aspects of performance, much more than just the initial boot time. Of course, this fast-boot on an SSD should be darn near instantaneous start times - unless of course it's not possible to speed up that swirling MS windows logo on boot. (Is that the bootup time bottleneck? Heh.)

    With the memory footprint of something like Windows7 64-bit these days, a partial hibernation might be a good idea since full hibernation may require writing an 8GB or larger file to disk depending on how many applications are open. If you leave everything open and then hibernate, cold-booting might be faster, especially on an SSD OS drive.

    1. Re:SSDs are a better overall solution by jjjhs · · Score: 1

      I'm going to get an SSD when the price per GB is the same as HDD. I'm not going waste money just to boot Windows faster. My boot takes up to 30s to desktop, it isn't loaded with the crap that makes it significantly longer for other people even with newer systems.

    2. Re:SSDs are a better overall solution by Pope · · Score: 1

      Riiight. Because having Windows boot faster is *clearly* the only thing SSDs have going for them.

      --
      It doesn't mean much now, it's built for the future.
    3. Re:SSDs are a better overall solution by jawtheshark · · Score: 1

      Has Microsoft solved the problem that it's really friggin hard to separate user data and system data on a Windows Vista/7 installation? This is the best way I found to do it. On XP it was much easier to do and possible without a reinstallation.

      I might be overseeing something, but given the popularity of SSD, it should be two clicks on a live system to do this and a (normal, GUI selectable) option during a normal install.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    4. Re:SSDs are a better overall solution by davros74 · · Score: 1

      Then you're going to be waiting a while. Even before SSDs, there were obvious advantages to running more than one HDD in a system. Back when RAM was very expensive, it was usually worth it to have a second HDD just to hold the swap file.

      Tiered storage is done in Enterprise and no reason a similar approach cannot be done for the home user. You can easily get 2TB drives today cheap. You will not see SSDs there at the same price point for a while. The performance benefits of SSD are not really needed to bulk storing your DVD rips. Application loading, or any other application that tends to do lots of small random reads/writes will greatly benefit from an SSD.

      For me, the small (120GB-ish) SSD replaces my old stragegy since the mid-90s of using a smaller, more expensive 15K RPM SCSI disk as the primary boot drive, and a cheaper, larger, slower IDE or SATA disk for storage. These days even a 3-tier storage solution is very practical: fast SSD OS drive, larger SATA 7200pm HDD for data and games, and an external 2TB+ NAS for bulk storage, archiving, backups. I don't think $200 is unreasonable for a performance oriented drive. Trying to do a 15K RPM SAS for $200 is practically impossible (being that a good PCI-e SAS controller will probably be equal to or exceed the cost of a SATA-III SSD).

      I guess technically I have a 4-tiered system, since after getting the SSD, I didn't junk my 15K RPM SCSI drive. But since it's only 72GB, it was inadequate for Windows7 + Linux dual-boot. So SSD for OS, 15K RPM SCSI for user data, video editing/encoding, internal SATA 7200RPM for normal data, games, photos, etc, and then 2TB external NAS. High performance drives are always going to carry a price premium (15K SAS) - but on a modern day Sandy Bridge system (easily run at 4.5GHz), the old spinning HDD is really the bottleneck in the computer for almost all tasks - but yes, it's too expensive currently to replace ALL spinning HDD in a system with SSD. But I would contend that a $100 price premium for something that could quintuple your disk performance, is not a bad investment.

      If you are the type what wants just a single HDD in their system, then yes, SSDs (or any other performance oriented drive, e.g., 15KRPM SAS) will simply be too expensive if you want more than 100-300GB of storage in your system.

    5. Re:SSDs are a better overall solution by davros74 · · Score: 1

      It's not as nice as Linux or MacOS X, but you can change the "Location" of most directories under C:\Users\. You cannot relocate Application Data, unfortunately, but just about everything else (Documents, Downloads, Videos, Photos, Music, etc).

      My biggest annoyance with Windows7 and user storage so far is when downloading large files off the Internet. I have an Atom based NAS that can sustain about 85MB/sec transfer rate. When downloading something like a 4GB DVD ISO file, I choose to save it directly to the NAS, but Windows has this brain-dead idea that it should save it first to Temporary Internet Files (under c:\Users !!), and only THEN transfer it over the network to the NAS. When this temporary download area is on the SSD - that really irritates me! 4GBs of unnecessary writes, followed immediately by 4GB of deletes (hopefully, with TRIM, right)? Still, totally unnecessary since my NAS link is more than fast enough to handle downloading something off the Internet at about 1MB/sec.

      But I agree, since Windows 7 now clearly has all user data neatly tucked into C:\Users, it should not be much of a stretch to just support having \Users on a different drive, like E:\Users. But alas, that's not easy to do unless you think of it before you install Windows (there are hacks to move the entire Users directory, but it must be done during the installation - once Windows is installed, it is not possible to relocate the C:\Users folder).

    6. Re:SSDs are a better overall solution by jawtheshark · · Score: 1

      I know that. The problem is that formerly (under XP), you right clicked on "My Documents", declared a new location and everything was done. Now you need to do that for every folder manually. That's really bad design, the XP way was clean, efficient and pretty much 100% automatic (it did offer to copy all your data). Moving the folders out of "My Documents" was a really bad move in Vista/7. I do realize that the XP method was really just the user data and not the "rest" (settings, registry, etc...) but to most users that was what's really important. It also made it damn easy to backup the "important stuff".

      With my first experiences on 7, I hit on this hard, as I was used to do proper partitioning separating operating system, programs and user data. I never managed to do it as cleanly as on XP and had to settle for a mere user-data/everything-else separation.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    7. Re:SSDs are a better overall solution by 0123456 · · Score: 1

      Riiight. Because having Windows boot faster is *clearly* the only thing SSDs have going for them.

      For the average user, that is the only benefit they'll see. Particularly because they'll only be able to fit the OS on the SSD and their applications and data will have to live on a hard drive.

    8. Re:SSDs are a better overall solution by 0123456 · · Score: 1

      Back when RAM was very expensive, it was usually worth it to have a second HDD just to hold the swap file.

      Back when RAM was very expensive, people would buy external RAM drives just to hold the swap file.

      In 1990, 128MB of RAM for a VAX was a staggering amount of money, whereas 128MB in a box with a SCSI interface was about $50k.

    9. Re:SSDs are a better overall solution by davros74 · · Score: 1

      Totally agree. This inflexibility (and surprising disk space requirements - 25GB!) forced me to scrap my 15K RPM SCSI drive as my boot drive when I upgraded my computer to a Core i7. I typically had my OSes partitioned onto the 72GB SCSI disk, and had applications on another, and user data on yet another HDD. But it was real clear early on that splitting a 72GB drive between Windows 7 and Linux was going to be too small, especially if I couldn't get ALL the user data off of C:\. Since applications' load times would benefit from an SSD, I finally caved a little and got the 120GB SSD and let windows and all its applications just go to C:\, and then went through the agreeably painful process or relocating every folder that has a "Location" tab to another disk. There's about 10 or so directories to relocate in Windows 7, per user, rather than just one "My Documents" as in XP.

      On the linux side, root is on the SSD, /var is on 15K RPM SCSI, /opt and /home on my SATA 7200pm disk (750GB), and /tmp on tmpfs (16GB RAM!). It's not that hard to properly partition for performance and ease of backup on the linux side. But my Windows7 partition is just a muck of everything so I guess if I want to back Windows up, just have to concede I have to create a 30GB partition image file or larger, just because everything is all thrown into C:\. On linux, I backup user data with rsync to external drives, and make parition images of the root and boot drives so that recovering on a new bare metal drive is really fast (just restore the partition image, then boot). Then create a new /home partition and rsync the data back. The partition images are small enough to put on a USB stick or DVD-R. But my Windows7 image has to stay on the NAS until I get a BDXL burner!!!

    10. Re:SSDs are a better overall solution by Tarlus · · Score: 1

      but Windows has this brain-dead idea that it should save it first to Temporary Internet Files (under c:\Users !!), and only THEN transfer it over the network to the NAS

      Using IE to download the files?

      --
      /* No Comment */
    11. Re:SSDs are a better overall solution by jawtheshark · · Score: 1

      On Linux it's easy... Very easy. My moms desktop (Linux, yes, I know) had a dying 500GB disk... or that's what SMART claimed. Due to lack of time, I decided to do several small steps in order to avoid data loss, and minimize downtime. First move her data to another 500GB SATA disk I had lying around (I first tried to make an image of the original disk, but that failed) and mounted that disk at /home. The system itself remained on the failing disk, but her data would be safe. (Step 1, not much work). Then I took a 160GB SATA disk I had lying around, installed Linux on it using a different computer so I could do it at my leisure at home. She was running 32-bit Linux, so I took the opportunity to upgrade to 64-bit. Then I swapped the defective disk with the 160GB disk, made sure her data disk was mounted correctly and presto! Working system. (Step 2. It was quite some work, but the percieved work for my mom was pretty much the disk swap). Now, the last step will be to buy a 16GB SDD, move the system from the 160GB disk (How much does a typical Linux installation take? 4GB max?) to that 16GB SSD. I'm not there yet, because I usually pool some tech purchases together in order to save money on shipping.

      While I did have some work, I managed to keep the downtime for my moms machine very low. I don't imagine I could have done anything similar with Windows (I might be wrong of course).

      I'm no big fan of Windows 7, and when I bring up the pain of program/data separation, I usually get slammed. (Do note there are other problems... It's not the only gripe I have with 7) Reactions typically are: Who partitions these days? Why bother... etc... Well this is why one bothers and the SSD problem just emphasizes the problem. Glad I found someone who thinks at least likewise on these issues.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    12. Re:SSDs are a better overall solution by operagost · · Score: 1

      Back when RAM was very expensive, people would buy external RAM drives just to hold the swap file.

      Those people had no business being anywhere near a computer system.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    13. Re:SSDs are a better overall solution by ColdWetDog · · Score: 1

      "Easy".

      I don't think that word means what you think it means.

      --
      Faster! Faster! Faster would be better!
    14. Re:SSDs are a better overall solution by jawtheshark · · Score: 1

      *grin* For the given task at hand and the given time I had (which is why it was important to do it in small steps, and where preparation could be done when time was at hand), I'd call it "easy". So, how would you have done it? In an easier way, moving the important data as quickly as possible from the failing disk and with the same (or less) downtime? I'm listening.... The end result must be the same: data disk spinning, system disk SSD and upgraded from 32-bit to 64-bit.

      Bonus points for a solution involving Windows 7. Keep in mind that making an image of the disk wasn't possible any more.

      As said, I'm listening.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    15. Re:SSDs are a better overall solution by davros74 · · Score: 1

      but Windows has this brain-dead idea that it should save it first to Temporary Internet Files (under c:\Users !!), and only THEN transfer it over the network to the NAS

      Using IE to download the files?

      You give me hope. Are you saying this is just stupid IE behavior, not Windows7? Then good, I haven't gotten around to installing Firefox yet. I had to use IE on the initial install to download motherboard drivers (obviously not the Intel NIC drivers), video drivers and such (and the 64-bit slackware 13.37 iso). So as soon as I get Firefox installed I can avoid that nonsense. Of course, these days, what version of Firefox to install? 3.6? 4? 5? 6? Yeesh. That's a whole 'nother debate. Heh.

    16. Re:SSDs are a better overall solution by Anonymous Coward · · Score: 0

      Faronics, the developer of Deep Freeze, had an utility called Data Igloo that would allow you to move the user profiles. I'm not seeing it currently on their site, but they have a user guide for the product - http://www.faronics.com/assets/IGS_Manual.pdf

    17. Re:SSDs are a better overall solution by Anonymous Coward · · Score: 0

      Windows 7 supports symbolic links (http://www.windows7home.net/how-to-create-symbolic-link-in-windows-7/ presents a how-to). Installing Windows on an SSD with certain select directories (like Download and the steam directory) redirected to a second drive has worked very well for me.

      You might be able to boot into a rescue command prompt using the install DVD and redirect C:\Users with your OS drive offline.

  18. Always with the Fast Boot... by S810 · · Score: 1

    It seems that every version of Windows has promised a "Fast Boot-up Mode". I wonder if this one will actually deliver on its age old promise.

    --
    "I think you know what I'm talkin' about, Mr. President; We're gonna kill us a mummy!" - Bruce Campbell as Elvis Presley
    1. Re:Always with the Fast Boot... by jawtheshark · · Score: 1

      Broken Promises. Cracks me up every time I see it, and I'm not a Mac user.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
  19. tux on ice by wirelesslayers · · Score: 1

    TuxOnIce do a pretty good job for me, takes like 10s ~ 12s. laptop specs are: core i3, sata HD and 4gb ddr3.

  20. Re:And it took them *this* long... by Gription · · Score: 1

    Your thinking of it backwards. It isn't so much that they, "figured this out". It is more of a case of, "We are stacking the cards this much higher".

  21. Re:And it took them *this* long... by bemymonkey · · Score: 2

    They didn't really figure out anything new - it's more like they're forcing a half hibernate on people who'd usually just shut down or reboot.

    For those of us who already use the available sleep/standby states or hibernate, the difference will be unnoticeable, because the reboots we perform (i.e. after software or driver installation, or after Windows updates) will probably still require the full shutdown we've come to know and loathe. :(

  22. Re:And it took them *this* long... by ByOhTek · · Score: 1

    Actually, faster than hibernate, slower than sleep/wake (without the power trickle requirements). Unlike either, you don't keep a lot of application states.
    Faster than a standard start from shut down.

    For people that don't hibernate/sleep their systems, it will probably be nice.

    --
    Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
  23. Re:And it took them *this* long... by neokushan · · Score: 2

    If you read the article, the hybrid booting is only part of the upgrade.

    It’s faster because resuming the hibernated system session is comparatively less work than doing a full system initialization, but it’s also faster because we added a new multi-phase resume capability, which is able to use all of the cores in a multi-core system in parallel, to split the work of reading from the hiberfile and decompressing the contents. For those of you who prefer hibernating, this also results in faster resumes from hibernate as well.

    --
    +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
  24. They're breaking the only reliable fix!!! by Anonymous Coward · · Score: 1

    This makes me think that the universal fix-all solution to Windows problems - rebooting - will cease to work!

  25. Why are people not using hibernate? by jader3rd · · Score: 1

    That's so strange that people aren't using hibernate. That's mostly all I ever do. I still know some people who think that hibernate will draw battery power and don't use it. I also notice that it's the default button in the Windows 7 start menu, when really hibernate should be the default. Perhaps if the UI explained it better that hibernate wouldn't draw any power more people would use it. I never want a "fresh state", generally the only thing forcing me to lose my user session state is patch Tuesday.

    1. Re:Why are people not using hibernate? by 0123456 · · Score: 1

      1. Wastes 6GB of disk space on my laptop which often has 2GB or less free.
      2. Who wants to keep running Windows for months accumulating Windows Crud?
      3. My old Windows laptop would lose its wireless LAN every once in a while and had to be rebooted to recover.

    2. Re:Why are people not using hibernate? by Osgeld · · Score: 0

      4. windows does not always wake up, vista and 7 will try to recover the first few reboots then freak out. your steam account thinks its installed on a new machine

      5. post bios windows 7 only takes a few seconds to boot anyway, use msconfig if otherwise, you do not need 178 updaters running 24/7

    3. Re:Why are people not using hibernate? by jader3rd · · Score: 1

      1. Wastes 6GB of disk space on my laptop which often has 2GB or less free. 2. Who wants to keep running Windows for months accumulating Windows Crud? 3. My old Windows laptop would lose its wireless LAN every once in a while and had to be rebooted to recover.

      I'll give you point 1, if you're on an SSD. Do you think clearing off some files might be worth the faster start up times? I haven't experience point 2 in about a decade, so that might be something you're chosing to run on your Windows computers. For point three, every once in a while means you should hibernate by default. If the problem is the device reset the device, not the whole computer.

    4. Re:Why are people not using hibernate? by 0123456 · · Score: 1

      Yeah, I forgot the 'Sorry, I don't feel like getting up today' bug.

    5. Re:Why are people not using hibernate? by shutdown+-p+now · · Score: 1

      Have you ever tried hibernating a machine with 12Gb of RAM? It takes ages to dump that to disk.

  26. Hmm by Anonymous Coward · · Score: 0

    Sounds like it will be great for persistent ring0 rootkits that don't require a physical file to exist.

  27. Re:And it took them *this* long... by bemymonkey · · Score: 1

    "For people that don't hibernate/sleep their systems, it will probably be nice."

    Of course - still sucks for the rest of us though :p

    I was hoping for an *actual* speed-up in the full boot process :(

  28. Re:And it took them *this* long... by bemymonkey · · Score: 1

    Also results in faster resumes from hibernate as well... at least in systems which are CPU-limited (as opposed to IO-limited) when coming out of hibernate.

    Those with SSDs are on the safe side, I suppose.

  29. Boot time isn't Window's problem by grimmjeeper · · Score: 3, Interesting

    The biggest problem I have when running Windows, especially in a corporate environment, is all of the crapware that doesn't start until I log in. Those are the programs that decide to do massive tasks as soon as they're started. They bog down the network connection and thrash the hard drive doing their startup scans. They make the desktop completely unusable for significant lengths of time after login.

    I suppose the fast boot to a login screen is useful. I'm able to get to the login screen quickly and log in. Then I can go get my coffee and read the paper while the startup applications take forever to do whatever it is they are doing. But it still doesn't solve the core problem of having a computer that is up and useful to the end user in a reasonable amount of time.

    Now, it should be obvious that the blame here is not entirely on Microsoft. They have no control over what crap the end user (or corporate IT monkeys) install on the desktop. They can't control what gets started up when the user logs in. Microsoft has no way to prevent an idiot from writing an anti-virus package that does a complete system scan (that bogs down the entire system while it's running) when it is first started by the user. There's nothing stopping a startup program from waiting for a slow network connection to time out, causing the entire startup process to basically hang. There's nothing Microsoft can do to prevent a program to rebuild it's entire search index at startup, thrashing the disk to the point where the entire system is unresponsive while it's running.

    But Microsoft is not entirely blameless either. The root of the problem was the decision to make the console the central focus of operation.There is absolutely no reason why so much of the software has to start up as soon as the user logs in. There is no reason why it cannot be tied to the startup of the computer. And if that software was tied to computer startup there would be no reason it could not be identified for hibernation just like the kernel, resulting in not only a faster boot time but a faster time to actual usefulness of the desktop.

    1. Re:Boot time isn't Window's problem by Anonymous Coward · · Score: 0

      WinPatrol's delayed start-up is your friend. I'm not sure how much it'd help with the scans (the IT "monkeys" will probably get mad if you kill the scans entirely) but I've noticed that the general start-up stuff isn't so bad if you delay half of it for about 30 seconds or so.

      Of course, you could always just get more RAM. You'd be surprised at the number of things you can run at the same time with 8 GB of RAM (at least if you only just upgraded from 2 GB).

    2. Re:Boot time isn't Window's problem by bertok · · Score: 1

      Now, it should be obvious that the blame here is not entirely on Microsoft.

      It's got nothing to do with Microsoft, and everything to do with using mechanical drives. Upgrade to an SSD, and your problems will vanish.

    3. Re:Boot time isn't Window's problem by Anonymous Coward · · Score: 0

      Microsoft has no way to prevent an idiot from writing an anti-virus package that does a complete system scan (that bogs down the entire system while it's running) when it is first started by the user.

      I haven't used Windows in a long time now, but I find it hard to believe that it doesn't feature the equivalent of renice and ionice (ie. lowering the priority to cpu and disk timeshare for tasks that are supposed to do "background" stuff), or that the startup sequence would allow one if its tasks to block off everything else. And if Windows 7 doesn't currently prioritize getting to a usable desktop over everything else then there's always room for improvement. Which is probably exactly what W8 will try to achieve (one can hope).

    4. Re:Boot time isn't Window's problem by grimmjeeper · · Score: 2

      Now, it should be obvious that the blame here is not entirely on Microsoft.

      It's got nothing to do with Microsoft, and everything to do with using mechanical drives. Upgrade to an SSD, and your problems will vanish.

      Right, because it's so practical to replace my 9TB RAID array with SSDs...

    5. Re:Boot time isn't Window's problem by Anonymous Coward · · Score: 0

      Windows 7 was the first OS I've used where the hibernate feature was both reliable and robust enough to use. Usually, you end up with extremly bad data corruption errors as the error checking isn't what it should be on the hardware or on the software; the combination of a serialized bus (PCI-E) and more sane driver setup for win7 (WHQL required or certain features are disabled) has made that possible. I've actually left VM's running for several days straight on my desktop, go to check my e-mail via the start menu icons, and then notice "oh vmware is running, hey the VM is still running...cool!". I've had exactly 1 instance where my machine came out of hibernate half-cocked. Mind you though, I've got a RAID0+1 array for my win7 install; takes it 5 seconds to get to desktop.

      Laptops are a different matter but the same rules apply.

      Everyone at where I work uses hibernate and half my job is tracking down problems with windows XP imploding due to it. If what they're talking about here is a rock-solid hibernate feature for laptops and desktops that works well under extreme loads, I'll be one happy monkey for sure.

    6. Re:Boot time isn't Window's problem by grimmjeeper · · Score: 1

      The problem, as I see it, is that there are half a dozen or more applications all trying to start at the same time. You can try to push them to lower priority but they're all trying to do their thing at the same time. You get several applications using the network and scanning the hard drives, even at a low priority, and your system bogs down to the point of uselessness. Without the ability to use a delayed start on my corporate machines, I can't stop even lower priority processes from overloading my computer for several minutes.

    7. Re:Boot time isn't Window's problem by grimmjeeper · · Score: 1

      I'd love to be able to use the hibernate feature on my systems. However, corporate policy is a little short sighted. Big surprise, I know. I have to log off the PC when I leave for the night. I have to leave the PC running. At any time outside of normal working hours, a corporate IT person is supposed to be able to remotely log in to perform maintenance or push upgrades to my system. If they can't get in, I get written up (which, if it happens enough, can result in an "involuntary career path adjustment" for me). So I have to log in each and every morning, waiting for all of the startup crapware to finish bogging down my system.

    8. Re:Boot time isn't Window's problem by davros74 · · Score: 2

      Don't replace the 9TB RAID, just add an SSD for Windows (120GB or so). Get two and RAID0 if you want and it's yet faster still (however, be warned that most likely RAID with SSDs will lose TRIM support).

      Keep the 9TB RAID array. My current motherboard (ASUS P8P67 Deluxe) has 4 SATA3G ports, 2 intel SATA6G ports (raid-able) and 2 Marvell SATA6G ports (raidable). 4 or 6 HDD systems are completely possible now without having to get an add on PCIe controller - assuming your case has room for the drives.

    9. Re:Boot time isn't Window's problem by grimmjeeper · · Score: 1

      That's all well and good but the problem is the anti-virus and other programs which insist on doing a full disc scan or index when they start up. They dig through the entire array every time I log in. And there's a lot of raw data there I use to do my work. I suppose the only real solution there is to put that array on a server somewhere and access it remotely from my desktop. That way I don't have to log in to the computer that has the array.

    10. Re:Boot time isn't Window's problem by jader3rd · · Score: 1

      Starting the Vista (http://blogs.msdn.com/b/oldnewthing/archive/2011/08/17/10196425.aspx) auto start applications were given lower priority.

    11. Re:Boot time isn't Window's problem by PJ6 · · Score: 1

      Amen to that.

      So many times I've worked with IT whose only priority is to minimize work. You get lazy compliance of security and other policy requirements, leading to machines configured with absolutely no regard to usability.

    12. Re:Boot time isn't Window's problem by Anonymous Coward · · Score: 0

      The Gold Standard is iPhone iPad performance. Before I get flamed.. They are pushing 512MB ram and 64GB disk... That is a valid amount to run older versions of windows on.

      Fact is that while Mac doesn't have as fast a "cold boot" time, most Mac users RARELY reboot except when Apple tells them. I go weeks between reboots on my 5-year old MacBook. Restart after Hibernate is under 30 seconds.. With Apps available where the left off... Even if the battery ran down!

    13. Re:Boot time isn't Window's problem by Billly+Gates · · Score: 1

      SSDs have a history of unreliability. THey die fast if you page a lot or if the disk is near full as then each sector gets written many times over again and there is a limit to the amount of writes.

      I wont replace them until they approach the reliability of mechanical drives. ... of course I do not have the luxury of tape backup or a nice automated backup service on my home pc or at work.

    14. Re:Boot time isn't Window's problem by Nysul · · Score: 1

      A program doesn't have to start up when you start up the computer, you can use task scheduler to start up or update programs at certain times of the day

    15. Re:Boot time isn't Window's problem by grimmjeeper · · Score: 1

      It does when corporate IT installs it on your computer and won't let you schedule it instead.

    16. Re:Boot time isn't Window's problem by Anonymous Coward · · Score: 0

      Actually, there is something Microsoft can and in fact did do. Since Vista, Windows has I/O priorities. Not yet at mainframe levels, but it's there. And startup applications are set to low I/O priority, so the user gets a more responsive desktop earlier. Rebuild an entire search index at startup? Sucks to use the search then; it's going to be a long wait until the background process gets it's I/Os'.

      An even more aggressive solution wold be to profile startups, and on the next boot prioritize the most efficient processes. I.e. slow apps are started last. Document this, and there would be a very clear initiative to properly optimize those startup apps.

    17. Re:Boot time isn't Window's problem by Anonymous Coward · · Score: 0

      Priority doesn't matter when it comes to disk I/O bandwidth issues (especially related to seek). I agree with you, but in reality it isn't as simple as it seems.

  30. Just like Google? by kurt555gs · · Score: 1

    My Samsung Chromebook has REALLY fast startup mode. All the time.

    --
    * Carthago Delenda Est *
    1. Re:Just like Google? by Anonymous Coward · · Score: 0

      So does my paper and pencil, and it's about as useful as your Chromebook.

    2. Re:Just like Google? by Shoe+Puppet · · Score: 1

      I'm shocked to hear even paper and pencil now require an internet connection.

      --
      (+1, Disagree)
  31. Back to the future? by Anonymous Coward · · Score: 0

    I still don't get how PC laptop users shutdown before closing the lid.

    I bought my first Mac 10 years ago now and have been using Mac laptops ever since. All this time I just close the lid and it goes to sleep and when I open the lid it's there waiting for me to type my password in to unlock it.

    The only time I reboot is when Software Update demands it, which is a few times a year.

    Why is it that after all this time, the IBM PC industry still can't get its act together with regards to sleep? I've never had one that would do it properly like the Macs do.

    1. Re:Back to the future? by grimmjeeper · · Score: 1

      It's not that users can't hibernate when they "shut down" for the day. It's that the common solution for solving so many problems in Windows is a reboot at least once a week. Users are so accustomed to this that they just shut down out of habit.

    2. Re:Back to the future? by emt377 · · Score: 1

      I bought my first Mac 10 years ago now and have been using Mac laptops ever since. All this time I just close the lid and it goes to sleep and when I open the lid it's there waiting for me to type my password in to unlock it.

      When you close the lid on OS X it turns off the screen, does a sync(), and starts hibernating remaining anonymous pages to disk. When you open again it resumes the in-memory state. If you let it sleep long enough for the battery to fully drain (I'd guess in a week or two) it will resume from the checkpointed state on disk.

      I rarely reboot my 2008 Mac Pro either, I always have a lot of state - multiple VMs etc - up and running so constantly rebooting it would be ridiculously tedious. Every few months it gets rebooted due to a software update, the rest of the time I just put it to sleep (cmd-opt-eject) when not using it. It spins down and puts my external raid unit to sleep as well.

      IMO more benchmarks should measure user-experience response. For instance, the time from when you open a laptop to when it's connected to a local wifi network and ready to use. I'd guess that's 2-3 seconds for a modern MacBook Pro. Maybe 10 seconds if allowed to completely drain, but that depends on memory size and how much it had to checkpoint. On my Mac Pro the slowest factor is actually the two Dell WFP3008 displays I use as my main desktop; they take about 7 seconds to come on from DisplayPort wake. (My old 24" Apple Cinema display from 2004 comes on immediately though, but it's over on a different table and I usually put VMs on it full screen with a separate keyboard and mouse. Ubuntu, CentOS, WinXP, or Win7 depending on what I'm doing.)

    3. Re:Back to the future? by perryizgr8 · · Score: 1

      so you mean to say your mac behaves in the exact same fucking way every windows system has done since xp?

      --
      Wealth is the gift that keeps on giving.
    4. Re:Back to the future? by Anonymous Coward · · Score: 0

      Why do you have to be so rude? Let the little apple fanboy feel special. Only Apple products have the special magic that makes them work ! The magic is so awesome that he wants to pay twice the cost. Chinese made computers that are manufactured in the same foxconn factories that most major manufacturers use become special when you add a apple logo to them.

      Think of the children !

  32. Just moving the problem really by dingen · · Score: 1, Insightful

    So instead of waiting for the system to boot up, you now have to wait for the system to shut down (because it is writing the files required for fast booting). What an innovation!

    --
    Pretty good is actually pretty bad.
    1. Re:Just moving the problem really by Pionar · · Score: 1

      Reminds me of the scene in Office Space where Peter's trying to duck out before the boss sees him and has to wait for all the processes to finish saving state.

    2. Re:Just moving the problem really by Sockatume · · Score: 2

      Not really, because unlike a real hibernation it's not writing the whole RAM contents to disk. The idea is that you skip a whole lot of reinitialisation of the OS that isn't really necessary.

      --
      No kidding!!! What do you say at this point?
    3. Re:Just moving the problem really by dnewt · · Score: 1

      So instead of waiting for the system to boot up, you now have to wait for the system to shut down (because it is writing the files required for fast booting). What an innovation!

      Well, generally when you're starting your computer up, you're waiting for it to get to a usable state so you can get some useful work (and I use the term loosely) done with it. When you're shutting down, you don't tend to care as much about how long it's going to take. Granted, there's still situations when you might care, but it's not like startup when you almost always do. If someone said to me, "I can make it so that your computer always starts up instantly. There's one catch though, it'll be added on to the time your computer takes to shut down." I'd say, "Sure, I'll take it!"

      Also, as others have pointed out, it's only a kernel image that's written to disk, which is considerably smaller than the usual hibernation file. I get the impression it won't take anywhere near as long.

    4. Re:Just moving the problem really by DeadboltX · · Score: 1

      If I am going to be turning off or hibernating a computer then chances are I am walking away from it, and don't care how long it takes to shut down.

    5. Re:Just moving the problem really by roc97007 · · Score: 1

      You already have to do this now with Windows XP hibernation. and it does take forever. I suspect Windows 8 merely renamed a misfeature they already had.

      What's really fun is if you close the lid while it's hibernating. Then in your next meeting, you open the lid, and (assuming you didn't get the dreaded "resume error" and lost everything) it resumes hibernating. What a feature! So all you have to do is to wait for it to finish resuming, and then you can do the "fast startup". Winning!!!!

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    6. Re:Just moving the problem really by ihavenospine · · Score: 1

      My users never "wait" for the computer to shutdown. They click shutdown and walk away, not caring much if the computer hangs before halting or not... On the other hand they complain more often about slow startup caused by roaming profiles and group policies. So any speed up in the boot/logon process is welcome.

    7. Re:Just moving the problem really by Anonymous Coward · · Score: 0

      Plus it isn't actually shutting down Session 0 so there's that...

    8. Re:Just moving the problem really by jargonburn · · Score: 1

      You're still using Windows XP? :-) I'm fairly certain the Windows 7 sets an internal flag while performing shutdown/restart/hibernate-style operations with the purpose being to prevent other power-saving states from being applied. I know it does this while installing updates. I think even Vista may do this, though I'm too lazy to fact-check...and besides, it's Vista..*ugh*

    9. Re:Just moving the problem really by roc97007 · · Score: 1

      > You're still using Windows XP? :-)

      Well, yeah. So are a lot of people...

      > I'm fairly certain the Windows 7 sets an internal flag while performing shutdown/restart/hibernate-style operations with the purpose being to prevent other power-saving states from being applied. I know it does this while installing updates. I think even Vista may do this, though I'm too lazy to fact-check...and besides, it's Vista..*ugh*

      The question I have to ask myself; are these features worth the $160 it'd take to upgrade? Probably not. So XP it is. Besides, XP works fine as a program loader.

      However, my daughter's (newer) laptop has Win 7 Pro installed, so it's worth a try to see if they fixed this.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    10. Re:Just moving the problem really by roc97007 · · Score: 1

      I have to add a side note: I could double the disk space in my workstation or switch my laptop to SSD for the price of a Win7 upgrade, and those things definitely take priority.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    11. Re:Just moving the problem really by Gib7 · · Score: 1

      You know that you can easily change the behaviour of closing the lid ? First thing I do when setting up a new notebook is setting the lid close behaviour to "do nothing". If I want to standby or power down, then it takes me an extra second or so to press the power button. Otherwise, I'm just closnig the lid to get to the cables behind the notebook, or so my boss doesn't see the screen, or because I'm carrying the notebook into the other room.

    12. Re:Just moving the problem really by roc97007 · · Score: 1

      Yes, I know, and I now have my notebook set to do that. It amused me to see how inept the default settings behaved in real world environment.

      But being what I would like to think of as a responsible IT person, I try to see it from the user standpoint, not the uber-geek standpoint. Those settings (and "mandatory customization" settings in general) are often difficult for the non-technical to find. You know the people -- the ones with work to do, who don't necessarily know or want to know or have a job that requires knowing administrative minutia of their laptop, which is after all ONLY A TOOL to get their ACTUAL work done, which doesn't include doing their own wintel administration.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  33. Reality, the theory by Lexx+Greatrex · · Score: 2

    When I was young my dad and I built a go-kart that used the power train straight out of my grandmother's electric wheelchair. It was fast and looked cool and for a time I felt like the Alain Prost of my entire neighborhood. There was one small problem though... my grandmother was still using her wheelchair at the time. So when she wanted to go out, we would put the battery and motor back in the wheelchair and when I wanted to use the kart we would swap it back. It took about twenty minutes and since she only went out once or twice a week, it wasn't too much of a hassle (for me at least.) It is at this point in the story that my mother pointed out something so ridiculously obvious that it would probably baffle, disorient and possibly even permanently educate Microsoft kernel developers... you know who you are... you have been warned...

    My dad, being an enthusiastic amateur engineer improved the swap out time by mounting the whole assembly to a bracket that we could take out of one and bolt into the other in under ten minutes. I remember him and me being excessively proud of this rapid start up time. But then my mother dropped a bombshell that changed the face of go-kart engineering in our household forever. She suggested that we use the DC motor and battery pack from the Flymo lawnmower that sat gathering dust in the garden shed because my Dad hated using it. The mower motor and battery were both lighter and with a bit of gearing, the kart was faster than ever. I was happy, granny was happy, dad was happy and the startup time was reduced from ten minutes to zero seconds.

    1. Re:Reality, the theory by roc97007 · · Score: 1

      That's it exactly. Redesign, not reuse. Microsoft will never get it.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    2. Re:Reality, the theory by im_thatoneguy · · Score: 2, Informative

      I'm confused, are you recommending we buy a second computer to use while booting our primary one?

      Story fail.

    3. Re:Reality, the theory by Lexx+Greatrex · · Score: 1

      I draw no conclusion in my story. It is your comprehension or lack thereof that leads you to draw a conclusion that you think is "fail"; so ... if you send me your microsoft.com email address, I can send though some kernel design ideas....

    4. Re:Reality, the theory by Anonymous Coward · · Score: 0

      Reading through your story it is immediately obvious that..

      1) you are stupid

      2) you are stupid because your family is stupid

      3) your opinion isn't worth anything because you haven't done anything in your life that makes it worth anything.

      But please .. for the love of god, atleast make your anti-ms troll comments somewhat entertaining. Its the least you can do ..

  34. Malware friendly by Anonymous Coward · · Score: 0

    Great. This means Windows becomes even more convenient for malware. Now malware writers don't have to worry about trying to hijack registry entries and squirrel away executables in obscure locations to restart on system reboot. Windows does this for them.

    1. Re:Malware friendly by grimmjeeper · · Score: 1

      Seems to me that the file is written only after all user applications have shut down and you're left with only ring 0 operation. Then when you start up, the entire file is loaded before ring 0 starts any user space applications. I'm pretty sure the operating system won't even keep a copy around once the boot process is over, and even if they did they'll overwrite whatever you do to it. So in order to manipulate the file, the malware has to have access to ring 0 already. And if that's the case, I think you have more important problems to worry about.

  35. That's worse than Windows XP by Anonymous Coward · · Score: 1

    Windows XP can wake up from hibernation in that time, and then your computer is pretty much directly usable.
    But Windows 8 will have to still load the user session - so you get less functionality, in more time. Hip hip.

  36. Re:And it took them *this* long... by neokushan · · Score: 1

    Not necessarily. Annoyingly, they almost glance over this point, but if we read it carefully -

    which is able to use all of the cores in a multi-core system in parallel, to split the work of reading from the hiberfile and decompressing the contents.

    This sounds more to me like they've implemented a sort of FIFO system that allows the contents of the file to be decompressed and loaded as it's still being read from disk. It also implies (but doesn't directly state) that the operation is CPU bound, even on typical mechanical hard drives. I'd believe this, as even a cheap, slow mechanical HDD is capable of read speeds of 50-80Mb/s, which probably takes longer than 1s for a single core CPU to decompress, parse and load.

    --
    +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
  37. S3? by Anonymous Coward · · Score: 0

    Just curious since most pcs dont go unused for that long anyhow, why not just do a S3 suspend? Juet a thought...

  38. Re:And it took them *this* long... by ByOhTek · · Score: 1

    It is irrelevant to the hibernate/sleep users, because those processes are almost completely hardware bottlenecked dependent.

    So, what you are saying, is it sucks for people who are dealing with hardware bottlenecked options, that the software won't fix it???

    You should be looking for someone other than an OS vendor to fix that issue.

    --
    Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
  39. Re:And it took them *this* long... by adonoman · · Score: 1

    They're doing that too in the form of intializing devices in parallel.

  40. How about a fast shut down mode by sproketboy · · Score: 1

    How about a fast shut down mode like I have with my Mac? Also, can we kill the damn install updates on shutdown "feature"?

    1. Re:How about a fast shut down mode by JustAnotherIdiot · · Score: 1

      Windows has a fast shut down, it's called pulling the power.

      --
      What do I know, I'm just an idiot, right?
    2. Re:How about a fast shut down mode by tycoex · · Score: 1

      Before I installed Ubuntu on my laptop it had Vista on it. I had to hold down the power button to shut down the computer because if I tried to shut it down properly it would hang on the "shutting down" screen for 15+ minutes.

    3. Re:How about a fast shut down mode by JustAnotherIdiot · · Score: 1

      1. It was a joke, sorry you didn't catch that.
      2. The laptop equivalent of pulling a power cord would be to yank the battery.

      --
      What do I know, I'm just an idiot, right?
    4. Re:How about a fast shut down mode by tycoex · · Score: 1

      I know it was a joke I was just throwing in a real world experience where I actually had to do that.

      Holding down the power button is equivalent to pulling the plug in newer computers.

    5. Re:How about a fast shut down mode by sproketboy · · Score: 1

      LOL

  41. Re:And it took them *this* long... by bemymonkey · · Score: 1

    Is decompressing data that much work? I'd assume modern CPUs (say, starting from Athlon X2 or Core Duo) are more than capable of handling the amount of data a hard drive can pump out sequentially... hell, these are processors that benchmark at 100MB/s+ for encrypting AES. Shouldn't reading and decompressing the page file be much less CPU-bound?

  42. Re:And it took them *this* long... by bemymonkey · · Score: 1

    No no, you misunderstand - my devices sleep and hibernate just fine. It's just that I was hoping for improvements in the time it takes to perform a full reboot, like after Windows Updates or driver installation... :)

  43. Re:And it took them *this* long... by bemymonkey · · Score: 1

    Sounds good - but how big is the real-world performance gain? ;)

  44. The next hype for Windows 8 will be by Pop69 · · Score: 1

    "Easier And Faster! Your Productivity Will Double!"

    The same line they've trotted out with Windows 95 and every version since.

    Would it kill them to get some new copy or are they just going to keep regurgitating the same crap every release and watch their OEM monopoly on new computer installs sell it without any effort whatsoever ?

  45. Windows .. by Anonymous Coward · · Score: 0

    Yeah.. thats the ONLY explanation. I guess your brains capabilities are too limited to come up with anything new. How does it feel to be so stupid?

  46. Why do we reboot? by Anonymous Coward · · Score: 0

    The only reason I reboot a computer is because Windows has hosed itself somehow. If it's going to keep the same instance alive with this scheme, I lose the benefit of rebooting.

  47. A short review of Soluto. by bmo · · Score: 5, Insightful

    OK so I tried Soluto in a VM. I was curious and downloaded it.

    Granted that a VM is not a real machine, it shouldn't make any difference in this sort of software. But it does. The VM install of Windows is pretty spare. It has only a few programs that I actually fuck around with in Windows. It takes under 10 seconds to get to login and under 5 for the desktop to appear. So it's no slouch.

    1. Soluto's a pig. Oink Oink. It will not even install if you have less than 512MB of RAM, which a lot of people do if they're still running XP (which is a huge amount of people). This means typically 256 or 384MB or 512MB with "shared graphics memory" cutting it down. I know, people should upgrade, but this isn't some sort of 3D modeling program, it's just a startup trimmer and browser fixer.

    2. It's a sloth. It's slow as molasses in January. The install is slow and the interaction is slow. And its disk footprint is huge for what it does.

    3. It /insists/ on using flashy 3D graphics calls. I know that you have to please the drooling masses somehow, but this is one of the main causes of #2. In a VM it turns the interface /unusable/. I had flashbacks of Norton in the 9x days.

    In short, this program has loads of fat that should be cut off and thrown in the fire. It should reflect what it purportedly does - speed up your machine. This is not done by adding useless frippery.

    --
    BMO

    1. Re:A short review of Soluto. by firewrought · · Score: 1

      OK so I tried Soluto in a VM.

      Awesome... I had to friend you for that post.

      --
      -1, Too Many Layers Of Abstraction
  48. Re:A short review of Soluto. Follow up. by bmo · · Score: 3, Insightful

    What a passive-aggressive piece of shit.

    An animated frowny-face when I go to Install? And second guessing me?

    Fucking really?

    I'm sorry, but this is unacceptable in a utility software.

    There is a quality I see in good software. I call it 'neatness'. It's a tough quality to describe. Neat software does something useful, does it with aplomb, and has a simple, spare, self-descriptive interface that does not surprise the user in bad ways. But it's more than that. It's software that, when used, puts a smile on your face because of its elegance.

    Soluto is anything but that.

    --
    BMO

  49. Shutdown Speed by Anonymous Coward · · Score: 0

    Has anyone else thought about speeding up how long it takes for a computer to shut down?

    Back when I had Tiger installed on my MacBook, it would take about half a minute, not with Snow Leopard, it takes 2 seconds (when there are no programs running). On some laptops, you need to wait for the thing to shutdown before you can close the lid. My laptop would sometimes go into sleep mode if I shut the lid during power down.

    Not to mention it's nice to have something turn off almost instantly when you need it to.

  50. I know this one by roc97007 · · Score: 1

    Ooooh, deja vu! It'll turn out that it starts up faster because it does a lot of the work during shutdown to prepare for the fast startup, just as windows does now, only (probably) worse. And so when I go to the meeting my laptop will turn on fairly quickly but at the conclusion of the meeting it'll take forever to turn off. Until I figure out where in a plethora of wizards and dialog boxes is the checkmark to turn off the feature. Just as I had to do with my current laptop. It'll be a managerial line item to say "yes we have fast turn-on just like Apple", but will be simply a rebranding of the current hibernate technique which is the reason for that embarrassing 5 or 10 minutes at the end of meetings while we all wait for our laptops to prepare for the next "instant on".

    Ok, got that one. It'll be a mandatory "disable", like Superfetch in Windows 7.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    1. Re:I know this one by roc97007 · · Score: 1

      And no, rather than being a solution, "suspend" is just an invitation for the dreaded "cannot resume" error.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  51. Filename Length by Anonymous Coward · · Score: 0

    Is Windows still limited to a filename length of 8.3 for system files?

  52. small SSD boot accelerator? by bill_mcgonigle · · Score: 1

    That much thrashing indicates something is wrong and/or you have too little RAM.

    It could be swapping, but it could also be seeking like crazy, especially on a slow laptop hard drive.

    I'd like to see a way to buy a cheap amount of SSD ( ~= RAM size on mobo, SATA 6Gbps even) and dedicate that to hibernate activities. If I hibernate my laptop, nearly all the wake-up time is reading the memory image from disk.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  53. Re:And it took them *this* long... by neokushan · · Score: 1

    I guess that depends on how much it's compressed and what it's compressed with. Not to mention the other operations the CPU must perform to load that data into memory. I'm sure it'd be I/O bound if you were just bltting the whole pagefile back to memory, but there's probably a bit more to it than that. I couldn't possibly say, though, it's certainly not a topic I know a great deal about.

    --
    +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
  54. Users already hate the fast shut down mode! by Zemplar · · Score: 1

    Hopefully this will be better then the fast shut down mode (a.k.a. "blue screen of death") that Microsoft has developed and deployed already.

    By the way, did they ever get a patent on the blue screen of death? If not, I'm sure there's a market in there somewhere!

    1. Re:Users already hate the fast shut down mode! by roc97007 · · Score: 1

      At first I didn't know what you were talking about. (Until I read the body of your article.) To my knowledge, the only "fast shutdown mode" was holding down the power button. But then, of course. BSOD. How could I forget? The only problem is, it was kinda random. The computer decided you should quit working, and ping! fast shutdown. "Well, gee, Wally, I guess it's time to go home."

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  55. Re:And it took them *this* long... by swalve · · Score: 1

    I have to agree. It must be more difficult than I think to come up with a algorithm that maintains a semi-active "hiberfile.sys" while the OS is running. Something like an "idle" task that copies parts of RAM to disk so that when the hibernate button is pressed, there is less writing to disk that needs to be done. (Although I think they have something like that already set up, if you have some flash ram dedicated to one of those turbo-cache modes.)

  56. Re:And it took them *this* long... by bemymonkey · · Score: 1

    "I'm sure it'd be I/O bound if you were just bltting the whole pagefile back to memory, but there's probably a bit more to it than that."

    Why would there be more to it? When you wake from standby, nothing much happens at all, and the stuff in memory afte rstandby is likely to be the same as what's written back in when waking from hibernate...

    I'm out of my depth here too, so this is just speculation on my part :)

  57. Instant BSOD! by kawabago · · Score: 1

    Everyone will want it!

  58. More coming features from MS by Anonymous Coward · · Score: 0

    I recall several recent "Windows 8 to Feature xyzzy" stories. Extra points for those who have actually encountered the word "xyzzy" in the distant past. Anyway, do you recall them doing this same PR drill for Windows 7? For Windows Vista? And what percentage of those "coming to Windows real soon now" features were actually shipped? And of those that did ship, how many annoyed the hell out of you? Or did anything quasi-useful for you at all? Actually, I wouldn't know the answers to those questions because my company still deploys XP. What about yours?

    Microsoft needs to remind you that they still exist, and if they can generate some enthusiasm for a new version of Windows that will likely ship only after another year or two then they have scored extra free points as well. Never mind that a SSD will be a Windows 8 installation requirement. What? The referenced article failed to mention that? Again, I wouldn't know the answer to that question either because I didn't read the article (like every other good Slashdotter).

    As Microsoft become less relevant, I predict they will become even more noisy. But folks, I believe much of this is simply empty bluster by a company in serious decline. Who am I, you ask? Why, an Anonymous Coward of course.

    --
    AC

  59. Inject stuff into kernel more easily by FormOfActionBanana · · Score: 1

    This sounds like an interesting vector for injecting code into the running kernel. Shut down; remove disk; edit hiberfil.sys; reinstall disk; restart.

    I sure as **** hope there's a good quality digital signature on that file! As they're talking about speed, it doesn't seem like a huge probability.

    --
    Take off every 'sig' !!
  60. Woopie! by jweller13 · · Score: 1

    Amazing that after 30 years of Windows a fast bootup is considered something to get giddy about. There's even a stupid as hell commercial for it at the movie theaters.

  61. Re:And it took them *this* long... by ByOhTek · · Score: 1

    With Windows, that happens about once a month, and honestly, usually doesn't take that long unless your IT group has seriously fucked up.

    --
    Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
  62. Windows already takes an age to shutdown by JustNiz · · Score: 1

    *sigh* All this will mean is an even longer shutdown.
    Even before this new 'feature' gets added, WTF is all the work that windows is doing during shutdown?
    Surely all it really needs to do is kill everything that isn't actively writing to disk.

  63. Re:And it took them *this* long... by nabsltd · · Score: 1

    which is able to use all of the cores in a multi-core system in parallel, to split the work of reading from the hiberfile and decompressing the contents.

    This also implies that MS is compressing the data. I'm not as familiar with Windows 7, but I'm fairly sure that XP does not compress hiberfil.sys...it's always as big as RAM.

    I hadn't heard a change for Vista or 7, and I imagine writing a compressed file would slow down hibernation a lot, so you might win on resume, but you'd pay on the other end.

  64. Can we all please remember... by roc97007 · · Score: 1

    ...that windows 95 had a "fast startup mode". ACPI has been around since 1996, and it has never worked consistently or well. M$ has to rebrand the techniques as "instant on" because everyone else in the world has "instant on" that actually works. But you know that they'll tweak it, fix some issues, introduce new issues, and Windows 8 "instant on" will sort-of work, better on some hardware than on others, will have the usual issues (loooonnnngggg hibernation times to prepare for "instant on", resume errors, etc) and perhaps some new issues, and won't be any better total experience than your suspend/resume and hibernate features are now. Because Microsoft can't resist the temptation to reuse existing code rather than redesign. They think they can achieve redesign with marketing, rebranding, and resetting customer expectation. Sadly, to a certain extent, they're right.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  65. 91 Processes by ThatsNotPudding · · Score: 0

    WIth just Outlook running as the only 'user program', my work comp has 91 running processes listed. Including a Bluetooth service. On a desktop.

  66. Why do we still care about boot time? by Anonymous Coward · · Score: 0

    Can I ask why restart time is so important?

    How often do people really restart / boot from cold boot?

    Admittedly, I'm on a Mac 95% of the time, so perhaps I don't know how Windows operates, but my Mac has uptime's running in the weeks, if not months easily. The only time it ever gets restarted is when there's a system update that requires it or there's something reaaaalllyyy screwing up the system (which happens so infrequently that I can't remember the last time I did so.) On the Macbook Pro, I close the lid when I'm done. I come back, I open the lid and it's there and ready. On the iMac, I put it to sleep when I'm done. I come back, shuffle the mouse (or hit a key) and it's there and ready. I can't tell you how long it takes to wake from sleep, but it's something like less than 5 seconds.

    Who are all these people who are still rebooting their computer all the time?

    1. Re:Why do we still care about boot time? by Anonymous Coward · · Score: 0

      Who are all these people who are still rebooting their computer all the time?

      People who are constantly installing software that "requires" a reboot (i.e. People who install redundant software and little games constantly).

      Of course, there is a small percentage who restart because they have machines with too little memory that page too much; reboot makes things feel faster from a different angle.

  67. Re:And it took them *this* long... by Ihmhi · · Score: 1

    will probably still require the full shutdown we've come to know and loathe. :(

    Oh noes, a whole minute! Maybe two on some computers!

    In b4 low UID Slashdotters talking about computers they had to start with a crank shaft.

  68. Run less shit when you log in by Sycraft-fu · · Score: 1

    Or buy a more powerful computer.

    There's nothing Windows can do to help you if you choose to have a million things start up on login. Those programs have to be loaded off your disk and that is that. It has no magic voodoo to speed anything up.

    So part of it is just not loading so much on startup. That will take some time, no matter what. Another part is making sure you have enough RAM. If the system has to start paging out while it is loading. That really slows shit down.

    Ultimately, if you want to have a bunch of stuff load, have a lot of RAM and an SSD. That'll do the trick. It is about 5 seconds on my system from login to done. I load a ton of stuff too. Off the top of my head I have Steam, Origin, Impulse, Spectraview, NOD32, and Live Messenger all start, and I probably forgot one or two.

  69. No the solution is to go yell at IT by Sycraft-fu · · Score: 1

    Seriously, your problems there sound 100% the fault of incompetent IT, not Windows (I say this as an IT guy). If your system runs a virus scan on login that is fucking retarded. There is NO reason to do such a thing. If they want to run a regular full scan (something I am not convinced is useful with on access scanning) it should be done at night when nobody is around.

    There's nothing Windows, or any other OS, can do to fix it. When you have something hitting your disk heavy it will slow down since disks aren't good at random access.

    1. Re:No the solution is to go yell at IT by davros74 · · Score: 1

      Seriously, your problems there sound 100% the fault of incompetent IT, not Windows (I say this as an IT guy). If your system runs a virus scan on login that is fucking retarded. There is NO reason to do such a thing. If they want to run a regular full scan (something I am not convinced is useful with on access scanning) it should be done at night when nobody is around.

      If your IT is anything like my IT, full virus scan scheduled to run at "night" means begin at 5pm. I cannot kill the process, but at least I can suspend it, then resume it when I really leave for the evening. (Really sucks when you try to remote in from home in the evening to get some work done and the remote connection is slow as heck because of the AV scan). Would think 2am would be a better time, but no control over it.

    2. Re:No the solution is to go yell at IT by grimmjeeper · · Score: 1

      I don't know how it works where you are but all of the companies I work for have a "one size fits all" mentality when it comes to corporate IT. Yelling at IT to change something is like trying to push a rope. It just doesn't accomplish anything. They aren't interested in helping you get work done. They are only interested in keeping their costs down and that means applying the same image to every single computer in the entire company. And when you complain, their solution is to suggest applying the corporate standard as they close the ticket. Running it up the flag pole doesn't help because the IT management doesn't know a thing about computers beyond the cost to buy them.

  70. Re:And it took them *this* long... by Anonymous Coward · · Score: 0

    Suck my dick you fucking faggot.

  71. Re:A short review of Soluto. Follow up. by LordLimecat · · Score: 1

    Do you have a better recommendation for software which does what Bootvis did before it was discontinued ages ago? And includes a wiki-style database of apps and what the recommended setting is for them? And that is both free, and free for commercial use?

    No? Oh, ok then. Im sure I can just recommend to my parents or friends that they fire up Autoruns-- Ill just warn them to be careful not to do anything that will absolutely hose the system.

    Myself, I was impressed by the program, because it allowed startup editing in a way that even non-tech literate folks could understand, while not allowing them to do anything super terrible to their machine (like disabling those system drivers-- GP should have his head checked if he thinks a "general user" utility should allow access to those). It also has support for at least IE, Firefox, and Chrome, for disabling plugins-- again, in a way that the average joe could use, without needing to understand "about:plugins", and "tools -->extensions --> plugins".

    I think most of the people complaining about Soluto are folks who are upset that its not another Sysinternals Autoruns, which is fine, because we dont need another one of those. This is meant to be used by folks who DONT know what all the various windows services are and which are safe to disable. I think its a fine piece of software, and nowhere near as bloated as is being implied (50mb of RAM at worst). And as for disk space, are you REALLY complaining that it uses 33MB of disk space on install? Oh the horror. And its startup time!! A terrible ~1 second! Oh noes!

    I really hope you dont do any support for friends and family, because it sounds like youre really out of touch.

  72. Great by Anonymous Coward · · Score: 0

    We have seen some drastic improvements over the years from Microsoft for faster booting. Windows 7 is far better than Windows XP in booting and shut down time. Hoping Windows 8 to be far more superior. Still there will be some dependencies.
    [Read More - http://goo.gl/QzBdi]

  73. Re:And it took them *this* long... by PhrstBrn · · Score: 1

    I'd say it depends on the compression, and how fast you can compress.

    If you use one of the newer processors that has the AES instruction set and take advantage of that, you could easily compress faster than you can write to disk. With a 2 to 1 compression ratio, you've theoretically doubled how fast you can hibernate.

  74. html5?!!! by perryizgr8 · · Score: 1

    wtf?? have i gone insane or did an ms blog just use html5 video tag instead of flash or silverlight?

    --
    Wealth is the gift that keeps on giving.
  75. Insert some joke here by bryan1945 · · Score: 1

    My Mac can full reboot in about 45 seconds. Hibernate mode is "hit space button, sneeze, ah I'm back." Whatever, no one here cares, I'm just like taking jabs at Windows since I spend way to much time fixing them at work.

    --
    Vote monkeys into Congress. They are cheaper and more trustworthy.
  76. Long shutdown, short startup. by AbRASiON · · Score: 1

    There was talk of something like this a while ago.
    I think it's great - sure it would be nice if the machine could genuinely re-boot from cold start to desktop shorter but this is the next best thing.

    Our machines have turned off automatically on shutdown for years, so I am going to walk away when I set my machine to shut down. If that means it takes longer but next boot up is significantly shorter, definitely not a problem with me. That's just clever design as far as I'm concerned, regardless of 'cheating' or not.

    I wish I could find the article but basically Apple does clever stuff like this to make things seem quicker. I've heard that when you switch between tasks, it pulls up a screenshot which it took the last time you used that app. It displays this quickly and then while your eyes are looking for what to press, it's actually still loading the real application back into memory. It's simple and effective at making things seem quicker than they are -again cheating but ultimately a good user experience.

  77. Ha ha ha ha ha by pinkushun · · Score: 1

    I laugh at these mortals who have to reboot!

  78. Here we work with users by Sycraft-fu · · Score: 1

    We are in the customer service business. Our job is to facilitate users getting the work they need done. It must be done safely, legally, and all that, you don't get to run around and do as you please, but we work with people. We don't say no unless there's a good reason and generally we don't say no at all, we just say "No you can't do that, but here's an alternative." For example we won't allow FTP to be used because it is insecure, but we'll get you setup with SFTP (SSH) no problem.

    If your IT department isn't like that, that sucks. However don't then go and get mad at MS or want them to fix it. They can't make Windows magically handle a mandatory on-login virus scan faster. That can only be done with hardware that is better at handling random access, namely an SSD. Even then it'll slow things down, the real answer is off-hours scanning, or the real real answer is don't perform full scans on a schedule there is no reason.

    1. Re:Here we work with users by grimmjeeper · · Score: 1

      Did you not read my original post where I explicitly said that it's not Microsoft's fault? Did you not notice that I titled it "Boot time isn't Window's problem"? In a nutshell, I said basically that while Microsoft could have designed Windows a little better, the blame falls squarely on the shoulders of the people who write the software that launches when you log in. That software which smegs up the system with all sorts of activity is poorly written. And when you're stuck with it because IT doesn't want to change it, there's nothing Microsoft can do about it.

      I'm happy that your IT department is an exception to the rule. It's great that you and your colleagues "get it". I wish all IT departments were run like that. However, how your department handles things doesn't make the slightest difference to what I'm talking about.

  79. Patches at night - Arrgh! by billstewart · · Score: 1

    I use a laptop, and work from home several days a week, especially the days I have early morning phone calls (i.e. mid-morning phone calls on the East Coast, which is not where I live :-) Overnight software installations that trigger reboots mean that occasionally I get downstairs and find that my machine has rebooted, so I have to log in, restart my VPN, restart Outlook, restart my browser, figure out what documents I had open and restart them, and it's at least 5 minutes before I'm able to dial in to a phone call, and more like 10 minutes before I'm ready to work.

    And this new "fast startup mode" that doesn't save my sessions isn't going to help that.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:Patches at night - Arrgh! by Reverand+Dave · · Score: 1

      We never patch unannounced. Plus we're a smallish agency (>250 users) we had to eliminate our VPN due to budget cutbacks so we don't encounter these types of issues.

      --
      I got here through a series of tubes
    2. Re:Patches at night - Arrgh! by billstewart · · Score: 1

      Not patching unannounced is a really good policy. But dropping your VPN? Your employees were ok with having to come in to the office every day, and your management's ok with the loss of productivity? Wow!

      --

      Bill Stewart
      New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    3. Re:Patches at night - Arrgh! by Reverand+Dave · · Score: 1

      Our VPN was only used at a small remote location. Whenever you hear some jagoff complain about "big government" thank them for the productivity loss.

      --
      I got here through a series of tubes
  80. Compare and contrast to Apple's approach by ToasterMonkey · · Score: 0

    You have to laugh a little... but it's not a bad idea

    Apple:
    Resume from low power reliably.. quickly
    Power buttons sleep by default
    Users tolerate very short default sleep timers because of the fast resume. Saves lotsa power.
    Portable systems default with SafeSleep on.. writes hibernation data, !quickly!, prior to entering low power mode, resumes from the faster available method - in case battery runs out in low power mode.
    Desktops can optionally use it, great in case of unreliable power
    Replaced hibernation with a better sleep & transparent hibernation, users trust/use sleep

    Microsoft:
    Windows resume from low power state has bad track record
    Hibernation is a roll of the dice, slow as shutdown
    Microsoft understandably cannot change user opinion/momentum
    Make hibernation "look like" power off.. log out users, etc.
    No need to copy Apple's fast hibernate because users don't expect shutdown to be instant, but they could
    Replaced shutdown with hibernation in shutdown clothing

    It is clever, I'll give them that.

  81. Re:A short review of Soluto. Follow up. by Anonymous Coward · · Score: 0

    Whenever someone hands me their laptop, I press the button which used to read "start", enter "msconfig", press enter, go into startup, disable ALL THE THINGS except $chat_client, hit ok, ok, reboot, upon boot check the box and press OK again.

    The next day they say their laptop has gotten much faster. Gosh. Don't need a fancy tool to disable all those TSR/notification area roaches.

    TRWTF is people see me running a modified Ubuntu and think I'm some kind of computer genious. Then proceed to hand me their laptop running Windows which I haven't run on my own boxes for over 10 years (but msconfig hasn't gone away in all those years).

  82. Does it work with Full Disk Encryption? by billstewart · · Score: 1

    I used to use Hibernate fairly often with my laptop. But then Corporate IT installed Checkpoint's Full Disk Encryption feature, which disables Hibernate for some reason. Does this new version of hibernate have the same limitations?

    I only use full reboot for three reasons - either I've installed some new software that needs it (usually Microsoft Patch Tuesday, or occasionally other software that insists on it), or else I've had my laptop unplugged for long enough that Sleep Mode has failed or gotten hosed(it used to go into Hibernate if the battery got low enough, but it can't do that any more), or occasionally I'll plug the laptop into an external monitor and it can't figure out what it's doing with video (sometimes an extra Sleep/wakeup fixes that.)

    This new feature is helpful if I've shut the machine down because of battery, but otherwise I really do need a full shutdown.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  83. Re:A short review of Soluto. Follow up. by bmo · · Score: 1

    Msconfig is not exactly difficult to understand.

    The only reason people don't use it more often is that they don't know about it.

    It does the job.
    It doesn't give you any crap about doing its job.

    Therefore I consider this good software. I consider it far better than a glitzed up bells and whistles replacement for msconfig.

    --
    BMO

  84. Nothing new by badatnicknames · · Score: 1

    There's nothing really new here. This seems to be no different from logging out and then doing a hibernate. It's probably because users don't understand hibernate that they are able to pass this off as fast boot. If users were in the habit of hibernating it would make no difference. They should be announcing faster hibernate not fast startup. This fast startup will not help with restarting for software updates or to install new hardware.

  85. Re:A short review of Soluto. Follow up. by bondsbw · · Score: 1

    Then use msconfig, and leave Soluto to people who need it.

    It might surprise you, but some people actually don't know what BOOT.INI and WIN.INI and SYSTEM.INI mean. Some people don't know the difference between startup items and system services.

    If you do, STFU and stop wasting everyone's time, including yours, complaining about something that can seriously help other people. I have to fight against your kind day in and day out, just to let me design software so that our users might actually want to use it.

    --
    All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
  86. Boot time vs Shutdown time by Anonymous Coward · · Score: 0

    Trying to reduce boot times is nice and all... but it should not be done at
    the cost of "shutdown time".

    Windows 7 takes much longer to shutdown than Windows XP and it's quite
    annoying.

    Now I read this slashdot article and things are about to get worse with
    Windows 8 it seems:

    More shutdown time BAH !

    (Posted on usenet too :P !;) =D)

    Bye,
        Skybuck.

  87. Other than Windows, is there any other OS by melted · · Score: 1

    Other than Windows, is there any other OS that people actually have to reboot every couple of weeks? I forget when I last had to reboot the MacBook Pro I'm typing this on. Probably a couple of months back. Same with my company issue Linux Thinkpad. Fix the motherfucking reboots. I don't care how long it takes to boot if I only reboot it once in a couple of months.

  88. Logging to a domain slow by jones_supa · · Score: 1

    Why has it always been so slow to log on to a domain in Windows? Even in 7, it can still sit there for minutes. If it was implemented in a sane manner, I bet you could transmit and process a lot of information in mere 10 seconds, even if it included the credentials, network drive mappings, policies and some scripting.

    1. Re:Logging to a domain slow by rant64 · · Score: 1

      Why has it always been so slow to log on to a domain in Windows?

      It isn't that bad. If it takes any longer than 4-5 seconds to authenticate and process your user policies and scripts then you're doing it wrong.

      it can still sit there for minutes

      It kinda depends on what you mean by 'there'. In smaller environments, additional time is usually caused by:
      * incorrect network setup (dns, usually)
      * insane synchronous startup/logon scripts or those that do "software deployment". Those are a damn joke.
      * roaming profile that has become way too big.

      The "always wait for the network at startup" setting in computer policies may help. It ensures that all services are started and GPO processing has completed before the logon screen is presented. It may take a while longer before the user may enter his credentials, but the desktop then appears more responsive sooner. A particular example is when there are instances of SQL Express installed on a laptop, for whatever purpose, that can really stall the logon process as the database server is still starting.
      Also, first logging on and then leaving for hot beverage is not always an option because of company policy against unlocked desktops.

      In some cases, like very large corporate environments, there is a lot to take care of at logon time. In enterprise desktop provisioning, you can't tie anything to a computer because the user may log on from any system, not just a roaming desktop but Citrix, VDI, whatever, so all of the desktop setup has to take place at that point as if you were a new user.

  89. Re:A short review of Soluto. Follow up. by LordLimecat · · Score: 1

    Grats, that breaks a lot of things.

    For instance: Drivers arent listed, and some drivers (antivirus, web filtering, etc) REQUIRE certain services to be running in order for things to work right. For example, Bluecoat labs web filter (k9) will simply end up blocking all of your internet access if you try to disable it that way (you need to fix the winsock stack, and remove the driver). Or some versions of Norton will simply end up bluescreening you if you do that.

    So if you follow your plan, and it ends up bluescreening the person's laptop, what then? "Whoops, sorry, guess its time to reformat"?

    Or what happens when you end up disabling their WiFi manager, and the next day they realize their laptop wont autoconnect to wifi, and they dont know the passwords? "whoops, i guess you should know all the wifi passwords by heart"?

    Or when you end up disabling their Cisco VPN service, and now the GUI part simply doesnt launch before login, which is a requirement for connecting to their office network? "Oh well, at least your laptop is faster"?

    Once again, it sounds like youre out of touch. MSConfig disable all is a shotgun approach that works some of the time, but you usually end up disabling some crap they actually WANTED. Why havent you heard about it? Probably because they now think A) they dont want to keep bothering you about it and B) you sort of made it worse and they feel bad telling you that.

    The fact that you havent run windows on your boxes for 10 years is maybe an indicator that you shouldnt be pretending you ARENT out of touch, either. Maybe you should consider using it occasionally rather than assuming that you need to make all windows boxes resemble your version of Zen computing-- some users actually LIKE google toolbar or whatever.

  90. Re:A short review of Soluto. Follow up. by LordLimecat · · Score: 1

    MSConfig is a hammer that breaks a lot of things, and shouldnt be used the way people are using it. It is possible to leave a computer unbootable by disabling services that AV relies upon for example-- see my post above.

    And MSConfig does NOTHING to tell you how long each service takes to load, which is what bootvis and soluto both do. For example, I had Eraser on my laptop, and found out that that service takes 15 seconds to load. I sort of wanted the program, but not that badly, so out it went. MSConfig wouldnt have given me that info, and I dont think bootvis works on Win7 x64.

    If you want a replacement for msconfig, you should REALLY be looking at sysinternals Autoruns, which does way way more than MSConfig (drivers, winsock stack, services, startup list, codecs, etc).

    Honestly, MSConfig is a poor piece of software to use in the way you are using it for a large number of reasons:
        * It will pop up a scary warning the next time that user boots
        * A lot of MS Articles ask you to switch to "minimal startup" for testing, and then set it back to normal. Any user following these instructions would undo all your work.
        * It assumes that there are no vital 3rd party dependencies that will be broken by "disable all"
        * It doesnt give you any way to check the digital signature on windows programs, which might lead to you leaving "Svchost.exe" (an infected copy) enabled
        * And contrary to your belief, a lot of the time, no, it doesnt do the job, and will easily miss the commonest of viruses.

    Its utility is mainly in troubleshooting, and not much else.

  91. Re:A short review of Soluto. Follow up. by LordLimecat · · Score: 1

    I know about msconfig, and I would recommend Soluto above it for 50% of the cases, and sysinternals Autoruns for the other 50% (especially since it can be downloaded straight from http://live.sysinternals.com/

  92. Reminds me of FastBoot on the Amiga in 1996 by johnpod · · Score: 1

    Nice to see the PC world is slowly catching up with the Amiga and only 15 years behind on this one. I seem to remember approx 8 sec boot time from cold with my old 0.5GB HD. http://aminet.net/package/util/boot/FastBootV1_0 Where are my datatypes and arexx ports? I am still waiting for those.

  93. My old C-128 by Anonymous Coward · · Score: 0

    with a 1MB ram drive for a hard drive would boot to a usable desktop in about 2 seconds. Full GEOS desktop ready to go.