Please enable JavaScript to view this site.

A-Shell Development History

1. (WINDOWS) A-Shell/Windows now supports the Microsoft COM interface. A new license flag "COM" has been added to activate it. Refer to the separate documentation on the A-Shell ActiveX SDK for more details.

2. COPY.LIT, ERASE.LIT, MOVE.LIT can now display more than 6 digits without reverting to exponential notation. (Believe it or not, this has become an issue for people copying or deleting more than 1 million blocks at a time.) Note that the LIT versions did not change because the fix is in the common ashell resource file. (VERSYS will now indicate version 58 of the ashell resource.)

3. A new MIAME.INI file option, SWAPWAIT=#### has been implemented to allow you to specify something other than the default wait within the terminal driver when swapping screens or screen sizes. Units are milliseconds. Currently this only affects the wyse50 driver, and was implemented because the standard wait is a full 1 second, which is apparently necessary on some versions of the terminal but not on terminal emulators. The main downside of the extra wait occurs within PolyShell, where it delayed the repaint of the new screen when swapping sessions. To allow this to remain as flexible as possible, the default value of zero simply causes the terminal driver to use its normal wait time (which in the case of wyse50 is equivalent to SWAPWAIT=1000. So to minimize the wait, set SWAPWAIT=1.

In order to allow this to be set on a terminal by terminal basis, SET.LIT 1.2(129) now supports a SET SWAPWAIT {#} subcommand. If the {n} value is specified, it sets the SWAPWAIT time, otherwise it displays the current setting.

4. Three new ++PRAGMA's have been added to COMPLP:

++PRAGMA ALIGN2: align MAP1 on 2 byte boundaries (default)

++PRAGMA ALIGN4: align MAP1 on 4 byte boundaries

++PRAGMA ALIGN8: align MAP1 on 8 byte boundaries

Each affects only subsequent MAP statements. (The very first MAP1 in the program, however, is always at a fixed position relative to the start of the program and thus cannot have a force alignment.)

These are mainly useful in situations where you want to create a multi-level MAP structure to exactly match a C language structure (typically for XCALL interfacing.) 4 byte alignment may also be marginally more efficient with some processors and data types.

WARNING: Changing the alignment can affect how overlays work, so be careful. For example, consider the following:

MAP1 A1,S,5

MAP1 A2,S,5

MAP1 AX,S,16,@A1

With the normal 2 byte alignment, A2 will start in the sixth position with the AX overlay. But with 4 byte alignment, A2 will start in the eighth position of the AX overlay.

5. (AIX) TRIAD catalog interface implemented (via XCALL CIM...) (Refer to TRAID documentation for details on the individual opcodes.) The MacDonald catalog interface using XCALL MPSCOM is still functional.