Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!usc!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.dcom.modems
Subject: Re: Problems with TB+ 5.0 roms...
Message-ID: <7167@cbmvax.UUCP>
Date: 29 Jun 89 04:53:05 GMT
References: <5343@stiatl.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 34

In article <5343@stiatl.UUCP> pda@stiatl.UUCP (Paul D. Anderson) writes:
> 
> 1) I subscribed to uunet service.  I have been unable to contact them
> at their 800 number with the TB modems.  They attempt to sync up, but
> then just drop the line after a 20 seconds or so.  I have tried this
> with micropackets on and off (S120).

Are you setting S50=255/254 to force calling in PEP mode?  This may
be neccessary when calling uunet.
 
> 2) When using a 5.0 TB to a 4.0 TB in interactive mode locally, the
> modems sometimes fail to sync up until the 5.0 modem is power cycled.

We just got a bunch of rack-mount TB+ modems that came with 5.0 roms,
but I really haven't had a chance to check for reliability.

I also got a pair of the T2500's to play with V.32.  When calling in
PEP mode from a Hotel phone in S.F. back to PA, I noticed they did
seem to almost always retrain once or twice after a minute or two
of operation.  I don't know whether to attribute this to some kind of
bogus PBX in the hotel or some "improvment".

They may have changed the retrain algorithm - it's always one of those
tradoffs to retrain only when you "need to" or when it might "help"
and the line is idle...  If so I hope there's some way to control this.

BTW, the V.32 worked pretty good when calling Tymenet to access BIX,
but I haven't tried any uucp testing to see whether it's "better" than
TB+/PEP...

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)