Problem running FBA during "replacing registry hives"

[Guest]

When I try booting my target image for first time to let FBA run, XP Embedded
starts, FBA runs, but stops where it does the "replacing registry hives" with
an error: "System accounts manager initialization failed. A device attached
to the system is not functioning. Error: 0xc0000001". The machine then
reboots and BSODs.
I build the image with no errors or warnings, so I think all of the
components are there. I am using a SCSI drive, and have loaded the drivers
for it.

 

[KM]

Sturm,

First check \windows\FBALog.txt for any errors.

Make also sure you got proper Target Device settings set up in TD (one of the possible reason why you see the error could be that
you set wrong boot device settings for Windows directory).

Also, make sure you have got enough storage and RAM space to run through FBA (turn off pagefile is enabled).

 

[Guest]

I am using an SDI disk, 650MB, 192MB of RAM. The image is about 220MB in
size. I am trying to do this is VMWare, with vmware set to use physical disk
1 (the SDI disk, with a single partition which is set to active) to boot from
as a SCSI device. I have created my own VMWare SCSI disk .sld file with the
proper drivers and imported into the database. It does boot, but FBA gets the
error I mentioned. I will have a look at the FBA log file when I get back. I
have made sure that TD drive/partition settings are correct (C: is boot
drive, C:\windows and C:\documents and settings are alsp specified, as is the
correct partition and drive #. The drive size is also set to 650MB, it is a
FAT partition, and I have FAT and FAT format added to TD). Boot.ini looks
good too. Someone mentioned that I may need to specify some sort of offset
value in boot.ini if using an SDI disk to boot from? That sounded kind of
vague, anyone know more about that?

 

[KM]

Sturm,

Are you loading an SDI file locally?
I mean do you have something like this in your boot.ini:
ramdisk(0)\WINDOWS="Microsoft Windows XP Embedded" /fastdetect /rdpath=multi(0)disk(0)rdisk(0)partition(1)\ramdisk.sdi
/rdimageoffset=4096

The offset rdimageoffset should be set to the offset of the PART blob inside the SDI file. By default it is 4096 but you can check
it out with SDIMGR.wsf.

Since you mention you got to the phase when you see FBA runs, you got through the ntldr and most likely loading the SDI properly.
However, you don't want to capture pre-FBA image to the SDI. FBA will require a few reboots and it is not possible with the RAM
(SDI) boot.
You will need to run the image through FBA first and then capture the post-FBA image in an SDI file.