I'm not 100% sure but you may not need that dependency and it will probably
work well with your custom shell. This particular dependency chain usually
occurs (i believe) because TSF doesn't function with Minlogon so it has a
component dependency on Winlogon which in turn has a dependency on Explorer.
My image has always used Winlogon which didn't appear to have a
dependency on Explorer when built with SP2.
KM Dependancy Explorer ... in my XPE projects i always integrate the dependency and derive explorer ... The dependancy explorer has checkboxes to save the component chain script ...dependency explorer refuse to generate these files completely. ... I tested on development system "XP Professional with SP2 German" ... (microsoft.public.windowsxp.embedded)
Re: Session manager ...minlogon while the windows explorer component depends on winlogon.... the component from the config or modify it to remove the minlogon ...dependency, or disable minlogon or winlogon in you configuration. ... (microsoft.public.windowsxp.embedded)
Re: Custom Application on Custom Shell. ... for the first time I used winlogon + explorer shell and then ... > add the minlogon.... But while the dependency check the TD put the ... And It works quite well with FBA and after FBA. ... (microsoft.public.windowsxp.embedded)
Re: .Net 1.1 and MinLogon ... You can add .NET Framework in TD configuration and then do the dependency... Choose MinLogon and run the dependency check again. ... the .Net Framework 1.1 has a dependency on WinLogon> which also brings in Session Manager which conflicts with> MinLogon. ... (microsoft.public.windowsxp.embedded)
