NTDETECT.COM missing from build

[Pete]

Why would NTDETECT.COM be missing in my build. I built an
image in TD without any warnings or errors but
ntdetect.com is not in the image. Please help me.

Pete

 

[Pete]

I just noticed that this only happens when the "Build
Type" is Debug. ????

 

[Pete]

I take that back, it happens on both debug and release.
It seems like this started happening after I installed
some QFEs.

 

[Pete]

I figured out my own problem. My bad.

 

[Slobodan Brcin \(eMVP\)]

And what was the problem at the end?

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Pete]

Slobodan - Actually, I am still seeing something a
problem happen when I build a debug type build. If I set
it to debug type, my ntdetect.com does not exist. If I
build in release mode, it works fine. I'm keeping the
destination the same.

 

[Brad Combs]

Pete,

It is a little confusing. Debug actually doesn't work in XPe. It's an issue
that has been noted and will probably be fixed in LHe.

HTH,
--
Brad Combs
Imago Technologies, LLC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

Pete,

Debug build is not currently supported by MS for XPe. Here is a quote: "None of the shipped components have a debug version, so
selecting a "Debug"
build actually gives an incomplete runtime image.".

 

[Pete]

Thank you all for the help.

-----Original Message-----

Slobodan - Actually, I am still seeing something a
problem happen when I build a debug type build. If I set
it to debug type, my ntdetect.com does not exist. If I
build in release mode, it works fine. I'm keeping the
destination the same.

.