> I was not asking to be spoon fed.  I spent several days bouncing around
> various documents, web sites, forums, news groups, etc. trying to find
> something that would point me in the right direction.  Mostly what I found
> was a huge pool of unconnected information.  It is often difficult to discern
> if the informaton you are reading pertains to Vista, to XP, or even to
> Windows 3.1.
>
> I did ask some specific questions.
>
> 1.  Is there a way to make Windows XP automatically log the user off when he
> terminates an application that was automatically loaded on logging in?  I
> have found many references to setting up the automatic log in, with more
> options than I could have ever imagined.  So, I can pick one and go with it,
> but there doesn't appear to be any information about which of the options
> might be more or less secure, which options are likely to be around in the
> future, which might go away, etc.
>
> 2.  My second question was asking for a road map regarding recommended
> practices for starting up and shutting down applications.  I can spend weeks
> reading through numerous posts about what does and doesn't work, often with
> no way to tell what expertise the poster has.  There are numerous instances
> where Microsoft has provided guidance regarding recommended ways of doing
> things.  I was looking for a place to start my research.  It sounds to me
> like there are no documented suggestions, so I am forced to pick a direction
> and hope it doesn't lead to a dead end.  I had hoped that someone could help
> me avoid some known pit falls.
>
> Thanks for your input.
>
> jfh
> --
> jfh

"Jaelani" wrote:

> 1. AFAIK, a user can only be automatically logged off by Windows
> itself if the shell process is terminated. You will have to use a
> third party software or a script if you want that to happen for any
> application you have specified. For me, I would rather use a script
> which is launched at user login. In turn, that script will launch the
> needed application and wait until it is terminated. When that happen,
> the script can logoff the current user.
>
> 2. There are many ways to make an application automatically launched
> at system startup or at user login. Many are stored in the registry
> and some in configuration files. Almost all available methods can be
> used with all kind of applications. But there are restrictions such as
> type of application, dependency with other application, security/
> privilege, and timing issues. It would be a bit too long to describe
> each methods.

> 1.  You suggest a script launced at login, that starts the application(s),
> waits for them to terminate, then logs off.  I can easily write a .bat file
> and place it in the users startup folder.  If it simply starts the
> application in line, it will sit there until the application exits.  I can
> then put a logoff comand in the .bat file.  Is this what you had in mind?
>
> 2.  I am aware of at least 13 different places to specify an application or
> program to be run at system startup or login.  You said, "But there are
> restrictions such as type of application, dependency with other application,
> security/privilege, and timing issues. It would be a bit too long to describe
> each methods."  Where are these restrictions documented?  Where can I go to
> get details about each of the methods?  This is the fundamental problem I am
> having right how.  There are too many choices and I have no information on
> which to base a decision about which choice to use.  I was hoping that I
> didn't have to try each choice independently and run countless tests on each
> configuration to determine what was best.  I hoped, I could learn from
> others.  Is there no one who knows, or is willing to share this info?
>
> --
> jfh

"Jaelani" wrote:

> 1. Yes, that's exactly what I have in mind. Don't know if Windows
> Script (WSC, JS or VBS) is capable of performing this task, but if it
> does, it can be used to avoid having a console window.
>
> 2. None that I know of, sorry. Most websites describes only several
> methods. In Microsoft website, this information are scattered. Some
> are in the Knowledge Base and some are in the MSDN Online Library. The
> least known and hard to find ones are the ones from the Knowledge Base
> which are usually provided for administrators and programmers in
> technical manner. Some only contain instructions on how to utilize it
> without explaining what it actually do, what it requires and what is
> affects in details.
>
>
> As far as I can see, you want your system to run in so-called "kiosk"
> mode where your main application starts automatically PRIOR the
> windows desktop by replacing the shell. However, some Windows
> components may not yet be available during this stage. You application
> might need to manually start any required components that are not yet
> available.
>
>
> John Hughes wrote:
> > 1.  You suggest a script launced at login, that starts the application(s),
> > waits for them to terminate, then logs off.  I can easily write a .bat file
> > and place it in the users startup folder.  If it simply starts the
> > application in line, it will sit there until the application exits.  I can
> > then put a logoff comand in the .bat file.  Is this what you had in mind?
> >
> > 2.  I am aware of at least 13 different places to specify an application or
> > program to be run at system startup or login.  You said, "But there are
> > restrictions such as type of application, dependency with other application,
> > security/privilege, and timing issues. It would be a bit too long to describe
> > each methods."  Where are these restrictions documented?  Where can I go to
> > get details about each of the methods?  This is the fundamental problem I am
> > having right how.  There are too many choices and I have no information on
> > which to base a decision about which choice to use.  I was hoping that I
> > didn't have to try each choice independently and run countless tests on each
> > configuration to determine what was best.  I hoped, I could learn from
> > others.  Is there no one who knows, or is willing to share this info?
> >
> > --
> > jfh
>

> I currently have a .bat file that I am placing in the users startup folder
> which starts the applications correctly.  I am having numerous issues with
> making things work just the way I would like, but the basic concept is
> working.  Thanks for your help with this.
>
> The "kiosk" mode is exactly what I am trying to set up.  Is there more
> documentation about how to do this somewhere?  Or, is this another example of
> things that will have to be mined out of the extensive online resources?
>
> Again, I thank you for your help.
>
> --
> jfh
>
>
> "Jaelani" wrote:
>
> > 1. Yes, that's exactly what I have in mind. Don't know if Windows
> > Script (WSC, JS or VBS) is capable of performing this task, but if it
> > does, it can be used to avoid having a console window.
> >
> > 2. None that I know of, sorry. Most websites describes only several
> > methods. In Microsoft website, this information are scattered. Some
> > are in the Knowledge Base and some are in the MSDN Online Library. The
> > least known and hard to find ones are the ones from the Knowledge Base
> > which are usually provided for administrators and programmers in
> > technical manner. Some only contain instructions on how to utilize it
> > without explaining what it actually do, what it requires and what is
> > affects in details.
> >
> >
> > As far as I can see, you want your system to run in so-called "kiosk"
> > mode where your main application starts automatically PRIOR the
> > windows desktop by replacing the shell. However, some Windows
> > components may not yet be available during this stage. You application
> > might need to manually start any required components that are not yet
> > available.
> >
> >
> > John Hughes wrote:
> > > 1.  You suggest a script launced at login, that starts the application(s),
> > > waits for them to terminate, then logs off.  I can easily write a .bat file
> > > and place it in the users startup folder.  If it simply starts the
> > > application in line, it will sit there until the application exits.  I can
> > > then put a logoff comand in the .bat file.  Is this what you had in mind?
> > >
> > > 2.  I am aware of at least 13 different places to specify an application or
> > > program to be run at system startup or login.  You said, "But there are
> > > restrictions such as type of application, dependency with other application,
> > > security/privilege, and timing issues. It would be a bit too long to describe
> > > each methods."  Where are these restrictions documented?  Where can I go to
> > > get details about each of the methods?  This is the fundamental problem I am
> > > having right how.  There are too many choices and I have no information on
> > > which to base a decision about which choice to use.  I was hoping that I
> > > didn't have to try each choice independently and run countless tests on each
> > > configuration to determine what was best.  I hoped, I could learn from
> > > others.  Is there no one who knows, or is willing to share this info?
> > >
> > > --
> > > jfh
> >

> I currently have a .bat file that I am placing in the users startup folder
> which starts the applications correctly.  I am having numerous issues with
> making things work just the way I would like, but the basic concept is
> working.  Thanks for your help with this.
>
> The "kiosk" mode is exactly what I am trying to set up.  Is there more
> documentation about how to do this somewhere?  Or, is this another example of
> things that will have to be mined out of the extensive online resources?
>
> Again, I thank you for your help.
>
> --
> jfh
>
>
> "Jaelani" wrote:
>
> > 1. Yes, that's exactly what I have in mind. Don't know if Windows
> > Script (WSC, JS or VBS) is capable of performing this task, but if it
> > does, it can be used to avoid having a console window.
> >
> > 2. None that I know of, sorry. Most websites describes only several
> > methods. In Microsoft website, this information are scattered. Some
> > are in the Knowledge Base and some are in the MSDN Online Library. The
> > least known and hard to find ones are the ones from the Knowledge Base
> > which are usually provided for administrators and programmers in
> > technical manner. Some only contain instructions on how to utilize it
> > without explaining what it actually do, what it requires and what is
> > affects in details.
> >
> >
> > As far as I can see, you want your system to run in so-called "kiosk"
> > mode where your main application starts automatically PRIOR the
> > windows desktop by replacing the shell. However, some Windows
> > components may not yet be available during this stage. You application
> > might need to manually start any required components that are not yet
> > available.
> >
> >
> > John Hughes wrote:
> > > 1.  You suggest a script launced at login, that starts the application(s),
> > > waits for them to terminate, then logs off.  I can easily write a .bat file
> > > and place it in the users startup folder.  If it simply starts the
> > > application in line, it will sit there until the application exits.  I can
> > > then put a logoff comand in the .bat file.  Is this what you had in mind?
> > >
> > > 2.  I am aware of at least 13 different places to specify an application or
> > > program to be run at system startup or login.  You said, "But there are
> > > restrictions such as type of application, dependency with other application,
> > > security/privilege, and timing issues. It would be a bit too long to describe
> > > each methods."  Where are these restrictions documented?  Where can I go to
> > > get details about each of the methods?  This is the fundamental problem I am
> > > having right how.  There are too many choices and I have no information on
> > > which to base a decision about which choice to use.  I was hoping that I
> > > didn't have to try each choice independently and run countless tests on each
> > > configuration to determine what was best.  I hoped, I could learn from
> > > others.  Is there no one who knows, or is willing to share this info?
> > >
> > > --
> > > jfh
> >