bill@bilver.UUCP (Bill Vermillion) (09/01/90)
I have been running a Trailblazer Plus for about 2 years.
Everything has been going smoothly.
About 6 weeks ago I noticed that system would hang on an outgoing
newsfeed. It happened sporadically and I assumed it was a problem
on the feed end.
I just switched to a new system, new hardware '386 vs 68000, new
software ESIX V.3.2 Rev D vs Xenix III, and the problem is still
here.
On outgoing feeds with protocol g enabled in the modem, the system
will just stop somewhere between 150 to 200k. When tried with
smaller files, eg ~50K, it would stop in the 4th file - that's how
I determined it was in the 150k to 200k range.
Turning the protocol in the modem off and letting the machines
handshake will get everything through - but slowly.
I can receive with NO problem. Incoming of 2 to 3 megs are
flawless. I also had a hang with an outbound xmodem transfer, but
it only happened once - so it may not be part of the problem.
I did a hardware reset via the hole in the back of the modem, and
put the parameters back the way they are supposed to be.
Prior to 6 weeks ago the modem performed flawlessly and NO CHANGES
were made to the stored setting on the old system when this
occured.
I am waiting for a return call from Telebit next week, but in the
meantime has anyone else experience this. Do you have any hints.
The modem is running at locked interface of 19200bps with CTS flow
control. The old system was running at 9600 with no flow control.
The problems were the same.
Help!
bill
--
Bill Vermillion - UUCP: uunet!tarpit!bilver!bill
: bill@bilver.UUCPhowardl@wb3ffv.ampr.org ( WB3FFV) (09/06/90)
From article <944@bilver.UUCP>, by bill@bilver.UUCP (Bill Vermillion): > I have been running a Trailblazer Plus for about 2 years. > Everything has been going smoothly. > > On outgoing feeds with protocol g enabled in the modem, the system > will just stop somewhere between 150 to 200k. When tried with > smaller files, eg ~50K, it would stop in the 4th file - that's how > I determined it was in the 150k to 200k range. > > -- > Bill Vermillion - UUCP: uunet!tarpit!bilver!bill > : bill@bilver.UUCP Hello Bill, I just wanted to say that I too have seen this problem. I have PEP connections to about 12 different machines on a regular basis, and feed news to about 8 of them. One site that I talk to shows the exact symptoms you describe above, but all of the others have no trouble at all. This happens if I call them, and even if they call me. I eventaully get everything through, but it takes many repeated calls. If you or anybody else on the net come up with any possible soultions to this problem please let me know.... ------------------------------------------------------------------------------- Internet : howardl@wb3ffv.ampr.org | Howard D. Leadmon UUCP : wb3ffv!howardl | Advanced Business Solutions TELEX : 152252474 | 210 E. Lombard St - Suite 410 Telephone : (301)-576-8635 | Baltimore, MD 21202
olaf@ntc.UUCP (Olaf Kaestner) (09/08/90)
In article <944@bilver.UUCP>, bill@bilver.UUCP (Bill Vermillion) writes: > I have been running a Trailblazer Plus for about 2 years. > Everything has been going smoothly. > > About 6 weeks ago I noticed that system would hang on an outgoing > newsfeed. It happened sporadically and I assumed it was a problem > on the feed end. > > Help! > Bill, we had similar problems until we changed the value of internal register S58 to 2. We had it at 3 before and we would get random lockup and data loss on the line. I hope that S58=2 solves your problem, too. Let me know! Olaf
howardl@wb3ffv.ampr.org ( WB3FFV) (09/11/90)
From article <316@ntc.UUCP>, by olaf@ntc.UUCP (Olaf Kaestner): > In article <944@bilver.UUCP>, bill@bilver.UUCP (Bill Vermillion) writes: >> I have been running a Trailblazer Plus for about 2 years. >> Everything has been going smoothly. >> >> About 6 weeks ago I noticed that system would hang on an outgoing >> newsfeed. It happened sporadically and I assumed it was a problem >> on the feed end. > > we had similar problems until we changed the value of internal > register S58 to 2. We had it at 3 before and we would get > random lockup and data loss on the line. > > I hope that S58=2 solves your problem, too. Let me know! > Olaf Hello Olaf, I also use the Telebit Trailblazer, and have experienced the same problem that Bill has seen (but only with one of the eleven sites that I talk with) and I have the S58 register set to 2. I DO use hardware flowcontrol, and it works great, and I agree that having S58=3 is asking for trouble. I don't know if this is Bill's problem, but it sure isn't the solution on my side. If anybody has any other good ideas I would love to hear them... ------------------------------------------------------------------------------- Internet : howardl@wb3ffv.ampr.org | Howard D. Leadmon UUCP : wb3ffv!howardl | Advanced Business Solutions TELEX : 152252474 | 210 E. Lombard St - Suite 410 Telephone : (301)-576-8635 | Baltimore, MD 21202