From: utzoo!decvax!ucbvax!info-vax Newsgroups: fa.info-vax Title: 600 baud TAC use and VAX/VMS bug Article-I.D.: ucbvax.64 Posted: Tue Mar 22 10:17:46 1983 Received: Wed Mar 23 22:07:04 1983 >From GEOFF5@SRI-CSL Tue Mar 22 10:16:05 1983 Received: by UCBVAX.ARPA (3.331/3.17) id AA01506; 22 Mar 83 10:17:27 PST (Tue) To: devon@MIT-MC Cc: info-vax@SANDIA, protocols@RUTGERS, kfl@MIT-MC, cstacy@MIT-MC, jurgen@MIT-MC, bean@MIT-MC, rem@MIT-MC Remailed-Date: 21 Mar 1983 1941-PST Remailed-From: the tty of Geoffrey S. GoodfellowRemailed-To: Info-VAX@SRI-CSL.ARPA: ; I read in your old mail today that you can change the speed of your connection to a TAC with the @D R command. To set it to 300, you do @D R 373, for 600, @D R 438. Some Bell 103 compatible modems, it was pointed out, are capable of 600 baud. I tried this, on the dialup connection between my vax and the MITRE- TAC. It almost worked. The Vadic 3451 triple modem on my vax can understand 600 baud using the Bell 103 protocol, but the modem at the TAC couldn't understand the 600 baud coming back at it. No problem, says I, I will use SPLIT SPEED and send to the TAC at 300 but recieve at 600! The command @D R 437 should set up the TAC end to do this, and SET TERMINAL /SPEED=(600,300) TTD5: should do the right thing on the vax end. It didn't work. So I tried SET TERMINAL /SPEED=(300,600) TTD5:. Still no luck. A little fooling around with a VT100 proved to my satisfaction that the vax command SET TERMINAL /SPEED=(m,n) is always interpreted as SET TERMINAL /SPEED=n. What a lose! I am doing something stupid? Is this a known VMS bug? (We are running V3.1). Shoudl I call DEC? Tomorrow I will try using SYSTEM SERVICES to try to do the split speed without messing with grody DCL. More news as it happens! ...Keith