Your best friend for file transfer.

Fetch application logoFetch

file type suffix (4 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 11 years ago by tenu
  • Latest reply 11 years ago from Jim Matthews
  • tenu Member

    I have used the earlier version of fetch and always just transfer over entire folders of files as raw data. then transfer them back to my mac later without any issue.
    This time, I transfered over as binary and raw data, and when it comes back, it defaults my photoshop files, ending in nothing or .ps, as Post Script files. It is set to raw data! So why is it doing anything to them? they of course cannot be opened now.
    Two other things. If I transfer individually, I can change the file type and specify photoshop 8bim and this of course makes them work fine. I have also changed the Suffix preference to make .ps be photoshop, but on my brand new transfers, it still does the same thing and makes them post script -- uploading and downloading.
    What should I do? Any help would be greatly appreciated.

    Posted 11 years ago #

  • Jim Matthews Administrator

    When a .ps file shows up with a Postscript icon that means that its type and creator codes were set that way. The contents of the file are unchanged -- the only thing affected is the icon, and what program will be run when you double-click the icon. You should still be able to open these files by using the Open command in Photoshop's File menu.

    I don't have an explanation for why new transfers would not respect the change you made to the suffix mapping. What did you enter in the Type and Creator fields of the .ps suffix mapping?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 11 years ago #

  • tenu Member

    Well I apparently just needed to restart the program in order to make the suffix changes take affect. However, before I did that, I did try opening the .ps files in photoshop and they were not parsable. As soon as I brought them back over, with the suffix changes in affect, they were openable. This still poses a problem as I had transfered over to my backup server a few other files of which I had no suffixes. When I download them to my mac, I still cannot open these even in the programs I know they came from, but I also dont know what to do for creator types.

    I dont mind using macbinIII from now on, I'm just confused as to why raw data appears to work differently now, and I'm also confused as to why I indeed cannot open my files with the programs in which they were created, if only the icons are wrong. I changed the type and creator in resedit, and I was able to open them. I have the same problem even with Simple Text files, btw.

    But really, since I have things working, I guess it doesnt matter. I just thought I would mention that it does seem to affect opening the files. Thank you very much for replying so quickly and being concerned. I really do love Fetch.

    Posted 11 years ago #

  • Jim Matthews Administrator

    Thanks for the follow-up. Apparently those programs care about the type and creator codes, and not just the contents of the files. So it's good that you found a workaround.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 11 years ago #

Topic closed

This topic has been closed.