HORM/Dismount problem/question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We use HORM for quick bootup. I want to have a two drive system, with C:
write protected and data on D: unwrite-protected. I've followed the
instructions from

http://msdn2.microsoft.com/en-us/library/aa460084.aspx

regarding dismounting volumes in a HORM Configuration,but it doesn't exactly
work.

I receive good return codes from the Lock Volume and Dismount Volume of D:
using DeviceIoControls calls prior to the SetSuspendState. It hibernates. I
receive good return codes from the Unlock Volume upon resume from
hibernation. I can even programattically edit an existing file on D: and it
will contain the changes through the next reboot. However, if I create a new
file on D: it will not persist through the next reboot. And if I
programaticallly delete a file on D:, it will revert to the undeleted version
on the next reboot.

It is as if I'm half fooling the EWF in that existing files on D: can be
modified/saved. But no new ones can be created or old ones deleted.

Any ideas of what I might be doing wrong, or what I might try?

My 'disk' is a compact flash, configured as a 'fixed' disk. Should the
above procedure work for compact flash?
 
I found my problem. I had created the D: drive using FDISK, after doing my
FBA (my SBC had recommended this as a way to create a write-able D: drive).
So the EWF tools never knew about D:. To fix it, I created the D: drive
using the Target Designer, and now the disk shows up as disabled when I would
do a ewfmgr d:, and after doing the lock/dismount/hibernate/unlock
methodology for making drive D: writeable, it works with HORM.
 
Can you give more details about how you create the D: drive using the Target
Designer? Thanks.
 
In reading my earlier post, I may have misstated how D: got created.

First, the wrong way. In order to make a writeable D: my SBC manufacturer
recommended using FDISK to create C: (followed by formatting it and
bootprep-ing it). In TD, in the Enhanced Write Filter component settings set
up one protected volume. Copy the files created by TD onto the C: and boot
it. After FBA runs, an EWF partition will be created after C:. Using
FDISK delete the EWF partition and now create the D: partition. Since it was
created post-FBA, EWF has no control over it and it is writeable. But it
doesn't work with HORM as I painfully learned.

The correct way. Use FDISK to create C: and D:. Format both C: and D:.
Bootprep C:. In TD, in the Enhanced Write Filter component settings tab set
up two protected volumes. Copy the files created by TD onto C: and boot it.
After FBA runs, both C: and D: will be protected by EWF. Disable EWF on D:.
Using the microsoft code from the link shown earlier, programmatically lock
and dismount D: prior to hibernating. Upon resume from hibernation, unlock
D: and it will be writeable.
 
:
Thank, Hanleyh1. This is very helpful.
In reading my earlier post, I may have misstated how D: got created.

First, the wrong way. In order to make a writeable D: my SBC manufacturer
recommended using FDISK to create C: (followed by formatting it and
bootprep-ing it). In TD, in the Enhanced Write Filter component settings set
up one protected volume. Copy the files created by TD onto the C: and boot
it. After FBA runs, an EWF partition will be created after C:. Using
FDISK delete the EWF partition and now create the D: partition. Since it was
created post-FBA, EWF has no control over it and it is writeable. But it
doesn't work with HORM as I painfully learned.

The correct way. Use FDISK to create C: and D:. Format both C: and D:.
Bootprep C:. In TD, in the Enhanced Write Filter component settings tab set
up two protected volumes. Copy the files created by TD onto C: and boot it.
After FBA runs, both C: and D: will be protected by EWF. Disable EWF on D:.
Using the microsoft code from the link shown earlier, programmatically lock
and dismount D: prior to hibernating. Upon resume from hibernation, unlock
D: and it will be writeable.
Click to expand...
 
Back
Top