Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!umn-d-ub!nic.MR.NET!shamash!nis!com50!bungia!orbit!pnet51!shawn
From: shawn@pnet51.cts.com (Shawn Stanley)
Newsgroups: comp.sys.apple
Subject: Re: Various observations
Message-ID: <165@orbit.UUCP>
Date: 11 Oct 88 20:45:45 GMT
Sender: root@orbit.UUCP
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 27

c60c-3aw@web-3d.berkeley.edu (Andy McFadden) writes:
>1) While I'm among the first to praise ProTERM, it does have some rather
>   odd bugs.  For instance, I connected my //gs to a Toshiba 1200 (IBM
>   compatible) and tried to talk at 19200 baud.  All we got was garbage.  After
>   dropping it to 2400 baud, everything worked fine.
>
>   Acting on past experience (explained next), I switched to Z-Link.  Had no
>   problems with talking, and an Xmodem transfer worked just fine.

It's possible that ProTERM doesn't use interrupts.  Or it doesn't buffer the
data at high speeds.  Whichever; check out your control panel options and
maybe enable buffering yourself.

>4) My modem (a Zipper 2400, actually a Prometheus ProModem 2400G) doesn't
>   return numerical codes after hanging up, so ProTERM never realizes that
>   the phone was hung up.  Note that it DOES recognize a busy signal, so it
>   probably isn't related to the init string.  Anybody have similar probs?

Are you sure you aren't having problems with maybe carrier handshaking?
Or is it when YOU hang up?  In that case, if your DTR isn't enabled when
you receive the status code, chances are you will lose it.  Then again,
maybe it's not either of these...
>c60c-3aw@widow.berkeley.edu (Andy McFadden)


UUCP: {rosevax, crash}!orbit!pnet51!shawn
INET: shawn@pnet51.cts.com