Given the volume of people who misunderstood my reply, I must have phrased my response rather badly.<P>blindmouse:<P>Read what I said carefully. I didn't say that IE did the same as Windows on the Mac. I meant that file download behavior was browser-implementation specific and that it wasn't an indication of a magical property of the Macintosh hardware or OS that made it better for downloading files from a network.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>Looks like microsoft's Mac SW team has some tips for the Win team...<HR></BLOCKQUOTE><P>Precisely my point.<P>John Campbell:<P>When I said "Same for Netscape, whatever its system is.", the word 'system' refers to 'file download mechanism', not to OS. Sorry for the confusion.<P>resteves:<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>I suppose it is possible that this behavior *could* be implemented on Windows, but that begs the question of why it is not done this way. All of the programs I know of on the Mac will work this way. I wonder if it has anything to do with how the OS operates, making it more difficult to do this on a Windows machine. (I find it hard to believe that it would not be done if it was easy.)<HR></BLOCKQUOTE><P>C'mon, resteves, neither behavior is anything more than trivial to implement. This was a design decision. From my programmer's eye, what happened in the Windows port of IE was that some management guy said "hey, why don't we use the IE file cache to store partially downloaded files and then copy them to their intended destination when they're done?", and then passed the code work off to some intern. I suspect the original motivation was to allow features like transparent resumes if a download from an HTTP 1.1 server is interrupted.<P> <BLOCKQUOTE><font size="-1">quote:</font><HR>All I can base it on is my personal experience and what is said on this thread. The original poster said that he could *not* just move the file without having the extra space available to write to before it deletes the original, even if it is just 'moving' within the same drive. So if what you say is correct, how come he could not do it. (I am not saying you are wrong, but then what was stopping him?)<HR></BLOCKQUOTE><P>I believe the original poster's problem was that IE was doing this:<P>CopyFile (temp, final);<BR>DeleteFile (temp);<P>instead of this:<P>MoveFile (temp, final);<P>That's why I said the codework was done by an intern. You could use a debugger to find out for sure, but that's what it looks like IE is doing. Stupid? Yes.<P>On Windows filesystems, as on just about any others, you can move a 100MB file anywhere you want on the same partition with 3 MB of free disk space. Try it if you don't believe me. (Numbers used for illustration purposes only. No files were corrupted in the writing of this post).