The point is that this particular build of Windows is Read Only, since it resides on CD.
Any build of NT based windows need specific mass storage drivers in order to be able to boot and see the machine hard disks.
Now, a VMware built image will have the specific VMware drivers, as ASSR
already found out the hard way with the SCSI/IDE HD image problem, and this is why the Dhilip89
tutorial includes a step to change them with the "Standard PCI IDE Controller" ones.
That's why I proposed the alternate way of building using Qemu (that way there is no need to change the drivers as a Qemu installed NT System already uses "Standard PCI IDE Controller" driver).
If a "normal" window on the particular machine use any Mass Storage Driver different from the "Standard PCI IDE Controller" one, it will most probably BSOD with STOP 0X0000007b.
In other words, ETBoot is NOT an easily "portable" build, it is more like a "diskless station" XP Embedded build, very specific to the hardware.
I have no idea
about an easy enough procedure to be able to change the drivers and/or customize the build for different machines, the only practical way I see is to build ETBoot directly on the target machine.
Any idea would be appreciated.