3.91h+ Changes - 10/15/02
The INDEX command may now specify BADKEYS or LISTBADKEYS to effect the same processing as DUPKEYS and LISTDUPKEYS performs. If both LISTBADKEYS and LISTDUPKEYS are specified, then all bad keys are listed ahead of dupkeys. They can be distinguished by whether or not they are duplicate.
Several changes were made to enhance client server processing, including performance improvements, logon improvements, and a couple of CS bugs fixes.
Concerning Unix shell calls the following flag combinations are prevented- -W and -C -R and -C -W and -R In other words Without Shell, Restore Screen, and Continue are mutually exclusive options. If more than one is specified at a time error 2222 is generated.
A new shell call flag is enabled:
- -E or -e indicates that any os errors returned from the shell should be reported (as error 4500+) Otherwise shell call operating errors are ignored.
Occasionally Windows returns error values for fairly nominal exceptions. So the -e is provided as an error return sensitivity level flag.
The -M (minimize) flag has been enhanced. If a lower case m is specified, the shelled to task is initiated in minimized mode with the task appearing on the Windows Taskbar. If an upper case M is specified, the same thing happens execept the task does not appear on the taskbar. Furthermore SPOOLCMD calls use lowercase m.
The HELP file search now uses the following directory sequence: - Current Directory - Base Node of First Drive Statement (where second parm points) - BR Starting Directory Note that the HELPDFLT statement refers to filename not dirname.
The maximum length of printer initialization strings has been expanded from 32 bytes to 64 bytes.
As of 01/21/03, OnQ4 always calls Onq with serial number 12345. BR verifies licensing issues before calling OnQ4, allieviating the need for further verification. So you will need to replace both ONQ4.EXE and ONQ.EXE when updating OnQ4. Be sure to remove or rename obsolete copies of ONQ4.EXE or you could get frustrated.
ONQ4.EXE will now search for ONQ4.BAT before looking for ONQ.EXE. This optional batch file enables the setting of the IQDD environment variable before calling ONQ. This may need to be done because variaous releases of Windows operate differently, in that they don't all propagate environment variables the same.
ONQ4.EXE, ONQ4.BAT and ONQ.EXE should all be present in the same directory WHICH MUST BE IN THE WINDOWS SEARCH PATH. One way to accomplish that is to put these files into the Windows directory.
If used, ONQ4.BAT must set environment variable IQDD, and may optionally set other variables before calling ONQ.EXE. Be sure to include the %1 %2 %3 %4 %5 parameters on your ONQ.EXE call. This will pass the necessary parameters from ONQ4.BAT to ONQ.EXE via the batch file.
If ONQPATH is specified in the configuration file, it becomes the "current" directory during the call to ONQ.
The END key was not setting the FKEY value for FIELDS operations within a window.
In Unix shell calls, -W (without shell) -C (continue) and -R (restore) are mutually exclusive.
Deletion of a protected file under Windows was failing.
The client server model failed to properly display and recognize decimal points.
When a client server connection is broken, the client and server now go closeout on their own.
The system would hang if a RESTORE= command was issued to a printer file.
The configuration printer file was expanded incorrectly. This has been corrected.
The color attributes for a field being exited were being applied from row 1 column 1 instead of the field specifications.
An assertion failure occurred when the operating system reported a zero file time value during a file search.
3.91g Changes - 6/24/02
Error 4270 would occur when starting approximately one of fifty sessions.
Performing a RESTORE to a printer file caused BR to hang.
Shell call was desensitized to called program return codes. More is coming in future releases on this topic.
Field Plus was not working properly on scrolling fields (scrolling fields handle more data than the field space allows for).
The VERSION function was limiting version to 16 bits.
3.91f Changes - 6/01/02
A new configuration file FONT parameter is supported:
- FONT 3DFONT=fontname
This supports two fonts simultaneously, one for background and captions and one font for input fields.
The OPEN #0: string can contain the keyword MAXIMIZE or NOMAXIMIZE which will override the user's INI settings. If not specified, the "Save Font Size And Position" settings will govern.
We have removed restrictions on program size that were in place for compatibility with versions prior to 3.9. This was causing error 2260 unnecessarily.
A new error code has been defined which catches a situation that was causing GPF's:
4120 - Invalid Y2K data found in a Y2K index field
OPTION 27 suppresses the above error code, but also suppresses all other special key processing (e.g. U for uppercase) when invalid Y2K data is encountered in a Y2K sensitive key field.
ONQ now works in 3.9 Windows. Windows models require a launch program called onq4.exe. In client/server mode OnQ runs under the client only. Consequently Unix environments will require an SMB capability such as Vision FS or Samba. The following error codes have been added:
4601 - Invalid WSID 4602 - Invalid Session 4603 - OnQ not licensed. 4604 - Could not open the WBSERVER.DAT file. 4605 - Could not lock the OnQ "In Process" byte. 4606 - Could not get lock offset (should never happen). 4607 - Specified user is not logged into BR. 4608 - Unable to add Onq user. 4609 - Invalid ONQPATH specified. 4610 - ONQPATH not specified - required by Windows (and CS) models. 4611 - ONQ4.EXE not found.
ONQPATH is required by Windows and Client Server models. Onqpath needs to be a full BR path referencing a non-UNC Drive statement. A UNC Drive statement references a UNC drive in the second parameter. (UNC drives will be allowed in a future release.)
New Error Codes generated by a shell call:
4500 + OS error code = code
Known examples: 4502 File not found. 4513 Insuficient permissions for executable during unix shell call. 4591 Process killed by timeout. 4592 Unix fork failed. 4596 Unix process signalled. 4597 Unix process stopped.
This is the first official client/ server release.
The BR-VB interface has been reworked.
The significance of certain keyboard characters has been revised:
- = changed
^A - break ( this was ^C ) ^B - page up (back) ^C - copy to clipboard ^D - delete ^E - end field ^F - page down (forward) ^G - backtab ^H - backspace ^I - tab ^J - next field ^K - prior field ^L - right arrow ^M - enter ^N - left arrow ^O - field minus ^P - print screen ^Q - toggle insert mode ^R - up field (rise) ^S - toggle hold mode (stop)
- ^T - down field ( this once was ^V )
^U - field plus ^V - paste clipboard content ^W - home ^X - cut to clipboard
- ^Y - was REPAINT SCREEN in Unix - now HELP (back where it was)
unchanged in Windows - still HELP ^Z - restore field ^[ - escape ^\ - toggle translation of numerics to linedraw characters
- ^- - repaint screen ( this once was ^Y )
use the minus key on the top row of the keyboard along with the control key
OPTION 26 suppresses the creation of .BAK files.
RENAME now supports the -F flag to force deletion of files when it is necessary in order to complete the rename process.
Note- Something that seems to have been overlooked in the documentation is that the GO command now supports the parameters RESTORE and NORESTORE. This tells BR to either redisplay the screen after each STEP, or not to.
Significant BR Install Shield Changes
After the License Approval, the installation location is confirmed with a browse option and the automatic creation of any missing directories. This much is unchanged.
If the user selects a new location, it is now properly honored by the installation setup. However, no changes are made to user provided configuration files. This means YOU ARE RESPONSIBLE TO PROVIDE THE PROPER DRIVE STATEMENTS IN A WBCONFIG.SYS FILE PLACED ON THE INSTALLATION MEDIA prior to installation.
To support updating with Install Shield:
If a WBCONFIG.SYS file HAS BEEN PROVIDED by the programmer:
- If a pre-existing WBCONFIG.SYS file is found at the target location, the operator is asked if the new file should replace the existing file. THE DEFAULT ANSWER IS TO RETAIN THE CURRENT FILE. If the operator requests REPLACE then a backup (.BAK) copy is made before installing the new file.
- If no pre-existing WBCONFIG.SYS file is found the provided configuration file is installed.
If a WBCONFIG.SYS file IS NOT PROVIDED by the programmer:
- If a pre-existing WBCONFIG.SYS file is found, no configuration file changes are made by the installation process.
- If no pre-existing WBCONFIG.SYS file is found, the installation process creates a WBCONFIG.SYS file consisting of only one drive statement.
If a pre-existing WB.INI file is found, it is renamed BR.INI after appending any existing BR.INI file to it. So the result is to combine the WB.INI and BR.INI data into one BR.INI file, and REMOVAL OF THE WB.INI FILE.
Several processing characteristics would cause COMBO BOX buttons to disappear. These behavior is no longer occurring.
UNC filenames were not being properly processed in Windows version, yielding erratic filename interpretations.
RENAME was overwriting target filenames instead of generating error 4150.
DIR -P was not stopping when Ctrl-A was pressed.
Unix could not handle print queue names longer than 8 characters.
FILENAMES UPPER_CASE was not finding all files when performing a DIR command.
FILENAME UPPER_CASE was only being recognized as UPPERCASE. The underscore was missing from the code.
DIR *. or AA*. was including base matches which had a non-null suffix. For example DIR X*. would find XXX.YYY.
CFORM was not detecting the case when the compiled length exceeded 255.
BR LINUX security authentication was not accepting valid passwords.
BR was creating zero byte spool files when a spool file was opened, but no printing was done. This caused WBSPL files to continue to build.
In version 4, shell call was not executing properly.
Error 2260 was being generated by extremely large array sizes.
Under certain cases data could be entered beyond the end of a field, eventually causing BR to go into an endless loop.
Multiple concurrent flags were not being recognized properly on DOS style commands, such as COPY and RENAME.
If a program was in the process of repainting a screen while it was being moved by the operator, it could cause a GPF.
Error 122 was being caused by improper rounding of subscripts internal to BR.
Several window resize GPF problems existed.
Several BTREE2 corrections were made. We are now proceeding with BTREE2 verification.
File VERSION capacity was increased to allow use of dates as version numbers.
Removed an assertion failure for invalid printer name. Now generates error 4128.
BRSERIAL.DAT processing now ignores the second decimal position. (e.g. 3.90 === 3.99)
Anonymous client server setup was returning a null LOGIN_NAME$ instead of retrieving it from the server BRLISTENER.CONF specification.
Added searching of PATH during Windows shell call.