In Genesis the MTU is 576, in Miami it's 552. Those and the TCP buffer values are the defaults. However, I reduced AWeb's max network connections to 3, from 12. That seems to be helping. It seems to take longer to grind to a halt sometimes, and when it seems to be halting it sometimes starts moving again somewhat after a bit. Other times I can keep it going pretty much indefinitely.
And then there's times like today, where it grinds to a halt after a short time no matter what. I had to resort to telnetting again as the only thing that will keep it going.
I'm playing with some other TCP settings that have the potential to optimize browser speeds.
From what you've written, it sounds like you need to reduce latency, not increase overall speed. For example, increasing MTU to 1500 will reduce overhead and increase transfer speed. It also increases latency and makes stalls more likely on slow connections. Reducing MTU to 296 does the opposite.
If you're doing wild experiments with settings, I suggest you write down what was changed, why, and what the original settings were. I say that because some undesirable side effects may not become apparent for quite some time. Also, if your problem is mainly with the A1200, double check your serial device settings in Genesis. Maybe you're using some buggy serial.device replacement or your baud rate is a little too high for the A1200. Flow control should be RTS/CTS if at all possible.
Some 34k and 56k modems can be flashed with upgraded firmware that improves performance -- you might check with your modem's manufacturer.
