|Let us help you run your business.|
Product: CometInstall534.exe Version: Comet Build 534 Date: January 8, 2021 Download the latest release now! 1. Prevented a crash introduced in the .533 release that could occur if you referenced MESSAGE$ following an E61 - Program Not Found in a program compiled with Comet16. The .533 change only correctly addressed Comet32-compiled programs.
Changes in previous releases: Build 533 1. Prevented a crash that could occur if you referenced MESSAGE$ following an E61 - Program Not Found. Build 532 1. Prevented a crash that could occur if an SSTP_DUPLEX_POST packet was received by XAP. Build 531 1. Prevented a crash that could occur if the starting position for the MOVE function was set to 0. Build 530 1. Changes to FSTAT for compatibility with Comet16: - FSTAT now returns E11 if the file is not found and the DIR= parameter had been set to blanks. This is the same result you get if no DIR= is used and the file is not found. - The EXCP variable will be reset to E00 at the beginning of each FSTAT. - If the file is not found but a valid DIR= parameter was set, FSTAT will continue to return just the name of the next file in the directory. EXCP will be set to E11 so you will be able to test it as another way to handle the file not found case. As before, any EXCP= path will not be taken as the FSTAT was considered successful. In previous releases the contents of EXCP was unpredictable. Build 529 1. Added an additional \r\n for XAP REDIR in support of current Chrome and Edge browsers. This is now required when redirecting from one https site to another. Build 528 1. Prevented a crash that could occur when using ENCRYPT or DECRYPT. In Comet32-compiled programs this could occur if CryptoSetKeyInfo() returned an error but it was ignored and a subsequent ENCRYPT or DECRYPT was attempted. In Comet16-compiled programs this could occur if the second parameter to ENCRYPT or DECRYPT was null. E45 (Invalid Parameter) will now be issued to prevent the crash. Build 527 1. Eliminated a possible crash when running a program compiled with Comet16 that uses ASCHEX. The crash could occur if the length of the string to be converted was only 1 byte long. Build 526 1. Eliminated a possible XAP crash if a very large query string was written to the XAP session keyed file. Data is now truncated to 7900 bytes to prevent memory overflow. 2. Comet will no longer ask the Security Server for file server licenses when a node connects. The user will be granted as many as they require regardless of the limit on the license. Build 525 1. Corrected a problem in PutFormat. If used following screen I/O the data may not have been formatted correctly. Build 524 CosC 1. Eliminated possible crash or hangup of CosW if an invalid session number is requested when using /s:[session-number] on your CometAnywhere shortcut. If an invalid session is requested you will instead be assigned the next available one. Keep in mind when using /s: that session numbers are relative to 0 regardless of what starting partition or terminal number you have assigned in the [COMET SYSTEM OPTIONS] section of your configuration. Build 523 1. Prevented the CPU from locking up if the "name" parameter in a MAP for a REPLACE statement is a string with a length of 0. Read more about the REPLACE statement using a MAP. Build 522 1. Corrected a problem that could have caused a crash if invalid parameters were set for the Comet DateTime function. Build 521 1. Corrected a problem that could have set all XAP cookie expiration timeouts to days even if a different duration such as minutes or hours had been requested.