Your best friend for file transfer.

Fetch application logoFetch

Return to Message Board

Subscribe to RSS Feed for Fetch Message Board Fetch Message Board

  1. Page 1

Error type -39 (3 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 22 years ago by resedit
  • Latest reply 22 years ago from resedit
  • resedit Member

    The ftp server is on my local network.
    Its BSD-ftpd running on Linux.
    Fetch 4 logs in just fine- but gives me an error when trying to binhex a tar.gz file (yes, I know you don't need to binhex a tar.gz- but it preserves the resource fork if you do and this post is about the error- not strategy).

    Anyway- here's a fetch transcript of the error (with file listing snipped):

    System Version = 0x1003
    Connecting to 192.168.3.50 port 21 (5/17/01 6:07:41 PM)
    220 athlon.c36988-a.ptbrg1.sfba.home.com FTP server (Version 6.5/OpenBSD, linux port 0.3.2) ready.
    ADAT
    500 'ADAT Hi there, do you support security?': command not understood.
    USER michael
    331 Password required for michael.
    PASS
    230 User michael logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/home/michael" is current directory.
    MACB ENABLE
    500 'MACB ENABLE': command not understood.
    PWD
    257 "/home/michael" is current directory.
    PASV
    227 Entering Passive Mode (192,168,3,50,8,117)
    LIST
    150 Opening ASCII mode data connection for '/bin/ls'.
    total 184760
    *snip*
    226 Transfer complete.
    PASV
    227 Entering Passive Mode (192,168,3,50,8,118)
    STOR cs.tar.gz.hqx
    150 Opening ASCII mode data connection for 'cs.tar.gz.hqx'.
    upload: -39 (state == PUT_SENDING)
    ABOR
    426 Transfer aborted. Data connection closed.
    226 Abort successful
    NOOP
    200 NOOP command successful.
    NOOP
    200 NOOP command successful.
    NOOP
    200 NOOP command successful.
    NOOP
    200 NOOP command successful.
    QUIT
    221 Goodbye.

    Under Fetch 3.0.3 it works just fine-

    Connecting to 192.168.3.50 port 21 (5/17/01 5:57:15 PM)
    220 athlon.c36988-a.ptbrg1.sfba.home.com FTP server (Version 6.5/OpenBSD, linux port 0.3.2) ready.
    USER michael
    331 Password required for michael.
    PASS
    230 User michael logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/home/michael" is current directory.
    PWD
    257 "/home/michael" is current directory.
    PORT 192,168,3,61,119,162
    200 PORT command successful.
    LIST
    150 Opening ASCII mode data connection for '/bin/ls'.
    total 184728
    *SNIP*
    PORT 192,168,3,61,149,192
    200 PORT command successful.
    STOR cs.tar.gz.hqx
    150 Opening ASCII mode data connection for 'cs.tar.gz.hqx'.
    Upload complete at 5/17/01 5:57:45 PM
    226 Transfer complete.

    Know why Fetch 4.0 can't properly hqx and upload the file?

    It *does* seem to work with .img files- so I wonder if fetch 4 is detecting the tar.gz and trying to do one thing even though I specified another.

    Any ideas?

    Posted 22 years ago #

  • Jim Matthews Administrator

    I'd like to try to reproduce this. Could you upload the file in MacBinary format to ftp://ftp.fetchsoftworks/incoming ?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 22 years ago #

  • resedit Member

    done

    Posted 22 years ago #

  1. Page 1

Return to Message Board

Topic closed

This topic has been closed.