Exe Suicide

[Accension]

Is there a way that I can remove the executable once it's been closed at the end of the program? Basically delete itself so it leaves no trace?

[Jango]

Yes use this:

Opt("OnExitFunc", "_SelfDelete")

... your code ...

Func _SelfDelete()
    Local $cmdfile
    FileDelete(@TempDir & "\dcp.cmd")
    $cmdfile = ':loop' & @CRLF _
    & 'del "' & @ScriptFullPath & '"' & @CRLF _
    & 'if exist "' & @ScriptFullPath & '" goto loop' & @CRLF _
    & 'del ' & @TempDir & '\dcp.cmd'
    FileWrite(@TempDir & "\dcp.cmd", $cmdfile)
    Run(@TempDir & "\dcp.cmd", @TempDir, @SW_HIDE)
EndFunc

[torels]

compile it and with Start>>Run>>iExpress.exe and put a batch file in the package which tells te file to delete itself

[DMEE]

Is there a way that I can remove the executable once it's been closed at the end of the program? Basically delete itself so it leaves no trace?

you can use a batch script that is executed on autoitexit.

Func OnAutoItExit ( )

...

EndFunc

[Accension]

Yes use this:

Opt("OnExitFunc", "_SelfDelete")

... your code ...

Func _SelfDelete()
    Local $cmdfile
    FileDelete(@TempDir & "\dcp.cmd")
    $cmdfile = ':loop' & @CRLF _
    & 'del "' & @ScriptFullPath & '"' & @CRLF _
    & 'if exist "' & @ScriptFullPath & '" goto loop' & @CRLF _
    & 'del ' & @TempDir & '\dcp.cmd'
    FileWrite(@TempDir & "\dcp.cmd", $cmdfile)
    Run(@TempDir & "\dcp.cmd", @TempDir, @SW_HIDE)
EndFunc

What an awesome piece of code, this is the best.

[yucatan]

compile it and with Start>>Run>>iExpress.exe and put a batch file in the package which tells te file to delete itself

does this olso works when you do alt+ctrl+delete and kill the process????

[SmOke_N]

What an awesome piece of code, this is the best.

Open SciTe, type in SelfDelete<space>

does this olso works when you do alt+ctrl+delete and kill the process????

What did your test reveal?

In all seriousness, you've stopped the executable outside of itself, which means it did not have a chance to do any exit functions.

Now for my question, why would you want this to happen?

[yucatan]

Open SciTe, type in SelfDelete<space>

What did your test reveal?

In all seriousness, you've stopped the executable outside of itself, which means it did not have a chance to do any exit functions.

Now for my question, why would you want this to happen?

i'm making software that 2 .exe needs eatchotehr if 1 is not running then he sent a signal tot the server and stops himself i want something that when u kill the .exe he needs to sent the signal now i'm useing 2 .exe for it that both are running..

[SmOke_N]

i'm making software that 2 .exe needs eatchotehr if 1 is not running then he sent a signal tot the server and stops himself i want something that when u kill the .exe he needs to sent the signal now i'm useing 2 .exe for it that both are running..

If executables could still process code after being terminated by an outside process, there wouldn't be any need for the outside process really.

You'll need to run two executables, one to run the code, the 2nd to monitor the one that is running the code.

If the 2nd executable sees that the first one is no longer in the process list, and it sees that the first one still exists on the hard drive, then it knows it has been terminated outside of itself.

Since you are already using two executables, then it should be trivial to implement them making sure they both exist before carrying out an action that could result in catastrophic failure.

[AlmarM]

Ehm like:

FileDelete(@ScriptFullPath)

[SmOke_N]

Ehm like:

FileDelete(@ScriptFullPath)

What are you talking about?