Your best friend for file transfer.

Fetch application logoFetch

files converting to binary (9 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 9 years ago by Jasonium
  • Latest reply 9 years ago from Jasonium
  • Jasonium Member

    I have a problem with files being converted to binary, which are unopenable by the client. Here is the situation
    I'm using a box running windows 2000 SP4, using bulletproof ftp on it. I also have a G4 on that network. All of my files are backed up to the win2k box. I can connect to the win2k box across my intranet and copy files which open just fine. The problem occurs when a client connects using fetch. They can copy the files just fine, but they are being converted to binary and cannot be opened. The client can, however, change the file type and signature using filebuddy, and the files will open. Is there a way to make the type and setting copy through transfer?

    Aloha - Jasonium

    Posted 9 years ago #

  • Jasonium Member

    I should also add that I am using Linksys WRT54G Wireless G Router. For the win2k box's IP, the ports are wide open from 1 to 60000.

    Posted 9 years ago #

  • Jim Matthews Administrator

    If the files open correctly after having their type/creator changed that suggests that the file contents are fine; they just have the wrong type/creator.

    If a client is downloading files (copying them from the server to her Mac) she can use the Suffix Mapping feature in Fetch to have the correct type/creator information assigned. For this to work the files need to have the correct file name suffixes (e.g. MS Word files should end with ".doc").

    If the client is uploading files to the server (and you are downloading them over your intranet) there's nothing you can do in Fetch to get the right type/creator information assigned. I would use FileBuddy, HappyTyper, or some other utility to fix the type/creator (assuming that the files have the correct file name suffixes). And I would try dragging the files onto the application you want to open them with; many applications can open files with missing type/creator info if the files are dropped on them.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 9 years ago #

  • Jasonium Member

    Jim - thanks for the response. Here is a little more information.
    As a workaround - I have the client log onto my server using OSX (command to retrieve files. When he is done downloading the files, they open fine. It is only when he uses fetch. Because OSX won't allow him to upload from the finder, I have him use fetch, and then I use filebuddy to fix the type/creator. This also happens if I use fetch across the intranet, behind the firewall on local IPs.

    -"If a client is downloading files (copying them from the server to her Mac) she can use the Suffix Mapping feature in Fetch to have the correct type/creator information assigned." - Does this work for uploading as well as downloading?

    -"For this to work the files need to have the correct file name suffixes (e.g. MS Word files should end with ".doc")." The files originate from powercadd, and I have been unable to find any suffixes on them. Only the filetype of Pd%4 and creator being *PwR .

    Thanks for fetch - It has worked great for me for years now - this is the only problem I have ever encountered.

    Aloha - J

    Posted 9 years ago #

  • Jasonium Member

    Upon further inspection - I still cannot find an extension for either the good files which will open in powercadd, or for one of the files converted to binary after being transferred by fetch.

    I did get a file to download with the correct filetype and creator by setting the default binary tpye/creator, in the preferences, to match the powercadd files.

    Posted 9 years ago #

  • Jim Matthews Administrator

    If the file names don't have a suffix that you can map to Pd%4/*PwR then setting that to be the default type/creator is your best bet.

    Unfortunately that only helps for downloading. There's no way for Fetch to tell the NT server what the type/creator should be for an uploaded file, so fixing them with a utility like FileBuddy is probably your best bet.

    Thanks,

    Jim Matthews
    Fetch Softworks

    [This message has been edited by JimMatthews (edited 10-04-2004).]

    Posted 9 years ago #

  • Jasonium Member

    Jim - I have spoken with the programmer of powercadd, and he stated that they don't use suffixes.
    "PowerCADD has never had a document suffix. Even under OS X the file type
    and creator information is used. We do realize that in OS X there is the
    option of using file extensions but have not moved in that direction
    currently."

    So this means I'm screwed?

    Posted 9 years ago #

  • Jim Matthews Administrator

    You could pick your own suffix for these files (e.g. .pcad) and enter a suffix mapping in Fetch to map them to Pd%4/*PwR.

    I think a situation like yours, where Mac files are being stored on a Windows server, is a good example of why applications should support file name extensions (and not just type/creator), because non-Mac servers don't handle type/creator well.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 9 years ago #

  • Jasonium Member

    Jim - thats exactly what I did and it worked. It just means that I have to rename nearly 10,000 files and clients have to remember to add the extension before they upload. But it works - thanks for your help.

    Posted 9 years ago #

Topic closed

This topic has been closed.