How to identify a given VBScript from others on Process List??
I have quite a few VB Scripts running concurrently; the whole set is duplicated on several PCs, all running conncurrently on all PCs. Most of the PCs are free running, and occassionally I check in on them using LOGMEIN.COM. Occassionally there is a problem with one script and I need to just kill it off the Process list and restart it. But I do not know which {wscript] entry on the Process list is which. Is there a way to name a script so that it is identifiable on the list?
Alternatively (maybe preferrrably), a way to make a script that kills a certain script? If so I would just make a selection of script killers.
OS = Vista Biz 32
Alternatively (maybe preferrrably), a way to make a script that kills a certain script? If so I would just make a selection of script killers.
OS = Vista Biz 32
ASKER
"Executable"?? I am getting progressively handier at VBScript, but do not want to get into VB. Is that what you meant? Is it possible there is some sort of 'compiler' that will take a VB script and spit out a VB program?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wikkard: wow, thanks. I had no idea such were available. VBS2EXE looks quite good, and is a whopping nine bucks. I'll give it a go.
Do you think the EXE file will execute faster than the VBS?
Do you think the EXE file will execute faster than the VBS?
ASKER
Thanks for being so timely.
Mike
Mike
It may run a little faster, it all depends how the converter utility (vbs2exe for example) works internally.
If they actually convert the code to native code then it could run faster depending on what the scripts actually do.
If they actually convert the code to native code then it could run faster depending on what the scripts actually do.
I would suggest you look into creating executables from your scripts, this would be fairly easy to do. This would allow you to name each one as needed.