1556.8.2 |
Revise |
ATE: ATE About box now shows the correct number of nodes licensed on the server when the ATE license was issued from the server. |
1556.8.1 |
Fix |
ARY(0) detection patch in 1556.7 was not properly handling case where the array reference occurred within a function parameter list. |
1556.7.2 |
Fix |
Certain combinations of tracing options were resulting in corruption of AMOS-to-native filespec conversions. These mostly resulted in failed file lookups or opens, but in some cases, could have resulted in the process hanging. |
1556.7.1 |
Fix |
References to element 0 of an array, i.e. ARY(0), were failing to trigger subscript-out-of-range errors when the reference occurred within an expression within an XCALL or function/procedure call parameter list. They were being treated as array base references instead, but the resulting expression evaluation was potentially causing a segmentation fault. The most likely occurrence of the problem was within TRACE.PRINT statements, where it is common to have expressions such as: TRACE.PRINT "ARY(X) = "+ARY(X)+"..." Such an expression should have triggered—and now does—error 8 if X = 0. |
1556.6 |
Fix |
Add server-side logic to address the XTREE 32K row width limit (see 6.4.1556.5 below) for older ATE clients. |
1556.5.3 |
Fix |
String expression: close a loophole which was allowing a small underflow condition on the string stack. In some cases, this was leading to a segmentation fault. |
1556.5.2 |
Fix |
Environment variable: in some cases, command lines with %env% vars, especially unrecognized ones, were resulting in garbage on the command line. |
1556.5.1 |
Fix |
(Windows) XTREE: close loophole in which a tree with width > 32K would result in an overflow condition possibly leading to memory corruption. This is a client-side fix; see 6.4.1556.6 for addressing it on the server side. |
1556.4.4 |
Revise |
|
1556.4.3 |
Revise |
ATEGFK.SBX 1.0(105) eliminates a five second delay in the case where the source file exists but has zero bytes. |
1556.4.2 |
Fix |
SUBMIT.LIT 3.3(158): Fix obscure problem causing subscript out of range error sometimes when using the /W switch. |
1556.4.1 |
Fix |
INSTR(spos,subject,pattern,flags): When one of the INSTRF_xxx flags was specified, the spos was being applied to the pattern rather than the subject. This was no problem if spos=1, but would likely cause failure of the search otherwise. |
1556.3 |
Fix |
Minor refinement to XTREE/ATE protocol to close loophole resulting in spurious screen garbage under obscure scenarios. |
1556.2.4 |
Fix |
Windows installer: during a new installation, or when updating from a version prior to 6.4, in some cases the installer was forcing a reboot. That has been stopped. |
1556.2.3 |
Fix |
Close an obscure loophole which could have resulted in bad attempts to free memory (possibly even a GPF). UNIX only. |
1556.2.2 |
Fix |
XTREE: Multi-line editable cells (cformat ME) in property sheets where not allowing the use of the ENTER key to insert a line break. |
1556.2.1 |
Fix |
ODTIM: option &h01000000 (do not output month) was only working if option &h00000008 (output month as a number) was also specified. Documentation fix: the documentation had the wrong value for the option to not output date punctuation; it said &h00400000 but should be &h00200000. |
1556.1.2 |
Fix |
XTREE: in some cases, an answer array passed as ANSARY(1) with element size of 24 was being misinterpreted as an array descriptor, causing a failure to load some or all of the lines. |
1556.1.1 |
Fix |
APEX: selective page printing (when starting from other than page 1) was failing to initialize the auto-pitch font. |
1556.0.2 |
Fix |
Close segmentation fault window when passing F4 parameters to ASQL.SBR. |
1556.0.1 |
Revision |
Installer enhancement: script files %MIAME%\ash_custom1.bat and %MIAME%\ash_custom2.bat will now be executed during installation/update, at the start of the file copying and at the end, respectively, if they exist. This provides a way for sites to exercise some control over the update process, perhaps by shutting down background services using A-Shell and then restarting them. Or by saving/restoring customized components or files that you don't want updated in a normal A-Shell update. Note that all the install package contains sample versions of these two files, any customizations you make will not be overwritten. |
