Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > microsoft.public.scripting.vbscript > #11964 > unrolled thread

Stopping background script

Started by"Dave \"Crash\" Dummy" <invalid@invalid.invalid>
First post2018-05-25 15:25 -0400
Last post2018-05-26 10:34 -0400
Articles 7 — 4 participants

Back to article view | Back to microsoft.public.scripting.vbscript


Contents

  Stopping background script "Dave \"Crash\" Dummy" <invalid@invalid.invalid> - 2018-05-25 15:25 -0400
    Re: Stopping background script "Dave \"Crash\" Dummy" <invalid@invalid.invalid> - 2018-05-25 15:41 -0400
      Re: Stopping background script "Auric__" <not.my.real@email.address> - 2018-05-26 06:53 +0000
        Re: Stopping background script "Dave \"Crash\" Dummy" <invalid@invalid.invalid> - 2018-05-26 10:23 -0400
      Re: Stopping background script JJ <jj4public@vfemail.net> - 2018-05-26 14:24 +0700
    Re: Stopping background script "R.Wieser" <address@not.available> - 2018-05-26 11:04 +0200
      Re: Stopping background script "Dave \"Crash\" Dummy" <invalid@invalid.invalid> - 2018-05-26 10:34 -0400

#11964 — Stopping background script

From"Dave \"Crash\" Dummy" <invalid@invalid.invalid>
Date2018-05-25 15:25 -0400
SubjectStopping background script
Message-ID<pe9nvs$72h$1@dont-email.me>
I have a small VBS script that starts at startup and then runs
continuously in the background. How can I locate and stop the script?
I've done it before, but that was long before Windows 10 and the onset
of senility. I know there is a list of running applications somewhere...

-- 
Crash

Genius is the ability to see the obvious.

[toc] | [next] | [standalone]


#11965

From"Dave \"Crash\" Dummy" <invalid@invalid.invalid>
Date2018-05-25 15:41 -0400
Message-ID<pe9otd$da7$1@dont-email.me>
In reply to#11964
Dave "Crash" Dummy wrote:
> I have a small VBS script that starts at startup and then runs 
> continuously in the background. How can I locate and stop the script?
>  I've done it before, but that was long before Windows 10 and the
> onset of senility. I know there is a list of running applications
> somewhere...

Okay, I found how to stop wscript.exe, but it doesn't say which script
it is hosting. I'll have to see what happens if I have multiple scripts 
running.
-- 
Crash

I take great pride in my humility.

[toc] | [prev] | [next] | [standalone]


#11966

From"Auric__" <not.my.real@email.address>
Date2018-05-26 06:53 +0000
Message-ID<XnsA8EDF2F78A7E6auricauricauricauric@85.214.115.223>
In reply to#11965
Dave "Crash" Dummy wrote:

> Dave "Crash" Dummy wrote:
>> I have a small VBS script that starts at startup and then runs 
>> continuously in the background. How can I locate and stop the script?
>>  I've done it before, but that was long before Windows 10 and the
>> onset of senility. I know there is a list of running applications
>> somewhere...
>
> Okay, I found how to stop wscript.exe, but it doesn't say which script
> it is hosting. I'll have to see what happens if I have multiple scripts 
> running.

Sysinternals Process Explorer will display a process's command line in the 
Properties dialog. I imagine other, similar programs can as well.

-- 
You howl and wail like a banshee.

[toc] | [prev] | [next] | [standalone]


#11969

From"Dave \"Crash\" Dummy" <invalid@invalid.invalid>
Date2018-05-26 10:23 -0400
Message-ID<pebqld$o9h$1@dont-email.me>
In reply to#11966
Auric__ wrote:
> Dave "Crash" Dummy wrote:
> 
>> Dave "Crash" Dummy wrote:
>>> I have a small VBS script that starts at startup and then runs 
>>> continuously in the background. How can I locate and stop the
>>> script? I've done it before, but that was long before Windows 10
>>> and the onset of senility. I know there is a list of running
>>> applications somewhere...
>> Okay, I found how to stop wscript.exe, but it doesn't say which
>> script it is hosting. I'll have to see what happens if I have
>> multiple scripts running.
> 
> Sysinternals Process Explorer will display a process's command line
> in the Properties dialog. I imagine other, similar programs can as
> well.

Thanks! I have Process Explorer and located the instance of Wscript.exe
that is running my script.
-- 
Crash

I'm not archaic, I'm retro!

[toc] | [prev] | [next] | [standalone]


#11967

FromJJ <jj4public@vfemail.net>
Date2018-05-26 14:24 +0700
Message-ID<1nhlnw51yte3f.1rgcuqgev6fd9.dlg@40tude.net>
In reply to#11965
On Fri, 25 May 2018 15:41:32 -0400, Dave "Crash" Dummy wrote:
> Dave "Crash" Dummy wrote:
>> I have a small VBS script that starts at startup and then runs 
>> continuously in the background. How can I locate and stop the script?
>>  I've done it before, but that was long before Windows 10 and the
>> onset of senility. I know there is a list of running applications
>> somewhere...
> 
> Okay, I found how to stop wscript.exe, but it doesn't say which script
> it is hosting. I'll have to see what happens if I have multiple scripts 
> running.

Use WMI's Win32_Process class to find the process commandline and kill it.

[toc] | [prev] | [next] | [standalone]


#11968

From"R.Wieser" <address@not.available>
Date2018-05-26 11:04 +0200
Message-ID<peb7vu$1hgu$1@gioia.aioe.org>
In reply to#11964
Dave,

> How can I locate and stop the script?

If stopping the script is all you're out for, than you could have it create 
a dummy file (in the temp folder?) and have it regulary check if its still 
there.  If not, terminate.

That way the only thing you need to do is to delete that dummy file ...

Though I agree with the other posters that having a program handy by which 
you can actually find the program which is running the script is 
preferrable.

... just don't run the same script twice. :-)

Regards,
Rudy Wieser 

[toc] | [prev] | [next] | [standalone]


#11970

From"Dave \"Crash\" Dummy" <invalid@invalid.invalid>
Date2018-05-26 10:34 -0400
Message-ID<pebr8q$sfs$1@dont-email.me>
In reply to#11968
R.Wieser wrote:
> Dave,
> 
>> How can I locate and stop the script?
> 
> If stopping the script is all you're out for, than you could have it
>  create a dummy file (in the temp folder?) and have it regulary check
>  if its still there.  If not, terminate.
> 
> That way the only thing you need to do is to delete that dummy file 
> ...

Thanks! I use text files to otherwise modify running scripts. In fact, a
modification to one of those data files is why I wanted to stop and
restart the script, which only loads the data at startup.

> Though I agree with the other posters that having a program handy by
>  which you can actually find the program which is running the script
>  is preferrable.

Yes. As it happens, I am only running one script in the background so
there is only one instance of wscript.exe running, which I can stop in
Task Manager.

> ... just don't run the same script twice. :-)

No.

FYI, the script I wanted to restart is one that randomly selects the
quotation I include with my signature.
-- 
Crash

Whenever I meet a hot chick these days she's wearing scrubs.

[toc] | [prev] | [standalone]


Back to top | Article view | microsoft.public.scripting.vbscript


csiph-web