[Info-vax] SET TERM /TTSYNC on ancient VMS versions

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Fri Aug 17 11:46:14 EDT 2018


On 2018-08-16 21:11:58 +0000, hans.huebner at gmail.com said:

> I would argue that software flow control undesirably mixes ...

You can argue that all you want and you're arguably entirely correct, 
but this is the way old systems and particularly OpenVMS works.

You can argue that you should be able to use any control keys and 
you're arguably correct there too, but this is the way that old systems 
and particularly OpenVMS works.

Arguments can be made around RS/EIA/TIA-232 support and versions and 
pinouts and wiring and what might or might not work with flow control 
and otherwise.

Arguments can be made about the lack of compatibility, interoperability 
and commonality of serial wiring back in the 1980s, and some of those 
arguments wouldn't truly plumb the depths of the mess that existed back 
then.

Y'all can try to transplant that newer UARTs and the processors used in 
newer serial controllers are vastly faster and with massively more 
buffering than the old stuff, but that doesn't make the old stuff work 
any faster.

Y'all can make many arguments — correctly, I might add — but you're the 
one that wants to run a long-unsupported fossil-era Lisp on a 
fossil-era OpenVMS (or VAX/VMS) configuration.

And to do "new" things with it.

Which means you're going to get to experiment within the configuration 
and see what works and what does not, and work within what does work 
for whatever goals you might have for that old Lisp environment you've 
established.

This software is from a ~quarter-century ago, and the hardware and the 
wiring and the expectations and the assumptions then were... different.

TL;DR: Try it.  If it displays untoward behaviors, don't do that.



-- 
Pure Personal Opinion | HoffmanLabs LLC 




More information about the Info-vax mailing list