dhb@masscomp.UUCP (Don Barstow) (10/29/84)
-----------------------
I have a friend running Xenix on a TRS-80 MOdel 16
who is trying to establish a uucp link to the uucp
network so we can send mail to each other. The
company that has agreed to be his link is running 4.2
on a VAX.
After lots of work, we have it to the point where his
machine will call and establish a link to the other machine,
but then uucico just dies. I had him run uucico with "-x9"
to see the debugging info. It got through establishing that
his end was master, the protocol used was the "g" protocol,
and got to where his uucico was going to send a mail message
file to the other end. The last several lines of output were
work type S file number 5
wmsg S D.xxxxx D.xxxxx
send 210
remsg
Almost immediately after this, he got his shell prompt back.
(the xxxxx stands for the company name of his link)
Some added info - his STST file said TALKING, both LCK files
were still in his spool directory, and his LOGFILE said
"call to ... succeeded". Also, the LOGFILE at the other
end said "caught signal 1".
He also made sure that his modem would not disconnect if the
Model 16 dropped DTR, or if he received "space" from the
remote modem. In fact, his modem continued to hang onto
the phone line after both uucico's had quit.
I am baffled. Any idea as to what could be going on here?
I have been looking at our sources, but I am sure we run a
different version, and I don't even know what version Radio
Shack supports on the Model 16. Any help would be appreciated.
Please mail responses back to me.
Don Barstow ...{ihnp4, allegra}!masscomp!dhb
Masscomp, Inc. (617) 692-6200, ext. 444
One Technology Park
Westford, Mass. 01886geoff@desint.UUCP (Geoff Kuenning) (11/08/84)
In article <119@masscomp.UUCP> Don Barstow writes about a problem getting a
Xenix (aka System III?) UUCP to talk to a 4.2 system, and describes the
symptoms in detail.
Interestingly enough, I have recently reported *exactly* the same problem
to UniSoft regarding their System V uucp. It talks fine to 4.1 and anything
else except 4.2. So this must be some sort of incompatibility between the
4.2 and System V uucp's.
Anyone have a solution? I'd sure like UniSoft to find out about it, since I
have a 4.2 site that rather desperately needs to connect to me.
--
Geoff Kuenning
First Systems Corporation
...!ihnp4!trwrb!desint!geoffbsa@ncoast.UUCP (Brandon Allbery) (11/10/84)
> Article <196@desint.UUCP>, from geoff@desint.UUCP (Geoff Kuenning) +---------------- | In article <119@masscomp.UUCP> Don Barstow writes about a problem getting a | Xenix (aka System III?) UUCP to talk to a 4.2 system, and describes the | symptoms in detail. Model 16 Xenix is V7; no USG ioctl calls, they're closer to Berkeley ioctls. --bsa -- Brandon Allbery @ North Coast Xenix | the.world!ucbvax!decvax!cwruecmp! 6504 Chestnut Road, Independence, Ohio | {atvax!}ncoast!{tdi1!}bsa (216) 524-1416 \ 44131 | E1439@CSUOHIO.BITNET (friend's acct.) ---------------------------------------+--------------------------------------- `Confusion is my natural state.'
bobw@ncoast.UUCP (w2551080h2867511) (11/13/84)
() We have great luck running uucp from this Model 16 /Xenix (and my own company's similar system) with anything we've tried; including two vaxen daily through which we get uucp mail in one case, and net.news from the other. Feel free to query us via return mail if we can help. -- Robert L. Weinberg ...decvax!cwruecmp!ncoast!bobw Tridelta Indusries, Inc. ...decvax!cwruecmp!ncoast!tdi1!bobw V.P. Technology