hard drive+Safe Mode or ElTorito = Error 07B !?

  • Thread starter Thread starter Arthur
  • Start date Start date
A

Arthur

Hello,

I use the test template (with standard PC and standard
IDE) (60 - 70Mo) for a compatible mini windows on my
intel PIV.

- On hard drive: no problem, FBA OK, reboot OK, use OK.
- But if I try "SAFE MODE" (by F8) with the same
installation on hard drive -> Blue Screen 0007B
- And if I try to boot from an eltorito CD + EWF -> Blue
Screen 0007B

So whats happend ??

And when I try the same eltorito cd on another pc (AMD
Athlon), its working !!!

Please, I'm losting...
how explains blue screen with safe mode ??
and why the eltorito CD works on the AMD and not on the
intel ?
 
Arthur,

XPe does not support Safe mode by default (registry entries for safe mode
are missing) so this error is to be expected.

You have different hardware platforms.
What platform did you use for FBA and creating El-torito CD?

There is high possibility that you will need to create different El-torito
CD's for each different hardware you have.

Regards,
Slobodan
 
ok for safe mode, slobodan,

but for create eltorito and ewf, i use the intel p4 !!
And the result is:
- error with this pc (Intel P4)
- and ok with the other (Amd Athlon) or with VMWare !!!

So... my brain heats...
 
So basically what you are saying is:
You run FBA on Intel MB. And create CD from post FBA data.
And this CD is working on AMD and not on Intel platform, right?


Do you have two different builds in TD or one build for both platforms.
How did you make those builds?
Also if you have two separate builds there might be that you are missing
some settings in build created for Intel platform.

I have tested El-torito boot on Intel 875 chipset, this means that it can be
done.

Regards,
Slobodan
 
"
So basically what you are saying is:
You run FBA on Intel MB. And create CD from post FBA data.
And this CD is working on AMD and not on Intel platform,
Click to expand...
right?
"

Yeah! its exact.

1/ Im using target designer on my pc intel (I want create
the runtime for this PC).
2/ Im creating runtime on 650 Mo partition, C:
3/ Im booting, FBA runs (with Eltorito in cd-drive),
reboot, and win embed. works perfectly.
4/ I activate EWF et swap mounted devices.
5/ I create Eltorito CD.

Result:
El torito CD doesnt work on my intel pc. (error 007B)
But if I try this CD on VMWare or on an another computer
(AMD), its working!!!!!

But warning:
i'm using WINLOGON SAMPLE MACRO (+ Secondary IDE +
Eltorito + CD driver + autolayout + your EWF Ram registry
and I remove enhanced write filter)
AND NOT T.A... Its why eltorito-runtime can work on an
another PC!

But its doenst explain why my runtime works on hard drive
in PC intel and not on eltorito CD.
Maybe CD-Rom driver ??

I know: I can try a runtime with T.A. on my Intel, but
how explain whats happend ? (I want understand!!)

PS: Sorry for my english.
 
It does not make any sense that you can't boot your CD on device that was
used during FBA, and that you can boot it on other device.

This would mean that you have done all necessary steps to create bootable
Et-torito, but nevertheless you should recheck your steps.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/htm
l/cdtbsetprepusage.asp
Describes how to use etprep and commands that are performed by this util.

Since you are using RAM EWF approach suggested by me, you should call etprep
in phases or do manually changes in registry.
Read more info on:
etprep /flip
etprep /reset <----- This is needed to avoid 7B bug check.

Check EWF to make sure it is configured and working properly. You can enable
it, and test it on HDD. Later you can commit changes you make with etprep.

You obviously have enough drivers because your device booted from HDD, and
because it boots on another platform.
If you can see El-torito disk from your XPe image then whole driver stack is
loaded.

I don't understand what you mean by not using T.A.

T.A.(target analyzer?) - You mean you have not used TA or TAP to import
your hardware requirements.
This could indicate you missed something from required drivers/services
(don't know what exactly).

Let us know about your progress,
Slobodan
 
thks a lot,

i believe that's a etprep problem:
because on intel PC(developpement pc) hard disks analyzed
by FBA are really present so a ETPREP problem gives me a
007B error.
But on AMD PC (test pc) hard disks previously analyzed by
FBA dont exist so that maybee bypasses the problem...

result: a nonsense for you and me... :-)

I all will start again.
 
ok now its working

it was a etprep problem.
In fact, i modified manually registry (mounted devices)
without using etprep:

*Before (normal config after FBA):
Hard Drive C: and D:
CDROM E:
El Torito F:

*After my modif. :
Hard Drive: D: and E:
CDROm: F:
Eltorito: C:

IT WAS A MISTAKE

*Good parameters (after modif.) are:
Hard Drive: F: and D:
CDROM: E:
ElTorito C:

It explains my problem...!
 
This does not explain your problem, AFAIK you need only El-Torito as C:
everything else can be removed from registry. XPe will assign volume letters
during the boot.

Problem you had was strange, but since you solved it...

Regards,
Slobodan
 
Arg... same problem again...

So an added component is certainly guilty because with a
minimum of components, its working...

I will try to add components one by one for find the
guilty... but it will be long!

And can you tell me what ETPREP changes in registry with
the reset option (What is Redbook/IMAPI service ?)

Thks.
 
Open HKLM\SYSTEM\CurrentControlSet\Services

Find Imapi - It must be present.
Change start value for this driver to 0

Also find redbook and change start value for this driver to 0

Both drivers must be present, and their start value must be 0 so they would
be loaded by ntldr.

Regards,
Slobodan
 
Ok, its working !
Problem was here.

But a last question,
boot is very slow, can i patch this ? Windows Ram Driver
can help me ?

Thks again for all.
I become a eltorito's specialist ;-)
 
I don't think that you can speed El-Torito boot.

If you use ram boot from CD.

1. You will loose significant amount of memory that is equal to XPe
partition size.
2. Your boot loader of ntldr. need to load whole SDI file to memory before
it attempts to boot.
3. There are no seek times on CD that are slow. But whole image is loaded in
RAM.
4. There are no later timings when you access some file that is loaded.

This is acceptable for small images based on files that are almost always
needed.

Regards,
Slobodan
 
Back
Top