EWF, El Torito & ETPREP Problems

[Craig]

Hi all,

I've been struggling with this for a while now and had some very useful info
supplied by Slobodan. This message consolidates everything in one place.

I have a target created with all of the QFEs that has the appropriate EWF
and El Torito components installed. This target boots from HD successfully
with and without EWF enabled ... EWF works correctly too. I've used
Slobodan's approach for enabling EWF without the interim step of creating an
EWF partition because of the problem I had with the "standard" approach
described in XPe help ... EWFMGR C: would always come up blank. I also did a
low-level format on the HD so that variable was eliminated.

Anyway after FBA completes, my system configuration is as follows:

EWFMGR

No EWF volume is detected ... this is what I expect.

EWFMGR C:

Type RAM
State DISABLED
Volume ID 4C 98 74 5D 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
MaxLevels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes

My Computer shows the following:

EMBEDDED (C as FAT
Windows XP Embedded (El Torito) (D
EMBEDDED (E as FAT32

This all looks correct ... but should the ET disk (E be formatted FAT32?

EWFMGR -enable appropriately enables EWF on the next boot and it operates as
expected.
The FBA log shows the installed El Torito driver.
ETPREP -reset responds with "Start value for Redbook/IMAPI services reset to
zero." and
"Failed to swap El Torito disk drive letter. Error = 0x2."

Another problem is that after the reboot, EWFMGR -disable fails with error
87.

Needless to say, I can't make a post-FBA El Torito disk that works.

Any ideas?

Thanks,

Craig

 

[Slobodan Brcin]

Just to problem with EWFMGR -disable

ewfmgr C: -commitanddisable

Slobodan

 

[Dan Simpson [MS]]

The Etprep error "failed to swap El Torito disk drive letter" is a known
issue. In most cases, it reports as failed when it did in fact succeed.

Your E: does not need to be FAT16. Only your C: must be FAT16/BIGDOS.

After verifying that EWF works, disable EWF as Slobodan suggests. Then run
etprep. Boot back to your development platform and run hd2iso again, using
your post-FBA run-time image on C:. Create your post-FBA CD-ROM and test
it. Hopefully, things should work.

Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Just to problem with EWFMGR -disable

ewfmgr C: -commitanddisable

Slobodan

Hi all,

I've been struggling with this for a while now and had some very useful info
supplied by Slobodan. This message consolidates everything in one place.

I have a target created with all of the QFEs that has the appropriate EWF
and El Torito components installed. This target boots from HD successfully
with and without EWF enabled ... EWF works correctly too. I've used
Slobodan's approach for enabling EWF without the interim step of

creating

an
EWF partition because of the problem I had with the "standard" approach
described in XPe help ... EWFMGR C: would always come up blank. I also

did

a
low-level format on the HD so that variable was eliminated.

Anyway after FBA completes, my system configuration is as follows:

EWFMGR

No EWF volume is detected ... this is what I expect.

EWFMGR C:

Type RAM
State DISABLED
Volume ID 4C 98 74 5D 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
MaxLevels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes

My Computer shows the following:

EMBEDDED (C as FAT
Windows XP Embedded (El Torito) (D
EMBEDDED (E as FAT32

This all looks correct ... but should the ET disk (E be formatted FAT32?

EWFMGR -enable appropriately enables EWF on the next boot and it

operates

as
expected.
The FBA log shows the installed El Torito driver.
ETPREP -reset responds with "Start value for Redbook/IMAPI services

reset

to
zero." and
"Failed to swap El Torito disk drive letter. Error = 0x2."

Another problem is that after the reboot, EWFMGR -disable fails with error
87.

Needless to say, I can't make a post-FBA El Torito disk that works.

Any ideas?

Thanks,

Craig

 

[Craig]

Dan,

In our case, I've believe that Etprep is giving the "failed to swap El
Torito disk drive letter" becase it is indeed failing to swap the disk drive
letter. This is confirmed because the system still boots successfully from
the HD after running Etprep.

I'm assuming that the drive letters to be swapped are C: and the CD drive
.... in the latest configuration that's E: ... the ET drive is now F:
Etprep does this by flipping keys in HKLM/System/MountedDevices. I've
tinkered with this by manually flipping the \DosDevices\C: with
\DosDevices\E:, and the system then tries to boot from HD, but hangs at the
Welcome screen. What exactly does Etprep do to the registry?

What else can be done to overcome this problem? Note that I have gone
through this process sucessfully in the past using the "stock" procedure
explained in TD help. The first time was during the Advanced XPe Class
offered by A7 Engineering.

Thanks,

Craig

The Etprep error "failed to swap El Torito disk drive letter" is a known
issue. In most cases, it reports as failed when it did in fact succeed.

Your E: does not need to be FAT16. Only your C: must be FAT16/BIGDOS.

After verifying that EWF works, disable EWF as Slobodan suggests. Then run
etprep. Boot back to your development platform and run hd2iso again, using
your post-FBA run-time image on C:. Create your post-FBA CD-ROM and test
it. Hopefully, things should work.

Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Just to problem with EWFMGR -disable

ewfmgr C: -commitanddisable

Slobodan

Hi all,

I've been struggling with this for a while now and had some very

useful
info

supplied by Slobodan. This message consolidates everything in one place.

I have a target created with all of the QFEs that has the appropriate EWF
and El Torito components installed. This target boots from HD successfully
with and without EWF enabled ... EWF works correctly too. I've used
Slobodan's approach for enabling EWF without the interim step of

creating

an
EWF partition because of the problem I had with the "standard" approach
described in XPe help ... EWFMGR C: would always come up blank. I also

did

a
low-level format on the HD so that variable was eliminated.

Anyway after FBA completes, my system configuration is as follows:

EWFMGR

No EWF volume is detected ... this is what I expect.

EWFMGR C:

Type RAM
State DISABLED
Volume ID 4C 98 74 5D 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
MaxLevels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes

My Computer shows the following:

EMBEDDED (C as FAT
Windows XP Embedded (El Torito) (D
EMBEDDED (E as FAT32

This all looks correct ... but should the ET disk (E be formatted FAT32?

EWFMGR -enable appropriately enables EWF on the next boot and it

operates

as
expected.
The FBA log shows the installed El Torito driver.
ETPREP -reset responds with "Start value for Redbook/IMAPI services

reset

to
zero." and
"Failed to swap El Torito disk drive letter. Error = 0x2."

Another problem is that after the reboot, EWFMGR -disable fails with error
87.

Needless to say, I can't make a post-FBA El Torito disk that works.

Any ideas?

Thanks,

Craig

 

[Rob Neff]

Craig,

Don't know if you're still having problems, but it's pretty close to my
scenario which is now working (knock on wood). However, I'm following the
MS example with EWF partition.

A couple comments -
* ETprep swaps the ET drive (not the CD) and C: For etprep to work, you
must boot up from the HD with an El Torito CD disk (pre-FBA is okay, as long
as the second disk image shows up in explorer or disk manager) in the
target. Otherwise it doesn't know what to flip with! (Pretty obvious when
you think of it, but it bit me once).

* You can still boot up on the HD after etprep, it depends on what's
connected and the order of boot-up devices in your BIOS. If you do boot
from the post-etprep HD, that partition (the system disk) will show up as a
non-C: drive, if etprep did its thing correctly.

I don't see what you see when running "ewfmgr" and "ewfmgr C:", but then
again, that's where we're different. I see something similiar to the how-to
example in MSDN (but the percentage is screwed up, apparently non-fatal).

Rob

Dan,

In our case, I've believe that Etprep is giving the "failed to swap El
Torito disk drive letter" becase it is indeed failing to swap the disk drive
letter. This is confirmed because the system still boots successfully from
the HD after running Etprep.

I'm assuming that the drive letters to be swapped are C: and the CD drive
... in the latest configuration that's E: ... the ET drive is now F:
Etprep does this by flipping keys in HKLM/System/MountedDevices. I've
tinkered with this by manually flipping the \DosDevices\C: with
\DosDevices\E:, and the system then tries to boot from HD, but hangs at the
Welcome screen. What exactly does Etprep do to the registry?

What else can be done to overcome this problem? Note that I have gone
through this process sucessfully in the past using the "stock" procedure
explained in TD help. The first time was during the Advanced XPe Class
offered by A7 Engineering.

Thanks,

Craig

The Etprep error "failed to swap El Torito disk drive letter" is a known
issue. In most cases, it reports as failed when it did in fact succeed.

Your E: does not need to be FAT16. Only your C: must be FAT16/BIGDOS.

After verifying that EWF works, disable EWF as Slobodan suggests. Then run
etprep. Boot back to your development platform and run hd2iso again, using
your post-FBA run-time image on C:. Create your post-FBA CD-ROM and test
it. Hopefully, things should work.

Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

Just to problem with EWFMGR -disable

ewfmgr C: -commitanddisable

Slobodan

Hi all,

I've been struggling with this for a while now and had some very useful
info
supplied by Slobodan. This message consolidates everything in one place.

I have a target created with all of the QFEs that has the

appropriate
EWF

and El Torito components installed. This target boots from HD successfully
with and without EWF enabled ... EWF works correctly too. I've used
Slobodan's approach for enabling EWF without the interim step of creating
an
EWF partition because of the problem I had with the "standard" approach
described in XPe help ... EWFMGR C: would always come up blank. I

also
did

a
low-level format on the HD so that variable was eliminated.

Anyway after FBA completes, my system configuration is as follows:

EWFMGR

No EWF volume is detected ... this is what I expect.

EWFMGR C:

Type RAM
State DISABLED
Volume ID 4C 98 74 5D 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
MaxLevels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes

My Computer shows the following:

EMBEDDED (C as FAT
Windows XP Embedded (El Torito) (D
EMBEDDED (E as FAT32

This all looks correct ... but should the ET disk (E be formatted FAT32?

EWFMGR -enable appropriately enables EWF on the next boot and it operates
as
expected.
The FBA log shows the installed El Torito driver.
ETPREP -reset responds with "Start value for Redbook/IMAPI services reset
to
zero." and
"Failed to swap El Torito disk drive letter. Error = 0x2."

Another problem is that after the reboot, EWFMGR -disable fails with error
87.

Needless to say, I can't make a post-FBA El Torito disk that works.

Any ideas?

Thanks,

Craig

 

[Craig]

Rob,

I'm able to replicate the ewf scenario using the "standard" procedure ...
ewfmgr and ewfmgr c: give me the correct indications. I also can see the
"image" drive in Explorer. Success came when I created an extended partition
sized way beyond what it should have needed and setup a too-large logical
disk in it ... something strange going on there.

Running etprep -all successfully deletes the ewf volume, but returns an
error 01 when it fails to flip the drive letters. Subsequently, the ET CD I
create gives a BSOD with the "7B" error. The claim is this means "something"
required for the boot is missing. I don't believe this since my image boots
successfully and repeatedly from HD before I run etprep.

Microsoft's statement about the failure message from etprep being a false
alarm appears to be incorrect.

Eventually I'll make this work ... it shouldn't be this hard.

Craig

Craig,

Don't know if you're still having problems, but it's pretty close to my
scenario which is now working (knock on wood). However, I'm following the
MS example with EWF partition.

A couple comments -
* ETprep swaps the ET drive (not the CD) and C: For etprep to work, you
must boot up from the HD with an El Torito CD disk (pre-FBA is okay, as long
as the second disk image shows up in explorer or disk manager) in the
target. Otherwise it doesn't know what to flip with! (Pretty obvious when
you think of it, but it bit me once).

* You can still boot up on the HD after etprep, it depends on what's
connected and the order of boot-up devices in your BIOS. If you do boot
from the post-etprep HD, that partition (the system disk) will show up as a
non-C: drive, if etprep did its thing correctly.

I don't see what you see when running "ewfmgr" and "ewfmgr C:", but then
again, that's where we're different. I see something similiar to the how-to
example in MSDN (but the percentage is screwed up, apparently non-fatal).

Rob

Dan,

In our case, I've believe that Etprep is giving the "failed to swap El
Torito disk drive letter" becase it is indeed failing to swap the disk drive
letter. This is confirmed because the system still boots successfully from
the HD after running Etprep.

I'm assuming that the drive letters to be swapped are C: and the CD drive
... in the latest configuration that's E: ... the ET drive is now F:
Etprep does this by flipping keys in HKLM/System/MountedDevices. I've
tinkered with this by manually flipping the \DosDevices\C: with
\DosDevices\E:, and the system then tries to boot from HD, but hangs at the
Welcome screen. What exactly does Etprep do to the registry?

What else can be done to overcome this problem? Note that I have gone
through this process sucessfully in the past using the "stock" procedure
explained in TD help. The first time was during the Advanced XPe Class
offered by A7 Engineering.

Thanks,

Craig

The Etprep error "failed to swap El Torito disk drive letter" is a known
issue. In most cases, it reports as failed when it did in fact succeed.

Your E: does not need to be FAT16. Only your C: must be FAT16/BIGDOS.

After verifying that EWF works, disable EWF as Slobodan suggests.

Then
run

etprep. Boot back to your development platform and run hd2iso again, using
your post-FBA run-time image on C:. Create your post-FBA CD-ROM and test
it. Hopefully, things should work.

Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.


Just to problem with EWFMGR -disable

ewfmgr C: -commitanddisable

Slobodan

Hi all,

I've been struggling with this for a while now and had some very useful
info
supplied by Slobodan. This message consolidates everything in one place.

I have a target created with all of the QFEs that has the appropriate
EWF
and El Torito components installed. This target boots from HD
successfully
with and without EWF enabled ... EWF works correctly too. I've used
Slobodan's approach for enabling EWF without the interim step of
creating
an
EWF partition because of the problem I had with the "standard" approach
described in XPe help ... EWFMGR C: would always come up blank. I also
did
a
low-level format on the HD so that variable was eliminated.

Anyway after FBA completes, my system configuration is as follows:

EWFMGR

No EWF volume is detected ... this is what I expect.

EWFMGR C:

Type RAM
State DISABLED
Volume ID 4C 98 74 5D 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
MaxLevels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes

My Computer shows the following:

EMBEDDED (C as FAT
Windows XP Embedded (El Torito) (D
EMBEDDED (E as FAT32

This all looks correct ... but should the ET disk (E be formatted
FAT32?

EWFMGR -enable appropriately enables EWF on the next boot and it
operates
as
expected.
The FBA log shows the installed El Torito driver.
ETPREP -reset responds with "Start value for Redbook/IMAPI services
reset
to
zero." and
"Failed to swap El Torito disk drive letter. Error = 0x2."

Another problem is that after the reboot, EWFMGR -disable fails with
error
87.

Needless to say, I can't make a post-FBA El Torito disk that works.

Any ideas?

Thanks,

Craig

 

[Slobodan Brcin]

How about a little test.

Find my doc on www.xpefiles.com that describes how to configure RAM EWF
without temporary partition.
If you have old EWF temp partition delete it.

Swap manually drive letters in registry. And manually enable ewf also in
registry. Shut down device.

You can read following article it can help you with drive letter swapping:
http://www.microsoft.com/windows/embedded/community/tips/xp/runtimepartition
..asp


So you can probably skip using etprep.exe, I have not tried this.

Regards,
Slobodan

Rob,

I'm able to replicate the ewf scenario using the "standard" procedure ...
ewfmgr and ewfmgr c: give me the correct indications. I also can see the
"image" drive in Explorer. Success came when I created an extended partition
sized way beyond what it should have needed and setup a too-large logical
disk in it ... something strange going on there.

Running etprep -all successfully deletes the ewf volume, but returns an
error 01 when it fails to flip the drive letters. Subsequently, the ET CD I
create gives a BSOD with the "7B" error. The claim is this means "something"
required for the boot is missing. I don't believe this since my image boots
successfully and repeatedly from HD before I run etprep.

Microsoft's statement about the failure message from etprep being a false
alarm appears to be incorrect.

Eventually I'll make this work ... it shouldn't be this hard.

Craig

Craig,

Don't know if you're still having problems, but it's pretty close to my
scenario which is now working (knock on wood). However, I'm following the
MS example with EWF partition.

A couple comments -
* ETprep swaps the ET drive (not the CD) and C: For etprep to work, you
must boot up from the HD with an El Torito CD disk (pre-FBA is okay, as long
as the second disk image shows up in explorer or disk manager) in the
target. Otherwise it doesn't know what to flip with! (Pretty obvious when
you think of it, but it bit me once).

* You can still boot up on the HD after etprep, it depends on what's
connected and the order of boot-up devices in your BIOS. If you do boot
from the post-etprep HD, that partition (the system disk) will show up

as

a
non-C: drive, if etprep did its thing correctly.

I don't see what you see when running "ewfmgr" and "ewfmgr C:", but then
again, that's where we're different. I see something similiar to the how-to
example in MSDN (but the percentage is screwed up, apparently non-fatal).

Rob

Dan,

In our case, I've believe that Etprep is giving the "failed to swap El
Torito disk drive letter" becase it is indeed failing to swap the disk drive
letter. This is confirmed because the system still boots successfully from
the HD after running Etprep.

I'm assuming that the drive letters to be swapped are C: and the CD drive
... in the latest configuration that's E: ... the ET drive is now F:
Etprep does this by flipping keys in HKLM/System/MountedDevices. I've
tinkered with this by manually flipping the \DosDevices\C: with
\DosDevices\E:, and the system then tries to boot from HD, but hangs

at
the

Welcome screen. What exactly does Etprep do to the registry?

What else can be done to overcome this problem? Note that I have gone
through this process sucessfully in the past using the "stock" procedure
explained in TD help. The first time was during the Advanced XPe Class
offered by A7 Engineering.

Thanks,

Craig

The Etprep error "failed to swap El Torito disk drive letter" is a known
issue. In most cases, it reports as failed when it did in fact succeed.

Your E: does not need to be FAT16. Only your C: must be FAT16/BIGDOS.

After verifying that EWF works, disable EWF as Slobodan suggests. Then
run
etprep. Boot back to your development platform and run hd2iso again,
using
your post-FBA run-time image on C:. Create your post-FBA CD-ROM and test
it. Hopefully, things should work.

Dan


--
This posting is provided "AS IS" with no warranties, and confers no
rights.


Just to problem with EWFMGR -disable

ewfmgr C: -commitanddisable

Slobodan

Hi all,

I've been struggling with this for a while now and had some very
useful
info
supplied by Slobodan. This message consolidates everything in one
place.

I have a target created with all of the QFEs that has the appropriate
EWF
and El Torito components installed. This target boots from HD
successfully
with and without EWF enabled ... EWF works correctly too. I've used
Slobodan's approach for enabling EWF without the interim step of
creating
an
EWF partition because of the problem I had with the "standard"
approach
described in XPe help ... EWFMGR C: would always come up blank.

I
also

did
a
low-level format on the HD so that variable was eliminated.

Anyway after FBA completes, my system configuration is as follows:

EWFMGR

No EWF volume is detected ... this is what I expect.

EWFMGR C:

Type RAM
State DISABLED
Volume ID 4C 98 74 5D 00 7E 00 00 00 00 00 00 00 00 00 00
Device Name "\Device\HarddiskVolume1" [C:]
MaxLevels 1
Clump Size 512
Current Level 1

Memory used for data 0 bytes
Memory used for mapping 0 bytes

My Computer shows the following:

EMBEDDED (C as FAT
Windows XP Embedded (El Torito) (D
EMBEDDED (E as FAT32

This all looks correct ... but should the ET disk (E be formatted
FAT32?

EWFMGR -enable appropriately enables EWF on the next boot and it
operates
as
expected.
The FBA log shows the installed El Torito driver.
ETPREP -reset responds with "Start value for Redbook/IMAPI services
reset
to
zero." and
"Failed to swap El Torito disk drive letter. Error = 0x2."

Another problem is that after the reboot, EWFMGR -disable fails with
error
87.

Needless to say, I can't make a post-FBA El Torito disk that works.

Any ideas?

Thanks,

Craig

 

[Rob Neff]

My comments are embedded:

Rob,

I'm able to replicate the ewf scenario using the "standard" procedure ...
ewfmgr and ewfmgr c: give me the correct indications. I also can see the
"image" drive in Explorer. Success came when I created an extended partition
sized way beyond what it should have needed and setup a too-large logical
disk in it ... something strange going on there.

I'm not sure exactly what you mean by success. Also, is your TD .slx file
set up for the actual size of the boot partition? (Although I got a
different error - "A problem is preventing windows from accurately checking
the license on this computer." error code 0x80090006 in this case. Not
exactly intuitive as to where it came from! But maybe by changing your
actual partition size it now matches what TD expects the image to go into.)

Running etprep -all successfully deletes the ewf volume, but returns an
error 01 when it fails to flip the drive letters. Subsequently, the ET CD I
create gives a BSOD with the "7B" error. The claim is this means "something"
required for the boot is missing. I don't believe this since my image boots
successfully and repeatedly from HD before I run etprep.

Yeah, something funny is going on here, but I'm not experienced enough to
know what. You can try the "etprep -flip" by itself of course, but I don't
think that will shed any new light on it.

Microsoft's statement about the failure message from etprep being a false
alarm appears to be incorrect.

Eventually I'll make this work ... it shouldn't be this hard.

Amen to that!

I'd try Slobodan's suggestion, since you're already familiar with his
non-EWF partition technique.

Craig



as

[snip]

 

[Craig]

I tried the "manual etprep disk flip" registry edit last week ... tried it
again this morning and it worked (mostly).

After FBA-before "etprep" my config was as follows (one physical HD
installed):

Disk 0: 500 MB "C" 2000 MB "D"
CD: "E"
Disk 1: 500 MB "F"

Did the reg edit to flip the values of C and F keys
ewfmgr c: -enable
etprep -delete deleted 1 EWF partition
etprep - reset ... logfile shows redbook reset and failed to flip responses
manually powered off
booted to XPe CD
hd2iso to create image
moved image to host ... burned ET CD
ET CD boots to BSOD on target

Post "manual etprep" the target boots from HD with some message boxes about
not being able to write to C: ... EWF is running

Disk 0: 500 MB "F" 2000 MB "D"
CD: E
Disk 1: 500 MB "C"

This looks like the flip worked.

ewfmgr f: returns the appropriate status about the enabled ewf volume

So it's a matter of figuring out the BSOD.

Craig

My comments are embedded:

Rob,

I'm able to replicate the ewf scenario using the "standard" procedure ....
ewfmgr and ewfmgr c: give me the correct indications. I also can see the
"image" drive in Explorer. Success came when I created an extended partition
sized way beyond what it should have needed and setup a too-large logical
disk in it ... something strange going on there.

I'm not sure exactly what you mean by success. Also, is your TD .slx file
set up for the actual size of the boot partition? (Although I got a
different error - "A problem is preventing windows from accurately checking
the license on this computer." error code 0x80090006 in this case. Not
exactly intuitive as to where it came from! But maybe by changing your
actual partition size it now matches what TD expects the image to go into.)

Running etprep -all successfully deletes the ewf volume, but returns an
error 01 when it fails to flip the drive letters. Subsequently, the ET

CD

I
create gives a BSOD with the "7B" error. The claim is this means "something"
required for the boot is missing. I don't believe this since my image boots
successfully and repeatedly from HD before I run etprep.

Yeah, something funny is going on here, but I'm not experienced enough to
know what. You can try the "etprep -flip" by itself of course, but I don't
think that will shed any new light on it.

Microsoft's statement about the failure message from etprep being a false
alarm appears to be incorrect.

Eventually I'll make this work ... it shouldn't be this hard.

Amen to that!

I'd try Slobodan's suggestion, since you're already familiar with his
non-EWF partition technique.

Craig



as
long as

[snip]

 

[Slobodan Brcin]

I'm curious.

Why ewfmgr f: returns correct status?
If everything is ok it should be C: that is protected, right?

Check your ARC path, also have you rewired your CD drive, and removed HDD?

Regards,
Slobodan

I tried the "manual etprep disk flip" registry edit last week ... tried it
again this morning and it worked (mostly).

After FBA-before "etprep" my config was as follows (one physical HD
installed):

Disk 0: 500 MB "C" 2000 MB "D"
CD: "E"
Disk 1: 500 MB "F"

Did the reg edit to flip the values of C and F keys
ewfmgr c: -enable
etprep -delete deleted 1 EWF partition
etprep - reset ... logfile shows redbook reset and failed to flip responses
manually powered off
booted to XPe CD
hd2iso to create image
moved image to host ... burned ET CD
ET CD boots to BSOD on target

Post "manual etprep" the target boots from HD with some message boxes about
not being able to write to C: ... EWF is running

Disk 0: 500 MB "F" 2000 MB "D"
CD: E
Disk 1: 500 MB "C"

This looks like the flip worked.

ewfmgr f: returns the appropriate status about the enabled ewf volume

So it's a matter of figuring out the BSOD.

Craig

My comments are embedded:

Rob,

I'm able to replicate the ewf scenario using the "standard" procedure ...
ewfmgr and ewfmgr c: give me the correct indications. I also can see the
"image" drive in Explorer. Success came when I created an extended partition
sized way beyond what it should have needed and setup a too-large logical
disk in it ... something strange going on there.

I'm not sure exactly what you mean by success. Also, is your TD .slx file
set up for the actual size of the boot partition? (Although I got a
different error - "A problem is preventing windows from accurately checking
the license on this computer." error code 0x80090006 in this case. Not
exactly intuitive as to where it came from! But maybe by changing your
actual partition size it now matches what TD expects the image to go into.)

Running etprep -all successfully deletes the ewf volume, but returns an
error 01 when it fails to flip the drive letters. Subsequently, the ET

CD

I
create gives a BSOD with the "7B" error. The claim is this means "something"
required for the boot is missing. I don't believe this since my image boots
successfully and repeatedly from HD before I run etprep.

Yeah, something funny is going on here, but I'm not experienced enough to
know what. You can try the "etprep -flip" by itself of course, but I don't
think that will shed any new light on it.

Microsoft's statement about the failure message from etprep being a false
alarm appears to be incorrect.

Eventually I'll make this work ... it shouldn't be this hard.

Amen to that!

I'd try Slobodan's suggestion, since you're already familiar with his
non-EWF partition technique.

Craig



Craig,

Don't know if you're still having problems, but it's pretty close to my
scenario which is now working (knock on wood). However, I'm

following
the

MS example with EWF partition.

A couple comments -
* ETprep swaps the ET drive (not the CD) and C: For etprep to work, you
must boot up from the HD with an El Torito CD disk (pre-FBA is okay, as
long
as the second disk image shows up in explorer or disk manager) in the
target. Otherwise it doesn't know what to flip with! (Pretty obvious
when
you think of it, but it bit me once).

* You can still boot up on the HD after etprep, it depends on what's
connected and the order of boot-up devices in your BIOS. If you do boot
from the post-etprep HD, that partition (the system disk) will show

up
as

a
non-C: drive, if etprep did its thing correctly.

I don't see what you see when running "ewfmgr" and "ewfmgr C:", but then
again, that's where we're different. I see something similiar to the
how-to
example in MSDN (but the percentage is screwed up, apparently non-fatal).

Rob

[snip]

 

[Rob Neff]

ewfmgr F: returning enabled status is normal (I think). At this point, the
drive letters are reversed, and the system reboots. But it's still looking
for the hard drive as the boot device, so it boots the HD which is now F:

EWF is enabled for whatever the system disk is (as I understand it), so when
the HD is removed and you make an El Torito CD out of it, then put it back
in the CD drive with no HD present (or change the BIOS to look at the CD
first), then it boots up to the C: drive and everything is normal again (ewf
enabled for the system C: drive).

I also get the msgs about not being able to write to C:, this is apparently
because some things on the system disk are hardcoded to the C: drive, which
is now the (unwriteable) El Torito image, not the HD.

Rob

I'm curious.

Why ewfmgr f: returns correct status?
If everything is ok it should be C: that is protected, right?

Check your ARC path, also have you rewired your CD drive, and removed HDD?

Regards,
Slobodan

I tried the "manual etprep disk flip" registry edit last week ... tried it
again this morning and it worked (mostly).

After FBA-before "etprep" my config was as follows (one physical HD
installed):

Disk 0: 500 MB "C" 2000 MB "D"
CD: "E"
Disk 1: 500 MB "F"

Did the reg edit to flip the values of C and F keys
ewfmgr c: -enable
etprep -delete deleted 1 EWF partition
etprep - reset ... logfile shows redbook reset and failed to flip responses
manually powered off
booted to XPe CD
hd2iso to create image
moved image to host ... burned ET CD
ET CD boots to BSOD on target

Post "manual etprep" the target boots from HD with some message boxes about
not being able to write to C: ... EWF is running

Disk 0: 500 MB "F" 2000 MB "D"
CD: E
Disk 1: 500 MB "C"

This looks like the flip worked.

ewfmgr f: returns the appropriate status about the enabled ewf volume

So it's a matter of figuring out the BSOD.

Craig


procedure
... ET
CD to
my work,
you okay,
as do
boot

show

up

as
a
non-C: drive, if etprep did its thing correctly.

I don't see what you see when running "ewfmgr" and "ewfmgr C:",

but
then

again, that's where we're different. I see something similiar to the
how-to
example in MSDN (but the percentage is screwed up, apparently
non-fatal).

Rob

[snip]