From: jj4public@outlook.com   
      
   On Thu, 4 Aug 2022 19:36:38 -0700 (PDT), muta...@gmail.com wrote:   
   >   
   > If you think this would be nice, then what   
   > would you propose exactly?   
      
   I've already mentioned that. The protocol implementation should be in form   
   of sent/received data, instead of hardware signals. Again, it not wrong, but   
   there will be drawbacks.   
      
   > And could this have been figured out decades ago?   
   >   
   > Or was something missing?   
      
   I'm pretty sure hobbyists have done similar in the past, except that, they   
   aren't pushlished, or we haven't heard of it.   
      
   > Does error-correction belong in modems or applications,   
   > as happened in real life?   
      
   In modems, in terms of physical location (its ADC has a basic error   
   correction). And in application, in terms of concept.   
      
   > Or does it belong in the os?   
      
   It depends on the involved protocol. Hence, application implementation.   
      
   > If someone types:   
   >   
   > rm -fr /scratch   
   >   
   > And line noise of "enter" happens after   
   > the "/", who failed to think things through?   
      
   Error correction is not a 100% guarantee to be able to correct all errors.   
   There are times when it's simply overwhelmed by outside force. And that   
   includes implementations in current modern error correction algorithms. Even   
   NASA encounters data errors.   
      
   > I'm interested in changing the bios specification.   
   >   
   > Within the limits of the old computers.   
   > Or close.   
   >   
   > Specifically I am after fopen of 0x80   
      
   Well, from the OS'/firmware's point of view, a serial port is seen as a   
   device, instead of a file. Low level thinkering would be needed to change   
   that behavior. The question is, do you want to keep compatibility, or not?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)