jpeg download problem from ClubWeb
Paul McGee
for viewing hence the large size) that I uploaded, when viewed here or
at several North American sites, requires at least three tries before it
will download/display successfully, on either ADSL or lowly dialup.
Typical behaviour is that maybe 2% will load, then "FILE CONTAINS NO
DATA" error warning. Refresh (in any manner), same thing at about 40%.
Refresh again and it will either complete or "NO DATA" at about 90%.
Now the real puzzler. Acquaintances in England and Australia were asked
to test the file. It loaded quickly and flawlessly half a world away!
Also as I needed to transfer this (and another file) to a history
archives in Montreal I finally uploaded both files zipped to the same
directory. There is no problem at all downloading that much larger zip
file (contains two items).
Acquaintances in N. America have tried the JPEG with different browsers
and I have tried it with both Firefox (my usual browser) and IE. The
only one handling it without "NO DATA" error was Opera, and that could
have been chance.
Any ideas? I don't ordinarily publish the web address as my Clubweb site
is strictly used for sending large files to either customers or
suppliers in an FTP context (uploaded from here, as required, by the
usual FTP method; those for whom the files is destined simply access it
the normal browser way after being advised by me. There is, quite
deliberately, nothing but the file directory there. Files are removed as
soon as the user confirms receipt.) Should tech support need details
give me call.
Michael Schouten
The type of error you're recieving is caused because a web browser will
start displaying an image before it finishes downloading. I have often seen
this type of error when displaying image files in the PNG format, but not so
often with JPGs. In either case, it would be caused by a lost packet or
some misplaced image information. Because the browser window is
decompressing and displaying as it goes, if it runs into such an error, it
has difficulty proceeding. And of course the larger the file, the more
chances for these errors to crop up.
Ironically, a refresh tends to pick up where an image display left off,
taking the 20% or whatever that had already been completed and downloading
the rest from there. This is why it gets progressively farther every time
you refresh.
In order to avoid this problem, what you can do, rather than displaying the
image by simply clicking on a link to it, is right click on the link to the
picture and select "Save Target As" from the menu instead. This will give
you the option to save the file directly to your hard drive as a standard
FTP transfer rather than displaying it. This is also why the ZIP file works
fine... it's also a straight data transfer to download it.
Now why one browser or one location may appear more stable is another
question. Could simply be chance, or perhaps browser settings or features.
I don't know which ones have protection against this kind of display fault.
Hopefully this answers your questions. If you have any more, we'll be happy
to answer to the best of our abilities.
Have a great day!
"Paul McGee" <oneone...@interbaun.com> wrote in message
news:1189jj5...@corp.supernews.com...
Paul McGee
I just made the same photo into a "Progressive JPEG" and so far it has
not shown the problem. The non-progressive one still has that problem.
Not sure if that is a fluke or not (could be that a download very
shortly after an upload of the same could have something cached at your
end still so could d/l very quickly if that is the case.)