error at emulating drive (WinPE)

[Elementelist]

Hi all,

I am using iPXE for a while now and I am having some problems with a machine.
When I change the IDE controller from IDE to AHCI the WinPE images freeze at:

emulating drive 0x81
entering bootmgr.exe with parameters at 0x02a390

All the other machines boot correctly with no problems at all.
I use a pre-built binary from rom-o-matic.eu with my own script.

I've tried different output files and the .pxe one boots but the hard drive is not recognized when Acronis or Ghost loads up in WinPE.
When i reboot the machine and enter the BIOS the hard drive does not get recognized anymore. To fix it i have to disconnect/connect the drive again.
Also i've tried to use different versions of wimboot and other bootmgr.exe files that sadly dont work either.

I am guessing this is a hardware related problem but maybe you guys got an idea?
The machine is a POS (Senortech) with an Aptio BIOS and a Realtek B01 D00 NIC.
When i set the protocol on IDE everything works flawless.
thanks in advance!

[mcb30]

(2016-02-04 12:13)Elementelist Wrote:  I am using iPXE for a while now and I am having some problems with a machine.
When I change the IDE controller from IDE to AHCI the WinPE images freeze at:

emulating drive 0x81
entering bootmgr.exe with parameters at 0x02a390

...

I am guessing this is a hardware related problem but maybe you guys got an idea?
The machine is a POS (Senortech) with an Aptio BIOS and a Realtek B01 D00 NIC.
When i set the protocol on IDE everything works flawless.
thanks in advance!

It sounds like a BIOS bug. Have you checked for a BIOS update?

Michael

[sebus]

It is something with the .wim itself. I have exact same issue on Latitude E5410. Other .wim images work on it, just this one (WinPe SE 10) does get stuck in the exact place

[NiKiZe]

Sounds like there is a mass storage controller driver in the wim that is not compatible with the hardware but is still loaded. Had similar issues with a win7 boot.wim where someone else had added all storage drivers from some driver packs, I just started with a clean winpe instead and everything worked without problem.

[sebus]

That is not the case. I can boot the iso (with the very same .wim inside) from same ipxe/pxelinux with grub just fine.
Can boot the iso from USB stick (direct, via Easy2boot etc)

Just wimboot that does not like that .wim

[davidvicky]

I have been injecting directly into the PXE rep boot image to save time. I have verified that I have the files in a driver directory (driver.0 in this case) in the i386\system32 directory.