Instead of flash memory, wouldn't it be possible to use volatile RAM and a battery?
Printable View
Instead of flash memory, wouldn't it be possible to use volatile RAM and a battery?
if your looking at fast boot times, then look down the road of hibernation.. your looking at bootup time of less than 10 sec's in most cases.. also remember to remove all the auto settings in then bios for your drives set em manual.. this say you will save alittle more time.
I am playing around with the Eval version of windows Embedded studio to see If I can reduce the boot up time. At present I have a 117mb footprint that boots to the windows XP shell and has NO swap drive at all hence would be suitable for Flash drive (I aready have the ide flash adaptor so not far off)
What I would say though is from experience XPe is not that much quicker to boot than regular XP as it only really a component version of it. Even with stripping out things I didn't need for the 1st attempt (COM1, LPT, IE, DirectX, LAN) it still take 45seconds on a Eden800 to boot from cold.
I presume these devices that use Windows Embedded don't really turn off when you hit the power button and are in effect doing a STR ???
Sure would, the correct name for this is non-volatile RAM. a couple of years ago there was a clever little design that took old 72pin RAM and generated a clock...Quote:
Originally Posted by eCar™
(ehhh... ok a little explanation is in order here, what you call RAM is actually "Dynamic RAM", which requires a constant clock being supplied to it or it loses it's memory, the opposite to this is "Static RAM" which doesn’t require a clock, and hence is good for battery backed use, but it has its down sides as well)
And then put the whole thing behind an IDE controller... *poof* instant cheap non-volatile battery backed up storage! I think they went out of business! :(
I haven’t seen anything like this is the last few years, great idea tho...
Yes, although I hate hibernation as it seems to always be a problem.Quote:
Originally Posted by CdRsKuLL
And your quite correct about the correct hard drive setting for the BIOS setup, don’t leave anything set to automatic, as that eats tons of time at boot up.
The one exception to this is in the case of a removable hard drive, in which case you do want to leave it set to automatic (‘cuz it might not always be there, or may change size, type, etc)
Nice.... you must of stripped alot out to get it that small, is network support still left in?Quote:
Originally Posted by NJay
Which one??Quote:
Originally Posted by NJay
That can't be true, 'cuz that would mean Microsoft lied to us, and we know that doesn't happen :lol: Have you tried BOOTVIS yet? Could be a third party device driver slowing you down. The "party line" from the good folks at M$ is that a "minimally configured" system can boot in 17 seconds, I have not seen this actually happen, and my experiences sound similar to yours... Actually my favorite embedded version of Windows is not Win NTe or Win XPe, but Win 2000! (Yeah I know it is not componentized). I can strip out all but 8 processes running and give an 850Mhz P3 the "feel" of a 2Ghz P4! And still have networking, plug-n-pray, graphics, etc). BTW that 45 second boot time is the same for my stripped Win2k.Quote:
Originally Posted by NJay
Lost you on STR? STR to me means a string?Quote:
Originally Posted by NJay
But if I get your question correctly, the power status of embedded devices can be alot different than a standard PC with ATX psu, like holding up power, etc. Naturally this is not "doable" in a car! (Ignoring tank circuits, UPS, etc)
Njay this is interesting.
any documentation?