COBOL programming tools from NORCOM

     Products     Prices and Purchasing     Support     News     Partnerships     Home   Contact Us   Downloads



Legacy ScreenIO 2.4 Status Log

December 31, 2001 ScreenIO 2.4 support was terminated because of a lack of interest in the product.  We will no longer provide support, enhancements, or bug fixes.  This would be a good time to consider moving up to GUI ScreenIO.  A conversion tool is available to simplify the migration.
Fixed bug that caused an abend in some runtimes AFTER your program did a STOP RUN..
(Fixed 2.4.093/January 27, 2000)
When you run a ScreenIO application with some 32-bit COBOLs, including Merant (Micro Focus) NetExpress and late versions of CA-Realia COBOL, a page fault (memory violation) could occur AFTER your program did a STOP RUN.  All you need to do is to distribute the latest runtime SCRWIN32.DLL; you do not need to relink or recompile your application to resolve this.
Fixed bug where timer exits failed to return some keystrokes.
(Fixed 2.4.093/November 16, 1999)
If you attempted to use a timer exit to simulate keys being pressed (as for a demonstration application), ScreenIO was failing to accept some keys.  We only know of one group using this function, so it is not particularly serious.
Fixed bug where timer exits failed to return keystrokes.
(Fixed 2.4.092/September 23, 1999)
If you attempted to use a timer exit to simulate keys being pressed (as for a demonstration application), ScreenIO was failing to accept the keys.  We only know of one group using this function, so it is not particularly serious.
Updated Micro Focus LINKING.TXT file to address various problems using ScreenIO with Micro Focus products.
(Fixed 2.4.092/June 23, 1999)
Because of the way Micro Focus applications are built, it is important to bundle ScreenIO applications in a certain way.  Although we thoroughly tested ScreenIO with Workbench 4.0.07, later versions of the Workbench runtime generated memory violations when bundled as instructed. 

Earlier documentation did not fully address this issue.  With help from Micro Focus technical support, we corrected the LINKING.TXT documentation file to address Micro Focus application support, including how to Animate ScreenIO applications.

Runtime .DLLs installed in the Windows\System directory conflicted with later CA-Realia compiler .DLL files.
(Fixed 2.4.091/April 20, 1999)
We had been placing our 32-bit runtime support .DLL files (SCRWIN32.DLL, CARCLW60.DLL, and CARFSW20.DLL) in the Windows\System subdirectory (as recommended by Microsoft).  This could cause runtime version mismatches if a CA-Realia user installed a compiler with later runtime .DLLs.  We modified the installation so it does not do this, and updated the readme files.
Panel editor was placing a LOW-VALUE in column 80 of user data fields.
(Fixed 2.4.090/February 25, 1999)
We had been placing a LOW-VALUE in column 80 of user field definitions in the copybook, which caused problems with the Fujitsu compiler; we now ensure this area contains SPACE.
ScreenIO Edit/Copy was not copying the entire data field
(Fixed 2.4.090/November 17, 1998)
When you used Edit/Copy to copy the contents of a ScreenIO field, ScreenIO only copied a portion of the data in a masked field.
Validation/masking bug when using ScreenIO with Fujitsu COBOL
(Fixed 2.4.090/November 17, 1998)
ScreenIO validation logic returned an error when the value entered was correct.  This related to how signs are handled in Fujitsu COBOL and did not affect any other compilers.
ScreenIO "Invalid WORK-S",
SCRMSG memory violations
(Fixed 2.4.078/August 25, 1998)
ScreenIO could generate an "Invalid WORK-S" error message when you tried to display a 25 line window panel.
ScreenIO 2.4 resource sharing, Function 19 memory violation (Fixed 2.4.076/August 24, 1998) ScreenIO was utilizing more resources than necessary while waiting for a user to hit a key or perform a mouse action.  We added a WaitMessage call in the wait-for-a-keystroke loop to relinquish control to Windows for up to 250 milliseconds if nothing was happening so that other applications could get more cycles.

Also fixed a potential memory violation that could occur when you called ScreenIO with Function 19 to yield to Windows during long batch jobs.

Panel Editor subscript and date field editing error
(Fixed 2.4.067/August 17, 1998))
The panel editor could exhibit a "subscript out of range" error if a field was created in column 1 of a panel.  Also, an error introduced in the July 22, 1998 update that incorrectly issued an error message on type 5 (date) fields with a PICTURE 9(8) was corrected. 
ScreenIO 2.4 Status Bar Width
(Fixed 2.4.067/July 22, 1998)
(32-bit product only)  The status bar was not being properly sized and painted when a window was resized.
ScreenIO 2.4 Floppy Menus
(Fixed 2.4.067/July 22/1998)
If the format of the options in the Alt+ definition of a Floppy Menu was A=option instead of Alt+A=option, ScreenIO would fail to include Alt+A, Alt+C, and Alt+S options when translating them to a Windows-style menu. 
Panel Editor subscript error
(Fixed 2.4.066)
The panel editor could generate a "subscript out of range" error if the length of a numeric field (as defined in the PICTURE clause) exceeded the length of the mask.
ScreenIO 2.4 Menu Updating
(Fixed 2.4.066)
ScreenIO was not always updating the contents of the menu if you modified them in your program. 

This was fixed incidental to adding Copy/Paste, since we had to ensure that the menu only offered these when they were appropriate.

ScreenIO 2.4 and Alt- keys
(Fixed 2.4.061)
When you specified the initialization option ALT-KEY-NOWIN, ScreenIO was returning the Alt- key value to your program, but it also forwarded it to Windows, which was incorrect. 

Now, if you select this option, ScreenIO traps all Alt- key combinations as documented in the manual.

ScreenIO State Save/Restore
(Fixed 2.4.061)
If you specify the name of a .INI file when your application makes its initialization call to ScreenIO, ScreenIO will save the state of your application window when you call Function 15 just before terminating your application, and will restore that state the next time the application is run.

Earlier releases did not save the state (normal or maximized) and did not save the location of a maximized window.  We fixed that.

ScreenIO Quits Responding
(Fixed 2.4.054)
Under Windows 3.1 and Windows 95, a ScreenIO application that repeatedly displays a panel (using panel-REPAINT-SCREEN = 'O') without waiting for user input, could quit responding.  

This happened because ScreenIO wasn't processing application messages, and the Windows 95 message queue could be filled up and the application would quit responding.  We now process all non-keyboard and mouse messages every time that you call ScreenIO.  Your application will run more smoothly now, too.

ScreenIO 2.4 and Alt- keys
(Fixed 2.4.054)
When you initialize ScreenIO with the flag SCREENIO-ALT-NOWIN, ScreenIO is supposed to return all Alt- key combinations to your program, except for critical Windows combos such as Alt-Tab and Alt-Space.  This didn't work properly in Windows 3.1 because it passes different messages for these events than WinNt and Win95. 
Zero suppression fails
(Fixed 2.4.054)
A masking error could cause leading zero suppression to fail when a negative value was displayed in signed numeric fields. The value displayed was correct, but the zeroes were not suppressed.
Close message handling
(Fixed 2.4.054)
Corrected handling of CLOSE requests so the "Do you really want to quit?" message is displayed consistently, regardless of whether the user selects the Windows Close option using the mouse, or whether they use the key combination that you specified in SCREENIO-CLOSE-VALUE or panel-CLOSE-KEYVALUE.

Previously, it was displayed when the Windows close was selected using the mouse, but not when the user pressed the function key you specified.

Panel Editor subscript error
(Fixed 2.4.054)
When adding fields to a panel, the panel editor could terminate with a "subscript out of range" message if you duplicated a field more than 46 times. This was an original ScreenIO bug present in earlier versions but because we hadn't used subscript checking, we never discovered it.
ScreenIO 2.1 and 2.2 Y2K bug: All releases of ScreenIO 2.1 (November, 1987), and early releases of ScreenIO 2.2 (March, 1993) had a bug which will abnormally terminate your application after the turn of the century with the error message "evaluation period has expired". 

This could happen with your applications as well as the Panel Editor.  If you are under maintenance, you would have been upgraded to ScreenIO 2.3 (October, 1995) or ScreenIO 2.4 (May, 1998) and you won't have a problem.

If you are still running obsolete compiler versions that are no longer supported, you can still obtain a Y2K compliant library for CA-Realia 3.1 or CA-Realia 4.2 from us by going here.











2000-2016 Norcom, all rights reserved 

Contact Norcom