Multi-Boot with EWF

  • Thread starter Thread starter DJ
  • Start date Start date
D

DJ

I was kind of surprised by EWF with the following:

I have a multiboot setup for CF or Hard drive

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XPe HD" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="XPe CF" /fastdetect

Which works great now but I was expecting to be required to change the
registry setting for the protected volume. Which is set to
(0)disk(0)rdisk(0)partition(1)

When I boot to CF (D:) EWF protects the d: drive. Which is what I
wanted.
Shouldn't the protected volume be 0)disk(0)rdisk(1)partition(1) ?
 
That is a very helpful link but I seem to be to thick headed to
understand the drive ordinals and how EWF uses them.
Thanks for the link.
 
Hi DJ,

Link describe how you can preassign volume letter to any partition on any disk before FBA even start. (They are not BIOS or disk
hardware order related).

EWF is strictly partition related so it is not interested in volume letter like C:, D:, etc.

In SP2 you can use two different ways to configure what should be used:
1. Like in SP1 configuration based on ARC names. (Same path convention and meaning as in boot.ini file)
2. Or IIRC you can bind it to diskdevice/partitiondeviceobject name.

Regards,
Slobodan
 
I have tried changing the drive letters like you showed. It works
great! One side effect that I have is if I remove the CF card and boot
to the HD XPe hangs at Welcome screen.

I have set up the multiboot Boot.ini which works perfect. EWF seems to
work perfect (But I never change the protected volume)
multi(0)disk(0)rdisk(0)partition(1)

XPe on HD
HD = C:
CF = D:

XPe on CF
HD = D: (Changed Registery)
HD = C: (Changed Registery)
 
DJ,

I have lost you :-(
What is that you are trying to do?
Why do you have HDD and CF present at the same time?
Where did you do FBA?
How did image appeared on CF?

Regards,
Slobodan
 
Here is my system:
VersaView1500P (Touch screen Industrial PC) used for a Display/Control
panel.
Normal operation would be CF as drive C: and HD as D: drive backup
writeable duplicate if emergency software change is required. Bios set
to boot to IDE1. (Works fine!)
Fallback operation would be HD as drive C: and CF as D: drive just
stays dormant. Bios set to boot to IDE0. (Works fine!)
Theft mode operation HD as drive C: and CF (probably in someones
camera) Either Bios mode works as Bios seems to fallback to IDE0 if all
fails. (System hangs at Welcome screen)

I ran FBA on the target with image on HD and CF plugged in (Secondary
IDE only available). Then I install a couple of applications (I want to
keep seperate from XPe image).
When everything is set I copy to CF and then Boot to IDE1.
The CF at this point is drive D: and HD is drive C: EWF is protecting
drive D:.
I rename the mounted devices as described in the Link and delete the
/??/ devices (but on nect boot the /??/ devices get reinserted).
I reboot and the system comes up with CF as dirve C: and HD as drive D:
EWF is protecting drive C:
Everything appears to work just as I would like, except now if I power
down and pull the CF the system will hang at welcome screen.

I never change any registery settings for EWF somehow it follows the CF
(I'm mystified).
The CF card is left as removable (Sandisk Utility flavor of the day
nolonger).
EWF setup with your EWF Ram Reg component (works perfect)
CF setup at NTFS (works perfect)
 
Hi DJ,

OK. You are not using multi boot since you change your disk boot order in BIOS. This change partition ARC paths.
When you delete mounteddevices they are filled by current values during the boot and they contain valid names as they should.
I never change any registery settings for EWF somehow it follows the CF
(I'm mystified).
Click to expand...

This would happen only if you use different ARC paths in your boot.ini for OS on HDD and CF. (This can happen only in case of multi
OS boot.ini and it is expected)

Also other cause could be hidden EWF volume that is present on some of your disks.

Regards,
Slobodan
 
No, I left out the Boot.ini part of the information Sorry.

The Boot.ini on both HD and CF have multiboot. They are simular between
the HD and the CF but the default is set to the booted device. This way
I can set Bois to a default Hardware depending if available.

If I tell BIOS to boot to rdisk(1) does it then tell the system it is
rdisk(0) ? That is starting to make sense if this is true.
 
DJ,
No, I left out the Boot.ini part of the information Sorry.

The Boot.ini on both HD and CF have multiboot. They are simular between
the HD and the CF but the default is set to the booted device. This way
I can set Bois to a default Hardware depending if available.
Click to expand...
If I tell BIOS to boot to rdisk(1) does it then tell the system it is
rdisk(0) ? That is starting to make sense if this is true.
Click to expand...

Yup it does :-)
So you will have to choose either multi OS boot. Or to do this trough BIOS.

Anyhow this mean that depending on method you use EWF will have to be configured trough registry differently depending on case :-(
Or you can look at SP2 vays to configure EWF so it does not depend on ARC path.

FYI: RAM Boot would be much better for you if you can use it.

Regards,
Slobodan
 
I have updated to SP2 but haven't looked at new features yet.
Do you have any good links for RAM Boot?
 
Back
Top