Well, it's a long shot, but System V Unix-style tty drivers, including the Cygwin emulation on Windows, have a parameter, "min," that tells the minimum number of characters that must be present in the input buffer before it will be activated. Programs that use the readline library (BASH, e.g.) or that operate in a character-by-character mode (Vim or Emacs, e.g.) will typically have this set to 1:
(running BASH) % stty -a ... ... min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts ... isig icanon iexten echo -echoe -echok -echonl -noflsh -tostop -echoctl -echoke
Your symptoms are consistent with "stty min 2", though I can think of no reason this would occur (a bug in agetty?), but you can confirm it by running "stty -a" and looking at what min setting it reports.
Randall Schulz
At 14:56 2003-03-14, BB wrote:
I am using agetty with both Win95 and WinXP. On WinXP everything works fine. On Win95, I have a problem.
When the Win95 machines modem answers the call, agetty correctly prompts for the login: id. I type it in and notice that every character I type is immediately echoed back to me (I'm using hyperterminal). This is as I would expect based on the agetty code. Each character is read and written back to the tty.
Once I enter the login id, agetty spawns login.exe. From this point on, the characters I type are echoed back to me on every second character. The problem is that if I type a command with an odd number of characters such as "ls\r", nothing happens. Once I type one more '\r' or even a space, the command is executed. The extra character I typed is also echoed back, usually after the next shell prompt.
What could be causing my input to be processed two characters at a time. This does not occur on an XP machine running agetty.
Thanks
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
