In my SATA Controller Identification tool I was using the TSaveDialog (Delphi 2010) but I got a report that under Windows PE the dialog is never shown.

There’s no exception and I didn’t really bother to check why it fails. Instead I decided to replace it with the GetSaveFileName API which does work under Windows PE.

Example:

After compiling the VMWare VMXNET3 Driver for Linux I needed a driver for the Windows PE Image as well.

Compared to what I needed to do for Linux this was a breeze!

First we need the VMWare tools again so I grabbed windows.iso from /vmimages/tools-isomages.

The driver files are in a cab file, VMXNET3.cab, extract this cab file somewhere and open the Altiris PXE Configuration tool.

Select the Windows PE Entry and click Edit:

Then click Edit Boot Image:

(more…)

I was booting a new VMWare Virtual Machine with Windows PE through Altiris for initial deployment but Windows PE halted with a BSOD:

0x0000005D means UNSUPPORTED_PROCESSOR (defined in bugcodes.h) so I expected there was a x86 vs x64 problem.

The VM was configured for a 32 bit OS:

The Altiris Job was configured to use Auto Select:

But instead of the x86 version of Windows PE, Altiris attempts to boot the x64 version and this explains the BSOD: VMWare prevents the CPU from going to x64 mode and thus Windows has no choice but to halt.

Workaround is to change the Automation pre-boot environment in Altiris to x86:

Note that it’s no problem to deploy an x64 OS using the x86 version of Windows PE so I don’t see any real problems with this workaround.