bill@bilver.UUCP (Bill Vermillion) (08/20/90)
I have running a node for a couple of years on an old Tandy 6000.
I am now running on a '386 so the problem that is still occuring
is not dependant on the machine.
I have been using a Trailblazer plus (the old grey model with 4.0
roms) since June 1988.
Because of some strange problems on the Tandy and not wanting to
invest any more $ in it, I was running with no flow control on it.
About 3 to 4 weeks ago one site that I was feeding was having
problems, in that a uucp transfer would just stop. About 150 to
200k would go through - and the system would just hang. The far
end would disconnect, but the Tandy would stay on line (because I
didn't have all the handshaking on the aux ports that were on the
original serial ports, that stopped working one day!)
So I didn't worry about it as a new machine was being brought up.
Installed everything this past weekend on a '386 25MHz, running
Esix V.3.2 revision D. (this is the exact same version the site
I am sending to is running).
Well, the problem persisted. He used to poll me. Now I can poll
him too, and still the exact same things occur. I tried sending a
large file to my feed site - something I had never done - and it
also quits sometimes after 150 to 200k (maybe a bit more).
I can receive with NO problems. I typically get 500k to 600k hunks
at a time but I can't send. If I split the outgoing news into
50k batches, a couple will get through at times. But after a few
the same thing happens.
Watching the modem lights during the transfer, all seems normal.
SD and RD are running normally - CTS goes on an off now and then.
The SD & RD lights pause now and then, and then all of a sudden
they are both off - and never come back. The modem on the far side
is sending something to me every 10 seconds or so (from
observations made during a phone call to track the problem) but
this side stays locked.
I ran with Uutry and watched and during a session where a few files
got transfered I did get an error message (I can't remember it and
didn't write it down but was on the order of "error 1", and then
later a "2", then a "3". It was increment the number each time.
But it did finish sending each file after an error. When it hung
there were no errors execpt the standard "failed".
Any hints as to where to look, or how to narrow down the problem
would be appreciated.
My gut reaction is that it is a hardware problem in the modem as it
occurs with the same modem on two different machines, and that I
have no problems receiving large files, just transmitting them.
Has anyone seen anything like this before.
bill
--
Bill Vermillion - UUCP: uunet!tarpit!bilver!bill
: bill@bilver.UUCP