913.3.1
(ATE) XCALL MIAMEX,91,OP,SYSBCLR,WINBCLR,WINTXTC (to set or retrieve the special Windows color associations) is now supported under UNIX/ATE as well as Windows.
913.3.2
(Windows/ATE) Trailing blanks on the text/label portion of an INFLD checkbox are no longer stripped (allowing you to use them for adjusting the spacing between the checkbox and the text).
913.3.3
(UNIX) Submitted jobs were failing to terminate when hitting the end of the CTL file (going into an infinite loop instead.) (Problem was introduced in build 910.)
913.2.1
(ATE) Clean up some problems with the reverse channel.
913.2.2
(Windows/ATE) A new flag, MBF'WRAP (4194304; same as MBF'PATHELLIPSIS) has been defined for use on buttons to cause the text to wrap onto multiple lines if it doesn't fit on a single line (and assuming the button is tall enough to display multiple rows of text).
913.1.1
Fix two INMEMO bugs. One was that under Windows, attempting to access a memo which was being edited would cause the application to get a read error abort, rather than MEMO LOCK. The other was that under UNIX, it would display the MEMO LOCK, but if you hit ^C, it would be stuck until the lock was freed. (Hitting ESC would have worked if you did it before hitting ^C.) Now, hitting ^C is treated as equivalent to ESC (i.e., it does a soft abort from the lock without accessing the memo.)
913.1.2
(Windows/ATE) Fix various problems in the new ATE reverse channel implementation of build 913.
913.0.1
(ATE) ATE reverse channel now supports multiple ATE clients from same IP address connected to same server. Previously, this may have appeared to work but was prone to lockup problems. Note that the port defined in the ATE configuration is now offet the number of jobs whose clients have the same IP address. For example, if you set the port to 30000, the first client from that IP will use that port, but the next one (i.e next instance of ATE on that PC or on a PC which shares the IP address by virtue of a some kind of proxy) will use 30001, then 30002, etc. So if you need to adjust your firewall to allow outbound connections from the server, allow a range of ports to account for the maximum number of ATE connections originating from the same IP.
The reverse channel listening procedure has also been changed to work better in a multi-session / multi-server environment (i.e. where one ATE client IP is running multiple ATE sessions to multiple servers.) Previously, the client would listen all the time for a request to establish a reverse channel connection. This created a potential conflict with multiple processes listening for connections on the same port at the same time. Now, it only starts listening when the ATECTL/C command is used to initiate a connection, and it stops listening as soon as the connection is accepted (typically this is an interval of a fraction of a second). So unless you managed to execute ATECTL/C simultaneously on two different servers connected to the same ATE client, there should be no conflict. (You can eliminate any possibility of a conflict by using different port numbers in the ATE configuration for different servers.)
913.0.2
Debug-level tracing of the A-Shell startup (when using the -trace command line switch) has been improved somewhat. First, more details have been added. Second, a problem with establishing the ashlog.log filename prior to identifying the miame.ini has been fixed. Previously, this was resulting in a log file called "tempashlog.log" in the user's Local Settings directory. (You might want to search for tempashlog.log and erase them if you have any.) Now the file is properly called ashlog.log and is in the directory defined by the user's TEMP (or TMP) environment variable.
To clarify the previous paragraph, although the normal location for the ashlog.log file is in the same directory as the miame.ini (or in the directory specified by the LOGDIR= statement in the miame.ini), certain trace operations may occur before A-Shell has established either of those locations. For those traces, it uses the TEMP directory to create ashlog.log. This can be particularly useful in debugging problems relating to not being able to access the miame.ini (such as networking problems).
So if A-Shell fails to launch correctly and you can't figure out why, try adding "-trace" to the command line (in the properties of the shortcut) and then look at the copy of ashlog.log that will be found in the TEMP directory for the user. For windows, this is typically: "c:\Documents and Settings\<username>\Local Settings\Temp\ashlog.log"
For UNIX, it will be "/tmp/ashlog.log".
Note that if the launch proceeds to the point where it starts to process the miame.ini file, subsequent log entries will go to the regular ashlog.log file in the directory where the miame.ini is (or as specified by LOGDIR=).
