1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

TASKEND vs. KILL.EXE

Discussion in 'Support' started by vefatica, Jun 23, 2008.

  1. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,883
    Likes Received:
    29
    Microsofts KILL.EXE, without "-f" (force), will terminate a FireFox session.
    TASKEND, without "/F", will not. This is significant in that if I use "TASKEND
    /F" ("/F" needed) on a ForeFox process then the next time I start FireFox I'm
    prompted to restore the previous, interrupted, session; whereas, with KILL
    (without "-f") I am not so prompted.
     
  2. samintz

    samintz Scott Mintz

    Joined:
    May 20, 2008
    Messages:
    1,188
    Likes Received:
    11
    What does TaskManager and/or Process Explorer do?

    -Scott

    vefatica <> wrote on 06/23/2008 01:12:27 PM:


    session.

    "TASKEND

    FireFox I'm

    KILL

     
  3. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,883
    Likes Received:
    29
    On Mon, 23 Jun 2008 12:17:11 -0500, you wrote:


    When I kill FireFox with TaskManager, a new one starts cleanly. When I kill it
    with ProcessExplorer, I get the "resume session" prompt. It's somewhat
    irrelevant since neither of those can be scripted.
     
  4. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    I managed to TASKEND Firefox properly but it required me to issue TASKEND <ff pid> several times quickly.

    Also TASKEND for notepad2.exe took at least two TASKEND commands. For builtin notepad.exe a single TASKEND seems to work every time though.

    As TASKEND /F simply kills/terminates the process instead of stopping it properly (sending SC_CLOSE to main window?) it naturally succeeds every time.
     
  5. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,883
    Likes Received:
    29
    Are you sure you killed it? After 6 TASKENDs FireFox disappeared from my desktop. But it was still running!
     
  6. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    I checked with Process Explorer.

    Sometimes Firefox may get stuck (permanently or just some seconds) when you close it, i.e. all FF windows are destroyed but the process is still running.
     
  7. nikbackm

    Joined:
    May 30, 2008
    Messages:
    194
    Likes Received:
    1
    Another TASKEND issue.

    When running as limited/normal user it displays this error message:

    C:\>taskend 3944
    TCC: (Sys) Not all privileges referenced are assigned to the caller.

    It still does its thing though.
     
  8. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    vefatica wrote:
    | ---Quote (Originally by nikbackm)---
    || I managed to TASKEND Firefox properly but it required me to issue
    || TASKEND <ff pid> several times quickly.
    ||
    || Also TASKEND for notepad2.exe took at least two TASKEND commands. For
    || builtin notepad.exe a single TASKEND seems to work every time though.
    ||
    || As TASKEND /F simply kills/terminates the process instead of stopping
    || it properly (sending SC_CLOSE to main window?) it naturally succeeds
    || every time.
    | ---End Quote---
    | Are you sure you killed it? After 6 TASKENDs FireFox disappeared
    | from my desktop. But it was still running!

    My normal way to kill Firefox is to run this batch program (killfox.btm):

    do while iswindow "*Firefox*"
    activate "*Firefox*" close
    delay 1
    enddo

    It works fine, and I don't get the "resume session/new" message from
    Firefox.

    TASKEND/F (for which I have the alias KILL) also terminated FF, but next
    start (even with the -url option) had the resume/new option.

    TASKEND without /F left 9 invsible FF windows (as reported by Vince's
    WHICHWIN). All were closed by KILLFOX.
    --
    Steve
     

Share This Page