Gibberish Warning: I'll be talking computers in this entry, and nothing but.
My dad's system has a virus, keeps replicating itself as .VBS files. Can't find the source of it. So I disabled the Windows Scripting Host and breathed a sigh of relief. No more VBScript. Or so I thought. With WSH gone, windows found another application to route the .VBS files to, or the virus re-enabled it. I'm not too sure which, to be honest, but the end result is the same either way: .VBS files were active again without any notable interruption. This upset me.
So, I made a batchfile. Destroy.bat. It reads as follows:
del %1 %2 %3
echo %1 %2 %3 >> c:\vbslog.htm
Then I made a .PIF telling the batch file to close itself on completion so we don't have stray command prompts lying around. And I changed the file associations on .VBS files so their default application was this batch file.
What does that do? It makes .VBS files self-destruct when activated.
It also makes for an incredibly mean practical joke, if instead associated with .MP3 files, or say... Word Documents.
Just to warn you up front, that joke is never half as funny as you think it is.
...unless you've made an extremely thorough backup.
...which your victim can't get to.
(I just know I'm going to regret publishing that.)