0x0000007B

  • Thread starter Thread starter Dietmar
  • Start date Start date
Hi Slobodan,
I send You a a piece of the registry from the Fat partition where the XPE
image was deployed.
I build a CD with ELTO patch and FBA startet with this CD present. After
that I cleaned MountedDevices and put ewfmgr c: -enabled. Than I boot
again and ewfmgr c: told me, that EWF with Ram overlay is enabled. The
Registry is from the running C:\ at this time!

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

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EWF\FBA]
"DiskSig"=dword:4f544c45

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EWF\Parameters]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EWF\Parameters\Protected]

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

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EWF\Enum]
"0"="Root\\LEGACY_EWF\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

All seemes to work with Your new Component

Dietmar
 
Dietmar,

Component "Enhanced Write Filter" was always there I now looked and found
that "El Torito CD" component has dependency on this component.
In future you should be more carefull when looking for components. I just
don't understand how you did not see "Enhanced Write Filter" component in
the list before.
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.
Click to expand...

So you have solved your problems and now your CD is working right?
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)
Click to expand...

Yup that give you hope that without EWF your XPP will have same delayed
write failed message if you include el-torito driver.

Regards,
Slobodan
 
My new component is same as my old component :-)
I just added entry to prevent usage of your invisible "EWF" component ;-)

Regards,
Slobodan
PS:
I'm glad that is finaly started to work.
 
Hi Slobodan,
it was as I told You. Dependencie check tells me, that there was an
conflict between both components. I killed "Enhanced Write Filter".
That this happend could be seen. New dependeny check says all is ok. And
my former 752 components are now 751.
Not all went right in XPE.
And 1 computer, where CD BOOT functions 1 of 8 isnt that what I call an
excellent programm.
The shuttle barebone is a present from me to my wife on birthday. Now I
will buy her another one,(... if she agrees...hihi).
You told me, that there is a chance to communicate with microsoft to get
another ntldr.
I am thinking that at least 7 of 8 persons have similiar problems with
boot from CD in XPE.
So Microsoft must have heard this. Can You help me to get another ntldr
(ewfntldr)?

Thanks to You
Dietmar

PS: I burned the last CD image to an DVD.
Boottime is now reduced about a faktor 4, now about 20 seconds (faster as
from HDD(!)).
 
Hi Slobodan,

Your right with ELTORITO. I think, ALL the problems came from there. I do
a try without eltority.sys ... lets see.

Dietmar
 
it was as I told You. Dependencie check tells me, that there was an
conflict between both components. I killed "Enhanced Write Filter".
Click to expand...

Forget about this. I said that it was expected and why it is expected,
please read again this conversation from start. or at least for few last
posts when I described what I have updated in new component.
And 1 computer, where CD BOOT functions 1 of 8 isnt that what I call an
excellent programm.
Click to expand...

Again: Can you please tell us these computers that do not work so that we
know in future which manufacturers and BIOS-es they use?
You told me, that there is a chance to communicate with microsoft to get
another ntldr.
Click to expand...

I did? Then sorry I ment ntdetect.com
I am thinking that at least 7 of 8 persons have similiar problems with
boot from CD in XPE.
Click to expand...

You are wrong, probably 100% persons that dealt with El-torito CD had this
problem and probably just gave up on certain boards and took the board that
work, or contacted MS.
So Microsoft must have heard this. Can You help me to get another ntldr
(ewfntldr)?
Click to expand...

ntdetect.com is the problem not ntldr.
I do not have this patch nor I do care about MS patches that come months
later or do not come at all. I fix things myself and make my work-arounds
for our internal usage.

Try sending feedback to MS they love to hear idea about new features or
about how they product work :-)
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

Anyhow about the MS contact try contacting person from following thread:
http://groups-beta.google.com/group...206c32a46ea/0408e0f1e054e3ef#0408e0f1e054e3ef


Regards,
Slobodan
 
Hi Slobodan,
so critical with Microsoft? But dont worry, I installed the game
Battlefield 1942 on Linux with an ATI 9800XT grafikcard, I dont think that
anything in this computerworld is more terrible...but at last it works.

Now here are the mainboards that DOESNT function for me with ELTORITO
CDROMBOOT. They all have the latest Biosversions I can got.

Asus P4T with i850 Chipset
Asus P4T-E with i850 Chipset
Asus P2B with BX100 Chipset
Asus P3B-F with BX100 Chipset
Asus P4C800Deluxe-E with i875P chipset (good motherboard but not for CDROM
BOOT)
Fujitsu-Siemens 1607 with VIA K8T800 (that is a very good motherboard but
not for CDROM BOOT)
Notebook Blockbuster Gericom N251SX based on N251S6 with SIS650 chipset


And now The one and only, that workes with CDROMBOOT of XPE:

Shuttle XPC SB61G2 with
Intel Springdale i865G Chipset and Phoenix Bios


I think ntdetect.com is a small programm that doesnt changed at all about
the XP and XPE versions as seen with IDA Disassembler, so with enough time
You can understand what's to do.

Dietmar
 
Thanks for black-listed boards.

So basically Asus BIOS has an issues and IIRC Intel BIOS-es (at least Intel
875 MB that I have).

Solution is simple if you know exact medium that you want to boot from just
use IoAssignArcName from your driver before XPe check phase that give BSOD
7B.
http://msdn.microsoft.com/library/d..._ceeba02c-47cf-4c25-a339-d55ee9ebc216.xml.asp

This is a hacky way to force exact ARC paths to specific disk driver. This
is to solve problem with missing information's that ntdetect.com does not
provide due to some troubles with BIOS.

Regards,
Slobodan
 
Slobodan,
Thanks for black-listed boards.

So basically Asus BIOS has an issues and IIRC Intel BIOS-es (at least Intel
875 MB that I have).

Solution is simple if you know exact medium that you want to boot from just
use IoAssignArcName from your driver before XPe check phase that give BSOD
7B.
http://msdn.microsoft.com/library/d..._ceeba02c-47cf-4c25-a339-d55ee9ebc216.xml.asp

This is a hacky way to force exact ARC paths to specific disk driver. This
is to solve problem with missing information's that ntdetect.com does not
provide due to some troubles with BIOS.
Click to expand...


How about just setting up "SystemPartition" value under [HKLM\SYSTEM\Setup] key?
I never tested that, though.

Although it may not work for "read" but just getting updated by the kernel during every boot to reflect system partition
information.

Also, if I recall correctly, the "systempartition" option can be supplied in the boot.ini but I don't remember whether it works on
x86 platforms. I just read about it along time ago in usenet.
 
Konstantin,

I have never tried to change this value (if it is permament value at all
that is). But main problem is that we don't know the disk/volume PnP id of
boot disk :-(
When we figure that out then call to IoAssignArcName is much simpler and
better than playing with undocumented registry values.

Regards,
Slobodan



KM said:
Slobodan,
Thanks for black-listed boards.

So basically Asus BIOS has an issues and IIRC Intel BIOS-es (at least
Intel
875 MB that I have).

Solution is simple if you know exact medium that you want to boot from
just
use IoAssignArcName from your driver before XPe check phase that give
BSOD
7B.
http://msdn.microsoft.com/library/d..._ceeba02c-47cf-4c25-a339-d55ee9ebc216.xml.asp

This is a hacky way to force exact ARC paths to specific disk driver.
This
is to solve problem with missing information's that ntdetect.com does not
provide due to some troubles with BIOS.
Click to expand...


How about just setting up "SystemPartition" value under
[HKLM\SYSTEM\Setup] key?
I never tested that, though.

Although it may not work for "read" but just getting updated by the kernel
during every boot to reflect system partition
information.

Also, if I recall correctly, the "systempartition" option can be supplied
in the boot.ini but I don't remember whether it works on
x86 platforms. I just read about it along time ago in usenet.
Click to expand...
 
Slobodan,
When we figure that out then call to IoAssignArcName is much simpler and
better than playing with undocumented registry values.
Click to expand...

I can't argue with that. API approach is definitely better than undocumented one. :-)

--
Regards,
Konstantin
KM said:
Slobodan,
Thanks for black-listed boards.

So basically Asus BIOS has an issues and IIRC Intel BIOS-es (at least
Intel
875 MB that I have).

Solution is simple if you know exact medium that you want to boot from
just
use IoAssignArcName from your driver before XPe check phase that give
BSOD
7B.
Click to expand...
http://msdn.microsoft.com/library/d..._ceeba02c-47cf-4c25-a339-d55ee9ebc216.xml.asp
This is a hacky way to force exact ARC paths to specific disk driver.
This
is to solve problem with missing information's that ntdetect.com does not
provide due to some troubles with BIOS.
Click to expand...


How about just setting up "SystemPartition" value under
[HKLM\SYSTEM\Setup] key?
I never tested that, though.

Although it may not work for "read" but just getting updated by the kernel
during every boot to reflect system partition
information.

Also, if I recall correctly, the "systempartition" option can be supplied
in the boot.ini but I don't remember whether it works on
x86 platforms. I just read about it along time ago in usenet.

--
Regards,
Konstantin


Hi Slobodan,
so critical with Microsoft? But dont worry, I installed the game
Battlefield 1942 on Linux with an ATI 9800XT grafikcard, I dont think
that
anything in this computerworld is more terrible...but at last it works.

Now here are the mainboards that DOESNT function for me with ELTORITO
CDROMBOOT. They all have the latest Biosversions I can got.

Asus P4T with i850 Chipset
Asus P4T-E with i850 Chipset
Asus P2B with BX100 Chipset
Asus P3B-F with BX100 Chipset
Asus P4C800Deluxe-E with i875P chipset (good motherboard but not for
CDROM
BOOT)
Fujitsu-Siemens 1607 with VIA K8T800 (that is a very good motherboard
but
not for CDROM BOOT)
Notebook Blockbuster Gericom N251SX based on N251S6 with SIS650 chipset


And now The one and only, that workes with CDROMBOOT of XPE:

Shuttle XPC SB61G2 with
Intel Springdale i865G Chipset and Phoenix Bios


I think ntdetect.com is a small programm that doesnt changed at all
about
the XP and XPE versions as seen with IDA Disassembler, so with enough
time
You can understand what's to do.

Dietmar
Click to expand...
Click to expand...
Click to expand...
 
Back
Top