Your best friend for file transfer.

Fetch application logoFetch

corrupt images- (8 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 20 years ago by Jack Andrews
  • Latest reply 20 years ago from Jim Matthews
  • Jack Andrews Member

    Using Fetch 4.0.2 and 4.0.3. No problem till a couple of days ago. Started experiencing all corrupt images on anything downloaded from my host server.

    Contacted them. No solution. Had someone try it from their PC. No problem. I am on a Mac G4, 1.25 gig ram, running OS 9.2

    Photoshop delivers an error like 'cannot open this file. Unexpected end-of-file encountered' when attempting to open one of the image that shows to be corrupt in the IE browser.

    Solution: downloaded a trial version of a competitive ftp client product and it worked faster and without the corruption problems.

    I have used Fetch for years and never had a problem. Sometimes intermittently slow downloads on my DSL. Otherwise, dependable.

    What's up?

    Jack

    Posted 20 years ago #

  • Jim Matthews Administrator

    Are these images starting on your Mac, and then you are uploading them to the server, and they show up as broken in IE when you view them from the server?

    Could you send me the URL of one of the broken images, or upload one of the images to the incoming directory of ftp.fetchsoftworks.com (leave the User ID and Password fields blank) and tell me the name of the uploaded image? I'd like to see what is actually being uploaded. You could also upload the file under a different name with the other FTP client for comparison's sake.

    Thanks for reporting this,

    Jim Matthews
    Fetch Softworks

    Posted 20 years ago #

  • Jack Andrews Member

    Jim:
    No. True the images were originally uploaded from the Mac to the server, but that was 2 years ago. Since then we have used only Fetch and with no problems uploading/dwnloading. A few days ago I had to make an edit to the site. As is routine, I downloaded the entire site folder and contents. Not a big deal. Do it all the time.

    When I tried to open the html file, Adobe Golive 6.0 would freeze. After a couple of attempts and re-downloading just what I needed, I opened the html file in my browser and saw the corrupted images. Not one good image. The hypertext was there OK.

    I then downloaded files from another site on the same server. Same problem.

    I emailed the host and their reply was basically, "no clue".

    I will upload to you a zipped file of a problem html and images.

    Jack

    Posted 20 years ago #

  • Jack Andrews Member

    Forgot to mention again that the site looked fine online. Only problem was after downloading. Of course, I did not upload anything new with this issue open.

    Jack

    Posted 20 years ago #

  • Jack Andrews Member

    Jim
    The url to see the page as it should look is www.kitchensandbathsdallas.com/products.htm
    The corrupted version has been uploaded to ftp.fetchsoftworks.com

    Jack

    Posted 20 years ago #

  • Jim Matthews Administrator

    Thanks for clarifying the issue. I don't see the files on ftp.fetchsoftworks.com -- could you email one of the corrupted image files to me (matthews @ fetchsoftworks.com) instead?

    Also, do you know what the Mode pop-up menu was set to when you downloaded the site? The choices are Automatic, Binary and Text.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 20 years ago #

  • Jack Andrews Member

    Text. I sent you the files.
    Jack

    Posted 20 years ago #

  • Jim Matthews Administrator

    Downloading images in Text mode will definitely corrupt them. You should use Automatic mode when you are downloading multiple files, when some are text files (such as HTML files) and some aren't. Fetch will pick which mode to use for each file based on the file name extension.

    Let me know if you see any problem using Automatic mode.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 20 years ago #

Topic closed

This topic has been closed.