melott wrote:
Hmmm... :-)
Its really quite easy. You have 2 choices, ParNet,
using the parallel port, or as you suggested serial
port.
I would probably go with serial.
This seems like a good overview of the options -- actually a few more than I was aware of, with the PC2Amiga hack and so forth.
Serial is a good thing to understand, because just about any machine can be wired up by good ol' RS-232. However, in this particular Amiga-to-Amiga case, I gather ParNet has one heck of a speed advantage -- at least 20K/s (I assume those are bytes), while you'll peak at about 14K off your average PC UART, and apparently a good bit less (4-5K?) on a stock Amiga. This might matter 'a lot' if you're talking about trucking CDs worth of stuff back and forth.
From there... if it were me, yes, I'd be drawn to the idea of using a PLIP link, while accepting how much of a pain in the *** that's bound to be.
In theory, this would let you do everything over IP, "the way it's meant to be,"* and give you the option of routing the older machine onto the Internet itself, through the 1200 with a proper "cheap" network card, etc. In practice, this requires you to have enough experience with IP in general for that idea to even sound attractive, what with trying to chase down appropriate stacks and so on.
If you do go for a serial link, the "NCP" option sounds like an interesting (and presumably not-expensive-or-rare) way to make it more convenient than juggling terminal programs at both ends. Nothing fancy about it, as a Psion owner I can say it's just a simple protocol for file and printer sharing across a serial link, nothing to do with IP or anything complicated... but it looks like the Amiga implementation lets you access things as devices, which would make it much more like having a "network" than two machines hung together by shoelaces and twine.
Good luck! [...and let me second that, yes, the cable you're looking for should have
25-pin ends, if there was any doubt.]
*Of course, now everyone will sneeze at the way IP has overhead and so forth... because not everyone thinks that one-protocol-everywhere is the way it was really meant to be. But that's kind of the point of it, it lets you unify everything on one stupid protocol (and "internet") instead of many different ones.