[comp.sys.amiga] Amiga to Mac?

diradin@phoenix.Princeton.EDU (Dean I Radin) (04/04/89)

I use an Amiga 500 to collect data in psychological experiments
and a Mac 512e (& Mac IIx) to analyze the results.  The Amiga
provides flexibility for attaching custom-made peripherals,
and the Mac has a wide selection of powerful stat programs.

So far I've written summary stat programs on the Amiga, then
manually transfer these stats to the Mac for further analysis.
I'd much rather transfer the raw data to the Mac directly.

Can someone tell me a way to transfer ASCII files from
an Amiga 500 to a Mac?  Is there a PD or commercial program
that will do this, or can it be done in some simple way I haven't
thought of?

Thanks,

    Dean Radin
    Contel Technology Center
    diradin@ctc.contel.com

usenet@cps3xx.UUCP (Usenet file owner) (04/05/89)

In article <7568@phoenix.Princeton.EDU> diradin@phoenix.Princeton.EDU (Dean I Radin) writes:
>Can someone tell me a way to transfer ASCII files from
>an Amiga 500 to a Mac?  Is there a PD or commercial program
>that will do this, or can it be done in some simple way I haven't
>thought of?

The most general way is to connect them through their serial ports,
assuming the Mac has one - I don't know.
To do this, get a Null modem adapter at Radio Shack. Plug it into
one of the computers, and find a cable to run to the second. Then
use kermit (available in the public domain for each machine) to
get them talking.

If you don't have kermit then you can write BASIC programs to
stuff bytes in the serial port at one end, and pull them off at the
other.

I don't guarantee that this will work. I have done it before
(Amiga <--> MessyDos clone) and it worked like a charm.
** MAKE ** sure you do not interconnect power sources and the like.
Depending on how picky each computer is, you may only need
to connect 3 wires between them. More likely, you'll need 7.
I do not remember which wires though.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In Real Life: Joe Porkka
porkka@frith.egr.msu
jap@syssun.cl.msu.edu  (35.8.1.1)

farrier@Apple.COM (Cary Farrier) (04/05/89)

In article <2368@cps3xx.UUCP> porkka@frith.UUCP (Joseph A Porkka) writes:
>In article <7568@phoenix.Princeton.EDU> diradin@phoenix.Princeton.EDU (Dean I Radin) writes:
>>Can someone tell me a way to transfer ASCII files from
>>an Amiga 500 to a Mac?  Is there a PD or commercial program
>>that will do this, or can it be done in some simple way I haven't
>>thought of?
>
>The most general way is to connect them through their serial ports,
>assuming the Mac has one - I don't know.

	The Mac does have a serial port, although it is not RS232.

>To do this, get a Null modem adapter at Radio Shack. Plug it into

	You don't need a null modem when connecting to the Macintosh.
	What you do need is a RS232->Apple Serial cable, connect the
	RS232 cable from the Amiga to the cable to the Mac.

>one of the computers, and find a cable to run to the second. Then
>use kermit (available in the public domain for each machine) to
>get them talking.
	
	You don't need any specific protocall, a text dump should
	work fine.  Configure both serial ports to the same baud
	rate (Use preferences on the Amiga, use a terminal program
	on the Mac), and set your Mac terminal program to recieve
	a text dump, and from the Amiga CLI enter "type myfile > ser:".

-- 
+----------------------------------------------------------------+
| This message does in no way reflect the views or opinions of   |
| any organization.  In fact, they illustrate just how           |
| disorganized things really are.                                |
+----------------------------------------------------------------+

mp1u+@andrew.cmu.edu (Michael Portuesi) (04/06/89)

farrier@Apple.COM (Cary Farrier) writes:

>         You don't need any specific protocall, a text dump should
>         work fine.  Configure both serial ports to the same baud
>         rate (Use preferences on the Amiga, use a terminal program
>         on the Mac), and set your Mac terminal program to recieve
>         a text dump, and from the Amiga CLI enter "type myfile > ser:".
> 

I believe that you must perform line-feed to carriage-return
conversion when going from the Amiga to the Macintosh.  The Amiga uses
LF as a line terminator, while the Mac uses CR.  Kermit will
automatically perform this translation.  If you use a straight text
dump, you will have to write a small program on one of the machines to
perform the translation.

--
Michael Portuesi * Information Technology Center * Carnegie Mellon University
INET: mp1u+@andrew.cmu.edu * BITNET: mp1u+@andrew
UUCP: ...harvard!andrew.cmu.edu!mp1u+

"Some say that knowledge is something that you never have" -- K. Bush

jwl@Feanor.Stanford.EDU (John Lockhart) (04/06/89)

In article <2368@cps3xx.UUCP> porkka@frith.UUCP (Joseph A Porkka) writes:
>In article <7568@phoenix.Princeton.EDU> diradin@phoenix.Princeton.EDU (Dean I Radin) writes:
>>Can someone tell me a way to transfer ASCII files from
>>an Amiga 500 to a Mac?  Is there a PD or commercial program
>>that will do this, or can it be done in some simple way I haven't
>>thought of?
        ------- Warning, Commercialism Follows --------
                (but hey, it *is* informative)
I'll admit, you can't do this right now, because it's still vaporware, BUT:
In V4#3 of Amazing Computing, there's an ad for a forthcoming product to
read/write Mac disks on an Amiga.  It will be put out by Central Coast
Software, the people who make Dos-2-Dos.  I called CCS up last month,
and found that they're aiming for June release.  The product will require
the purchase of a Mac-compatible disk drive, but they will have software
available so that you can use this drive as a regular Amiga drive.  A
guesstimated price (list) for the whole shebang (including Mac disk drive) 
was around $350.  That's about all I know; for more info, contact:
        Central Coast Software
        424 Vista Avenue, Golden, CO  80401, USA
        Phone (303) 526-1030

Hope this helps.
___________________________________________________________________________
                       -- John W. Lockhart
          jwl@feanor.stanford.edu    BIX: jlockhart

farrier@Apple.COM (Cary Farrier) (04/06/89)

In article <8YCefHy00Vsf4=7K5l@andrew.cmu.edu> mp1u+@andrew.cmu.edu (Michael Portuesi) writes:
>I believe that you must perform line-feed to carriage-return
>conversion when going from the Amiga to the Macintosh.  The Amiga uses
>LF as a line terminator, while the Mac uses CR.  Kermit will
>automatically perform this translation.  If you use a straight text
>dump, you will have to write a small program on one of the machines to
>perform the translation.

	I am using Mac Terminal 2.3, and it has an option called
	Line Feed which does this for you.  Sorry, I forgot to mention
	it.

-- 
+----------------------------------------------------------------+
| This message does in no way reflect the views or opinions of   |
| any organization.  In fact, they illustrate just how           |
| disorganized things really are.                                |
+----------------------------------------------------------------+

witting@topaz.rutgers.edu (Paul K Willing) (04/07/89)

In article <1210@internal.Apple.COM> farrier@Apple.COM (Cary Farrier) writes:

> In article <8YCefHy00Vsf4=7K5l@andrew.cmu.edu> mp1u+@andrew.cmu.edu (Michael Portuesi) writes:
> >I believe that you must perform line-feed to carriage-return
> >conversion when going from the Amiga to the Macintosh.  The Amiga uses
> >LF as a line terminator, while the Mac uses CR.  Kermit will
> >automatically perform this translation.  If you use a straight text
> >dump, you will have to write a small program on one of the machines to
> >perform the translation.

In a similar vien, would it be possible to connect one of apples new
FDHD (or whatever the call them) drives up as a second drive?  My
guess is yes, as long as a eject button were grafted upon that silly
paperclip eject button.  These drives are capable of reading both
Macintosh 800k, or IBM 1.44 Meg.  If it can read 1.44 Meg, it should
handle IBM 720k, which from the sound of the discussion, are semi
compatible with Amiga drives.  Sounds Keen to me.

Am I missing something?

paul
-- 
----------------------------------------------------------------
Graphiti on the wall of civil rights organization in the sixties
 
	"There is a town in Mississippi named Liberty
         There is a Department in Washington called Justice"

A more socially aware sort of .sig     witting@topaz.rutgers.edu

peter@sugar.hackercorp.com (Peter da Silva) (04/09/89)

In article <8YCefHy00Vsf4=7K5l@andrew.cmu.edu>, mp1u+@andrew.cmu.edu (Michael Portuesi) writes:
> The Amiga uses LF as a line terminator, while the Mac uses CR.

I wish people wouldn't do that. ASCII defines two alternatives for the
'new-line' sequence: either CR-LF or (if a single character is to be used)
just plain LF. The whole point to splitting LF and CR was to allow using
CR for overstriking, which doesn't work if you do a linefeed when you see
a CR.
-- 
Peter "Have you hugged your wolf today" da Silva      `-_-'
...texbell!sugar!peter, or peter@sugar.hackercorp.com  'U`

a553@mindlink.UUCP (Paul Rochon) (04/09/89)

I have been working on the same problem. The easiest way to do it is to set up
a null modem cable and send the files to the other computer using a modem
program. Or if you cannot do this you can use diga ( a telecomunication
program) which allows you to set you computer on remote. Then phone your system
from the mac and download the files to your system. Although to do this you
need two modems. The best way to prepare the files to be sent is to ARC then.
This is a utility that compresses the files and also allows you to take a
number of files and put then together into one directory that can be sent as
one file.
Coastal software - the same company that makes disk to disk is marketing a new
program called MAC to disk. This program will convert mac and amiga graphics
and asci files. It is not available yet but should be soon. But for the money
the MAC emulator called AMAX by readysoft is your best bet. It will allow your
amiga to emulate a mac. It sounds great and is really the best solution.

martens@shawnee.cis.ohio-state.edu (Jeff Martens) (04/09/89)

In article <3696@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>In article <8YCefHy00Vsf4=7K5l@andrew.cmu.edu>, mp1u+@andrew.cmu.edu (Michael Portuesi) writes:
:: The Amiga uses LF as a line terminator, while the Mac uses CR.
:
:I wish people wouldn't do that. ASCII defines two alternatives for the
:'new-line' sequence: either CR-LF or (if a single character is to be used)
:just plain LF. The whole point to splitting LF and CR was to allow using
:CR for overstriking, which doesn't work if you do a linefeed when you see
:a CR.

Actually, I'd rather see people use CR than linefeed, for a couple reasons:

1) Until Unix came along, just about everybody used CR for
end-of-line.  Unix was the renegade, and now a lot of newer systems
are copying the Unix "standard."

2) Terminals use CR rather than LF to end the line, so somewhere along
the way, to get a program to think a LF has been typed rather than a
CR, CR has to be mapped to LF.  Just think, AmigaDOS could be about 3
words shorter and run imperceptibly faster.
-=-
-- Jeff (martens@cis.ohio-state.edu)

..and on Wall St., the Tao is down in heavy trading...

ugkamins@sunybcs.uucp (John Kaminski) (04/11/89)

In article <1182@internal.Apple.COM> farrier@Apple.COM (Cary Farrier) writes:
[ buncha stuff about interconnecting a Mac & an Amiga chopped for brevity ]
>
>>one of the computers, and find a cable to run to the second. Then
>>use kermit (available in the public domain for each machine) to
>>get them talking.
>	
>	You don't need any specific protocall, a text dump should
                                    ^^^^^^^^^
                                    protocol?
>	work fine.  Configure both serial ports to the same baud

             Text dumps are OK, but they aren't error checking.

>	rate (Use preferences on the Amiga, use a terminal program
>	on the Mac), and set your Mac terminal program to recieve

          Why not just use a terminal emulator on the Amiga too?

>	a text dump, and from the Amiga CLI enter "type myfile > ser:".

          Careful!!!  AmigaDOS CLI and shell aren't quite like Bourne
          or csh or *sh -- they require all redirection to be specified
          immediately after the command name, i.e., type >ser: myfile.
          Besides, what is wrong with good ole copy myfile ser: ????

peter@sugar.hackercorp.com (Peter da Silva) (04/11/89)

In article <42377@tut.cis.ohio-state.edu>, martens@shawnee.cis.ohio-state.edu (Jeff Martens) writes:
> In article <3696@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
> ASCII defines two alternatives for the
> :'new-line' sequence: either CR-LF or (if a single character is to be used)
> :just plain LF.

> Actually, I'd rather see people use CR than linefeed, for a couple reasons:

> 1) Until Unix came along, just about everybody used CR for
> end-of-line.

Until UNIX came along people used 80-column card images, variable-length
records, Fortran carriage-controls, CR-LF, and LF. The only systems I know
of that just use a plain CR as a line-terminator are OS/9 and MacOS. One
of which is modelled on UNIX!

Some MS-DOS programs ignore the linefeeds and do not generate them, but an
MS-DOS text file is supposed to have a CRLF at the end of EVERY line.

> 2) Terminals use CR rather than LF to end the line, so somewhere along
> the way, to get a program to think a LF has been typed rather than a
> CR, CR has to be mapped to LF.

And sequences using DEL and/or BS have to be handled, and so on. The
amount of work you need to implement line-editing makes converting CR
to LF, to CRLF, to spaces to pad the line to 80-column card images,
and to a field-width for variable-length records, etc... trivial.
-- 
Peter "Have you hugged your wolf today" da Silva      `-_-'
...texbell!sugar!peter, or peter@sugar.hackercorp.com  'U`

UH2@PSUVM.BITNET (Lee Sailer) (04/11/89)

In article <5151@cs.Buffalo.EDU>, ugkamins@sunybcs.uucp (John Kaminski) says:
>
>In article <1182@internal.Apple.COM> farrier@Apple.COM (Cary Farrier) writes:
>[ buncha stuff about interconnecting a Mac & an Amiga chopped for brevity ]
>          immediately after the command name, i.e., type >ser: myfile.
>          Besides, what is wrong with good ole copy myfile ser: ????

copy will try to transmit the files Comment, if it has one.  Type won't.

ugkamins@sunybcs.uucp (John Kaminski) (04/12/89)

In article <89101.09:58:42.436125UH2@PSUVM> UH2@PSUVM.BITNET (Lee Sailer) writes:
>copy will try to transmit the files Comment, if it has one.  Type won't.

Since when?  I mean this quite literally.  I just tried cp myfile * and it
did not copy the comment.  Note that my cp is just Copy renamed (mv'ed? :^)
Since 1.3?  I tried this with a 1.2 disk and cp.  Besides, aren't directories,
filenames, and file comments concepts applicable only to block-structured,
(usually) random access devices?

lphillips@lpami.wimsey.bc.ca (Larry Phillips) (04/20/89)

In <5151@cs.Buffalo.EDU>, ugkamins@sunybcs.uucp (John Kaminski) writes:
>      Careful!!!  AmigaDOS CLI and shell aren't quite like Bourne
>      or csh or *sh -- they require all redirection to be specified
>      immediately after the command name, i.e., type >ser: myfile.
>      Besides, what is wrong with good ole copy myfile ser: ????

The problem with 'copy myfile ser:' is that SER: is buffered. 'copy myfile
AUX:' would be a better choice.

-larry

--
Frisbeetarianism: The belief that when you die, your soul goes up on
                  the roof and gets stuck.
+----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                |
| \X/    lphillips@lpami.wimsey.bc.ca or uunet!van-bc!lpami!lphillips  |
|        COMPUSERVE: 76703,4322                                        |
+----------------------------------------------------------------------+