Please enable JavaScript to view this site.

A-Shell Development History

990.9.1

The GDI printing directive //TEXTCENTER no longer requires quoting of the text argument if it contains commas. Quoting is still allowed, even recommended, but it's easy to overlook.

990.8.1

INFLD enhancement: TYPE |\ disables the display of the INFLD "about" box (normally triggered by Control-\). This is mainly a workaround for a problem where the about box is being triggered unexpectedly.

Also: don't show the SBR=INFDEF: codes in the INFLD about box when those codes are not active in the current call. (This would be the case at the dot prompt or anywhere TYPE "m" is active.)

997.0.1

Fix AUI_IMAGE / IMAGE.SBR problem: routine was failing to take into account the ALTPOS dialog grid scale factors (most noticeable when maximizing).

997.0.2

Minor tracing improvement: XCALL/XDEBUG traces now show the RUN module memory address.

997.0.3

Fix memory management minor problem: certain modules were sometimes being deleted twice from memory (probably harmless, definitely sloppy). Also, add more safety checking to memory deletion requests and better tracing of anomalies.

997.0.4

MX_USRIO Enhancement to allow for string searches.

997.0.5

INIX.SBX new version 5.0(600) replaces the 4.x version. New version requires 990.7 or higher, but performs better.

990.6.1

Add UNIX troubleshooting aid: if a segmentation fault occurs, the ashlog.log entry will now show the location counter. This can be used with the listing generated by the COMPIL /L switch to locate the last instruction.

990.5.1

Fix margin problem with maximizing main A-Shell/Windows window on secondary monitor. If the primary monitor was wider than secondary monitor, it was adding too much left margin, causing the last N columns to be cut off the right edge.

990.4.1

AUI_EVENTWAIT bug fix: EVW_RAW was not returning the proper ctlid value.

990.4.2

Compiler Fix.

990.4.3

UNIX/ATE server side fix: If a screen area save or restore was immediately followed by local (text mode) input operation, the keyboard may have been locked.

990.3.1

Fix a bug in the mechanism of storing/retrieving the last ashw32.exe command line. The only reported symptom was that A-Shell would report "?/ashw32.cl?" on the command line after being re-launched by the Update Center.

990.3.2

Fix GDI printing problem: //TEXTRIGHT was not working properly in landscape mode.

990.3.3

Fix Function/Procedure error handling problem: attempting to call a function or procedure from within an error trap was generating an error during error.

990.2.1

Fix DIR.LIT 3.0(141) so that it no longer treats /W as both /WIDE and /WARN.

990.2.1

Compiler enhancement: COMPIL.LIT 1.0(119) supports a new switch: /LF (List File) which creates a consolidated list file showing all of the source (with all of the ++include files merged in). Each line of the source is marked with the internal location counter, which is how BASIC errors report their location when a program is compiled without line numbers. This can be quite handy in tracking runtime errors, eliminating the need for inserting line numbers and other kinds of traces.

The list file will be named <prog>.LSX (LiSt with indeX)

Note: you can shorten /LF to /L.

990.2.1

Editor compiler enhancement: COMPIL.EXE 1.1.356 implements the -lf switch (equivalent to /LF described above). To add this to your compiler switches inside The Editor, you must add it in the "Custom Arguments" box at the bottom of the Compiler Settings dialog. Note that unlike with COMPIL.LIT, -lf cannot be abbreviated (and is case sensitive).

990.2.1

Error reporting enhancement: Now that we have a means of cross-referencing "location counters" with source statements, the location counter of the last error has been added to various error messages, including the TRACE=BASERR log message and XCALL ERRMSG (DERR).

Also, a new err(8) function has been implemented to retrieve the location counter corresponding to the last error. Note that by convention, location counter values are displayed in hex, but the Basic PRINT statement has no way to know this, so if you are going to PRINT the value of err(8) you should use MIAMEX,MX_OCVT, or the Fn'Dec2Hex$() function in the SOSLIB to output it as hex.

990.1.1

XTREE enhancement: add column definition parameter to allow exit on click.

990.1.2

XTREE fix: When sorting was disabled, clicking on a column header in order to make that the active column (for the purposes of auto-search based on keyboard input) wasn't always working.

990.1.3

COMPIL enhancement: The switch combination /B/T will now output the trace (i.e. the source listing) to the file <prog>.LST. This is useful for creating consolidated listings (with the ++includes all combined) but note that it probably isn't useful for locating errors (because /B outputs the error messages to the same file). So it should probably only be used after you have fixed all the compil errors. Also, don't try to use /T with The Editor, or it will think that every line of your program is an error.

990.1.1

Reorganize the internal embedded custom developer icons to correct the problem introduced very recently in which desktop shortcuts referencing one of the custom icons were having their icons changed after updating ASHW32.EXE. The new scheme should be immune to this problem as icons are added in the future.

990.1.2

Fix a problem with the mechanism of saving the last command line. It wasn't working if the %USERPROFILE%\A-Shell directory didn't exist. The effect was limited, but would have been noticeable when using the update center, which uses the feature to re-launch the session using the previous command line.

990.1.3

Fix an ATE problem where the $ATE expansion in the TAB(-10,AG_WINEXEC) command was clobbering the first two characters following "$ATE".

990.1.4

Fix intermittent problem of not being able to launch FTP after an update due to the need to re-register the FTPDLXcall.DLL. It now gets re-registered automatically on first use.

990.1.5

ATE no longer uses the local PC copy of ASTART.CMD[2,2]. This avoids a confusing conflict when ATE and A-Shell/Windows share a directory tree. Now, ATE looks for ATESTART.CMD looks for ATESTART.CMD[2,2] on the PC side before launching the TELNET session. ATESTART.CMD[2,2] would only be of interest if you wanted to customize the ATE environment by running one or more programs (perhaps, to customize the menus) before starting the TELNET session. The more common way to customize the ATE environment would be from the server side after you've connected.

990.1.6

DIR.LIT 3.0(140) no longer reports (by default) the "Warning: skipping incompatible filespec" message. (This was mostly an annoyance.) You can force the message to appear by using the new switch /WARN. When it does appear, it displays the full path (making it easier to find the offending file.)

990.1.7

Add new switch to DIR.LIT to display files in native format.