I disagree with you. Not all hardware is hibernate friendly.
With some tweaking sub-30 second boot times are easily achievable. Sub-15 seconds is doable with the right hardware mix.
Lets face it, boot time is rarely a factor in carpc. Whats more important is hibernation/resume or standby/resume time. Regardless what you do, 99% of the time, your hibernation/resume time is faster than your cold boot time. So I say, worry about the UI that fits you well, and if it runs fast enough in the desktop environment, ie your hardware is fast enough, and worry less about the boot time. If you like the way win7 is organized (personally i don't), the way it look (i like this), drivers (hit/miss on this one, but its not even released yet so.... wait and see), and other neat features (better OSK, native ts support, ssd optimization...etc.) then use win7, otherwise absolutely nothing wrong with winxp.
I'm currently using win7 and i like it over all. Saying that its clearly better than winxp, i don't think so.
I disagree with you. Not all hardware is hibernate friendly.
With some tweaking sub-30 second boot times are easily achievable. Sub-15 seconds is doable with the right hardware mix.
Yea I also agree that it's hibernation time which is most relevant to the CarPC use. Especially if you are using a more resource heavy front end like Centrafuse, where a fresh boot is pointless compared to hibernation. I can boot into XP faster than Centrafuse can load.
I have free access to Windows embedded version, so Im curious why go for it over a standard XP or windows 7 install? Isnt the embedded version a trimmed down version, sort of like TinyXP or Tiny7? Would that mean driver support is worse off? Driver support is crucial if you are using hibernation/standby because they can often break hibernation completely.
I never understood what takes CF so long to start up... nGhost parses every screen xml file into memory and loads every plugin before starting up, yet it displays almost instantly. WTH is CF doing that takes so long?
Former author of LinuxICE, nghost.
Current author of nobdy.
I dunno but I have already come up with a solution to fix that.
http://www.newegg.com/Product/Produc...82E16813500019
+
16gb of RAM
+
SuperSpeeds SuperVolume
Kind of excessive if all you want to do is speed up load times. I would suspect 16GB of ram would kill your hibernation times. Anyways, I have to admit CF is getting bulkier. It used to run just fine on 256 ram and a slow 1ghz Via processor, now I have to have 512mb ram to run it comfortably. But in my opinion and my purposes, it's still the best front end by far which is why Im sticking with it.
RevFE - Super fast, modular frontend. Most powerful skinning engine in existence. Strong enough for an i7 made for a fitpc.Originally Posted by mitchjs
Just a shame I can't justify a carpc to use it on anymore.
Poorly design hardware/bios has nothing to do with how fast an os boot.
And plus, I already gone through the whole hibernation/resume phase. I've done my share of optimizing my os for the best boot/resume time (best time was <10 sec resume) and came to a conclusion that its a total waste of my time, because every hardware is different and effect the resume/boot time too much. Even when i had <10 sec resume time, I wasn't satisfied.
Currently using s3 standby with a deep cycle battery and DSATX, and I will never look back to hibernation again. That brings me to perhaps the one nice thing about win7 that winxp doesn't have: hybrid sleep. My DSATX is set to hard off at a certain voltage level to prevent discharge, ie. if i leave it for a > 3 days. When this happens, instead of a complete reboot with windows xp, win7 will resume from the hibernation file.
I'm sorry to say, but even with 16gb of ram i doubt your computer will cold boot + CF boot that much faster, plus its a waste of money in my opinion.
Bookmarks