On May 03 22:48 95, Paul Edwards wrote to Mike Bilow:

MB>> like to go back to it.  It would just drop most of the 
MB>> characters during the paste operation, which is pretty hard 

PE> People have reported to me that this problem existed in all
PE> text mode applications (e.g. emacs), and was not specific to
PE> msged.  They also reported that the problem went away with
PE> the installation of warp.  BFN.  Paul.

The problem still exists even with Warp and is what I'd call a bug in
Msged.  It doesn't use blocking i/o (Peter don't read this :) ) and a paste
operation overflows the event buffer (EVent in os2scr.c).  

This isn't to say that there isn't/wasn't another bug in OS/2 that
contributed to this behavior.

The simple fix was to check for a full buffer before reading the keyboard
and not read from the keyboard until there was room in the buffer.  I sent
some netmail yesterday with some diffs that include this, but will post
here in case the netmail goes astray (2 longish messages with diffs).

from os2scr.c:

static int mykbhit(void)
{
    KBDKEYINFO ki;
        
    if (FullBuffer())
        return 0;

    ki.fbStatus = 0;
    KbdPeek(&ki, 0);

    if (ki.fbStatus & KBDTRF_FINAL_CHAR_IN) return (1);
    else return (0);
}


static int FullBuffer()
{
    if (((ebufin + 1) % EBUFSZ) != ebufout)
            return 0;
        else
            return 1;
}


The correct way to fix it would probably be to use separate threads for the
keyboard and mouse and use blocking i/o.  This might break the DOS support
though.  I haven't had time to explore this more fully.

Bill


--- Msgedsq/2 3.05wb.01