The buffer is indeed small, but not that small ;-) it's actually 64 bytes. XON/XOFF handshaking is not strictly speaking a speed and buffer size issue; slowing it down does indeed work, but I think it's because at the lower speeds it's never necessary to send an XOFF.
When using 'normal' one-character-at-a-time serial communication such as directly between an M100 and another computer there is no problem running at full speed using XON/XOFF. But when connected through USB, WiFi etc. it will be receiving multiple-character packets and AFAIK there is no way to tell the sender to stop part-way through a packet once it's been sent. The 'bridges' we used when we first got the M100 on the internet years ago allowed setting packet size; setting it to very low values let the M100 run at nearly full speed since the bridge looked after holding off the data until the M100 was ready. At least that's my recollection... m ----- Original Message ----- From: Kurt McCullum To: [email protected] Sent: Thursday, June 07, 2018 9:58 PM Subject: Re: [M100] BBSing with Model 200 John beat me to the reply. the 16byte buffer get overloaded before there is enough time to tell the wifi232 to stop sending. HTERM works wonders! I think it's the only way to have a terminal with that seed. I had to do quite a bit of software gymnastics to get mComm to handle 19200 with TELCOM. But I check for XOFF after every 2 or three bytes sent so it slows the transmission rate down. Kurt On Thu, Jun 7, 2018, at 5:29 PM, John R. Hogerhuis wrote: On Thu, Jun 7, 2018 at 4:01 PM Eric Nelson <[email protected]> wrote: With the M200, top speed I have tried is 2400 baud with no data loss. 9600 showed significant loss. I usually use this modem with my Amiga 1200 and Apple IIgs at speeds up to 14400 with no issue. I probably could go higher, but haven't tried. It’s the model 100 software that makes it not keep up. A combination of a small receive queue and display processing overhead. If the wifi232 can do real rts/cts you can get to higher rates using HTERM. Plus it handles utf-8 and some ansi escapes processing. — John.
