Closed
Bug 233741
Opened 21 years ago
Closed 19 years ago
download manager failing to save large files to network devices properly
Categories
(SeaMonkey :: Download & File Handling, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: spalmer, Unassigned)
Details
User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 I needed to download the Solaris install disk, software disk 1 and software 2 from Sun today (argh) in any case, all three compressed files are about 350 MB or greater. I used 'save link target' for each file and pointed each file to be saved on a network file share. Download manager reported that all three had successfully downloaded in about 2 minutes which is impossible through our network. So, I actually had to use IE on the same machine to save them to the network file share successfully. Reproducible: Always Steps to Reproduce: 1. find three large compressed files on a website. 2. using 'save link target as' each file one at a time to save to a network file share 3. open and watch download manager. 4. compare bytes to what really exists on the network file share. Actual Results: download manager reports all bytes for all three files are there when in reality approximately 1% of each file was saved. Expected Results: all three files should have been saved with the correct byte count.
Comment 1•21 years ago
|
||
> 1. find three large compressed files on a website.
Any chance of a URL to files that failed for you?
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 2•19 years ago
|
||
I wonder if the "network device" was relevant to this bug at all, or if it's just a dupe of bug 237623...
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•