Jump to content

Html-Kit Switches


Recommended Posts


Yes, pskill is a better option.

Because, I've found that XP home doesn't have the taskkill.exe facility usable. So, I need to use pskill instead, for XP home unattended scripts. And since I want to standardise on the scripts I use for pro and home, I end up using pskill on both.

Pskill is simple to use. SysInternals.com has a free package called PsTools that give many of the (unix) tools that we want on the windows command-line. PsKill is one of those, and is powerful and simple to use.

http://www.sysinternals.com/ntw2k/freeware/pskill.shtml

Windows NT/2000 does not come with a command-line 'kill' utility. You can get one in the Windows NT or Win2K Resource Kit, but the kit's utility can only terminate processes on the local computer. PsKill is a kill utility that not only does what the Resource Kit's version does, but can also kill processes on remote systems. You don't even have to install a client on the target computer to use PsKill to terminate a remote process.
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...