G
Guest
In XPe, the Winlogon component (and in my case Automatic Logon) may be
replaced with the Minlogon component. The Minlogon component provides a
single-user auto logon as 'system user'. For many embedded applications,
this is a more appropriate logon scenario, because there are no 'logon'
activities for many embedded applications. The user may not even be aware
that Windows XP is running in the background.
XPe component help article "Building a Single or Multi User Baseline
Configuration" suggests using the command shell when the Minlogon component
is used. If you try to use Minlogon with the Explorer shell, it is not
possible because of dependencies of the Explorer shell to the Winlogon
component.
It seems reasonable to use the Explorer shell with Minlogon. Minlogon could
be seen as a subset of Winlogon, and very properly be used in the normal
Windows Explorer shell. Some articles suggest building a Winlogon system
with the TD and post-build substituting the Minlogon component. This
practice demonstrates the apparent necessity to use Minlogon with the
Explorer shell, but does compromise the build somewhat.
Is there a way to use Minlogon and the Explorer shell together, and build
the system in the normal way with TD?
If the Minlogon, Winlogon, and Explorer shell components were/are designed
to do this (i.e. minimize coupling, maximize cohesion), the use of Minlogon
with the Explorer shell seems natural.
It is my understanding that the "Explorer shell" has the 'normal' Windows
user interface components: taskbar, start menu, desktop, etc.
....Jim Hughen
replaced with the Minlogon component. The Minlogon component provides a
single-user auto logon as 'system user'. For many embedded applications,
this is a more appropriate logon scenario, because there are no 'logon'
activities for many embedded applications. The user may not even be aware
that Windows XP is running in the background.
XPe component help article "Building a Single or Multi User Baseline
Configuration" suggests using the command shell when the Minlogon component
is used. If you try to use Minlogon with the Explorer shell, it is not
possible because of dependencies of the Explorer shell to the Winlogon
component.
It seems reasonable to use the Explorer shell with Minlogon. Minlogon could
be seen as a subset of Winlogon, and very properly be used in the normal
Windows Explorer shell. Some articles suggest building a Winlogon system
with the TD and post-build substituting the Minlogon component. This
practice demonstrates the apparent necessity to use Minlogon with the
Explorer shell, but does compromise the build somewhat.
Is there a way to use Minlogon and the Explorer shell together, and build
the system in the normal way with TD?
If the Minlogon, Winlogon, and Explorer shell components were/are designed
to do this (i.e. minimize coupling, maximize cohesion), the use of Minlogon
with the Explorer shell seems natural.
It is my understanding that the "Explorer shell" has the 'normal' Windows
user interface components: taskbar, start menu, desktop, etc.
....Jim Hughen