"BAD_SYSTEM_CONFIG_INFO" Error

[Noor Drummond]

Hi,

I am a little new to XP embedded, so my apologies if this
seems like a really simple question.

I run TAP, import all my drivers and build an image, all
of which works fine. However, when I attempt to boot the
image I created, off the F drive on my development machine
(C is the main drive, D is a DVD-ROM and E is a CD-
Writter) the OS begins to load (displaying the text-mode
progress bar). Just as I expect the XP splash screen to
appear I get a blue screen with a "BAD_SYSTEM_CONFIG_INFO"
error and code 0x00000074. My searches on the net suggest
that this error is due to a problem with the registry, but
I don't know how I can correct this. I have tried the
process several times and get the same error on a
completely different machine with completely different
hardware, as well as when I use TA instead of TAP.

Many thanks for any help. I have spent several days on
this and I really can't think of what to do next.

Regards,
Noor Drummond
(e-mail address removed)

 

[Lucvdv]

Hi,

I am a little new to XP embedded, so my apologies if this
seems like a really simple question.

I run TAP, import all my drivers and build an image, all
of which works fine. However, when I attempt to boot the
image I created, off the F drive on my development machine
(C is the main drive, D is a DVD-ROM and E is a CD-
Writter) the OS begins to load (displaying the text-mode
progress bar). Just as I expect the XP splash screen to
appear I get a blue screen with a "BAD_SYSTEM_CONFIG_INFO"
error and code 0x00000074.

Here are 2 possible situations, but I'm no more than 90% certain of
either that it causes this exact error code.


a) Is your development machine Win2000?

You need the XP boot loader in the active partition (C), just adding
XPe to the boot.ini of W2k alone doesn't work.
IIRC this was the reason the last time I had a stop 74.

Win2k can be started with an XPe boot loader, but not the other way
around. Just copy NTLDR and NTDETECT.COM from F: to C: (but don't
make any errors here ;-)

If you don't want to change your development system you can create a
boot floppy: format a floppy in Win2k or XP; copy boot.ini, NTLDR and
NTDETECT.COM from the XPe target drive onto it; and boot from that
floppy.


b) The target must be set up for booting as the correct drive letter
(root node in Target Designer, settings, target device settings), or
all registry entries will point to the wrong drive.

In your configuration, that may have to be drive D: (the 2nd harddisk
probably became F: now because it was installed after drive letters
were already assigned to the CD drives, for XPe everything will be new
and it could put the CD drives on E and F).

This doesn't always seem to be the case, sometimes a 2nd installation
inherits the drive letter assignments from the first: I think the
difference is whether you've allowed disk management to upgrade the
disks to dynamic or not.

 

[Andy Allred [MS]]

Noor,
The documentation for XPe states that you need to copy over the files
generated by Target Designer. This includes those boot/loader files that you
did not copy over.

Andy

 

[Bala Raja]

Andy:

I think MS has done an exceptional job with the
evaluation kit and documentation. However, Noor
is right. I'm still having problems booting winXPE on
my win2k development system. The documentation merely
states that files must be copied from the Windows
embedded images directory to the 2nd partition in
the development system. The documentation says nothing
about what to do when the dev. system is running win2K,
specifically the copying of the NT loader.

Regards,

Bala

 

[Noor Drummond]

Hi Andy,

Sorry if I caused offense, that was not my intention. All
I was trying to say is that it would be clearer if the
documentation explicitly stated this requirement. When
working on a development machine the boot drive has an
ntldr and ntdetect, so one (especially newbies like me) is
prone to assume that these should not be overwritten.
Also, this issue does not arise when developing on XP and
you can't directly copy the boot.ini, otherwise the win2k
installation becomes invisible.

Once again, sorry if I caused offense.

Regards,
Noor Drummond
(e-mail address removed)

 

[Andy Allred [MS]]

Hey Noor, I'm not offended, i'm just trying to help by supplying some
additional information.

And I'm glad to help you, so ask any question you want. <grin>

Also, we do take your feedback seriously, so if there is a problem with the
documentation or any other aspect of XPe, please let us know.

--
Andy

This posting is provided "AS IS" with no warranties, and confers no
rights.
=====================================================

 

[Andy Allred [MS]]

I see your other thread on this issue, i'll try to help you there.

--
Andy

This posting is provided "AS IS" with no warranties, and confers no
rights.
=====================================================