Your best friend for file transfer.

Fetch application logoFetch

Problem retrieving a large file (600MB) (4 posts)

  • Started 7 years ago by Sensei
  • Latest reply 7 years ago from Scott McGuire
  • Sensei Member

    The download almost completed; The nearly-complete file on my desktop was not playable. I am particularly curious about significance of *ftp_retrieve: -30000 (state == RGET_RETRIEVING)* and *500 Command not understood*
    Here is the transcript; any help greatly appreciated.

    Fetch 5.0.5 (5A835) PowerPC running on Mac OS X 10.4.6 (8I127) PowerPC English
    StuffIt Engine 0x812, StuffIt SDK Version 10.0.1
    Partial serial FETCH5X010-####-####
    Connecting to 72.##.##.## port 21 (OS X firewall is on) (4/26/06 6:01:54 AM)
    Connected to 72.##.##.## port 21 (4/26/06 6:01:54 AM)
    220-Welcome To Rumpus!
    220 Service ready for new user
    USER Tester
    331 Password required
    PASS
    230 User logged in
    SYST
    215 MACOS Peter's Server
    PWD
    257 "/" is current directory.
    MACB ENABLE
    200 MacBinary enabled
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A (ASCII)
    PASV
    227 Entering Passive Mode (72,##,##,##,11,192)
    LIST
    150 Opening connection
    -rw-r--r-- 0 5884199 5884199 Apr 24 14:14 05 myFile1.mp3
    -rw-r--r-- 0 12984474 12984474 Apr 24 16:13 myFile2.aif
    -rw-rw-rw- 0 472549805 472549805 Apr 25 08:55 myFile3
    -rw-rw-rw- 0 632088133 632088133 Apr 25 10:03 myFile4
    226 Transfer complete
    TYPE I
    200 Type set to I (Image) [MACBINARY ENABLED]
    SIZE myFile4
    213 632088448 bytes
    MDTM myFile4
    213 20060425170310
    PASV
    227 Entering Passive Mode (72,##,##,##,11,192)
    RETR myFile4
    150 Opening connection (632088448 bytes)
    Update check skipped at 04/26/2006 06:03 AM (next check after 04/26/2006 12:11 PM)
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    PWD
    500 Command not understood
    Unsuccessful transfer of myFile4 (632,086,432 bytes, 371,160 bytes/sec, 28:23 elapsed) stopped at 4/26/06 6:30:34 AM
    ftp_retrieve: -30000 (state == RGET_RETRIEVING)
    PWD
    257 "/" is current directory.
    TYPE A
    200 Type set to A (ASCII)
    PASV
    227 Entering Passive Mode (72,##,##,##,11,192)
    LIST
    150 Opening connection

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Could you check the following?

    * Open the Fetch Preferences
    * Click the Obscure tab
    * Make sure "Contact servers during long transfers" is unchecked.

    If it was checked, uncheck it, and please let us know if it was checked or not. (We believe that setting may not be compatible with the type of server you're downloading from.)

    And if you still have the partially downloaded file, you can finish downloading it without re-downloading the part that you've downloaded already by using Fetch's Resume Download command.

    You can read more information about Resume download in the Resuming an interrupted download help topic in Fetch Help (or just click on the link).

    Let us know if this helps, or if you have further questions.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

  • Sensei Member

    Hello--
    "Contact servers during long transfers" was checked. I have unchecked it, and will try downloading again the next time a large file is on the server.
    Any plans to make that setting compatible with the Rumpus server?

    Posted 7 years ago #

  • Scott McGuire Administrator

    Hi,

    Yes, fixing the conflict is on our list.

    However, you probably do not need the setting. It's meant to fix a problem with certain NATs or routers where the download will appear to stall at the very end of the download. If you are not experiencing that problem, you do not need the "Contact servers during long transfers" setting checked.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 7 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.