Re: Problems with Booting XPe from CD-ROM

Sean,

Run EWFMGR before ETPREP -all in the same session. It must be done before you reboot the OS; otherwise you cannot get here from
there.

Yup, this is what I was trying to uncover. Thanks for confirming.

Like I said someone else (I think it was Slobodan) found this trick. I tried it in SP2, and it worked. The reason you had to
delete the keys was because ETPREP did do it what was suppose to do.

Exactly. Etprep (RTM, SP1) wasn't doing that for me (and some others here) so we had to clean the MountedDevices key manually. But
my point was that this was the only trick required.

--
=========
Regards,
KM


In FP2007, the steps in the book still hold - my only addition is the EWFMGR. If EWFMGR c: -enable step is not needed, great! One
less step out of the 2 dozen.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit


"KM" <konstmor@xxxxxxxxxxxxxxxx> wrote in message news:OXug0o$QHHA.4448@xxxxxxxxxxxxxxxxxxxxxxx
Sean,

When you say "run EWFMGR c: -enable *before* Etrpep -all" do you mean the same session or with a reboot in between? I can't
imagine a reboot there, though. But I can't see a need for ewfmgr command during one session either.

For me it'd always been more stable to manually delete the MountedDevices key rather then running etprep commands when it comes
to EWF RAM Reg more.

--
=========
Regards,
KM


"Sean Liming (eMVP)" <sean_liming@xxxxxxxxxxxx> wrote in message news:%23Kt2bc$QHHA.4916@xxxxxxxxxxxxxxxxxxxxxxx
Booting from CD-ROM has always been a hit or miss task. FP2007 seems to be much more stable.
With SP1, I didn't find the need for the EWFNGR step as you pointed out, but others found it was needed. Creating a bootable
CD-ROM with SP2 was much worse. ETPREP was notworking as expected. Slobodan and others had found all sorts of tricks with
registry keys that had to be done. If you look at the history, running EWFMGR before ETPREP was part of the solution.

I have kept the EWFMGR step as a legacy. It works, and it it works it doesn't need to be fixed. The rest of the steps still
hold.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit


"Matt Kellner [MS]" <mattkell@xxxxxxxxxxxxxxxxxxxx> wrote in message news:eeDB8P$QHHA.4756@xxxxxxxxxxxxxxxxxxxxxxx
Sean: Regarding step 4 below: I haven't seen a need to manually issue an enable command to EWFMGR when running etprep. Etprep
takes care of adding the registry keys needed to run in RAM (Reg) mode and deletes the EWF volume, negating any changes to
EWF's RAM-mode configuration, so that call to EWFMGR would seem superfluous. Could you briefly explain what that extra step is
about? (Or is it that the extra step was needed in SP1 and is no longer needed in SP2 and above?)

--
Matt Kellner
SDET, Microsoft Windows XP Embedded Test Team

This posting is provided "AS IS" with no warranties, and confers no rights.
"Sean Liming (eMVP)" <sean_liming@xxxxxxxxxxxx> wrote in message news:e4UAMp8QHHA.1208@xxxxxxxxxxxxxxxxxxxxxxx

1. Are you using FP2007? There have been some improvements.
2. With the two partitions on the disk, I assume the rest of the drive is left unpartioned. Is this Correct?
3. Is EWF set to NOT run on start?
4. One extra step that has changed the instructions from SP1 to SP2 to FP2007, is the need to run EWFMGR c: -enable before
Etrpep -all.
5. Are you using the HD2ISO utility to create teh ISO images?

When the image reboots after etprep, the image on the drive will almost always BOSD. there is nothing that can be done to the
final image. Just create the final ISO.

Why Taskmanager Shell is behaving differently that Command shell is a bit of a mistery. I just went through the steps for a
customer recently and Command Shell worked just fine.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit



"Alexander" <boegelsack@xxxxxx> wrote in message news:1170065974.657568.168590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I've tried to boot a XP Embedded image from CD-ROM like described in
Chapter 11 of the XP Embedded Advanced book from Sean D. Liming. My
target is the Pentium based VMEBus Single Board Computer VR9 from SBS,
the HD is a 6 GB Microdrive from Hitachi, my drive is the DVD-R/-RW
drive SD-R6112 from Toshiba. Because there is no possiblity to connect
further IDE devices to that board, I've connected the driver via an
adapter to an USB port of the target board.
The image has been generated by first importing the Target Analyzer
informations about my target board and then adding the necessary EWF
and El Torito components and the Command Shell like described in the
book.
The first problem I have encountered is that after having booted the
image from disk with the Pre-FBA El Torito Disk in the drive ewfmgr
reported "Unable to find an Ewf volume" and ewfmgr c: reported "Failed
getting protected volume configuration with error 1" also the contents
of fbalog.txt showed that the EWF volume had been created. Diskpart
also found the 32 KB EWF volume after the two primary partitions I had
created on the disk (C: 160 MB, D: 900 MB). Furthermore the El Torito
disk had not been found.
I've solved this problem by replacing the Command Shell component by
the Task Manager Shell like in the EWF example in Chapter 10 of the
book from Sean Liming. Now my el torito disk had been found and ewfmgr
and ewfmgr c: yielded the expected outputs like described in the book.
In the explorer the following three partitions were visible:
C: 160 MB
D: 899 MB
F: 160 MB
E is the DVD drive. I assume that F is the El Torito drive generated
by the El Torito driver.

But now if I call etprep -all I get the following messages:
Deleted EWF partitions = 1
Start value for Redbook/IMAPI services has been reset to zero.
Failed to swap El Torito disk drive letter. Error = 0x1.

After that the system automatically reboots which ends with a BSOD
with the following outputs:
STOP: c000007b {Bad Image}
The application or DLL \??\C:\WINDOWS\system32\shsvcs.dll is not a
valid windows image. Please check this against your installation
diskette.

Every reboot brings this Blue Screen again.

So my two questions are: Why I need the Task Manager Shell to let the
El Torito Disk found and let ewfmgr find the EWF volume and why the
swapping of the disk drive letters get failed (I assume that the Blue
Screen is a consequence of this). I've read in a message on this topic
that USB drives will not function. Is this really true?

Who can help me? Any hint will be appreciated.













.

Relevant Pages

  • Re: Problems with Booting XPe from CD-ROM
    ... EWF is set to NOT run on start (Start EWF Enable is not ... With the two partitions on the disk, I assume the rest of the drive is ... Now my el torito disk had been found and ewfmgr ... that USB drives will not function. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Problems with Booting XPe from CD-ROM
    ... EWF is set to NOT run on start (Start EWF Enable is not ... With the two partitions on the disk, I assume the rest of the drive is ... Now my el torito disk had been found and ewfmgr ... that USB drives will not function. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Problems with Booting XPe from CD-ROM
    ... EWF protects by ARC path. ... After etprep swap and reboot you ... the drives and enabling EWF seemed not to be ok. ... I have tested also other things like adapting the Boot partition size ...
    (microsoft.public.windowsxp.embedded)
  • Re: EWF problem
    ... EWF will protect a partition by ARC path, ... Just make sure to match the Arc path from boot.ini when you switch to boot from CF to the Arc path in EWF registry branch. ... The errors you are seeing from ewfmgr for other drives are expected. ... do I change the disk() or rdiskparameter to '1'? ...
    (microsoft.public.windowsxp.embedded)
  • Re: 3B2 Disks
    ... being able to read the disk in its present format. ... 2 MFM drives on a custom controller. ... SCSI came much later as an add on card. ...
    (comp.sys.3b1)