Thread View: net.bugs
3 messages
3 total messages
Started by zben
Sun, 25 Mar 1984 03:48
Re: Terminal output: parity, 7 vs. 8 bits, etc.
Author: zben
Date: Sun, 25 Mar 1984 03:48
Date: Sun, 25 Mar 1984 03:48
14 lines
1258 bytes
1258 bytes
The terminal I am typing this on (a Volker Craig VC4404) has the bogosity to change bad-parity characters into question marks. Even in cursor addressing sequences. BSD 4.1 is nice enough to generate the parity for me, although I suppose I could do the STTY -EVENP if what you are suggesting comes to pass... Now, you ask, "But why do you have parity set on your terminal at all?". Our local IBM guru has a stick up his *** about having parity checking, and if the switch isn't on I can't talk to his funny IBM Series 1, running Yale code, that makes this terminal look like a 3270. Needless to say raw mode programs lose big this way... Ben Cranston ...seismo!umcp-cs!zben zben@umd2.ARPA
Re: Terminal output: parity, 7 vs. 8 bits, etc.
Author: Dave Martindale
Date: Sun, 25 Mar 1984 20:15
Date: Sun, 25 Mar 1984 20:15
3 lines
708 bytes
708 bytes
This only serves to point out that terminals as well as computers really should have independent control over whether they generate and whether they check parity.
Re: Terminal output: parity, 7 vs. 8 bits, etc.
Author: Ron Natalie <ron>
Date: Mon, 26 Mar 1984 12:41
Date: Mon, 26 Mar 1984 12:41
4 lines
633 bytes
633 bytes
Who needs these extra bits. Parity is for farmers.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads