sometimes things get transfered fine, othertimes not. Whats going on?
If a file on the A/UX system has Type “TEXT”, then when it is copied over to a MacOS disk, all ‘newline’ characters will be replaced by ‘carriage returns’. Sometimes this is what you want (that is when the file is, in fact, a TEXT file). Othertimes it’s not. Say for example you download a GIF file onto your A/UX disk. A/UX might think it’s a TEXT file. If you then copy it over to your MacOS disk and try to use Giffer on it, it won’t work. That’s because the newlines were changed, which is not what you want. The way to stop this is to convince A/UX that the file is of non-TEXT type. There are many applications out there (including the A/UX included ‘setfile’ program) that lets you modify this. Do this before you copy the file over to your Mac OS disk and all will be Okay. If you aren’t sure what the Type and Creator should be, you can just specify “BIN ” and “A/UX” (note space in BIN) and the file won’t be massaged during the copy/transfer. You’ll still need to eventually change them to
