TD suddenly starts reporting internal error after build or dep.check

[Guest]

After having done a few configurations before without problems, TD suddenly started coming with errors at the end of an image build. Also, when deleting a component from the configuration, a similar error comes up

"An internal error occurred while building the run-time image
"code=0x80070057
"description=the parameter is incorrect

I ran a few fixes (QFE's Q811279, Q823025 and Q832662, not in any particular order) but this didnt help. Does anybody have an idea what is causing this, and how I can resolve it? Thanks

Avi

 

[Brad Combs]

Avi,

The image is probably estimated as too large. It's a known issue.

http://groups.google.com/groups?hl=...c2e1ee%24d4c15020%243401280a%40phx.gbl&rnum=2.

HTH,

Brad Combs
Imago Technologies

After having done a few configurations before without problems, TD

suddenly started coming with errors at the end of an image build. Also, when
deleting a component from the configuration, a similar error comes up:

"An internal error occurred while building the run-time image"
"code=0x80070057"
"description=the parameter is incorrect"

I ran a few fixes (QFE's Q811279, Q823025 and Q832662, not in any

particular order) but this didnt help. Does anybody have an idea what is
causing this, and how I can resolve it? Thanks.

 

[Guest]

2 GB image is too large???? this makes working with TD a real pain, the posting you referred to was march 2003, how much time does MS need to fix a serious bug like this? Any reply from MS people on this

Thanks for the link Brad

 

[Brad Combs]

Avi,

From a strictly embedded standpoint 2GB is not suitable for about 99.5% of
the target hardware out there (Most of my targets are >200 MB). You can put
a giant hard disk in a system and boot a 2GB image, but at that size
wouldn't it be pretty close to Pro? Unless maybe you're supporting MUI. If
that's the case look through some old posts on how to deal with this issue.
HTH,

Brad Combs
Imago Technologies

2 GB image is too large???? this makes working with TD a real pain, the

posting you referred to was march 2003, how much time does MS need to fix a
serious bug like this? Any reply from MS people on this?

 

[Guest]

Brad
The only reason we are using XP embedded, because we can automatically generate a 'stable' OS that can use EWF to keep the one and only application running for years without worrying about incorrect windows shutdowns and changes to the system. So, the footprint is not an issue at all, and the application needs a lot resources..

Av

----- Brad Combs wrote: ----

Avi

From a strictly embedded standpoint 2GB is not suitable for about 99.5% o
the target hardware out there (Most of my targets are >200 MB). You can pu
a giant hard disk in a system and boot a 2GB image, but at that siz
wouldn't it be pretty close to Pro? Unless maybe you're supporting MUI. I
that's the case look through some old posts on how to deal with this issue
HTH

Brad Comb
Imago Technologie


posting you referred to was march 2003, how much time does MS need to fix
serious bug like this? Any reply from MS people on this