.PIF files

I think that Microsoft really dropped the ball on this one. It should have text files, similar to a standard Windows config.cfg file. Making it binary file not only served no purpose, but makes it much harder to make .PIFs en masse. Were it a text file, a simple script could make thousands of .PIFs in seconds. Sadly, with the binary file, the user will waste hours by manually setting each one in Windows' GUI.

(Please excuse the redundant acronym in the subject, but if I had not, I fear that you might have misunderstood what I meant by .PIF).

cool story bro

It's a little late to start complaining, don't you think?

Mr. Ballmer hasn't used .PIFs since 1995.

`
>yfw There's grown adults younger than PIF file.

>>5
Actually, PIFs were introduced in 1984 with http://en.wikipedia.org/wiki/TopView

so most adults here (myself included) are younger than this shit. And OP blames Microsoft for something IBM invented. He may as well blame MS for x86 ugliness.

.pif is awesome because not only the extension doesn't show, but you can rename an .exe to .pif and it will work the same.
There's only the stupid icon, I wonder if there's a way to change that?