eric@aplvax.UUCP (11/10/83)
I am trying to adapt uucp to work over the Sytek local network. I can get it to establish the circuit, and log in, but it fails in the transfer. My assumption is that this is because the uucp protocol wants a full eight bit transfer, and Sytek does not provide a full eight bit transparent data path. My question is, has anyone modified uucp to work over the Sytek net (or developed a protocol for it that does not require 8 bits?). Right now I am looking at breaking up every six bytes into 8 (I not only can't use the top bit, I also have to avoid XON/XOFF). If someone has a better way, I would like to hear about it. Thanks for any help that you can give me. -- eric ...!seismo!umcp-cs!aplvax!eric
eric@aplvax.UUCP (11/20/83)
I have gotten a number of responses to my original posting, and I would like to thank them all. Many were of the form - "Sytek does support 8 bit transfer, just turn off parity, etc.". The one thing I forgot to mention in the original article was that the Sytek units are connected to DEC DMF-32 boards, where the majority of the ports do not support EIA control lines. Therefore, the network must use XON/XOFF, and so eight bit transparency is not possible. The good news is that I have developed a new protocol for uucp that does not require all eight bits. It is essentially the same as the usual protocol, except that it breaks up the data into smaller pieces than eight bits in a byte. Throughput goes down, but the network and uucp tend to guarentee delivery, so higher than normal baud rates can be used effectively. Thanks again for all the replys. -- eric ...!seismo!umcp-cs!aplvax!eric
fred@hfhrv.UUCP (11/21/83)
I have used Sytek in the past to transfer 8 bit data to several apples from an pdp11 very successfully. Do You have the Sytek boxes set up to transfer in transparent mode? That is you should have command, parity, eom, and eia all set to none. Fred Thelander 313-876-7335
CCVAX.ron%nosc@sri-unix.UUCP (11/24/83)
From: Ron Broersma <CCVAX.ron@nosc> We use uucp over a Sytek local net at NOSC. The only thing that is gross about it is the L.sys entry. For flow control we use EIA at the host end, not XON/XOFF. That's the only way to go and it is easy with Emulex CS11s (DH lookalike). It is also possible with the Able DH but a little messier. The COMMAND sequence on your Tbox or Tmux should be set to BREAK or NONE. PARITY should also be set to NONE. Modifying the uucp protocol was not an option to us because a lot of the uucp hosts we talk to are micros with binary only licenses. There was one exception, I had to patch the binary on a Callan system because of a portability bug in the checksum routine. --Ron Ron@Nosc, ucbvax!sdcsvax!noscvax!ron, (619) 225-2148