Boot CD

[DPM]

I need to clarify something: does hd2iso need to run on the target that has
the 650 mb HD CD partition, or can I copy the post-FBA image to another
computer and run hd2iso there?

Also, can the oscdimg utility that comes with WinPE be used to build the ISO
image? I tried it, but the resultant CD does not boot. Is there a reason?

Thanks.

 

[DPM]

One other question: does "etprep /all" enable EWF, or do I need to execute
"ewfmgr c: -enable" before etprep?

Thanks,
Dean

 

[DPM]

Well, I think I followed the procedure to build a bootable CD correctly:
1. Created a 627 mb partition on my target HD, formatted in FAT32 (C;
2. Built my image, copied it to the boot partition;
3. Placed a CD with a previous copy of my image in the CD drive (this CD was
post-FBA - does it matter?);
4. FBA ran and rebooted into my shell without errors;
5. Removed the ElTorito CD and executed "ewfmgr c: -enable" and "etprep
/all";
6. Rebooted into WinPE and ran hd2iso to capture the image;
7. Used Nero to burn .iso to CD;
8. Booted CD, got "Stop 0x0000007B".

Can anyone see what I may have done wrong?

Thanks,
Dean

 

[Stefan Klein]

Its not intended to enable EWF manually. If its not running
automatically you've done something wrong. Check fba.log and ewfmgr
output like stated in the manual.

If you're familiar with vmware it may dramatically speed up creation time.

 

[DPM]

Its not intended to enable EWF manually. If its not running automatically
you've done something wrong. Check fba.log and ewfmgr output like stated
in the manual.

After FBA rebooted into my shell EWF was running, but disabled - which makes
sense, because I told TD to start it disabled.

So what starts it: etprep? I've seen some older threads in this newsgroup
that seemed to imply that "ewfmgr c: -enable" was necessary and some that
said it wasn't. Which is true?

If you're familiar with vmware it may dramatically speed up creation time.

I've used vmware and VPC, but I'm unclear how they can help. I still need
to run FBA "on the metal", as far as I can tell.

Thanks,
Dean

 

[Stefan Klein]

I created my bootcd with vmware. I included both 'hardware devices'
from vmware and my target machine. Before you can use hd2iso you'd have
to mount the vmware hdd (vmware-mount.exe - google it) in your host OS
and copy the content to your SDI harddisk since this is the only virtual
harddisk that will be detected by hd2iso. The SDI hdd must be
partitioned and set active (bootable) before. Leave some MB
unpartitioned (at least 8MB). You can always (quick) format your sdi hdd
without loosing those properties.

EWF overlay mode must be set to 'RAM' not 'RAM (Reg)'. It didn't work
for me when setting to 'Reg' mode. The manual is confusing in that
point. On one hand it says to leave 'ewf overlay mode' untouched (that
is RAM mode) on the other hand it says 'El Torito supports EWF RAM Reg
Mode only. EWF Disk and RAM modes are not supported in El Torito
configurations'. That gave me quite a hard time initially...

I didn't have had to enable EWF manually. The second boot should enable
it automatically i think. You just have to check for EWF errors, invoke
bootprep, shutdown the system, copy it to your SDI and use hd2iso.

The 'Enhanced Write Filter' component settings require to set 'Start EWF
enabled' to '0'. This should answer your question.

Use the manuals tutorial ('Windows XP Embedded Platform' help file):
Development Process > Deploy a Run-Time Image > Bootable CD-ROM > How to
Create a Bootable CD-ROM

 

[DPM]

Stefan,

I've followed the tutorial exactly, but my CD still fails with stop code 7B.
I tried both EWF RAM and RAM(reg) - no difference, in my case.

I'm beginning to think that this might be a motherboard issue. I'll
probably try this on another MB just to see if I CAN build a CD image that
boots.

Grr.

Thanks,
Dean