Stop 7B Error after Creating ETPREPed CD

[Santiago Allen]

Hi All,

This one is a little confusing to me simply because a more primitive
version of this image worked fine. Here is my problem:


1) I create My image have the HD on prim master and the cD on prim
slave (both devices on cable select) and let it run through FBA. After
It is done I ETPrep the drive and HD2ISO the drive.

2) The Created CD will report a Stop 7b on Bootup. If I remap the
Cable so that CD-ROM is now Prim Master, no Stop 7b, but there will be
a Windows Logon Stop c000021a instead.

Like I said, earlier Incarnations of this Same Image do not have these
problems. In fact, I can swap the CD-ROM from slave to master and not
receive any errors. The image is built on top of Minlogon Sample
Macro. The difference between this Image and previous working image is
that this image has added Developers Tools (DirectX Diagnostic Utility,
Registry Editor, Windows Accessories, Device Manager, System Control
Panel, and all dependencies of these components). Is this the
ntdetect.com problem described in other postings or something else?

Thanks in advanced,

Santiago

 

[Gordon Smith \(eMVP\)]

Hi All,

This one is a little confusing to me simply because a more primitive
version of this image worked fine. Here is my problem:


1) I create My image have the HD on prim master and the cD on prim
slave (both devices on cable select) and let it run through FBA.
After It is done I ETPrep the drive and HD2ISO the drive.

2) The Created CD will report a Stop 7b on Bootup. If I remap the
Cable so that CD-ROM is now Prim Master, no Stop 7b, but there will be
a Windows Logon Stop c000021a instead.

Like I said, earlier Incarnations of this Same Image do not have these
problems. In fact, I can swap the CD-ROM from slave to master and not
receive any errors. The image is built on top of Minlogon Sample
Macro. The difference between this Image and previous working image
is that this image has added Developers Tools (DirectX Diagnostic
Utility, Registry Editor, Windows Accessories, Device Manager, System
Control Panel, and all dependencies of these components). Is this the
ntdetect.com problem described in other postings or something else?

Thanks in advanced,

Santiago

What you're supposed to do is:
1. Build your image and copy it to the HD.
2. Use HD2ISO to burn a CD of this image (before FBA was run).
3. Reboot to run FBA ***from the hard drive*** having your "pre-fba" CD in
the drive.
4. Finalize your image after FBA runs
5. ETPrep
6. Use HD2ISO to burn a CD of this image (after FBA was run and after
ETPrep).

The CD from #6 should work.

It sounds as though you didn't do steps 2&3. FBA needs to see a CD with the
correct stamp in the CD drive.

 

[Santiago Allen]

Sorry Gordon,

I left the steps 2&3 Out of the discussion since I say " I create My
image have the HD on prim master and the cD on prim slave (both devices
on cable select) and let it run through FBA". Ive actually stopped
creating a pre-FBA CD every time since I discovered that all it needs
is a CD with correct Signature. FBA Runs correctly and the post-fba HD
image boots without a problem. So I have steps 1-6 correct. But the
CD does not work. Like I said, I have used the same procedure for an
image which is this exact image minus some developers/technicians
components and this works.

Thanks,

Santiago

 

[Slobodan Brcin \(eMVP\)]

Santiago,

Ive actually stopped
creating a pre-FBA CD every time since I discovered that all it needs
is a CD with correct Signature.

Ok. But you have valid CD (the one made from your HDD) present during the
FBA, right?

Regards,
Slobodan

 

[Santiago Allen]

Hi Sloboddon,

Yes I have a CD with the same signature and partition size (an old one,
but made from the same partition of the same HD and with the default
ELTO signature). I managed to fix my error by reverting the MSDN steps
for EWF Ram Reg mode and instead using EWF Ram mode. I thought
El-Torito CD's only work for Ram Reg mode, so why would this fix it?
This is especially confusing considering that the pre-developers tools
version works with Ram Reg.

Thanks,

Santiago

 

[Slobodan Brcin \(eMVP\)]

Santiago,

You might have missed some entry in configuring Reg RAM EWF.
Try:
http://www.slobodanbrcin.com/xpe/ewf/regramewf.html

Or more likely you simply missed some critical step in El-torito setup.

Try ewfmgr c: on your working CD and you will see that it is using Reg RAM
EWF.

Regards,
Slobodan

 

[Santiago Allen]

Thanks Again,

Here Is what I did to set up EWF Ram (Reg).

1) Disable FBA DLL/COM Registration rescource in component Enhanced
Write Filter
2) Add the following Registry Keys to the "Extra Registry Data"
portion of my image in TD

a)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}\UpperFilters
REG_MULTI_SZ
"EWF"

b)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0\ArcName
Reg_SZ
multi(0)disk(0)rdisk(0)partition(1)

c)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0\Type
Reg_Dword
1

3) Resolve Dependencies and Build Image

Is there anything missing?

Thanks again,

Santiago

 

[KM]

Santiago,

Here Is what I did to set up EWF Ram (Reg).

1) Disable FBA DLL/COM Registration rescource in component Enhanced
Write Filter

You should clear the "Start EWF Enabled" checkbox on the EWF component Setting page.

2) Add the following Registry Keys to the "Extra Registry Data"
portion of my image in TD

a)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}\UpperFilters
REG_MULTI_SZ
"EWF"

Add "VolSnap" value there if you happended to add "Volume Shadow Copy Service" component in your image.

b)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0\ArcName
Reg_SZ
multi(0)disk(0)rdisk(0)partition(1)

c)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0\Type
Reg_Dword
1

3) Resolve Dependencies and Build Image

Is there anything missing?

On SP2 I usually also add the following reg.key (just in case to make sure the checkbox above does not influence the actuall
behaviour):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume0\Enabled
Reg_Dword
0

 

[Santiago Allen]

Thanks for all of your help Everyone, the Volsnap addition was the key.
I hadnt realized this, but adding in my debug components brought in
Volume Shadow Copy Service. Thanks for the tip.

Thanks,

Santiago Allen