Newsgroups: comp.sys.amiga.emulations Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!sarah!newserve!bingsuns.cc.binghamton.edu!consp03 From: consp03@bingsuns.cc.binghamton.edu (Kriston J. Rehberg) Subject: Re: AmigaDos->Amax II disk copying help Message-ID: <1991Jun11.175236.9799@newserve.cc.binghamton.edu> Sender: usenet@newserve.cc.binghamton.edu (Mr News) Nntp-Posting-Host: bingsunm.pod.binghamton.edu Reply-To: consp03@bingsuns.cc.binghamton.edu (Kriston J. Rehberg) Organization: SUNY Binghamton References: <8283@oasys.dt.navy.mil> Date: Tue, 11 Jun 1991 17:52:36 GMT In article , andrewsr@u2.rutgers.edu (Rich Andrews) writes: |>I have gotten the best results by converting the Mac stuff to ascii |>(use BinHqx). Then transfer the files using TEXT option. This has |>worked well for me. You can even use Stuffit (with or without compression). Since Stuffit archives only occupy the data fork, you can get away with this: Mac -> IBM -> Amiga -> AMAX This way you don't get the file becoming outrageously large which can happen with 'BinHex'. Works perfectly for me. |>If you have access to an account, upload the driver and download it |>from A-MaxII. ^^^^^^^^^^^^^^^^^^ If you're using a mainframe accound, you're stuck with uploading an outrageously large binhex file and then downloading it again to AMAX. I did this for a while but when AMAXII came out with the transfer software, I use the mac>ibm>Amiga>AMAX method and it works every time. |>-Rich Kris +-------------------------------------------------------+ | Kriston J. Rehberg, SUNY-Binghamton Computer Services | | consp03@bingsuns.cc.binghamton.edu | | #include | +----------- Only Amiga makes it possible! ------- ;-b -+