winXP taskill runs via the cmd line but not via scheduled tasks or Explorer

[war_wheelan]

When I run 'taskill.cmd' (taskkill /f /im indii.exe /t NEWLINE Exit) in
command line mode, it works. If I attempt to run it via Scheduled
Tasks or Explorer it goes in to an infinite loop.

Has anyone experienced this phenomenon?

 

[Pegasus \(MVP\)]

This is perhaps because you have a batch file somewhere
that is called "taskkill.bat". Let's have a look at the command
line of your scheduled task!

When I run 'taskill.cmd' (taskkill /f /im indii.exe /t NEWLINE Exit) in
command line mode, it works. If I attempt to run it via Scheduled
Tasks or Explorer it goes in to an infinite loop.

Has anyone experienced this phenomenon?

This is perhaps because you have a batch file somewhere
that is called "taskkill.bat". Let's have a look at the command
line of your scheduled task!

 

[war_wheelan]

I renamed the .cmd to rabbit and received the same result(s). Also I
have other .cmd file(s) that I've created and they run with no problem.

 

[war_wheelan]

I forgot to mention something - the batch .bat / script .cmd files work
properly when executed from a command problem.

 

[war_wheelan]

I DON'T KNOW WHY IT DIDN'T WORK ORIGINALLY, BUT IT IS WORKING NOW WITH
THE FOLLOWING MODIFICAITONS

FILENAME 't.cmd'
call tasky.cmd
exit

FILENAME 'tasky.cmd'
taskkill /f /im indii.exe /t

Thanks for the responses.

 

[war_wheelan]

Pegasus,

You were correct my previous post worked via the command prompt, but
not with Explorer or Scheduled Tasks. Originally, I created a
'taskkill.cmd' file and as you know there exists a 'taskkill.exe'. My
'taskkill.cmd' file (taskkill /f /im indii.exe /t) would go into and
infinite loop until I added the .EXE extension to the command.

Regards,
war

 

[Pegasus \(MVP\)]

Pegasus,

You were correct my previous post worked via the command prompt, but
not with Explorer or Scheduled Tasks. Originally, I created a
'taskkill.cmd' file and as you know there exists a 'taskkill.exe'. My
'taskkill.cmd' file (taskkill /f /im indii.exe /t) would go into and
infinite loop until I added the .EXE extension to the command.

Regards,
war

It's a bad, bad, bad idea to give a batch file the same name
as a regular Windows command, as you just found out for
yourself. Why not use "taskkill1.bat", for example?