MODEM WOES (was WANTED 9600)

[fishern3485@cobra.uni.edu]

>> Wanted: external 9600 modem in good working order
>> 
>> (looking to upgrade from 2400)

> Check out the Prometheus 14.4 that Mac Warehouse and others are selling 
> for the mac.  I got mine for $102 delivered overnight.  I'm using it now 
> with ProTerm3.1.   I doubt that you will find 9600 baud much cheaper even 
> used....  Note:  Mac WareHouse calls this a LineLink14.4e...I've seen the 
> same modem in other mac catalogs under other names.

Just got it.  LineLink IIe -- haha, very interesting story here!
Bought it from Mac Mall, and in the manual, the USER MANUAL that comes
with the modem itself, the tech assistance number is the phone number
to MAC WAREHOUSE!!  I called for tech assistance and at first they
refused to help me because I got it from Mac Mall.  Bizarre......

I'm using my 144e right now and am having problems!
First off, ProTERM 3.0 seems not to like my 144e, as I have tried all
the modems listed, and only NULL MODEM CABLE can get the phone to
dial out at > 2400 bps. (just sits there, does not pick up...)
I am also losing data.  Text goes flying by (which I **liiiike* :)  )
but when the screen is forced to scroll, I start loosing the first half
(or so) of each line.  Bummer.

Also, the file transfers...  I have a test file that is 7040 bytes long,
and it takes my old 2400 modem 1:48 to transfer. (via kermit)  Here are
the timings for the 144e:
2400: 2:54!!  4800: 1:49  9600: 1:27  19,200: 1:23
There's no excuse for SLOWING DOWN at 2400.  The way I figure it, if my
'ol 2400 could bob up to about 3200, it'd be moving as fast as this 144e
does at 19,200. (file transfers anyway, the text is still MUCH faster)

I shall be calling the manufacturer Monday. (my manual does not even
include a listing of the S-registers, although it does tell me
to SET THEM in other places in the manual!!!)

I expected to reep the greatest benefit in my file xfers, but it seems
that my greatest plus now is that I can surf the newsgroups in half the time.

Owell...

(it's possible that 1/2 my problem is the //c itself, and the other half
 is the terminal program...  comments?)

-- 
Nathan Fisher
  FISHERN3485@COBRA.UNI.EDU