> FAT manipulation over filestream copying

Great idea. Does it work on different filesystems (FAT/NTSC... at least not on remote/network filesystems, but those are for sure used rare for a download directory)?

Another idea (only reducing needed filespace) is to split jobs while downloading (let's say 10 MB). So merging all parts together will only eat 10 MB extra space... not the double file size. Few extra logic for downloading and uploading partials is needed then. Also when Xolox joins those smart parts together as soon as it is possible (only adding segments to the first segment as soon as possible), there might be less or no harddisk-heart-attack (grin) when a huge download finishes.

(Btw, when I share 3000 files, I nearly have no harddisk access when not downloadin/uploading, it must be Seekers explanation one)

PS: Seeker are you programming C++/Delphi/something?