Does it do what it says on the tin?
I'd imagine that I'm not the only person on the .net to hate this, and thus say this, but due to the fact that I'm coming down with a cold/flu type thing and am feeling grumpy I thought I'd have a rant.
Why do people not use sensible names and conventions for files within archives?
For instance I download an archive for the docs for Smarty and Safair automatically expands the archive. Nice, saves me trouble. Except the folder it's extracted to bears no resemblance ot the name of the archive. The archive is "Smarty-2.6.0-docs.tar" and the resulting expanded directory? ... "manual". OK, so it's pretty easy to find it eventually, but it would be even easier to name the file logically and help thge end users [plus the likely hood of me having a directory called "Smarty-2.6.0-docs" that gets overwritten is a lot less likely that one called manual.
Worse yet are downloads which don't have any resemblance at all. I downloaded windows drivers for my epson printer the other day, and the archive expanded into a filename I simply couldn't understand or relate to the archive. We're mostly past 8.3 naming conventions, so can't we just get over it?
Oh, and whilst you are fixing this, please can you learn about mime-types on web servers? We've been doing this interweb thign for over 10 years now, and it ain't that difficult to do properly.