iglesias@UCI-ICSA.ARPA (Mike Iglesias) (10/14/85)
We've been having some strange problems with our DZ11 lines on our 780 for the last couple of weeks. Some of the lines refuse to autobaud at any baud rate higher than 300. This problems appears to come and go randomly, and doesn't always affect the same lines. For example this morning there were 6 lines that didn't work; now only 2 of those 6 refuse to autobaud. I've had 2 of the 3 DZs replaced by field service, but that didn't fix it either. Anybody seen this before? Got any suggestions? We're running v4.1 of VMS. Mike Iglesias University of California, Irvine iglesias@uci-icsa.arpa
GOET@HWALHW5.BITNET (10/16/85)
We also had problems with autobauding, although the symptoms were not the same as yours, but probably it may help solf your problems. When somebody typed a return, to get contact with the VAX (so he was in the autobaud-state), somebody else would get a few blanks on his screen. When a user logged off, somebody else would even get about 15 blanks. This only happened between lines in the same DZ11 or in the same octet in case of a DMZ-32, at speeds below 9600, and with the terminal lines set to even parity. Together with a software specialist of DEC, I found out that there were a few bugs in the TTDRIVER (VMS v4.1 and v4.2): 1. In the routine TTY$AUTOBAUD, at label 40$, a RSB should be inserted. This probably only causes that one has to type one <return> too much. 2. Also in TTY$AUTOBAUD at 30$ + "something" and at 50$, the MOVZBL causes the character in R3 (which was the one just typed), to be replaced by either a <return> or a <blank>. However, in R3 are also some error bits and the line-number the character was input from. The MOVZBL clears not only the error-bits but also the line-number, which causes the interference at the other lines. After we changed both MOVZBLs into MOVB, we got rid of the problems. Be careful that these are not (yet) official patches! Kees Goet Agricultural University, Wageningen. The Netherlands. GOET@HWALHW5
info-vax@cca.UUCP (10/16/85)
From: GOET%HWALHW5.BITNET@WISCVM.ARPA We also had problems with autobauding, although the symptoms were not the same as yours, but probably it may help solf your problems. When somebody typed a return, to get contact with the VAX (so he was in the autobaud-state), somebody else would get a few blanks on his screen. When a user logged off, somebody else would even get about 15 blanks. This only happened between lines in the same DZ11 or in the same octet in case of a DMZ-32, at speeds below 9600, and with the terminal lines set to even parity. Together with a software specialist of DEC, I found out that there were a few bugs in the TTDRIVER (VMS v4.1 and v4.2): 1. In the routine TTY$AUTOBAUD, at label 40$, a RSB should be inserted. This probably only causes that one has to type one <return> too much. 2. Also in TTY$AUTOBAUD at 30$ + "something" and at 50$, the MOVZBL causes the character in R3 (which was the one just typed), to be replaced by either a <return> or a <blank>. However, in R3 are also some error bits and the line-number the character was input from. The MOVZBL clears not only the error-bits but also the line-number, which causes the interference at the other lines. After we changed both MOVZBLs into MOVB, we got rid of the problems. Be careful that these are not (yet) official patches! Kees Goet Agricultural University, Wageningen. The Netherlands. GOET@HWALHW5