Re: Apple II Email (Network Connections)

[Jack Friess <jfriess@wctc.net>]

[This is being posted to csa2 and csa2.programmer]

Regarding Dave Althoff's ideas/thoughts about Apple II E-mail and the network 
connections (mainly using a Linux server talking through a network, cabled with 
RS-232-style wiring, and then a comm program at each station, Derek Taubert wrote:

[snip]

> Ding!  Ding!  Ding!  This is the most viable solution to the problem that
> I've heard yet.

[snip...snip...a lot of snipping...!!]

And:

> I agree 100% with the above evaluation of the situation.  It would be so much
> easier to write a mail client to use simple ASCII transfers over a serial
> line and a corresponding server on the Unix end than to try to coax an Apple
> ][ to speak TCP/IP.

Thanks, Derek.  You're right.  This has been, in fact, one of our options for a while 
now.  But we (maybe only I) wanted to explore at bit more the option of using 
LocalTalk (because of the greater flexibility and availability of resources to the 
A2--by booting off a Mac for file & program serving, use of HD for storage, and ease 
of print sharing).  Please remember (everyone), this is a school 
(kids--7-10-year-olds) or organizational network setting (20  A2's on the network, 
with Mac's and PC's), not just individual stand-alone A2's sending email.

Now, at this point, we are pretty pessimistic about the LocalTalk being a viable 
solution: 1) we can't get the COPS PC-L/T card working under WinNT (our preferred 
server); 2) The Apple PC-L/T card (which we have but have not tested) is not 
available any more and is not supported (correct me if I'm wrong on this); 3) BIG 
PROBLEM: the A2WSC is no longer available in the quantities schools/organizations 
would need, and remanufacture at a reasonable cost (under $100) is probably not 
feasible; 4) (what you alluded to) there is no TCP for the A2 and would be a gigantic 
programming problem, even if one could use the MacTCP for transfers to the POP 
server.  Any one of these are enough to knock this option out of serious 
consideration.

So where are we?  I just summarized to our group what I think the best option is (see 
if any of this sounds familiar to you?):


**Assumptions/Working Criteria (are there more?)**

Internet e-mail capabilities/access for the A2 from the classroom by kids.

Total hardware/software cost per workstation $100 or less; total hardware/software 
LAN cost $5,000 or less.

Network environment in which A2 workstations may be paired, but mostly are 50-100 
feet apart and 50-100 feet from the server.

The maximum services possible are needed from the network and server (e.g. email, 
printer sharing, file sharing, program sharing, etc.).  Limitations or voids must be 
known and listed.

There is _not_ a requirement for high speed data transfers (e.g. graphics, sound, 
etc.), but good/better performance is desirable.

Any permanent, or semipermanent, hardware installations (especially wire) should be 
able to accommodate growth (e.g. number of workstations) and advancements (e.g. 
phase-out of A2 text-based workstations and installation of www workstations).

There is no expectation, at this time, for a graphical interface--all data is 
text-based.

There is no expectation, at this time, to establish A2-based TCP.

The workstations will be: Apple IIgs, II, II+, IIe, IIe enhanced, IIc.  (Any not able 
to run the hardware, or withstand the riggers/demands of the network, can be 
eliminated, except the IIe enhanced.)   Limitations or incompatible computers must be 
known and listed.


**The Option**

We know  we can send email from a A2 running ProTerm, etc., through a modem to a 
Unix/Linux box to Pine, etc. and then the Internet.  This works.   We're pretty 
confident (although _we_ haven't done it) that we can do the same thing on a 
network--set up an A2 with a SSC, port it to a Linux box with RS-422 (or whatever) 
with terminal emulator null modem, and evoke Pine.

**Hardware**

Therefore, what we need to find out (or decide) before we go any further is:

*Exactly* what hardware (cards, connectors, adapters, wire) do we need to do this for 
the A2?

*Exactly* what kind of network hardware (routers, patch panels, connectors, etc.) 
will we need to connect the A2 (actually, up to 20 A2's) to the Linux box?

*Exactly* what hardware (cpu, RAM, HD, disk drives, cards, boards, connectors, 
adaptors, etc.) and software and versions of software (os, servers, bridges, drivers, 
etc.) will we need on the Linux box?


**Software**

Assuming we're going to run Slackware 96, with the appropriate drivers and POP mail 
sever software, we are going to eventually need (for this to work with kids, that is) 
some kid-friendly software.  Here's what we're thinking:

*terminal emulation*:  ProTerm is great, but too complex with too many options (file 
transfer, etc.) for kids (actually probably teachers, is more accurate) to learn 
quickly and operate without much support.  We're going to need a kid's version of 
ProTerm which can be loaded and run at an A2 off a 5.25 disk.  There are many 
questions about programming this (it will NOT be a Saturday afternoon AppleSoft 
programming project).  Until we agree on a new name, I'll refer to it as "KidTerm".

First question:  Does KidTerm already exist?

*E-mail client*:  Pine is great (depending on who you talk to), but too complex and 
too "adult" to be appealing to kids.   We're going to need a kid's version of Pine 
which can be accessed from the A2 using KidTerm.  There are many questions about 
programming this (it will NOT be a Saturday afternoon AppleSoft programming project).  
Until we agree on a new name, I'll refer to it as "Willow".

First question:  Does Willow already exist?


As we get further into this option (testing all the connections, capabilities, etc.) 
we will move into the programming phase, if indeed, we can't find KidTerm and Willow.  
I look forward to everyone's *constructive* input, no matter how small.


Jack Friess
Stevens Point, Wisconsin, USA


PS.  And Derek, if you're up to the programming challenge, we'd love to have you 
involved at that level, if you want to/have time/etc.  We're all operating the 
condition that all efforts are contributed and all products become public domain 
(freeware).