What Is oembios.bin For? Cannot Find Owning Component

[Guest]

Does anyone know what oembios.bin is for? It's fairly large, and I'd like to leave it out of my target image if I can

I cannot find the component that owns it, using the filter system, even with visibility cranked to the maximum.

 

[KM]

Theophilus,

The oembios.bin file goes with "Winlogon Support Files" component. You can
imagine Winlogon" depends on that component (and this is true).
Unfortunately for you, the "Winlogon Support Files" component visibility is
50 so you cannot see it regular way within TD.
You can see it, however, if you change the MinVisibility value for TD in
registry.

KM

Does anyone know what oembios.bin is for? It's fairly large, and I'd like

to leave it out of my target image if I can.

I cannot find the component that owns it, using the filter system, even

with visibility cranked to the maximum.

 

[Guest]

Thanks, but I have tried to change MinVisibility in the registry to a low value (say, 25), and after I restart Target Designer, the visibility in the Options dialog is still 100. I have changed every instance of MinVisibility in the registry to 25 and it is still the case. And a filter search for oembios.bin still comes up empty.

 

[KM]

Theophilus,

That is true :-( TD has a hardcoded minimum to 100.
Anyway.. you can use my XPeTools components (DependencyExplorer) to find out
component with visibility level from 0. That's what I am using here to
search for components.
You can find it on www.xpefiles.com (Development Uilities/Main).

KM

Thanks, but I have tried to change MinVisibility in the registry to a low

value (say, 25), and after I restart Target Designer, the visibility in the
Options dialog is still 100. I have changed every instance of MinVisibility
in the registry to 25 and it is still the case. And a filter search for
oembios.bin still comes up empty.

 

[KM]

Theophilus,

You are right. When I drag the component into my configuration, I do not see any section beside Setting either.
That must be a TD feature (not to explore components with visibility less than 100). Or a bug.

I don't know of any way to patch this "bug". Sorry about that.

You can always add/overwrite the oembios.bin file to your configuration using Add Extra Files section.

--
Regards,
KM

I patched Target Designer to remove the hard-coded limitation (it was overriding MinVisibility if less than 100). Now I can see

the "Winlogon Support Files" component.

...but when I expand the component, it doesn't show a Files node! It has a Settings node, but nothing else. Why would that be?

I just want to exclude oembios.bin without losing the other files in that component. Is there any way to force it to show that

Files node so I can "cross out" that one file?