Problems with Booting XPe from CD-ROM

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.

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@gmx.de> wrote in message
news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
> 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.
>

Hi Alexander. I'll try to address your issues below.

First off, if you're using a USB CD-ROM drive for your bootable CD-ROM
device, you will need to ensure that you're using Feature Pack 2007, which
includes support for booting from USB devices. Make sure you include the
"USB 2.0 Boot" component in your runtime, which will bring in all of the
components needed to support this feature.

There should be no particular reason why EWF should fail as it appears to
have here while using the Command Shell. The specific error you encountered
here may have been due to a bad FBA run during a previous runtime setup -
usually you can just redeploy your runtime (or rebuild and redeploy if
necessary), or you can also delete the EWF partition using DISKPART from the
safebuild. The EWF partition is setup during FBA.

As for the failure to swap drive letters: This may have something to do with
the USB support (or lack thereof), since your CD-ROM drive is connected via
USB.

Also, two common causes of drive-letter-swap failure are that the Pre-FBA El
Torito CD wasn't in the drive during FBA *AND* when etprep was run, or that
the Pre-FBA CD was either a different size than the hard drive partition
being processed (500 MB on CD vs. 600 MB on the HDD) or has a different El
Torito signature value (settable in Target Designer - we recommend you leave
it on the default setting).

In the first case above, you need to make sure the Pre-FBA CD is in the
drive right from the start of FBA, and that it remains there until FBA is
finished. You can take the CD out to install software or perform other
operations once FBA is finished, but you'll need to make sure you put it
back in before running etprep -all. This is because etprep scans all of the
devices to find the El Torito volume so it knows which drive letters to
swap. I realize this is an inconvenient process, but it's unfortunately the
way this one works.

As for partition/CD sizes and signatures: Internally, Windows identifies a
volume by both its signature (this gets set during FBA and can be modified
in the El Torito component) and by its partition size. A different
partition size will yield a different overall identifier. During FBA, the
system does a scan of all volumes and records the IDs of the volumes in each
physical device. It will record an entry for the El Torito volume on the
Pre-FBA CD at this time and associate it with the physical CD-ROM device and
its arc path. When you go to swap the drive letters with etprep, this scan
is performed again, and etprep then compares the active partition with the
El Torito volume if it finds one. The IDs have to match between the two in
order for the letter swap to occur - otherwise, the process will fail and
nothing will be swapped. This is why the partition size and signature of
the primary partition have to match those of the Pre-FBA CD. Note that the
Pre-FBA CD does not actually have to be bootable or contain any
information - it just needs to be a clone of the primary partition's layout.

I successfully tested a USB-based El Torito Boot scenario during testing of
Feature Pack 2007, and found that the only additional step in the process
was to make sure the USB 2.0 Boot component and its dependencies were
included in the runtime. I hope all of this helps.

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

This posting is provided "AS IS" with no warranties, and confers no rights.
"Alexander" <boegelsack@gmx.de> wrote in message
news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
> 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.
>

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@sjjmicro.com> wrote in message
news:e4UAMp8QHHA.1208@TK2MSFTNGP03.phx.gbl...
>
> 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@gmx.de> wrote in message
> news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>> 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.
>>
>
>

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@online.microsoft.com> wrote in message
news:eeDB8P$QHHA.4756@TK2MSFTNGP03.phx.gbl...
> 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@sjjmicro.com> wrote in message
> news:e4UAMp8QHHA.1208@TK2MSFTNGP03.phx.gbl...
>>
>> 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@gmx.de> wrote in message
>> news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>>> 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.
>>>
>>
>>
>
>

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@sjjmicro.com> wrote in message news:%23Kt2bc$QHHA.4916@TK2MSFTNGP03.phx.gbl...
> 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@online.microsoft.com> wrote in message news:eeDB8P$QHHA.4756@TK2MSFTNGP03.phx.gbl...
>> 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@sjjmicro.com> wrote in message news:e4UAMp8QHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>
>>> 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@gmx.de> wrote in message news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>>>> 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.
>>>>
>>>
>>>
>>
>>
>
>

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. 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.

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@nospam_yahoo.com> wrote in message
news:OXug0o$QHHA.4448@TK2MSFTNGP04.phx.gbl...
> 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@sjjmicro.com> wrote in message
> news:%23Kt2bc$QHHA.4916@TK2MSFTNGP03.phx.gbl...
>> 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@online.microsoft.com> wrote in message
>> news:eeDB8P$QHHA.4756@TK2MSFTNGP03.phx.gbl...
>>> 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@sjjmicro.com> wrote in message
>>> news:e4UAMp8QHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>>
>>>> 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@gmx.de> wrote in message
>>>> news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>>>>> 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.
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

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@nospam_yahoo.com> wrote in message news:OXug0o$QHHA.4448@TK2MSFTNGP04.phx.gbl...
>> 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@sjjmicro.com> wrote in message news:%23Kt2bc$QHHA.4916@TK2MSFTNGP03.phx.gbl...
>>> 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@online.microsoft.com> wrote in message news:eeDB8P$QHHA.4756@TK2MSFTNGP03.phx.gbl...
>>>> 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@sjjmicro.com> wrote in message news:e4UAMp8QHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>>>
>>>>> 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@gmx.de> wrote in message news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>>>>>> 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.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Yeah, the problems were all over the place. I could get XPe to boot from CD
on some systems and not others. I even tried the clean registry, but even
that didn't work.

Now that CD-boot seems stable in FP 2007. It would be nice to make the El
Torito driver a non-PnP driver like it was in NT Embedded so we wouldn't
need the Pre-FBA CD. Booting from CD is slow, and with USB boot available, I
am not sure how long CD-Boot will be around.

Regards,

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


"KM" <konstmor@nospam_yahoo.com> wrote in message
news:eagdbhARHHA.4276@TK2MSFTNGP02.phx.gbl...
> 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@nospam_yahoo.com> wrote in message
>> news:OXug0o$QHHA.4448@TK2MSFTNGP04.phx.gbl...
>>> 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@sjjmicro.com> wrote in message
>>> news:%23Kt2bc$QHHA.4916@TK2MSFTNGP03.phx.gbl...
>>>> 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@online.microsoft.com> wrote in message
>>>> news:eeDB8P$QHHA.4756@TK2MSFTNGP03.phx.gbl...
>>>>> 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@sjjmicro.com> wrote in message
>>>>> news:e4UAMp8QHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>>>>
>>>>>> 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@gmx.de> wrote in message
>>>>>> news:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>>>>>>> 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.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Hello Sean,

many thanks for your prompt response. I'm very happy to communicate
directly with the author of the book which is the basis of all my XPe
efforts.

Here are the answers to your questions:

1. I use XP embedded SP1 but am preparing for using SP2 in the hope
that my problems are solved then. I don' t know what FP2007 is. From
another answer I got the info that's is the "Feature Pack 2007". I
never heard about that. Is that's still newer than SP2? And where can
I get it? And is this compatible also with SP1 or only with SP2?

2. Yes, the rest of the drive is unpartitioned.

3. Yes, EWF is set to NOT run on start (Start EWF Enable is not
checked)

4. This I have not made because it is not in your book, but I will try
it. Is this step also necessary for SP1?

5. Yes, I used the HD2ISO utilty to create the ISO image.

Regards,

Alexander

On 29 Jan., 18:24, "Sean Liming \(eMVP\)" <sean_lim...@sjjmicro.com>
wrote:
> 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 Limingwww.sjjmicro.com/www.seanliming.com
> XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
> Toolkit
>
> "Alexander" <boegels...@gmx.de> wrote in messagenews:1170065974.657568.168590@m58g2000cwm.googlegroups.com...
>
> > 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.