Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1080
  • Last Modified:

Killing the process using a long file name

Is it possible to kill a process in Windows 2000 Server from the command line when the only information you have is the long file name?
0
billy21
Asked:
billy21
  • 6
  • 5
  • 4
  • +3
4 Solutions
 
SheharyaarSaahilCommented:
Hello billy21 =)

try to make it shorter.... like e.g the process name is ABCDEFGHIJKLM.exe
try making it ABCDEF~1.exe
means the first six characters, then a ~ then 1, then extension
0
 
billy21Author Commented:
What if it's ABCDEF~2.exe or even ABCDEF~6.exe.  Is there a more certain way?  Or even a way to find out the specific short name?
0
 
jdeclueCommented:
Yes... you need the Windows 2000 server resource kit, there is a tool to kill the process. If someone else doesn't reply first, I am off to see if I can find the name and how I did it.

J
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
jdeclueCommented:
Ok... forget that. What are you using to kill the process now. I use to be able to use the command line to view all of the processes, search them, and then pass the PIDs to the kill app.

j
0
 
SheharyaarSaahilCommented:
:)

my dear if u will goto Command Prompt and will try to see the files with names more than 7 characters.... u will see that all of them have been shorten to ABCDEF~1.exe..... DOS shortens all Long File Names using this format.....

why dont u give it a try urself..... start command prompt and try to search for long File Names..... u will get the idea :)
0
 
billy21Author Commented:
Yes but if I have three files..

ABCDEFGHIJKLM.exe - This would be called ABCDEF~1.exe
ABCDEFGHIJKLA.exe - This would be called ABCDEF~2.exe
ABCDEFGHIJKLB.exe - This would be called ABCDEF~3.exe
0
 
billy21Author Commented:
I used to have a command line utility that could even kill a process remotely.  Can't remember what that was called.  It could provide a list of PIDs too.
0
 
jdeclueCommented:
Yup.... when you do that use "DIR /X" to see the short names.

J
0
 
jdeclueCommented:
How about a real scenario... what exactly are you encountering? No if I's please. ;)

J

0
 
SheharyaarSaahilCommented:
yes i know that :)

but are u trying to say that all those files wud be running in background,,,,, first of all its a rare case that u will get such type of coincidence,,, secondly if by chance u have it,,, then im sure they all are not in the bakground processes.... when u will use the shorten name.... it will only kill the process of its running,,,, if its not running then it will give u an error...... !!!!

Are u trying to do it more Professionally :)
0
 
billy21Author Commented:
Sorry.  Someone just asked me this question.  i'm not certain of all the details.  He's gone home now.  We are programmers.  I'm guessing he needs to come up with an automated process.
0
 
nomi17Commented:
Here's a Command Line process killer that you may want to try out (it's freeware):
http://www.beyondlogic.org/solutions/processutil/processutil.htm
0
 
jdeclueCommented:
OK... developers... now that is a different story... from a development point of view it is much easier than scripting it. You can easily right a process that sees them with there long file names.
0
 
jkrCommented:
Use 'pskill' (http://www.sysinternals.com/ntw2k/freeware/pskill.shtml), e.g.

pskill TheProcessHasAReallyLongWoundNameButICanTypeIt.exe

usage: pskill [-?] [\\computer [-u username] [-p password]] <process name | process id>
0
 
billy21Author Commented:
For some reason he needs to do it from the command line.  Since I have no more info I might just end this here and split these points so not to waste your time.  I have a bunch of suggestions for my colleague so thank you all for your time.

-Billy
0
 
jdeclueCommented:
Wow, I have never seen so many people respond. I don't need points for this ;) Good luck.

J
0
 
BigC666Commented:
howdy,

have a look at this http://www.xmlsp.com/pview/prcview.htm

this will kill a process and show the pid of all running.

hope that this helps
0
 
SheharyaarSaahilCommented:
>> I have a bunch of suggestions for my colleague

lol :D
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 6
  • 5
  • 4
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now