R
Robbie Hatley
I've been having a problem recently on no less than two different
computers, both running Windows 2000 Professional: when downloading
files from the Internet, the download often stops at 50KB, with
Windows thinking that the download is complete, even if the actual
file size was 1.38MB or 11.85MB or whatever. Once this happens
once, it can take anywhere from 10 to 100 further attempts to get
the download to actually complete.
I did find a partial work-around, by accident: if I empty
the temporary Internet files, the next attempt to download
the file usually succeeds. It's as if Windows sees a 50KB
file named "Fred.zip" in it's cache, says "ah-ha, the user is
attempting to download "Fred.zip", and I've already cached
that file, so I'll just give the user the cached version!"
Windows doesn't bother to check that the cached version is
COMPLETE.
So, what would cause Windows to think that a 50KB partial
download of an 11MB file is "complete"? (Seems like a bug.)
And why does it keep offering-up the same 50KB piece of trash
as being an 11MB file? (Seems like a second bug.)
Are there any workarounds for these bugs, other than emptying
the cache and trying again? That is, is there some way to
keep downloads from cutting off at the 50KB mark (it's always
almost exactly 50KB) in the first place?
And why 50KB? If downloads are going to fail, why not at
11.7KB or 1.53MB or whatever?
computers, both running Windows 2000 Professional: when downloading
files from the Internet, the download often stops at 50KB, with
Windows thinking that the download is complete, even if the actual
file size was 1.38MB or 11.85MB or whatever. Once this happens
once, it can take anywhere from 10 to 100 further attempts to get
the download to actually complete.
I did find a partial work-around, by accident: if I empty
the temporary Internet files, the next attempt to download
the file usually succeeds. It's as if Windows sees a 50KB
file named "Fred.zip" in it's cache, says "ah-ha, the user is
attempting to download "Fred.zip", and I've already cached
that file, so I'll just give the user the cached version!"
Windows doesn't bother to check that the cached version is
COMPLETE.
So, what would cause Windows to think that a 50KB partial
download of an 11MB file is "complete"? (Seems like a bug.)
And why does it keep offering-up the same 50KB piece of trash
as being an 11MB file? (Seems like a second bug.)
Are there any workarounds for these bugs, other than emptying
the cache and trying again? That is, is there some way to
keep downloads from cutting off at the 50KB mark (it's always
almost exactly 50KB) in the first place?
And why 50KB? If downloads are going to fail, why not at
11.7KB or 1.53MB or whatever?