Tim Golden wrote:
> | Tim Golden wrote:
> |
> | > [gel]
> | >
> | > | I have written a python client server app [...]
> | > | I want to run the client end of the app more or less invisibly
> | > | (no console) on the XP clients when ever a users logs on.
>
> [Tim G]
> | > The normal way is to run
> The reason for the a seperate persistant check is because it will be
> used to enable software to be installed in whole lab of PCs but only
> allow a predifined number to run the software at any time one time.
> And then when a user stop using the software a licence will become
> available to for
Tim Golden wrote:
> | > [gel]
> | >
> | > | I have written a python client server app [...]
> | > | I want to run the client end of the app more or less invisibly
> | > | (no console) on the XP clients when ever a users logs on.
>
> While this isn't answering the question you first
> asked, might
Ravi Teja wrote:
> gel wrote:
> > Hi
> > I have written a python client server app that keeps an eye on
> > processes starting and ending on a client and makes decision on what to
> > do based on information from the server end. I want to run the client
> > end of the app more or less invisibly
gel wrote:
> Hi
> I have written a python client server app that keeps an eye on
> processes starting and ending on a client and makes decision on what to
> do based on information from the server end. I want to run the client
> end of the app more or less invisibly (no console) on the XP clients
Roger Upole wrote:
> You can use the Task Scheduler to run a script at login.
> It's not as robust as creating a service, but it's much less
> work.
>
> Roger
>
OK thanks Roger I will have a bit a look at that option. It is fairly
important for the solution to be robust, but this maybe eno
Tim Golden wrote:
> | > [gel]
> | >
> | > | I have written a python client server app [...]
> | > | I want to run the client end of the app more or less invisibly
> | > | (no console) on the XP clients when ever a users logs on.
>
> While this isn't answering the question you first
> asked, might
| > [gel]
| >
| > | I have written a python client server app [...]
| > | I want to run the client end of the app more or less invisibly
| > | (no console) on the XP clients when ever a users logs on.
While this isn't answering the question you first
asked, might I suggest an alternative approach?
You can use the Task Scheduler to run a script at login.
It's not as robust as creating a service, but it's much less
work.
Roger
"gel" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Hi
> I have written a python client server app that keeps an eye on
> processes starting and
| Tim Golden wrote:
|
| > [gel]
| >
| > | I have written a python client server app [...]
| > | I want to run the client end of the app more or less invisibly
| > | (no console) on the XP clients when ever a users logs on.
[Tim G]
| > The normal way is to run a Win32 service. There are several
|
Tim Golden wrote:
> [gel]
>
> | I have written a python client server app [...]
> | I want to run the client end of the app more or less invisibly
> | (no console) on the XP clients when ever a users logs on.
>
> You say "when[]ever a user logs on" but does this app
> need to be run on a per-user
[gel]
| I have written a python client server app [...]
| I want to run the client end of the app more or less invisibly
| (no console) on the XP clients when ever a users logs on.
You say "when[]ever a user logs on" but does this app
need to be run on a per-user basis? Or could it run all
the
Hi
I have written a python client server app that keeps an eye on
processes starting and ending on a client and makes decision on what to
do based on information from the server end. I want to run the client
end of the app more or less invisibly (no console) on the XP clients
when ever a users log
13 matches
Mail list logo
