Date: 07-12-2006 Subject: Patch RELEASE 9.1B Runtime Files Included you will find the patch release of: EMBEDINI 9.1B 12 Jul 2006 9,1,2,0 MAKEDEF 9.1B 12 Jul 2006 9,1,2,0 MAKECLI 9.1B 12 Jul 2006 9,1,2,0 MAKECON 9.1B 12 Jul 2006 9,1,2,0 ODSBAC32.DLL 9.1B 12 Jul 2006 PLBCLIENT 9.1B 12 Jul 2006 9,1,2,0 PLBCLICON 9.1B 12 Jul 2006 9,1,2,0 PLBCON 9.1B 12 Jul 2006 9,1,2,0 PLBDSIGN 9.1B 12 Jul 2006 9,1,2,0 PLBSERVE 9.1B 12 Jul 2006 9,1,2,0 PLBWIN 9.1B 12 Jul 2006 9,1,2,0 PLBWSEC.DLL 9.1B 12 Jul 2006 9,1,2,0 SA_DLL32.DLL 9.1B 12 Jul 2006 9,1,2,0 SUNAAMDX 9.1B 12 Jul 2006 9,1,2,0 SETGUID 9.1B 12 Jul 2006 9,1,2,0 SUNINDEX 9.1B 12 Jul 2006 9,1,2,0 SUNMOD 9.1B 12 Jul 2006 9,1,2,0 SUNSORT 9.1B 12 Jul 2006 9,1,2,0 SUNWADO.DLL 9.1B 12 Jul 2006 9,1,2,0 SUNWODBC.DLL 9.1B 12 Jul 2006 9,1,2,0 SUNWMSQL.DLL 9.1B 12 Jul 2006 9,1,2,0 SUNWSRV.DLL 9.1B 12 Jul 2006 9,1,2,0 PLBCMP 9.1B 12 Jul 2006 PLBDBUG 9.1B 12 Jul 2006 *============================================================================== Notes for WARNINGS: - The 9.1A PLBDSIGN designer sets the version for a PLF to a value that prevents the PLF from being loaded by any runtime/designer versions prior to 9.1A. The user should use the 9.1B PLBDSIGN instead of the 9.1A version to eliminate this problem. *============================================================================== The following files have been changed as follows: ------------------------------------------------------------------------------- PLBWIN - Corrected a problem where a file handle could be discarded when a PLBSERVE Windows runtime detected an open error caused when an AFILE/IFILE has been previously opened by a SUNFM file manager in an OPEN-ONCE mode and the Windows runtime is attempting to open the file directly or unmanaged. Note: 1. When a SUNFM file manager has a file variable opened in a OPEN-ONCE mode, then this file can only be opened as a managed file. Thus, the problem as described by this item should not occur under normal scenarios. - Corrected a F05 error caused by a change in the 9.1A patch relesae. This F05 error would occur when a PLFORM label reference was used in a CALL USING list and a ROUTINE/LROUTINE GUI object was a COLLECTION object pointer. The PLFORM label reference is a COLLECTION and should not cause a F05 error in this case. ------------------------------------------------------------------------------- PLBWIN - Modified the GetColResizeFlag and SetColResizeFlag methods for the LISTVIEW object to allow 256 columns to be supported. With this change the '*INDEX={index}' value can be 0 to 255 inclusively for these methods. ------------------------------------------------------------------------------- PLBCMP - Modified the SUBMENU object to support an alternate syntax format for a CREATE instruction. This alternate syntax allows a SUBMENU object to be created for a parent WINDOW object without requiring a MENU object. Format: [label] CREATE {window};{submenu}[,OBJECTID={value}] Note: 1. The parent object specified as {window} MUST be a WINDOW object as used in this alternate syntax format. - Corrected a problem where a forward reference to a FUNCTION label from a PERFORM instruction was causing bad PLC program code to be generated. This would cause indeterminate PLC program execution that could also cause a GPF error. Example: NDX FORM "1" . PERFORM NDX,FUNC1 STOP . FUNC1 FUNCTION ENTRY DISPLAY "TEST" FUNCTIONEND - Corrected a problem where the compiler could give an erroneous undefined variable errors at random locations in the program source after one of the following instructions was encountered: Example: Ifile IFILE NAME=filename Afile AFILE NAME=filename1 The compilation undefined variable errors would only occur when the 'filename' or 'filename1' variables were declared at the beginning of the program source and the IFILE/AFILE variables were declared toward the end of the program source for a large PLB program with a large number of data variables. ------------------------------------------------------------------------------- PLBDSIGN - Corrected a problem caused by the 9.1A designer where the PLF version was changed to indicate a newer PLF format by mistake. This caused O119 runtime errors when these PLF was compiled and used with runtime version prior to 9.1A. The 9.1B designer has been changed to detect the input PLF version and then output this version when a PLF is written. Note: 1. If a user PLF has been changed with a 9.1A plbdsign to cause the version conflict, a user can simply load the PLF using a 9.1B plbdsign designer and then save the PLF. This resets the PLF appropriate version so the PLF can be used with runtime/designer versions prior to the 9.1A release. - Corrected a problem where a FLOATMENU, IMAGELIST, MENU, SUBMENU, or TIMER object could be associated with a PANEL object. The consequences of these objects being associated with a PANEL was that a GPF error could occur when the PLF was closed and saved by the PLBDSIGN designer. ------------------------------------------------------------------------------- SUNIDE - Improvements were made to the source code window to help keep it displaying properly. -------------------------------------------------------------------------------