<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>That should do it :-)</div><div><br></div><div>On Fri, 2018-10-26 at 16:39 -0400, DJ-Pfulio via Ale wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>Any chance that someone would change the subject, so lurkers seeking help with</pre><pre>their raspberry pis don't get confused?</pre><pre><br></pre><pre><br></pre><pre>On 10/26/18 11:56 AM, Scott Plante via Ale wrote:</pre><pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"></blockquote></pre><pre>Actually, lack of good flow control was what inspired me to really learn vi</pre><pre>really well. I used to program all the time on a dumb terminal connected to a</pre><pre>Unix box, and if you just held down an arrow key to get midway across the</pre><pre>screen, the whole session would become jumbled and you'd have to refresh. So I</pre><pre>learned all the obscure vi keys to move around the screen and file instead of</pre><pre>arrow/page keys. Once internalized, it made me much more efficient even after I</pre><pre>had a reliable terminal connection or full desktop.</pre><pre><br></pre><pre>Scott</pre><pre><br></pre><pre>--------------------------------------------------------------------------------</pre><pre>*From: *"Jim Kinney" <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>></pre><pre>*To: *"Chris Fowler" <<a href="mailto:cfowler@outpostsentinel.com">cfowler@outpostsentinel.com</a>>, "Atlanta Linux Enthusiasts"</pre><pre><<a href="mailto:ale@ale.org">ale@ale.org</a>>, "Chris Fowler via Ale" <<a href="mailto:ale@ale.org">ale@ale.org</a>>, "Scott Plante"</pre><pre><<a href="mailto:splante@insightsys.com">splante@insightsys.com</a>></pre><pre>*Sent: *Thursday, October 25, 2018 8:12:39 PM</pre><pre>*Subject: *Re: [ale] Connecting to r-pi</pre><pre><br></pre><pre>Alcohol cures all flow control memories. I have no idea what you just said :-)</pre><pre><br></pre><pre>Had to calculate and test timings in early grad school. Signal propogation time</pre><pre>in wire plus time in detection circuits plus time to trigger action on detection</pre><pre>plus actual signal length, etc. Now add in the blasted data collection system</pre><pre>was getting data from multiple sources with different timings, yeah. Fun stuff.</pre><pre><br></pre><pre>On October 25, 2018 6:26:55 PM EDT, Chris Fowler via Ale <<a href="mailto:ale@ale.org">ale@ale.org</a>> wrote:</pre><pre><br></pre><pre><br></pre><pre><br></pre><pre> --------------------------------------------------------------------------------</pre><pre><br></pre><pre> *From: *"Scott Plante via Ale" <<a href="mailto:ale@ale.org">ale@ale.org</a>></pre><pre> *To: *"Alex Carver" <<a href="mailto:agcarver+ale@acarver.net">agcarver+ale@acarver.net</a>>, "Atlanta Linux</pre><pre> Enthusiasts" <<a href="mailto:ale@ale.org">ale@ale.org</a>></pre><pre> *Sent: *Wednesday, October 24, 2018 4:03:34 PM</pre><pre> *Subject: *Re: [ale] Connecting to r-pi</pre><pre><br></pre><pre> If you're inclined to believe Wikipedia, the early teletypes would</pre><pre> actually perform a carriage return to the left and line feed the paper</pre><pre> up one row on a LF, but the CR was necessary because of timing--it took</pre><pre> longer than the gap between characters to physically return the print</pre><pre> head so they added the CR to allow enough time. Apparently they</pre><pre> sometimes had to add NULs as well. Even some CRT terminals took too long</pre><pre> to scroll all the text up. Apparently they didn't have flow control back</pre><pre> then.</pre><pre><br></pre><pre> Very small buffers. Very small. I had a similar problem automating Nortel</pre><pre> Merdian PBX over its console. I wrapped up the expect send into a function</pre><pre> that put a pause between each character. I basically automated the PBX and</pre><pre> had to also simulate a person typing in the commands. If not, the PBX</pre><pre> missed characters I had sent. If a T1/PRI failed the program would try to</pre><pre> bring up and check. If it was still in alarm it would report the alarm and</pre><pre> create the ticket. </pre><pre><br></pre><pre><br></pre><pre> I used to have a TRS-80 and a "Gorilla Banana" printer. I could never</pre><pre> get the flow control to work with it, and had to write a program to</pre><pre> print stuff. It would manually pause a fraction of a second after each</pre><pre> line before sending the next one to the port. Those were the days! ha ha</pre><pre><br></pre><pre> I was hoping I would never hear about flow control and serial printers ever</pre><pre> again. And here you are...</pre><pre><br></pre><pre> XON/XOFF flow control is software and does have a tendancy to not work well</pre><pre> with small buffer serial printers.</pre><pre><br></pre><pre> Hardware could be either DTS/DSR or CTS/RTS flow on the printer. Using</pre><pre> that would have made it work better. The problem is that you need to know</pre><pre> what flow the printer supports or you need to set the DIP switches to the</pre><pre> flow you want.</pre><pre><br></pre><pre> My Okidata days are 20 years behind me. :)</pre><pre><br></pre><pre> </pre><pre></pre><pre>_______________________________________________</pre><pre>Ale mailing list</pre><pre><a href="mailto:Ale@ale.org">Ale@ale.org</a></pre><pre><a href="https://mail.ale.org/mailman/listinfo/ale">https://mail.ale.org/mailman/listinfo/ale</a></pre><pre>See JOBS, ANNOUNCE and SCHOOLS lists at</pre><pre><a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a></pre><pre><br></pre></blockquote><div><span><pre><pre>-- <br></pre>James P. Kinney III
Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
http://heretothereideas.blogspot.com/
</pre></span></div></body></html>