I'm having a quite strange behavior on one desktop computer, IBM/Lenovo Thinkcentre A55 when deploying a Windows XP image. A55 uses ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll)

The image in question has been created with VMWare ESX, and it is "Advanced Configuration and Power Interface (ACPI) PC," ACPI PIC HAL (Halacpi.dll). I'm using ZTIHalDetect.vbs to switch HAL, that is working perfectly (after some problems). All disk controller drivers have been imported, and the image has been created with -pnp switch, with rebuilt MassStorageDrivers section. Actually SCCM Build&Capture task does this, and I've even checked the captured image to be sure that this really happens. Any other model I've tested boots fine.

Now, when I drop this image on A55, it fails for stop error 7B when it first time tries to boot to Windows. When I change bios settings for ide controller from Automatic to Serial ATA, it boots fine and the process continues. After the mini-setup section you can change ide controller back to automatic from bios again, and it works.

This behavior would point to missing hd controller driver, but it isn't - it does not need any special driver in either mode. All other tested models boot fine without any error.

Strangely, when you build an identical image with ESX server, but you leave its HAL on "ACPI Uniprocessor PC," ACPI APIC UP HAL (Halaacpi.dll), the A55 boots fine without any changes in ide controller settings!

I know the image hal swapping should be officially done only between halaacpi and halmacpi, but http://www.myitforum.com/articles/15/view.asp?id=8997 states this can be done. So I'm just wondering, am I doing something wrong, or did I just hit a model that is not compatible with the method?

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

BTW, did you touch base with Johan, he is very good at replying to emails/twitter messages.