Horm...

**Custommx3** · 05-29-2008, 09:58 AM

Now that Ive gotten my carPC tweaked as much as I thought, now I want to improve my boot time. I coudl upgrade my hardware, but the $$ isn't worth a few seconds.

My questions.. HORM, does it require EWF?

Can I put 256MB of ram in my system, enable horm, and swap in a gig stick? Would this give me a small hibernate file and still be able to utilize 1Gb of ram?

**Tidder** · 05-29-2008, 10:17 AM

AFAIK it needs the ewf NT loader.

And no, I don't think you'll be able to do that with the ram. Have you ever upgraded ram and forgot you hibernated before hand? I've done it twice I think, both times blue screen.

**Tidder** · 05-29-2008, 10:20 AM

Haha, according to microsoft you should just see this:

Windows Resume Loader

Your system's memory configuration has changed since it entered
hibernation. If you proceed, the data needed to resume from hibernation
will be lost. To preserve this data, turn off the system power, restore
the orginal memory configuration and reboot the system. Otherwise, press
to delete restoration data and proceed to system boot menu.

Delete restoration data and proceed to system boot menu.

But I've never seen that, just blue screens.

Maybe this was part of an update or service pack. Who knows.

**Custommx3** · 05-29-2008, 12:10 PM

http://blogs.msdn.com/astebner/archi...01/273462.aspx

You must use EWF RAM or RAM Reg overlay types in conjunction with HORM
Ordinarily, NTLDR will check the header/signature of hiberfil.sys when the system begins the boot process in order to protect against a stale orphaned hiberfil.sys being booted. If a stale hiberfil.sys is detected, NTLDR will show a menu asking if you want to continue to resume or discard the hiberfil.sys and perform a full boot. You can create a file named resmany.dat (any size, any format) on the root of the boot partition (typically c

to suppress this check and allow your device to resume without any user interaction.
You must make sure to use the EWF NTLDR with HORM. EWF NTLDR is the only boot loader that has the logic to search for resmany.dat and skip the hiberfil.sys header check.

Would this alleviate that issue? or is this something else. Pardon the ignorance, I'm new to EWF and HORM.

**Custommx3** · 05-29-2008, 04:52 PM

Well, I took a laptop and setup EWF, popped out a 512MB stick, this left 256MB. Enabled hibernation,added the resmany.dat, and created the hibernation file.
I rebooted a few times to verify it worked, then put the 512MB stick back in. Still pulls that 256MB hibernation file w/ 768MB if ram!

**Zogg** · 05-29-2008, 05:01 PM

That is a neat trick, Custommx3.

I've been thinking about trying EWF and HORM. Did you just use the laptop's hard drive? If so did it make a big difference?

Since you seem to have gotten it to work pretty quickly, was there a recipe you followed? The thread on this is pretty big, so just wondering if you could point out a particular set of instructions that worked.

Thanks,
Z

**Custommx3** · 05-29-2008, 10:56 PM

Actually, after about 3 reboots, I got the BSOD

Its because I was using a 256mb hibernate file w/ 768mb Ram.

As long as the file is made with the ram you use, its good. I should have done this long ago..!!!!

**Custommx3** · 05-29-2008, 11:39 PM

Just HORM only...

Found it!

**Zogg** · 05-30-2008, 09:34 AM

Originally Posted by Custommx3

Just HORM only...

Found it!

Thank you very much, I will give this a shot today!

Z

**Tidder** · 05-30-2008, 09:39 AM

Probably BSOD'd cause something changed on the drive. I wouldn't think that HORM without EWF would work very good for very long. It might start referencing files that have been deleted or changed, and blue screen because of it.

On a side note, it's interesting you've found a little glitch in resuming from hibernation. It sounds like if you keep the ram you had in there when you hibernated, and just add to it instead of replace it, it will resume properly. Odd.