visibility question...

[Guest]

Hi,

Want to confirm if I am doing it right or not: Rebuild an image with .slx
which has standby problem (visibility=200), somehow, using the same .slx file
and rebuild it with visibility=1000 (default) ==> during the build process, I
saw a total 13 unnecessary component being removed: Class install - pcmcia &
flash memory, Network protocol. imaging devices & multi-port serial. class
install library - Eqnclass, Spx, Dgsetup & Dgrpsetu. CoDevice Installer -
multi-port serial, Primitive: MPRUI, common control library Policy 6, DGI+
Policy XPSP1, windows XP service pack 1 resource dll, C Runtime Library.
After that, "dependencies" checked and runtime image built with no error or
warnings.

Somehow, this image does not have the standby issue I had before !! Any
idea on why ?? or which component could be causing the system not to go in
standby ? Is it O.K. to use runtime image built with visibility = 1000 ?

Best regards,
Lawless

 

[KM]

Lawless,

This is the first time I hear that Visibility setting has any affect on the list of components that are includes by
DependencyChecker.
You have Auto-Resolve Dependency option turned on, right?
And you are saying that when you only changed the TD MinVisibility option from 200 to 1000 and re-build you saw some unnecessary
component being removed?

Just a theory: if you don't have some Class Installer components in your image, some drivers were not properly install or not
install at all. This may cause the Stanby feature not working.

 

[Michael Bate]

I have a very similar problem with visibility, as describe in this Jan
2005 post.

I have a RealTek audio device that requires installation after system
build. There is no .SLD component (or .INF either). When I do the
installation, it requires the file WDMAUD.DRV. This file is available
in a primitive with visibility 200. I set the Min Visibility to 100 (in
order to see everything - I could have set it to 200) and added the
component, then set it back to 1000 and performed Check Dependencies,
which immediately removed the component as being "unnecessary"

I reloaded the original SLX with WDMAUD.DRV, set the visibility to 100
and ran "Check Dependencies." This time the component was not removed.

According to my reading of the Help file, this is not how this is
supposed to behave. I assumed that "Visibility" affected only what was
visible in Target Designer, not what is included in the build.

Any comments?

BTW, this primitive is called for by a large number of other components,
most of which are specific to different brands of sound card. I could
not find one that appeared to be suitable for my situation and therefore
simply included the primitive.

- Michael Bate

Lawless,

This is the first time I hear that Visibility setting has any affect on the list of components that are includes by
DependencyChecker.
You have Auto-Resolve Dependency option turned on, right?
And you are saying that when you only changed the TD MinVisibility option from 200 to 1000 and re-build you saw some unnecessary
component being removed?

Just a theory: if you don't have some Class Installer components in your image, some drivers were not properly install or not
install at all. This may cause the Stanby feature not working.

Lawless wrote:

Hi,