waldron.Wbst@XEROX.ARPA (01/10/86)
Does anyone know of a way to patch Mex to allow 8 bit data to be passed to the terminal. I would like to have the remote host send graphics characters to the screen but Mex seems to AND off the 8th bit. Turning on DEBUG shows that valid 8 bit graphics characters are being sent but in normal terminal mode they get stripped. Thanks, Brian Waldron.wbst@Xerox.arpa
jb@terak.UUCP (John Blalock) (01/14/86)
> Does anyone know of a way to patch Mex to allow 8 bit data to be passed > to the terminal. I would like to have the remote host send graphics > characters to the screen but Mex seems to AND off the 8th bit. Turning > on DEBUG shows that valid 8 bit graphics characters are being sent but > in normal terminal mode they get stripped. > > Thanks, > > Brian > Waldron.wbst@Xerox.arpa Note that not all control key sequences get passed thru by MEX either - it's not just an eighth-bit problem. I also would like a patch so that I don't have to exit MEX to run vi remotely. (or any program with escape sequences/cursor addressing) John Blalock, W7AAY uucp: ...{noao,decvax,savax,ihnp4,seismo}!terak!jb phone: (602) 998-4800 us mail: CalComp Display Products Division (formerly Terak Corporation) 14151 N. 76th St., Scottsdale, AZ 85260
Burton.osbunorth@xerox.ARPA (01/17/86)
Mex has a related 8 bit problem. If I am connected to a 7 data bit, even parity host, such as Xerox's own PARCVAX, I cannot use XMODEM transfers unless I manually reset MEX to 8 bits, no parity. I have this problem in the PC version of MEX. I suspect, but don't know for sure, if this limitation is also present in CP/M MEX. This one deserves a patch. (Editorial: That's the trouble with software provided without source code distribution.) On a related matter, please note that my net address and that of other Xeroids has been changed from: Name.registry@Xerox.ARPA to: Name.registry@Xerox.COM Phil Burton Xerox Corp.