Please someone test 5.2 or 5.3 with a large config.

[sadicq]

You can try it ... but as far as I remember there was a splash screen which lasted a little more than with the cmdow.

Edited August 9, 2006 by sadicq

[Pliek]

I think that's why I did it my way, the dos screen is mutch shorter.

I can change it back with cmd /c so wpi does the command.

Do that after my problem is solved.

That wil also be after my vacation.............

Edited August 9, 2006 by Pliek

[sadicq]

Ok, I made a little exe you have to put on your cd or in your windows.

It accepts only one command-line parameter and that is a process name that should kill.

The AutoIT code

#include "process.au3"
If $cmdline[0] = 1 Then
	_RunDOS('taskkill /im "' & $cmdline[1] & '" /f')
EndIf

Not that complicated, right?

Usage

TaskKillS program.exe

I'll upload only the compiled version.

Link

Edit: I forgot to say it displays no splash screen at all.

Edited August 9, 2006 by sadicq

[Pliek]

Ok, I made a little exe you have to put on your cd or in your windows.

It accepts only one command-line parameter and that is a process name that should kill.

The AutoIT code

#include "process.au3"
If $cmdline[0] = 1 Then
	_RunDOS('taskkill /im "' & $cmdline[1] & '" /f')
EndIf

Not that complicated, right?

Usage

TaskKillS program.exe

I'll upload only the compiled version.

Link

Edit: I forgot to say it displays no splash screen at all.

Thanks sadicq, hope I can test it today...otherwise it wil be when I rerurn at about 2 weeks.

Have to clean my mind now....

LOL

[Pliek]

What is bohtering me is why I got the delay in 5.2 and 5.3 and not in my smooth runnig 5.1.

If someone can give a answer to that.......

Bye.

[Kelsenellenelvian]

Ok, I made a little exe you have to put on your cd or in your windows.

It accepts only one command-line parameter and that is a process name that should kill.

The AutoIT code

#include "process.au3"
If $cmdline[0] = 1 Then
	_RunDOS('taskkill /im "' & $cmdline[1] & '" /f')
EndIf

Not that complicated, right?

Usage

TaskKillS program.exe

I'll upload only the compiled version.

Link

Edit: I forgot to say it displays no splash screen at all.

Hey do you mind if I add this to the tools archive?

[sadicq]

Of course you can add it. It took me 2 minutes to make it.

[Kelsenellenelvian]

Dont mind if I change the icon do you? Also where does it need to be located for use? In the system32 dir or the install folder or what?

Edited August 10, 2006 by Kelsenellenelvian

[sadicq]

You can use whatever icon you want.

It can be put in the system32, but you can call it from anywhere as long as you include the full path.

[Djé]

Ok, I made a little exe you have to put on your cd or in your windows.

It accepts only one command-line parameter and that is a process name that should kill.

The AutoIT code

#include "process.au3"
If $cmdline[0] = 1 Then
	_RunDOS('taskkill /im "' & $cmdline[1] & '" /f')
EndIf

Not that complicated, right?

Usage

TaskKillS program.exe

I'll upload only the compiled version.

Link

Edit: I forgot to say it displays no splash screen at all.

Hey do you mind if I add this to the tools archive?

Kel & sadicq, please note that taskkill is only for XP Pro.

XP home has a tskill instead.

I'd reckon to use AutoIt's ad hoc function which will work in any case (see the AutoIt help file for the 'ProcessClose' function):

If $cmdline[0] Then ProcessClose($cmdline[1])

Compile it with the same name and use it the same way.

[sadicq]

I know that function. It oftenly fails to close some processes which are not responding or are using much cpu power. So, long story short, processclose is not an option.

I'll look into this later, and I'll consider rewriting that in vb .net as I'm trying to learn it right now.

Or I'll attach the original takkill to the exe and extract it when needed.

Anyway, I wrote that just to show you how easy it is to hide it ... so it's not vital for the non-XP users.

[Djé]

Yes, autoIt used to have problems with delays on heavy loads sometimes.

What about a loop forcing it?

If $cmdline[0] Then
	While ProcessExists($cmdline[1])
		ProcessClose($cmdline[1])
	WEnd
EndIf

Anyway, I was just mentioning this as Kel is looking for 'universal' solutions: we don't want bug reports saying TaskKillS is not working on some machine .

If you prefer to stick to the attached exe and fear an issue with the licence, maybe Process.exe (25Kb, freeware) from Beyonlogic is a good choice...