Thanks for the response. The configuration was designed for remote boot
using the XP supplied boot server so the FBA agent, system cloning tool,
etc. components were included. I built the system the same way I have
for about 6 other similar machines I am evaluating, e.g. major steps
include: ran tap.exe on the HW under an XP Pro, import PMQ file to CD,
trim component for small footprint per MSDN article, import target
componet to database, build system with TD, transfer to target system,
boot to FBA including reboot and seal, transfer back to development
machine, and use SDI tools to construct boot image. This all worked
correctly about a month ago and I had a working image that was loaded by
the target via PXE. However I did not use this image for about a month
and now when it loads via PXE the progress bar completes, a startup blue
screen (not BSOD!) with XPe identified at the lower right appears for a
few seconds and then just when I expect to see my full screen command
window (I have not included a graphical interface -- I use Minlogon and
Command Shell) the video dies (screen goes black) and the monitor status
light changes from green to yellow. The system appears completely dead
as indicated by no signal to the monitor and no response to keyboard
input, not even CTL-ALT-DEL.
In order to determine if my SDI file was corrupted I rebuilt everything
from scratch -- I didn't even use the same SLX file and I got the same
result. Therefore I suspected that something has gone wrong with the HW
but it runs Windows and Linux flawlessly so I have no other ideas. I am
hoping that there is some way to debug what is going wrong in the XPe
boot process. Note that I have other images for other devices that are
also more than 1 month old and I have not seen this problem with the
other systems.
JT
