Macro Component Bug or just me?

[Guest]

I have a piece of hardware x86 P4 Panel PC. Had to componentize the intel graphics chip, a SMBus driver, the Realtek Audio chip on it, and a custom pci card that has some serial chipset on it. The build is looking good and works great. No complaints there

What I want to do next is make a Macro component that drags in all of the relevant hardware components. This will allow people who buy the Panel PC to have a nice base starting point for their own developement and avoid some frustration

I took my .pmq off of the system (tap generated) and did a fresh import. There are 82 components associated with this build. We'll call this project space 'GOOD.slx'

I went to Component Designer made a Macro component that is dependent on these 82 components. I made a new project space (Bad.slx) and added this Macro component into it. I did a dependancy check (auto/resolve off) and did a dependancy check on my Macro component. I confirmed that it dragged in the 82 components. I confirmed the name and revision information for every component is an exact match in both project spaces

I turned on auto resolve on the dependancy check and went through both of the builds, chose a Winlogin/Explorer shell build. When they were done I again confirmed by hand (taking quite a bit of time) that each component was equivelent including revision of each component

My problem - Good.slx generates a working functional OS on my device. Bad .slx almost immediately blue screen crashes on startup (XPE splash screen and then blue screen - No FBA page at all)

I'm at a lose here. Has anyone seen anything similiar? I've recreated my results about 4 different times. Always if I import via .pmq it works. If I do not import then the build fails.

 

[Gordon Smith \(eMVP\)]

I've never witnessed that before. I use the 'import into CD to make a
hardware SLD' approach literally EVERY time I do a new XPE config. Did you
forget some other setting? Like maybe the drive letter change in your
settings for example?

--Gordon Smith (eMVP)

 

[Brad Combs]

Matt,

What is the blue screen that you are seeing? This will help solve the
problem. Thanks.

--
Brad Combs
Imago Technologies, LLC

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

I have a piece of hardware x86 P4 Panel PC. Had to componentize the intel

graphics chip, a SMBus driver, the Realtek Audio chip on it, and a custom
pci card that has some serial chipset on it. The build is looking good and
works great. No complaints there.

What I want to do next is make a Macro component that drags in all of the

relevant hardware components. This will allow people who buy the Panel PC
to have a nice base starting point for their own developement and avoid some
frustration.

I took my .pmq off of the system (tap generated) and did a fresh import.

There are 82 components associated with this build. We'll call this project
space 'GOOD.slx'.

I went to Component Designer made a Macro component that is dependent on

these 82 components. I made a new project space (Bad.slx) and added this
Macro component into it. I did a dependancy check (auto/resolve off) and
did a dependancy check on my Macro component. I confirmed that it dragged
in the 82 components. I confirmed the name and revision information for
every component is an exact match in both project spaces.

I turned on auto resolve on the dependancy check and went through both of

the builds, chose a Winlogin/Explorer shell build. When they were done I
again confirmed by hand (taking quite a bit of time) that each component was
equivelent including revision of each component.

My problem - Good.slx generates a working functional OS on my device. Bad

..slx almost immediately blue screen crashes on startup (XPE splash screen
and then blue screen - No FBA page at all).

I'm at a lose here. Has anyone seen anything similiar? I've recreated my

results about 4 different times. Always if I import via .pmq it works. If
I do not import then the build fails.

 

[Gordon Smith \(eMVP\)]

It sounds like you forgot a disk controller component.

 

[KM]

MattJ,

When you tool your .pmq off of the system and did a fresh import, did you do that in TD? (sounded like)
Why wouldn't you do that in CD directly? That will create the Macro component you need.

Also, check you min Visibility level set in TD. You may see only 82 components but it could be more (the components with lower
visibility are hidden for you). Set the min Visibility level in TD to a value <= 100.

Manually, check if components mentioned here
http://msdn.microsoft.com/library/d...html/xeerrstop7bmissingcriticalbootdevice.asp are in your
build (if you see 7B BSOD).

--
KM,
BSquare Corporation

I have a piece of hardware x86 P4 Panel PC. Had to componentize the intel graphics chip, a SMBus driver, the Realtek Audio chip

on it, and a custom pci card that has some serial chipset on it. The build is looking good and works great. No complaints there.

What I want to do next is make a Macro component that drags in all of the relevant hardware components. This will allow people

who buy the Panel PC to have a nice base starting point for their own developement and avoid some frustration.

I took my .pmq off of the system (tap generated) and did a fresh import. There are 82 components associated with this build.

We'll call this project space 'GOOD.slx'.

I went to Component Designer made a Macro component that is dependent on these 82 components. I made a new project space

(Bad.slx) and added this Macro component into it. I did a dependancy check (auto/resolve off) and did a dependancy check on my
Macro component. I confirmed that it dragged in the 82 components. I confirmed the name and revision information for every
component is an exact match in both project spaces.

I turned on auto resolve on the dependancy check and went through both of the builds, chose a Winlogin/Explorer shell build. When

they were done I again confirmed by hand (taking quite a bit of time) that each component was equivelent including revision of each
component.

My problem - Good.slx generates a working functional OS on my device. Bad .slx almost immediately blue screen crashes on startup

(XPE splash screen and then blue screen - No FBA page at all).

I'm at a lose here. Has anyone seen anything similiar? I've recreated my results about 4 different times. Always if I import

via .pmq it works. If I do not import then the build fails.

 

[Ann Adamson]

I have seen the same thing in the past, but I hadn't tried it again since
SP1 came out.
I planned to give it a try myself when I get the chance -- I will report
back what I find.

Ann Adamson

 

[Sean Liming \(eMVP\)]

Matt,

A lot of good answers have been posted so far. I also have not seen the
problem that you are running into, but the STOP 7B is a common problem. When
you ran TAP, was XP Pro SP1 running on your Panel PC or was the OS WinPE?

When you use Component Designer to create the Macro component, you might
want to add the "selector prototype" as the prototype for the component.
This builds in a picker list to you Macro component. Your customers can use
the picker list to choose the hardware device they want in the image. Saves
your customers time from running TAP.

Regards,

Sean Liming
XP Embedded Manager
A7 Engineering (www.a7eng.com)
Author: Windows XP Embedded Advanced and Windows NT Embedded Step-by-Step

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

I have a piece of hardware x86 P4 Panel PC. Had to componentize the intel

graphics chip, a SMBus driver, the Realtek Audio chip on it, and a custom
pci card that has some serial chipset on it. The build is looking good and
works great. No complaints there.

What I want to do next is make a Macro component that drags in all of the

relevant hardware components. This will allow people who buy the Panel PC
to have a nice base starting point for their own developement and avoid some
frustration.

I took my .pmq off of the system (tap generated) and did a fresh import.

There are 82 components associated with this build. We'll call this project
space 'GOOD.slx'.

I went to Component Designer made a Macro component that is dependent on

these 82 components. I made a new project space (Bad.slx) and added this
Macro component into it. I did a dependancy check (auto/resolve off) and
did a dependancy check on my Macro component. I confirmed that it dragged
in the 82 components. I confirmed the name and revision information for
every component is an exact match in both project spaces.

I turned on auto resolve on the dependancy check and went through both of

the builds, chose a Winlogin/Explorer shell build. When they were done I
again confirmed by hand (taking quite a bit of time) that each component was
equivelent including revision of each component.

My problem - Good.slx generates a working functional OS on my device. Bad

..slx almost immediately blue screen crashes on startup (XPE splash screen
and then blue screen - No FBA page at all).

I'm at a lose here. Has anyone seen anything similiar? I've recreated my

results about 4 different times. Always if I import via .pmq it works. If
I do not import then the build fails.

 

[Guest]

I have a resolution if not an explanation.

I orignally made the macro component by hand because of the behaviour of the custom PCI Card (and custom drivers). That's neither here nor there though.

What resolved it was importing the .inf to the CD directly and then make modifications at that point. Even though the Macro components ended up looking identical, again one would work and one wouldn't.

The parsing of the .pmq is doing something beyond just dragging in components. Is there any documentation on what the parser does besides the component drag in?

I still find it strange that I can have 2 identical project spaces (component wise) and have 1 work but not the other.

 

[Gordon Smith \(eMVP\)]

There are some components with the same exact name "Disk Drive" but are
really different. You may have chosen the wrong one in a list of apparant
duplicates.

--Gordon Smith (eMVP)

 

[vic]

It sounds like you forgot a disk controller component.

Or, perhaps, a different HAL component?

Vic

 

[KM]

I agree with Gordon.

So when you compare your pmq imported component to manually created Macro component, make sure you also check components' Extended
properties. Like in case of "Disk Drive", cmiXXXIds will be different.