TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Rod Speed
from: John Tserkezis
date: 1996-12-08 14:03:08
subject: rsend

-=> Quoting Rod Speed to John Tserkezis <=-

Hello Rod,

 JT> I wouldn't be the least bit suprised if it is buggy firmware
 JT> not being able to deal with many retrains and re-sends.

 RS> Yeah, almost certain, it shouldnt actually be retraining at all.
 RS> Just negotiating the session params properly in the first place
 RS> and say falling back a bit speed wise if the session deteriorates.
 
 It seems very much that my modem gets "over zealos" and tries to
connect at
a too higher speed in the first place.  The down-shift bit works (some of the
time), I just wish it would connect at the lower speed in the first place, as
it often drops carrier before it has had a chance to shift to the slower
speed.

 JT> I know my modems MNP implementation (EC and compression) is not
 JT> really compatible with many modems.  I've disabled everything to do
 JT> with MNP now, and my connections have become a LOT more predictable.

 RS> Certainly useful evidence.

 Another area that I would have liked to have a longer play with, is we had
a customer bring in an ACER PC, with its own internal supplied modem, (dunno
which brand but I *can* tell you they are shit).
 Anyway, I tested it calling my system.  Using any comms program on their
modem, after the connect, all I get is a bunch of repeating characters.
"-?-?-?-?-?-?-?" if I remember correctly.  On my end at home, it has no
connect message, just a NO CARRIER after it answers.
 I tried changing a few options in the limited time that I had it in, but
didn't come up with anything.
 Mind you, it had no trouble connecting to other BBS's
 
 RS> Well, a better modem at your end may well have more success calling
 RS> that particular modem/line if everyone else does better. Corse you
 RS> would want to try that and see rather than just buy and pray.
 
 JT> Pity no one offers a try-before-you-buy deal.  No bloody wonder.

 RS> I think the Modem SuperStor still does. As usual, cant put
 RS> my hand on a recent ad of theirs when I want one, but they
 RS> certainly used to have that in round device in the ad itself.

 I've found their number, I'll give them a call and see what they can work out.
Thanks.

PS  I've just come back and tested a new modem, a tossup between the hayes,
USR and the Netcom.  I have the USR first, so far, one failed call
to 3:632/348, and an aborted call (half way through the file) to 3:712/311.
 311 doesn't bother me as much, as I used to get 3-8 failed calls a month
(out of 30) anyway.  I think he *may* have changed his modem in that time
though.
 I have to call again and do some more testing with 632/348, it seems very
intermittant, probably just line noise.

John Tserkezis, Sydney, Oz. Fidonet: 3:712/610  Internet: jt{at}suburbia.com.au

... We are upping our standards... so up yours.
---
* Origin: Technician Syndrome (3:712/610)
SEEN-BY: 711/934 712/610
@PATH: 712/610 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.