12 replies to this topic

[pscEx]

To avoid questions about the "Why":
I'm working on a "barebone" version of multiPE, caused by the "competition".
And here the easiest and fastest way is to try and error by adding / deleting files in a bootable USB stick, and test the boot.

Inspite I think that the failure appears after all boot tasks, here the BCD:
(BTW: Same bad result with locale en-US)

Spoiler

Windows Boot Manager
--------------------
identifier {bootmgr}
device boot
description Windows Boot Manager
locale de-DE
inherit {globalsettings}
default {default}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device boot
path \windows\system32\boot\winload.exe
description Windows Setup
locale de-DE
inherit {bootloadersettings}
osdevice boot
systemroot \windows
detecthal Yes
winpe Yes
bootlog Yes
sos Yes
ems Yes

Windows Memory Tester
---------------------
identifier {memdiag}
device boot
path \boot\memtest.exe
description Windows Memory Diagnostic
locale de-DE
inherit {globalsettings}

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
description Hypervisor Settings
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Device options
--------------
identifier {7619dcc8-fafe-11d9-b411-000476eba25f}
ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi

When I build a flat target and create an ISO from it, it boots fine.
But the copy to an USB stick fails booting. The stick is prepared with rmpartusb and works fine with WIM based PEs and flat XP PEs.

When booting from the stick, according to the bcd sos option, drivers are reported as loaded. Also the correct kernel and hal are loaded.
Last loaded driver is disk.sys.

Then the screen is cleared, and a message about the used kernel apperars, including the info that bootlog is active.

After several seconds the BSOD appears with 0x0000007B.
EDIT by author: the misspelled 7F has been changed to the correct 7b
The bootlog ntbtlog.txt is not generated.

All google trials I made, did not find a remarkable solution.
Therefore @All: Please reanimate your magic crystal balls, polish them, and tell them my issue, and hopefully get a response which I can use.

Peter

Edited by pscEx, 01 December 2012 - 06:11 PM.

[steve6375]

You say you make an ISO and it boots fine - does it boot from a DVD/CD or from the ISO file placed on a bootable USB drive?
Does the USB drive boot under QEMU using RMPrepUSB Test using QEMU button?
Finally, will the same USB port of the same computer boot any sort of WinPE3 flat file from a USB drive ?

[pscEx]

Thanks, Steve, for the fast answer.
The "fine booting ISO" is booted in an emulator.

I'll try to answer all of your questions. But that will take some (latin) minutes.

(Can you give some more explanation, or a link about the QEMU question?)

Peter

[pscEx]

Sorry, I made a mistake.

The ISO is also not booting. Maybe in my tests I exchanged some iso-s.

Seems to be my homework now. No need of the communitie's magic crystal balls

Peter

[Sha0]

Sorry, I made a mistake.

7E seems a bit odd. If it's really not that there's a funny driver causing the problem, could it be that your osdevice isn't working? bcdedit /enum all /v might be interesting, too.

[Wonko the Sane]

7E seems a bit odd. If it's really not that there's a funny driver causing the problem, could it be that your osdevice isn't working? bcdedit /enum all /v might be interesting, too.

Wasn't it 7F ?


Wonko

[laddanator]

The stick is prepared with rmpartusb and works fine with WIM based PEs and flat XP PEs.

Peter

This may be getting off topic, but how are you flat file booting XP PEs?

[Sha0]

Wasn't it 7F ?

Oops. You're right. Well that's even stranger! What are the other codes on the screen, pscEx?

This may be getting off topic, but how are you flat file booting XP PEs?

The osdevice option for the BCD entry determines what the Windows (PE or non-PE) will consider to be the boot volume. If that's a RAM disk established with an .SDI file with a .WIM FS layered on top, so be it. Otherwise, you can choose some other volume that's available.

Short answer: bcdedit can let you change the osdevice option.

P. S. Remember the following confusion:

• The system volume is the filesystem where BootMgr and the BCD live; used for booting
• The boot volume is where the operating system lives

[pscEx]

Some wanted info:
The intermediate troubles came from a wrong osdevice in BCD, which I made to try to start USB with ISO on it.
Everyrthing now again works regularly.
All different PEs are made using the unchanged original created target directory.
(flat) ISO boots from VirualBox and from really burned CD.

(flat) USB stick as boot drive for qemu and VMWare boots fine (qemu it needs 'endless' time)

(flat) USB stick as boot drive fails (see description in the first post)..

@Sha0
The complete error code is
0x0000007B 0x80786B58 0xC0000034 0x00000000 0x00000000
(sorry for my first misspelling)

@Steve:
I never tried a different flat PE3.
I'm still trying to bring the (flat) ISO to the USB stick.
qEmu Test:

Besides the warning / error messages win7PE boots as in the above described direct qEmu boot.

Peter

[Wonko the Sane]

Good.
7B is not "queer" at all.


Wonko

[cdob]

0x0000007B 0x80786B58 0xC0000034 0x00000000 0x00000000

0x7B is the expected BSOD: missing boot drive.
Flat file USB booting is not supported out of the box.
USB drivers are loaded late, the boot drive is not available at flat file boot.

Qemu/VMware may map USB drive to a virtual internal disk, hence no USB booting.

There are USB booting hints in Windows 7 gold.
And there is Bootable Windows USB Stack (Windows Embedded Standard 7 Service Pack 1)

Try default USB drivers and

Hive_Load,System

Reg_Add,0x1,%reg%\ControlSet001\Control,BootDriverFlags,28

Reg_Add,0x1,%reg%\ControlSet001\Control\PnP,PollBootPartitionTimeout,30000

Hive_Unload

[pscEx]

Thanks, cdob! That brought the success!

I would like to give you 10 'I like this'. But unfortunatelly I'm limited to give only one.

I did a small change, following the actual documentation: Set BootDriverFlags to 4.
But I'll check also 28, later.

BTW: The 'native' boot of this flat USB stick needs 'endless' time. I estimate about 5 to 10 minutes until the desktop is up.
For the invented tests, I therefore decided, to boot the stick in VMWare. That needs only around one minute to bring the desktop.

BTW2: Can you give an explanation about PollBootPartitionTimeout? Google and BillyTheDoor do not tell very much.


Peter

[cdob]

I did a small change, following the actual documentation: Set BootDriverFlags to 4.
But I'll check also 28, later.

Windows 8 uses 28 and 30000 by default.
BootDriverFlags is a bit flag: 28 11100 includes 4 00100

To clarify: There is no need to set this at WinPE 4.

The 'native' boot of this flat USB stick needs 'endless' time.

That's long access time at this stick. Each file access is delayed, flat file reads al lot of files from USB dfrive.
Use a fast USB drive (short access time), a USB SSD is nice.

For the invented tests, I therefore decided, to boot the stick in VMWare.

Which VMware application do you use?
How do you connect the USB stick to virtual machine? USB drive or physicaldisk?

Can you give an explanation about PollBootPartitionTimeout?

KB2743013: STOP 0x0000007B error on reboot after Bitlocker drive encryption
http://support.micro....com/kb/2743013
PollBootPartitionTimeout : NEW VALUE: 0x0001D4C0 (120000 Decimal)

This value configures Windows to wait up to two minutes for the volume to come online during boot. If the timeout value is reached and the volume is not yet online, a STOP 0x00000078 INACCESIBLE_BOOT_DEVICE error will be displayed.

It's a manufactuer typo: 0x78

120000 Decimal seems to match 120000 miliseconds.

Therefore PollBootPartitionTimeout 30000 refers to 30 seconds.