Re: Problems with Booting XPe from CD-ROM

Tech-Archive recommends: Fix windows errors by optimizing your registry

Alexander,

First of all, nice description of all the steps you did. Very clear and easy
to read.

Two things there concerned me:

1) It sounded right that EWF showed protecting drive F: after reboot after
etprep launch. EWF protects by ARC path. After etprep swap and reboot you
hard disk partition is assigned F: letter, CDROM is on C:, right?

The easiest way I usually set this up is not using etprep at all. Just
simply build an image that includes all the components you mentioned, run
though FBA and then run ewfmgr C: /enable. The same time go to registry and
delete MountedDevices key. Then reboot the device and make sure EWF RAM Reg
is protecting you drive C: (you can safely reboot many times here).
Now you can capture the image and burn it on CD.

2) 7B BSOD doesn't seem to be related to the above problem unless etprep did
something else wrong there.
Again, I'd eliminate the step with etprep and just manually delete the
HKML\System\MountedDevices key instead.

Let us know if the above doesn't work for you.

Regards,
KM

Hello KM,

I have generated a new image depending on the imported Target Analyzer
Informations with the following additional components:
El Torito CD Support
Winlogon Sample Macro Component (there unchecking "Standard PC" in the
setting because the target is an "ACPI Uniprocessor PC")
CMD - Windows Command Processor
Registry Editor

In the settings of the EWF I have unchecked "Start EWF Enabled" and
set the Overlay Type to RAM(Reg). Furthermore I have disabled the "FBA
DLL/COM Registration" in the Resources of EWF. As described in the
website how to configure EWF RAM Reg mode I have also enabled NTLDR
and disabled EWF NTLDR.

After having booted from this image (with the Pre-FBA image in the
ISO9660/El Torito format on CD in the drive) and letting the FBA phase
to pass I got the following results from the EWF manager:

ewfmgr:
RAM(Reg) Configuration
Device Name "\Device\HarddiskVolume1"[C:]
HORM Not supported

ewfmgr c:
Type RAM(Reg)
State DISABLED

The CD drive has got drive E: and the El Torito disk has been
recognized as seen in fbalog.txt.

Then going on:

ewfmgr c: -enable

ewfmgr c: (to test the effect of the enable operation)
Type RAM(Reg)
State DISABLED
Boot Command ENABLE
so the command has been accepted but the state has not changed!

etprep /all
This command has indicated no error and the automatic reboot passed on
to the desired state but sometimes the following message popped up:

Windows - Delayed Write Failed
Windows was unable to save all the date for the file C:\WINDOWS
\system32. The data has been lost. This error may be caused by a
failure of your computer hardware or network connection. Please try to
save this file elsewhere.

I have also saved C:\Windows\system32\config before and after "etprep /
all". An offline analysis by regedit showed that in HKLM\System
\MountedDevices the values for \DosDevices\C: and \DosDevices\F: have
been changed indeed so the swapping seemed to work well.

After the reboot I asked again the EWF manager:

ewfmgr c:
Failed getting protected volume configuration with error 1. Incorrect
function

ewfmgr f:
Protected Volume Configuration
Type RAM(Reg)
State ENABLED
Boot Command NO_CMD

I believe that the error is that not the (now) C: partition (namely
the CD drive) is protected by EWF, but the (now) F: partition, that is
the former boot partition C: on disk. So the cooperation of swapping
the drives and enabling EWF seemed not to be ok.

Nevertheless I have made a ISO9660/El Torito image of the post FBA
image on disk by HD2ISO and burnt it to CD.
By booting from this CD I got again my old BSOD friend:

STOP: 0x0000007B (0xF7C45528, 0xC0000034, 0x00000000, 0x00000000)

I have tested also other things like adapting the Boot partition size
in the Target deivce settings to the exact value of the boot partition
on disk or to use NTLDR instead of EWF NTLDR but nothing helped.

If you have no more idea which can help me I think that this was my
last turn and I'll give up the Boot from CD business.

Hope you or any other can help me once more.

Regards,
Alexander




.

Relevant Pages

  • Re: Problems with Booting XPe from CD-ROM
    ... 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. ... With the two partitions on the disk, I assume the rest of the drive is left unpartioned. ... that USB drives will not function. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Problems with Booting XPe from CD-ROM
    ... El Torito CD Support ... In the settings of the EWF I have unchecked "Start EWF Enabled" and ... 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: 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)
  • Problems with Booting XPe from CD-ROM
    ... target is the Pentium based VMEBus Single Board Computer VR9 from SBS, ... informations about my target board and then adding the necessary EWF ... Now my el torito disk had been found and ewfmgr ... that USB drives will not function. ...
    (microsoft.public.windowsxp.embedded)