in reply to A killall for Windows

Even though you warned that it would probably only work on NT flavors of Windows, I gave it run through in Win98. When run with no arguments, it displays the usage imformation as expected. When run with the -d command line option, it silently fails. When run with a process name, it will display the process name followed by a colon and the text "no process killed".
Who says that programmers can't work in the Marketing Department?
Or is that who says that Marketing people can't program?

Replies are listed 'Best First'.
Re: Re: A killall for Windows
by Dog and Pony (Priest) on Jun 04, 2002 at 15:09 UTC
    That would be a natural behaviour, I guess. What happens (judging by the sound of it), is that it finds no processes in the process list, probably because it tries to find NT processes. :)

    Maybe should patch it up to croak on no processes returned (that would never be able to happen on a "supported" platform).

    Thanks for the help!

    You have moved into a dark place.
    It is pitch black. You are likely to be eaten by a grue.
[reply]
      I tried this on an XP box and while it did return "no process killed" it did kill the process that I passed it. So not sure what is going on there. Pretty cool gizmo I like it -

      jschmitz
[reply]

In Section Code Catacombs