Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!PENNDRLS.UPENN.EDU!GTHEALL
From: GTHEALL@PENNDRLS.UPENN.EDU (George A. Theall)
Newsgroups: comp.sys.dec.micro
Subject: RE: FIDONET ON COMPUSERV    Conf: (74) fRAINBOW
Message-ID: <8910112025.AA10689@remote.dccs.upenn.edu>
Date: 11 Oct 89 21:24:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25

Comments: Rainbow Echomail from BILL MAYHEW    Read: YES

There _is_ a "market" for a Rainbow TAPCIS
but I don't know how big it is.  Certainly it's in the dozens; I have my
doubts as to whether it's in the multiple hundreds, though.
Unfortunately the author of TAPCIS has been unwilling to release the
source code to date.  The more TAPCIS users express to *him* their desire
to see it on other platforms, the sooner this might change...
The Rainbow is not the only "problem machine", of course.  There are
dozens of other machines out there in a similar fix.
Some Rainbow users use LCTERM with scripts.  I believe there are some
sample scripts in one of the DECPC libraries.  Nowhere near as "slick"
as TAPCIS, but...
I know nothing about FOSSIL and I think it has been mentioned possibly
_once_ in the past two years on DECPC.  One of the interesting things is
to observe the difference in subject matter between DECPC and here; here,
there are a lot of messages related to Binkley, FOSSIL, and getting/keeping
OPUS/Fido running, while on DECPC there are virtually none of those, and
a lot more "how do I make printer X work with software Y on my Rainbow",
"how do I make DEC printer X work with my IBM PC",
Code Blue, DOS, and applications discussions.

--- ConfMail V4.00
* Origin: Still Servicing the Rainbow - Maybee Forever (1:101/1)
--- Via PCBGate v2.0a5