Please enable JavaScript to view this site.

A-Shell Development History

1144.2.1

Bug fix: AG_INFLD was complaining about an improperly terminated setdef when the TYPE "{" (charset) code was used.

1144.1.1

EZTYP refinement: when running in an ATE GUI environment (with the TYPE code |G added to the SBR=INFDEF: list to automatically use the GUI form of INFLD), the combination of GUI and non-GUI raw character input in the EZTYP routine was causing undue slowness, at best, and dropped characters at worst. (One symptom was that holding down the up arrow was now scrolling reliably upward, but was causing the display to jump up and down erratically.) Note that this fix only applies on the server side.

1144.1.2

ATE refinements in directing input (and especially typeahead) to the correct place (i.e. either the server or the client) when using GUI operations. (In a normal GUI program, virtually all of the real keyboard characters should be consumed on the client side, rather than sent directly to the server, but the reverse is true if the server uses any non-GUI input routines.) Previously, tiny timing gaps were allowing typeahead characters to sneak through when moving from one GUI input operation to the next, which sometimes led to confusion or dropped characters.

1144.0.1

ATSD refinement: ATSD.EXE 5.1.107 supports a new command line switch, "-proto2", which enables a new protocol for launching the A-Shell child sessions. While the old protocol was fine in 99% of the cases, some NIC drivers did not support it, with the result that sessions would appear to connect and then instantly disconnect. When the -proto2 command line switch is passed to ATSD.EXE (either via the ATSDSRV.INI or a shortcut), it now uses Microsoft-recommended WSADuplicateSocket protocol. This protocol requires ASHW32.EXE 5.1.1144.0 or higher, although only for the ASHW32.EXE which is launched on the server side. (It does not affect or depend on the telnet client version.)

1144.0.2

A-Shell/Windows now supports the -proto2 protocol in ATSD as described above. It continues to support the older protocol as well.

1144.0.3

New ? Tab command AG_TRACE allows the application on the server to clear, set, or query the trace flags on the ATE client in real time.