How to delete Winlogon Support Files?

  • Thread starter Thread starter alexnnr
  • Start date Start date
A

alexnnr

Hi,
I have normally working XPE build. Once upon a time I have increased
the boot partition to more than 1 GB (for hibernation support). So, I
included the Winlogon Support Files component to the build (files
oembios.*) Now I decided to abandon hibernation mode and restored the
partition size back to 120 MB. Since it is less than 1 GB, the build
don't need WSF component. But its visibility is less than 100. How can
I delete it from the configuraion? Of course I can delete files
oemsetup.* from the image but I hope any regular solution exists.
 
alexnnr,

Two possible ways:

1) Set the following reg.values:
[HKLM\SOFTWARE\Microsoft\Windows Embedded\Target Designer],MinVisibility=0
[HKLM\SOFTWARE\Microsoft\Windows Embedded\Component Designer],MinVisibility=0

2) Use XPeTools package (ConfigurationExplorer or DependencyExplorer component) to lower visibility level for your Configuration
only. (you will have to reload the Config after the vis change)
 
Thank you KM,
But, unfortunately, both methods don't work for me. Setting the
registry values lower than 100 doesn't decrease real visibility in TD,
it remains 100. (I already have read about this fact somewhere)
What about XPeTools. I set MinVisibility to 40 in the Dependency
Explorer and Configuration Explorer, saved and loaded again the
configuration, but still don't see any component with visibility lower
than 100. May be I do smth wrong? I heard about a patch for the TD.
Where can I get it?
 
alexnnr,

Sorry, did you changed that MinVisibility key under HKCU or HKLM key?
Should be HKCU.
E.g., [HKCU\SOFTWARE\Microsoft\Windows Embedded\Target Designer],MinVisibility=0.

I am on the road now and don't have access to my dev computer now with TD installed. When I get back to it I will double check the
steps I usually do to see components with vis.level < 100 (it is sometimes not easy).
 
AlexNNR,

Well... I remember that comment I made. THis is the reason I said I have to get back to my dev machine first :-) That will be next
week only.

The trick is that sometimes (!) it works just fine and I swear I could lower vis.level for my configuration to less than 100 and
see some really hidden components. But I could've played too much with CMI scripts there.

Btw, one possible workaround for you could be loading your SLX with CMIExplorer and deleting that component with a script. If you
want to know more about the tool, search this NG archive. We posted some scripts there.
 
Back
Top