1.1.2: the fault underneath the other three, and a second retraction Troubleshooting said the LAT freeze was fixed in 1.1.1. It said the same of 1.1.0 this morning. Both were wrong, and 1.1.1 is the worse of the two: it kills a session within minutes of any login. The page now leads with the fault that was killing every session underneath the others -- a new sequence number taken for every message sent, acknowledgements included, against a host that acknowledges only what carries slots, so the gap grew by one every keepalive until it passed MYI64's queue limit of 24 and the host stopped accepting anything at all. The three credit and acknowledgement faults found on the way are kept below it, each with the version it belongs to, because each was real. The trace section gains `kernel=in/dropped`, which tells a loss veetee inflicted on itself from a loss on the wire, and says what `unacked` should look like -- the number that was in the first trace of the day and went unread. Releases, Home and Getting Started carry 1.1.2 and say plainly that 1.1.0 and 1.1.1 are both to be avoided for LAT.
1.1.1, and a correction: 1.1.0 is the release to avoid for LAT Troubleshooting said the LAT freeze was fixed in 1.1.0. It was not. 1.1.0 introduced a worse version of the same fault, and anyone reading that page today would have drawn the opposite conclusion from the truth. It now gives both faults a version apart: what 1.0.0 got wrong by counting only what arrived, what 1.1.0 got wrong by reading the gaps in the numbering without counting the host's own acknowledgements, and why the result looked frozen rather than disconnected -- veetee sent LAT's keepalives from the first and did none of its deciding, so it went on acknowledging into a circuit the host had already released. Releases, Home and Getting Started carry 1.1.1 and say it should be taken in preference to 1.1.0.
1.1.0: the LAT credit fault, Close Session, and the signing order Releases gains a 1.1.0 paragraph, and Making a release gains a step that has now been got wrong twice: the winget manifests must be pointed at a release *after* the Windows zip is signed, because signing replaces both the zip and SHA256SUMS. Troubleshooting gains a section for the fault itself -- a LAT session going quiet after a while on a wire that drops frames -- saying what it looked like, that 1.1.0 fixes it, and how to watch a session with VEETEE_LAT_TRACE, including that the DATA variant writes the password out in clear. Using veetee gains Close Session, and says why a lone session keeps its screen when it ends while one of two does not. Roadmap is deliberately untouched: what 1.0 does not do is all still true, and 1.1.0 closed none of it.
veetee 1.0.0 Home, Roadmap and Releases carry the release: every milestone closed, the distribution questions settled (winget alone on Windows, no Flathub), and semver from 1.0 rather than the milestone scheme. Also corrects when RFC 2217 was proved against ser2net: 0.8.11, not 0.8.10, and it is a DECserver, Lantronix or Moxa that remains untried, not a real terminal server as such. Install examples move to 1.0.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Release 0.8.1
Flatpak, screen readers, faster output, Windows signing
Release 0.8.0: saved connections, logs, history search, copy and paste
VT500 menu Set-Up, Display Controls and fonts; release 0.7.1
0.7.0
Set-Up, sound, smooth scroll and CRT effects
Update for 0.6.0: Windows, keymap editor, key programming, recordings, fonts
Update for 0.4.0: VT500 models, colour, dual sessions Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016YDmAmHSpzviSn4u4VuqKw
Add veetee documentation Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016YDmAmHSpzviSn4u4VuqKw
Initial Home page