FBA Reboots Repeatedly
5/10/2007
Learn what to do when FBA reboots repeatedly.
Resolutions
If you are using Enhanced Write Filter (EWF), verify that you deleted the previous EWF volume. For more information, see Troubleshooting Enhanced Write Filter.
Otherwise, check the beginning of the fbalog.txt file to see if there are "invalid path" errors. If there are, then you need to rebuild your run-time image in the correct boot drive:
- In Target Designer, open your .slx file.
- In the Configuration Editor Pane, expand the .slx file and then choose Settings.
- On the Windows XP Embedded Client tab in the Details Pane, under Target Device Settings, choose Show.
The Target Device Settings appear. - Verify the boot drive and the locations of the Windows folders.
If you are using Enhanced Write Filter (EWF), verify that you deleted the previous EWF volume. For more information, see Troubleshooting Enhanced Write Filter.
Otherwise, check the beginning of the fbalog.txt file to see if there are "invalid path" errors. If there are, then you need to rebuild your run-time image in the correct boot drive:
- In Target Designer, open your .slx file.
- In the Configuration Editor Pane, expand the .slx file and then choose Settings.
- On the Windows XP Embedded Client tab in the Details Pane, under Target Device Settings, choose Show.
The Target Device Settings appear. - Verify the boot drive and the locations of the Windows folders.
Example
First Boot Agent (FBA) runs for several seconds, and then reboots repeatedly.
Some FBA reboots are to be expected when you configure some features. For example, if you add the Enhanced Write Filter to your run-time image, this will cause two reboots during the FBA phase. However, if FBA continually reboots, there may be a problem with your run-time image configuration.
The run-time image should not be in the same partition that is used by the XP embedded tools. If it is, then FBA may try to process, register, and build binaries in the same path that the XP embedded tools are on and ultimately generate exception errors, such as "invalid path" errors.
Target Designer defaults to the C drive, so the destination partition on the target machine might need to be changed.