0x0000007B

D

Dietmar

Hi all,
I build a BOOTCD from XPE and I am shure that I did exact everything as
You Slobodan told in Your tutorial.
I can see the CD after FBA connected as ELTORITO drive (with symbol of a
harddrive).
I have CDFS, FAT build from an *.slx for an SDI image, that works
wonderful from an USB drive)

I installed only new as component

EWF RAM Registry SP2
El Torito CD
EWFNTLDR
EWF Manager Console Application

(I have XPE SP2, that told me the devicemanager of my build after FBA.)

EWF is working (first disabled) as ewfmgr c: told me.
I cleaned the drives in MountedDevices.
I have only one FAT partition. I did twice the ELTO patch in the
bootsectors of the CDs.
First FBA works while the CD build first as template is in CD drive.
First, EWF is disabled, because of Your script for SP2 regramewf.zip.
On boottime I saw the white line arriving at the right side of the
monitor. Than happend exactly the same as my trys with real XPPRO: I saw
about a second the screen with Windows an than I got 0x0000007B as I know
from direct boot from USB drives...grrr.

Any ideas?
Thanks, Dietmar
 
S

Slobodan Brcin \(eMVP\)

Dietmar,

If you have done everything correctly then you are out of luck :-(
Read my remark section about BSOD 7B in my tutorial.

Some BIOS-es do not report correct information's and regular ntdetect won't
gather enough useful info required to match disk and ARC path later on in
kernel mode.

Try updating your computer BIOS.
Also this CD you should try to boot on several different computer types. If
it boots then you are 100% out of luck and you might try contacting PSS then
for ntdetect patch.

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan,
I wonder if this CD should boot on another PC.
I build an SDI image, which boots wonderfull to RAM on that computer from
USB drive, but: This USB drive connected to the other computer ends in
BSOD 0..07B.
I think You have build a lot of BOOT CDs from XPE.
Does any of those CDs boot on two computers with different hardware?
Another thing seems interesting: When I used the original chipsetdriver
for i875P from Intel, I got the 0...7B error for the boot from the SDI
image to ram. Thererfore I think, that there are many simliar but
different causes of 0...07B.
I build another CD with no extra software on it. And I believe: This one
will boot.

Thanks, Dietmar
 
S

Slobodan Brcin \(eMVP\)

Dietmar,

0x7B means that there is no boot partition fount at certain time during the
boot.
There are myriads of reasons why this could happen.

SDI boot should work always and it is mostly dependent on how you make your
image.
CD boot uses completely different driver stack and its reasons (problems)
are completely different and unrelated to SDI boot.
If you are using MB manufactured by Intel for el-torito boot I think that
with their BIOS you will be out of luck. Try different MB.

I avise you to use generic drivers to make tests first.
Use "Minlogon sample macro" component it will bring you generic drivers that
you need to boot from HDD on any computer. Then add El-torito support.
Does any of those CDs boot on two computers with different hardware?
Click to expand...
There are cases that it won't boot on computer that you used during the FBA
and that it boot perfectly normal on another computers with similar
architecture but with different BIOS.
Even completely different hardware can boot sometimes depending on your
image.

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan,
I have one question:
After running FBA with the ELTORITO CD in CDDrive
and clearing MountedDevices You enable EWF.
When do You make Your next ISO from this partition?
Direct after enabling EWF and shut down with FBA or do You boot this
partition once more to get full EWF?

Dietmar
 
S

Slobodan Brcin \(eMVP\)

Dietmar,

What ever you like. After the reboot EWF will start protecting your volume,
so you may boot it as many times as you want from HDD EWF will discard all
changes made during that boot.
You might want to try one boot on HDD just to verify that EWF is working.

Regards,
Slobodan
 
D

Dietmar

Hi all,
I tested the methode to build an bootable CD
with XPE on 8 Computers. ONE, a ShuttleX Barebone with Springdale Chipset,
works.
It displays first after boot the message, that "delayed write on drive C
failed", oh what a wonder! I testet CDs, DVDs, all the same.
But now I know thats not on me, that they don't work.
Perhaps all computers show the message 0x0000007B or stopped booting,
because of that behavior, THAT XPE WANTS TO WRITE TO CD, which is EWF
protected (I testet that for all CDs.)

Nice to hear from You all
Dietmar
 
S

Slobodan Brcin \(eMVP\)

Hi Dietmar,

Could you give us a list of computers (motherboards) that do not work it
would be usefull to someone else for refference if they want to use these
boards.
It displays first after boot the message, that "delayed write on drive C
failed", oh what a wonder! I testet CDs, DVDs, all the same.
Click to expand...

EWF is not working, and if you use my component then this should mean that
ARC path is wrong. Have you tampered with default ARC path that I set for
EWF?

Send us here boot.ini that you used for HDD FBA.
Also boot.ini that you use on CD/DVD.

Also after enabling EWF restart XPE on HDD and type ewfmgr C: let us know
what it says.

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan,
Arcpath is ALWAYS
multi(0)disk(0)rdisk(0)partition(1).
I know the behavior of XP with Arcpath, sometimes
very astonishing. I controlled it each time in boot.ini and in registry
setting for EWF. EWF works, I testet it very extremly but only on REAL
HDD.
I cant say what is XPE doing with writing on CD?!
I got sometimes the message, that windows failed with delayed writing on
CD, shown as ELTORITO harddrive, when I was on XPE harddisk after FBA. EWF
works on harddisk c, but not on CD drive shown as harddrive!!! That doesnt
make me wonder, because the arcpath for EWF at that time leads ONLY to the
real hhd as drive C: and I think not on drive C when it is the BOOTCD.
Something went wrong with EWF. Who ever said, that arcpath shown above
belongs to drive C:?

Dietmar
 
S

Slobodan Brcin \(eMVP\)

Dietmar,
I know the behavior of XP with Arcpath, sometimes
very astonishing. I controlled it each time in boot.ini and in registry
setting for EWF.
Click to expand...

Unfortunately this is what I was afraid of and this is the exact reason why
I asked for both boot.ini files that you used.
Or even better attach to this NG "system." file and boot.ini located on your
CD.

You should not play with ARC path when you make El-torito disk. It should be
multi(0)disk(0)rdisk(0)partition(1) for HDD boot.ini CD boot.ini and EWF.
multi(0)disk(0)rdisk(0)partition(1).
Who ever said, that arcpath shown above belongs to drive C:?
Click to expand...

If you have provided us with boot.ini then I would say that to you. As long
as your MountedDevices is empty when you look at it in offline image
registry hive and as long as you use multi(0)disk(0)rdisk(0)partition(1). in
your boot.ini and EWF config C: will be protected partition. This is just
simply how things work.

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan,
shown from the partition with the deployed image after FBA the ELTORITO CD
appears as drive D with a symbol of a harddisk. From those D location I
sent You the boot.ini and a part of the system file from there, which is
the major part of the registry but 4.5MB large.

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect


[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\FBA]
"DiskSig"=dword:4F544C45
"OVSize"=dword:00000000
"OVLevel"=dword:00000001
"PVConfigs"=dword:00000001
"EwfEnable"=hex(7):31,00,00,00,00,00
"EnableLazyWrite"=hex(7):30,00,00,00,00,00
"PVDisk"=hex(7):30,00,00,00,00,00
"PVPart"=hex(7):31,00,00,00,00,00
"PVDiskType"=hex(7):30,00,00,00,00,00
"PVType"=hex(7):31,00,00,00,00,00
"PVOptimize"=hex(7):30,00,00,00,00,00

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters]

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected]

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected\Volume0]
"Type"=dword:00000001
"Enabled"=dword:00000000
"ArcName"="multi(0)disk(0)rdisk(0)partition(1)"
"CompareBeforeAlloc"=dword:00000000

[HKEY_LOCAL_MACHINE\ControlSet002\Services\Fastfat]
"ErrorControl"=dword:00000001
"Type"=dword:00000002
"Start"=dword:00000004
"Group"="Boot file system"

[HKEY_LOCAL_MACHINE\FBA]
"Shell"="C:\\WINDOWS\\fba\\fba.exe -shell"
"DisplayWidth"=dword:00000320
"DisplayHeight"=dword:00000258
"DisplayBPP"=dword:00000020
"DisplayRefresh"=dword:0000003C
"FBADoPNP"=dword:00000000
"ComputerName"="OEM-WT4RMXSZI8R"
"DomainName"="OEM-WT4RMXSZI8R"

[HKEY_LOCAL_MACHINE\FBA\RegMigrate]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKCU]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKCU\Console]
"QuickEdit"=dword:00000000
"WindowSize"=dword:00320050
"ScreenBufferSize"=dword:012C0050

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet\Control]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet\Control\Lsa]
"ForceGuest"=dword:00000000

[HKEY_LOCAL_MACHINE\FBA\RunOnce]

[HKEY_LOCAL_MACHINE\LastKnownGoodRecovery]

[HKEY_LOCAL_MACHINE\MountedDevices]

[HKEY_LOCAL_MACHINE\Select]
"Current"=dword:00000001
"LastKnownGood"=dword:00000002
"Failed"=dword:00000000
"Default"=dword:00000001

[HKEY_LOCAL_MACHINE\Setup]

All seems to work
Dietmar
 
S

Slobodan Brcin \(eMVP\)

Dietmar,

Something is not right in the registry file that you sent me.
I need HKEY_LOCAL_MACHINE\ControlSet001\Services\EWF

Second there are entries in registry that my component did not included so
you are using "Enhanched Write Filter" component which should not be in a
image, my component is replacement for this component.
I guess that I forgot to write this in this release. I will update component
and doc to prevent this case.

You EWF was working in normal mode not the registry configured mode. (This
is written by ewfmgr when you use it.)
ewfmgr c: -enable
So EWF was never enabled.

Look:
[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected\Volume0]
"Enabled"=dword:00000000
Click to expand...

Enabled must be 1.

Regards,
Slobodan

Dietmar said:
Hi Slobodan,
shown from the partition with the deployed image after FBA the ELTORITO CD
appears as drive D with a symbol of a harddisk. From those D location I
sent You the boot.ini and a part of the system file from there, which is
the major part of the registry but 4.5MB large.

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect


[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\FBA]
"DiskSig"=dword:4F544C45
"OVSize"=dword:00000000
"OVLevel"=dword:00000001
"PVConfigs"=dword:00000001
"EwfEnable"=hex(7):31,00,00,00,00,00
"EnableLazyWrite"=hex(7):30,00,00,00,00,00
"PVDisk"=hex(7):30,00,00,00,00,00
"PVPart"=hex(7):31,00,00,00,00,00
"PVDiskType"=hex(7):30,00,00,00,00,00
"PVType"=hex(7):31,00,00,00,00,00
"PVOptimize"=hex(7):30,00,00,00,00,00

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters]

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected]

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected\Volume0]
"Type"=dword:00000001
"Enabled"=dword:00000000
"ArcName"="multi(0)disk(0)rdisk(0)partition(1)"
"CompareBeforeAlloc"=dword:00000000

[HKEY_LOCAL_MACHINE\ControlSet002\Services\Fastfat]
"ErrorControl"=dword:00000001
"Type"=dword:00000002
"Start"=dword:00000004
"Group"="Boot file system"

[HKEY_LOCAL_MACHINE\FBA]
"Shell"="C:\\WINDOWS\\fba\\fba.exe -shell"
"DisplayWidth"=dword:00000320
"DisplayHeight"=dword:00000258
"DisplayBPP"=dword:00000020
"DisplayRefresh"=dword:0000003C
"FBADoPNP"=dword:00000000
"ComputerName"="OEM-WT4RMXSZI8R"
"DomainName"="OEM-WT4RMXSZI8R"

[HKEY_LOCAL_MACHINE\FBA\RegMigrate]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKCU]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKCU\Console]
"QuickEdit"=dword:00000000
"WindowSize"=dword:00320050
"ScreenBufferSize"=dword:012C0050

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet\Control]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet\Control\Lsa]
"ForceGuest"=dword:00000000

[HKEY_LOCAL_MACHINE\FBA\RunOnce]

[HKEY_LOCAL_MACHINE\LastKnownGoodRecovery]

[HKEY_LOCAL_MACHINE\MountedDevices]

[HKEY_LOCAL_MACHINE\Select]
"Current"=dword:00000001
"LastKnownGood"=dword:00000002
"Failed"=dword:00000000
"Default"=dword:00000001

[HKEY_LOCAL_MACHINE\Setup]

All seems to work
Dietmar
Click to expand...
 
S

Slobodan Brcin \(eMVP\)

One more tip:

If you use "Enabled"=dword:00000001 with EWF config partition on disk ewf
config partition will take precedence and EWF will be disabled.
But after you copy image to CD (without enabling EWF) since config partition
would not be copied EWF would start working as enabled.

Regards,
Slobodan


Slobodan Brcin (eMVP) said:
Dietmar,

Something is not right in the registry file that you sent me.
I need HKEY_LOCAL_MACHINE\ControlSet001\Services\EWF

Second there are entries in registry that my component did not included so
you are using "Enhanched Write Filter" component which should not be in a
image, my component is replacement for this component.
I guess that I forgot to write this in this release. I will update
component and doc to prevent this case.

You EWF was working in normal mode not the registry configured mode. (This
is written by ewfmgr when you use it.)
ewfmgr c: -enable
So EWF was never enabled.

Look:
[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected\Volume0]
"Enabled"=dword:00000000
Click to expand...

Enabled must be 1.

Regards,
Slobodan

Dietmar said:
Hi Slobodan,
shown from the partition with the deployed image after FBA the ELTORITO
CD
appears as drive D with a symbol of a harddisk. From those D location I
sent You the boot.ini and a part of the system file from there, which is
the major part of the registry but 4.5MB large.

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded" /fastdetect


[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\FBA]
"DiskSig"=dword:4F544C45
"OVSize"=dword:00000000
"OVLevel"=dword:00000001
"PVConfigs"=dword:00000001
"EwfEnable"=hex(7):31,00,00,00,00,00
"EnableLazyWrite"=hex(7):30,00,00,00,00,00
"PVDisk"=hex(7):30,00,00,00,00,00
"PVPart"=hex(7):31,00,00,00,00,00
"PVDiskType"=hex(7):30,00,00,00,00,00
"PVType"=hex(7):31,00,00,00,00,00
"PVOptimize"=hex(7):30,00,00,00,00,00

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters]

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected]

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected\Volume0]
"Type"=dword:00000001
"Enabled"=dword:00000000
"ArcName"="multi(0)disk(0)rdisk(0)partition(1)"
"CompareBeforeAlloc"=dword:00000000

[HKEY_LOCAL_MACHINE\ControlSet002\Services\Fastfat]
"ErrorControl"=dword:00000001
"Type"=dword:00000002
"Start"=dword:00000004
"Group"="Boot file system"

[HKEY_LOCAL_MACHINE\FBA]
"Shell"="C:\\WINDOWS\\fba\\fba.exe -shell"
"DisplayWidth"=dword:00000320
"DisplayHeight"=dword:00000258
"DisplayBPP"=dword:00000020
"DisplayRefresh"=dword:0000003C
"FBADoPNP"=dword:00000000
"ComputerName"="OEM-WT4RMXSZI8R"
"DomainName"="OEM-WT4RMXSZI8R"

[HKEY_LOCAL_MACHINE\FBA\RegMigrate]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKCU]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKCU\Console]
"QuickEdit"=dword:00000000
"WindowSize"=dword:00320050
"ScreenBufferSize"=dword:012C0050

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet\Control]

[HKEY_LOCAL_MACHINE\FBA\RegMigrate\HKLM\System\CurrentControlSet\Control\Lsa]
"ForceGuest"=dword:00000000

[HKEY_LOCAL_MACHINE\FBA\RunOnce]

[HKEY_LOCAL_MACHINE\LastKnownGoodRecovery]

[HKEY_LOCAL_MACHINE\MountedDevices]

[HKEY_LOCAL_MACHINE\Select]
"Current"=dword:00000001
"LastKnownGood"=dword:00000002
"Failed"=dword:00000000
"Default"=dword:00000001

[HKEY_LOCAL_MACHINE\Setup]

All seems to work
Dietmar
Click to expand...
Click to expand...
 
D

Dietmar

Hi Slobodan,

I used only the component "EWF RAM Registry SP2"
build from Your script and
never "Enhanched Write Filter" component.
And believe me: EWF was working, enabled with
ewfmgr c: -enable

I saw this

[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\Parameters\Protected\Volume0]
"Enabled"=dword:00000000

too and just change it to 1.

I burned a new CD.
The only thing that happend is, that now on partition after FBA and CD
seen as harddrive
NO message was there: "delayed write on drive D failed"
and with the outside registry viewer I saw, that now

[HKEY_LOCAL_MACHINE\ControlSet001\Services\EWF\Parameters\Protected\Volume0]
"Enabled"=dword:00000001
is.
That means: My Computer(s) wont boot those CDs
and You can enable EWF with ewfmgr c: -enable,
witch works on the harddrive(!) but not on CD.
You MUST set the REGISTRY as above.

Dietmar
 
S

Slobodan Brcin \(eMVP\)

Dietmar,

I have uploaded new version of my compoent that will preven you from using
EWF componet in paralel with my component.
Download it from:
http://www.slobodanbrcin.com/xpe/ewf/regramewf.html
or from
www.xpefiles.com

Look closely at the middle pannel in TD and you will find component named:
"Enhanced Write Filter" (trust me) and remove it.

This is the only component that make ugly registry entries like:
[HKEY_LOCAL_MACHINE\ControlSet002\Services\EWF\FBA]
"DiskSig"=dword:4F544C45
"OVSize"=dword:00000000
"OVLevel"=dword:00000001
"PVConfigs"=dword:00000001
"EwfEnable"=hex(7):31,00,00,00,00,00
"EnableLazyWrite"=hex(7):30,00,00,00,00,00
"PVDisk"=hex(7):30,00,00,00,00,00
"PVPart"=hex(7):31,00,00,00,00,00
"PVDiskType"=hex(7):30,00,00,00,00,00
"PVType"=hex(7):31,00,00,00,00,00
"PVOptimize"=hex(7):30,00,00,00,00,00


Also since now your HDD is poluted with EWF config partition. You will have
to use diskpart.exe to find it and eradicate it. So that you can use
registry configured RAM ewf.
Or use "etprep /delete" once to do the same job.

Note that this partition always take precedence in regards to registry
configuration.

Regarding the: > NO message was there: "delayed write on drive D failed"
D: is new problem probably that you caused by experimenting with
MountedVolumes please make it empty when you look at it from offline
regedit.

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan,

your right, that there is an extra partition with "?" which was shown by
Winhex, a wonderfull HExeditor. But in middle pannel in TD there is no
entry "Enhanced Write Filter". I remember now, that I first added it, but
after delete it before building the image because dependenci check says,
this is an error together with your component.
A new dependency check says then all is ok. (?!)
But there seems to be rests of the old component remaining.

I have an other question: How can i distinguish between FAT16 for MSDOS in
the components and FAT16 for XP (with NTLDR searching in bootsector)? That
problem may be related to all the things that happend.

And one more: Must I build a complete new *.slx
or can I keep my old one? ARE there possibly rests of deletet components
when you use cut oder delete in middle pannel in TD?
Thanks Dietmar

PS. I never give up...hihi
 
S

Slobodan Brcin \(eMVP\)

Hi Dietmar,
after delete it before building the image because dependenci check says,
this is an error together with your component.
Click to expand...

I added this option few hours ago, so you are using new component now?
There are no residues when you remove component from project.

Can you send me your services\ewf registry entries after FBA with my new
component present?

Have you deleted this partition? Do that.

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan,
I have Your new Component.
I send You the part of the registry when I am ready.
Please answer my question how to deceide which
component is for FAT MSDOS and which for FAT XP.
They produce different Bootsectors(with msdos.sys or NTLDR).
Or You can tell me, what component with "FAT" in
the name of the component I have to use for XPE BOOTCD and which
components from the filesystems
and which are NOT allowed?

Thanks Dietmar
 
S

Slobodan Brcin \(eMVP\)

Diemtar,

There is only one FAT driver component for "all versions" of FAT.
As long as ntldr is loaded you have XP(e) boot sector on FAT. But this code
has nothing to do with FAT type. FAT has not changed for ages (since FAT32
was introduced).

BSOD 0x7B has nothing to do with file support it is much more restrictive
and tell you that boot partition was not found trough curently loded driver
stack. (This can mean anything except that FS is bad (BSOD 0x6B is used for
that))

http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr6b/default.aspx
http://msdn.microsoft.com/embedded/community/community/tips/xp/stoperr7b/default.aspx

Regards,
Slobodan
 
D

Dietmar

Hi Slobodan

I upgraded your Component from R8 to R10.
When I now run dependency check, I was told that this component is in
conflict with "Enhanced Write Filter". (Which I dont have...hihi.)
Suddenly this "Enhanced Write Filter" component appears in the middle of
TP?! When I delete it, nice dependency check installes it for me
again...grrr,
and then came the same errorwarning.
I did the follow: I deleted the appearing from hell component "Enhanced
Write Filter" by hand and build the new image without any more dependency
check. Now I am deploying my image on a totally new configured FAT
partition with 643MB and if FBA is ready, I send You the registry
entrances You wish.

Thanks Dietmar

PS. I told You, that on one computer (shuttle barebone with Phoenix Bios
and Springdale chipset) the CD boots XPE with errorwarning, that on drive
C: delayed write failed (cool computer this barebone, it starts XPE from
BOOTCD WITHOUT EWF enabled, thats make me hope for real XPPRO on that
machine). After I changed EWF to be enabled to a new CD, this message was
not seen anymore and XPE from Bootcd works perfekt on this wonderful
machine ,doesnt matter that this CD was build on a PC with different
hardware.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

XPPRO boots (not) from DVD 19
Another El torito problem 1
EWF RAM Reg and BSOD 7B 1
El Torito 4
El Torito CD boot fails with delayed write failure 4
simple fba Qs 1
EWF, missing HAL.DLL, and logical partition 2
Persistent data on xpe el-torito CD 1

Top