The entire file does get written to TMP First. There is a bug open for this.
Thomas Garson wrote: > On Tue, 11 Jun 2002 16:31:35 UTC, Michael Kaply <[EMAIL PROTECTED]> > wrote: > > > It saves to your TMP directory first. > > > > How much space do you have on the drive where your TMP directory is? > > Typically about 350MB free space. > > Does Mozilla write the entire file to TMP before it gets moved to the > location that was selected for save? > If so, I would consider that to be serious conceptual flaw. > > What happens if a large download is interupted? Older browsers would > leave an incomplete file in the download directory that, many times, > could be completed with WGET. I have had Mozilla freeze near the end > of a 500MB transfer, resulting in the aparant loss of all of the data > already downloaded. Not good. > > Thomas Garson > > > Thomas Garson wrote: > > > > > I have installed Mozilla 1.0 on my Warp 4 + SC system. > > > > > > In general, I am very upbeat about Mozilla. > > > > > > However, I tried to download some CD image files via my cable modem > > > connection using it and found that it didn't handle this well with > > > consistancy. Mozilla pops up the window to select the download > > > directory, but with certain files, it freezes either before or just > > > after poping up the actual download progress screen. I then must use > > > "killfeature" to get rid of the now nonresponsive Mozilla. > > > > > > Downloads that cause this behavior can be acomplished without incedent > > > using Netscape 4.61.
