Thanks for your feedback. I appreciate it.
The ability to view live data in hex or charts are features that actually very highly valued by many users. Granted, not everybody will ever need those features. And keeping the receive buffer size reasonable (e.g. up to a few 100k bytes is totally fine on most systems), performance is not an issue. And for users who never need to use the other views and find that the receive buffer is limiting their use case in anyway, the "Direct RX update of text display" bypasses the receive buffer entirely. You can even set the buffer size to 1 and the text display still works as expected with this option turned on. And if this is your preferred configuration, you can even save it as default so that every time you start CoolTerm or open a new terminal, this option is enabled by default.
Coolterm hangs - receive buffer too small ? (macos)
- roger
- Site Admin
- Posts: 528
- Joined: Fri Apr 24, 2009 12:41 am
- Contact:
-
- Posts: 19
- Joined: Wed Sep 10, 2025 12:39 pm
Re: Coolterm hangs - receive buffer too small ? (macos)
Thank you for your response.
My initial reaction when I noticed the terminal getting stuck while writing the BIOS was aghast disbelief, as I feared CoolTerm just managed to brick my NAS. Fortunately, I was calm enough not to reset the device in sheer panic, which would have corrupted the firmware that was still in the process of being written.
I'm currently in the middle of writing some technical instructions, and was looking for a free terminal solution, possibly cross-platform with an intuitive UI, and CoolTerm fits the bill. Otherwise I likely would not have bothered to get to the bottom of the problem I experienced. Many users may not take the time to investigate exclusive options, and instead move on and try some other software.
My initial reaction when I noticed the terminal getting stuck while writing the BIOS was aghast disbelief, as I feared CoolTerm just managed to brick my NAS. Fortunately, I was calm enough not to reset the device in sheer panic, which would have corrupted the firmware that was still in the process of being written.
I'm currently in the middle of writing some technical instructions, and was looking for a free terminal solution, possibly cross-platform with an intuitive UI, and CoolTerm fits the bill. Otherwise I likely would not have bothered to get to the bottom of the problem I experienced. Many users may not take the time to investigate exclusive options, and instead move on and try some other software.