1. POST = Power On Self Test. Yep, it's the bios start up time, from when the button is pushed to when it hands off to the OS. It has everything to do with the motherboard and bios, and nothing to do with whatever OS you have on there.
2. I must be old cuz I've had computers with 4MB of SIMM memory. Yes, 256MB is more than enough for windows. Most carpc's don't need much memory anyways because you're not dealing with large programs or files.
3. No. I mentioned the M2 in response to jmciver talking about the M2. You can substitute any power supply in what I said. The power supply provides power in the form of the various voltages on the rails, the amps when the demand calls for it, and as clean (low ripple) as possible. A motherboard doesn't care where the power comes from or how many blue led fans it has or the maker of the PSU as long as the power is there when it wants it.
subscribed
Ampie Case
2.5" Hard Drive 80GB Samsung 5400RPM
256 MB DDR2 PC5400
Xenarc 700TSV - VGA Monitor
Intel D945GCLF Motherboard
M2-ATX-HV
2005 Honda Civic
This is a great thread, I was going to actually start one about this topic before I saw it. I will try BOOTVIZ to see what takes so long to bring up my machine from hibernate. Chances are it's the 5200rpm WD drive that's not fit for a 512MB dump.
I always wondered if Windows dumps everything including empty memory addresses, or if it only dumps whatever is used up at the time it's shutting down. Guess it dumps everything at once, including zeros.
One of my biggest delays it the time from power to the PSU starting the machine. My 90W OPUS has a long delay which I will remedy with my own SD controller.
How will an extra shut down controller help your boot up time? Doesn't the opus have a shut down controller? Thanks.
-Ross
LiquidKernel:
well, bootvis won't help you much with that. A startup sequence includes your SDC delays, BIOS delays, and then resume/boot. bootvis can only help you after the BIOS for the boot part. However, with hibernation resume, the boot portion is simply a file dump into memory. It just takes the image it had created and slaps it onto your memory. There's no real bootup and nothing really to tweak other than decreasing the amount of RAM you have.
For example, I have 512MB of RAM and have been thinking about decreasing that to 256MB to get to music faster. With a stopwatch, this is my startup time:
1) Key turn to MB power on: 2 sec
2) BIOS to OS handoff: 15 sec
3) Resume from hibernate: 10 sec (<-- the time that bootvis reports)
total: 27 sec
If I decrease to 256MB, the only part that is affected is (3) resuming from hibernate. Cutting the memory in half approximately decreases that time in half, down to 5 seconds. My total startup time then would be 22 seconds.
Nerd2: No, it dumps everything. If you use hibernation, look for the file c:\hiberfil.sys. That file is the same size as your memory. Everything that's in memory is placed in the file. If you have 512MB of memory, you'll have a 512MB hiberfil.sys file.
Not an extra one, but a replacement for the OPUS. I will disable the onboard OPUS controller. It has a 8-10 second delay between key turn to MB power. The controller I'll write on an Atmel will have a shorter delay for the start up.
The OPUS does have one, but while it works, it could be better. Too bad they never released the source for the MCU on their PSU.
That was my initial thought as well. Even though BOOTVIZ does have an option for hibernate, it shouldn't make a difference. Another think I'll check out is using a faster hard drive. My gf's laptop with the same amount of ram takes half the time to boot up, and it's not that fast of a laptop either.
Bookmarks