Newsgroups: comp.sys.mac.comm
Path: utzoo!utgpu!cunews!bnrgate!bwdls61!usenet
From: bschmidt@bnr.ca (Ben Schmidt)
Subject: Re: Eudora and SLIP questions
Message-ID: <1991Jun28.013143.18576@bwdls61.bnr.ca>
Sender: usenet@bwdls61.bnr.ca (Use Net)
Nntp-Posting-Host: bwdlm14
Organization: Bell-Northern Research
References: <51337@ut-emx.uucp>
Date: Fri, 28 Jun 1991 01:31:43 GMT

In article <51337@ut-emx.uucp> jmm@ut-emx.uucp (J. Michael Morrison) writes:
>
>Greetings,
>
>Has anyone ever dealt with the situation of Eudora being 
>used in a public access lab environment?  Because Eudora 
>uses the System folder to save its mailboxes, it won't 
>really work.  Is there an ingenious solution that I just 
>can't see, or has anyone ever modified the program to do 
>such a thing?

In the HC Eudora stack I think you'll find the explanation of
how any number of different users can share a single Mac running 
Eudora by dragging their Eudora System folder files out of the
System Folder the first time they run it, and on all subsequent
occassions launching eudora by double-clicking on any of these
files in their *new* location, instead of double-clicking on 
the Eudora application itself.

>
>Also about Eudora, over a serial connection I seem to be 
>able to do everything except actually send mail.  Eudora 
>sends the message(s) completely and then just sits there.  
>After the timeout, Eudora announces that Eudora said, "" 
>and the server replied "".  Anyone ever come across this?

On the u of illinois server there are some detailed notes on
serial Eudora connections identifying all the user-settable (from
ResEdit) parameters for dial-in connections.  Eudora's initial
settings should work with cisco terminal servers since that is
what the U. of illinois uses.  But on any async connection 
all bets are off and you should examine the entrails of a
chicken to verify the auspices are favourable before sitting
down to configure a modern modem with its 60+ registers to reliably
connect to anything....  :^)

>
>Finally, SLIP.  Because I work for the state, the 
>expensive, commercial solutions are pretty much out.
>

TCP/Connect has the only commercial solution I've seen. There are 
some hacked NCSA telnets but you need a separate program to make
the serial connection to the SLIP server first, and then yah gotta 
quit from that program and bring NCSA up without the serial connection
dropping.  awkward.