Btrieve v6.15.430 for Windows NT/Windows 95 Client Engine Patch Update March, 1997 READCE.TXT ====================================================================== Contents ======== 1. General Information 2. File Listing 3. Updating Your Product 4. Changes and Enhancements 5. Known Issues 6. Customer Support 7. Disclaimer ====================================================================== 1. General Information ====================== Btrieve Technologies, Inc., has changed its name to Pervasive Software Inc. effective July 1, 1996. The name change reflects the company's expanding role as a leading supplier of database technology designed to bring client/server computing to the mass market. This patch update release will bring your existing Btrieve v6.15 for Windows NT/Windows 95 Client Engine product up to date with the most recent changes and additions. ====================================================================== 2. File Listing =============== The following files are included in this patch update: PATW32CE.BAT PATCH.EXE FILESCE.EXE V615CE.RTP ====================================================================== 3. Updating Your Product ======================== This section explains how to update your existing installation of Btrieve v6.15 for Windows NT/Windows 95 Client Engine. IMPORTANT: Be sure to back up your existing Btrieve components before installing this patch update. Here is a list of files that will be either updated or replaced. For all files that are updated, a valid copy of the file must exist or the update will fail. %WINDIR%\SYSTEM directory [ e.g., on Windows NT: c:\winnt\system on Windows 95: c:\windows\system ] W32MKDE.EXE Updated W32MKRC.DLL Replaced WBTRCALL.DLL Replaced WBTRTHNK.DLL Replaced WBTRV32.DLL Replaced The next table lists the expected file size and date stamps for all files to be updated: File Name Size Date Time --------- ---- ---- ---- W32MKDE.EXE 298,496 10-12-95 3:38p v6.15 *W32MKDE.EXE 320,512 10-07-96 8:22p v6.15.430 This patch update checks the file's date stamp and file size to confirm that it is updating the correct files. This update will run successfully if the components to be updated have the file date stamp from the original installation or current upgrade available on CompuServe. Before updating your system, be sure that the existing directories contain the files with size and date stamp as identified above. A '*' is used to mark the latest available version of a file. When this patch is applied, these files are checked to make sure they are up to date, but they are not modified in any way. If you have received other updates from Pervasive Software to test out fixes to problems, be sure to replace these copies with an officially released version from the list above. This patch update process will attempt to update all of the engine files in a set. If there is an error updating one of the files, the other updates are also backed out. This ensures that your executables are kept in a consistent state before and after the patch update is complete. ------------------------------------------- Steps for applying the Btrieve patch update ------------------------------------------- 1. Copy BTRW32CE.EXE (self extracting zip file) to the directory containing a copy of the files to be updated where the product was originally installed (e.g. C:\Program Files\BTI\Win32). 2. Run BTRW32CE.EXE to extract the batch and patch update files. 3. Run the PATW32CE.BAT DOS batch file. 4. After the batch file completes, check the V615CE.LST output file in the same directory for the patch update status. If you see status messages of the following form: error ept0036: Old File not found. However, a file of the same name was found. No update done since file contents do not match. you have attempted to apply the patch update against an invalid file. Check to be sure that you have the files as listed in this section above. 5. After the patch update has been successfully applied, you may delete all of the files listed in the File Listing section, above (Section 2). You may also delete the V615CE.LST file created during the patch update process. ====================================================================== 4. Changes and Enhancements =========================== Following is a description of the changes that have been made in this product update; only changes made after the initial product release are listed. * This version of the MicroKernel supports execution on Windows NT 4.0. The previous release would cause either a system hang or a GPF on Windows NT 4.0. * With this release of the MicroKernel, files located on a read-only device (such as a CD-ROM) or files marked as read-only by the operating system are opened in multi-engine file sharing (MEFS) mode without creating a .LCK file. In the previous release this could cause problems since .LCK files could not be created on a read-only device. * This update no longer experiences problems related to receiving status code 20 (MicroKernel or Btrieve requester is inactive) when the first Btrieve call made by an application on a fast machine. The WBTRV32.DLL 32-bit interface requester now retries to load the MicroKernel several times before returning a status code 20. The default number of retries is 5, but you can change this number by using the Windows 95 or Windows NT Registry Editor to change the value of the following key: HKEY_LOCAL_MACHINE\Btrieve Technologies\Microkernel Workstation Engine\Version 6.15\ Microkernel Interface\Settings\Load Retries. * Several problems related to using forward slashes ('/') in file pathname specifications (e.g., server/volume:\dir1\file.btr) have been corrected. Prior to this fix, the WBTRV32.DLL 32-bit interface could either reject certain Btrieve operations with a status 12 (MicroKernel cannot find specified file) or, in some cases, generate a GPF. * An attempt to create a file on a NetWare file server with a filename containing more than 8 characters now returns a status code 25 (specified file cannot be created). Previously, the MicroKernel was returning status 2 (I/O error). * A special registry key is now available to avoid status code 81 (lock error) problems in peer-to-peer environments. The MicroKernel uses temporary files to control access between multiple engines. The temporary files are created with the data filename extension replaced with a .LCK extension. On some peer-to-peer networks, deleting the .LCK file in multi-engine sharing causes the application to receive status code 81. To avoid this problem, use the Windows 95 or Windows NT Registry Editor to change the value of the following key to 0 (the default value is 1): HKEY_LOCAL_MACHINE\Btrieve Technologies\ Microkernel Workstation Engine\Version 6.15\ Microkernel Interface\Settings\Delete Tmp Files. Setting this key to 0 will instruct the MicroKernel to not delete temporary files in multi-engine file sharing (MEFS) mode. * In previous versions, if more than one workstation attempted a file recovery against a remote file, one of the workstations successfully opened the preimage file, while the other workstations received a status code 14 (Preimage Open Error). In this update, the other workstations wait until the file recovery is complete, instead of returning the error. * When an application performs several Gets with explicit Lock operations on a record that has just been updated, the MicroKernel may cause multiple locks to be applied against the same record before the system transaction completes the update operation. These extra locks are not released even if an explicit unlock operation is executed, causing another application to receive status 84 when it attempts to read the same record. This problem is fixed in this update. * In some situations, the MicroKernel does not correctly distinguish between explicit and implicit record locks. This can also result in an application receiving status 84 when it attempts to read records with lock. This problem is fixed in this update. * If your application is performing a high degree of concurrent updates in a peer-to-peer environment using the multi-engine file sharing option, you can realize a performance improvement by setting the /g parameter to the value 1:1. This parameter setting causes the engine to release file locks on any read or write operation, thus allowing other workstations quicker access to the same file or files. However, setting this option will degrade performance for applications that are performing bulk read/write operations in a single user mode. ====================================================================== 5. Known Issues =============== * You may experience one or more of the following problems when you uninstall Btrieve using Add/Remove Programs under the Control Panel in Windows 95 or Windows NT 4.0 or the Uninstall icon in the Btrieve Technologies Database program group in Windows NT 3.51. (1) Registry keys may not be completely removed: Use the Registry Editor on Windows 95 (REGEDIT.EXE) or Windows NT (REGEDT32.EXE) to delete the following key before re-installing this product on the same machine: HKEY_LOCAL_MACHINE\Btrieve Technologies. (2) The Btrieve Technologies Database program group/folder may not be removed. On Windows NT 3.51, you can delete this program group from the Program Manager. On Windows 95 and Windows NT 4.0, from the Start button select Taskbar->Start Menu Programs->Advanced and delete the program folder shortcut from within the Programs file folder. (3) Btrieve files installed in the %WINDIR%\system directory and in the Btrieve installation directory (by default c:\bti\win32 on Windows NT 3.51, c:\Program Files\bti\win32 on Windows NT 4.0/Windows 95) may not may not be completely removed by uninstall. These can be removed using a DOS command prompt, Windows File Manager, or Windows Explorer. * Btrieve for Windows NT/Windows 95 v6.15 does not support using locale-specific alternate collating sequences (ACS) by passing a locale's country ID and code page number to the MicroKernel via the Create (14) operation. To use an ACS other than the one for the default locale, you must create a user-defined collating sequence. For more information on ACS files and their use, see the Btrieve Programmer's Manual. * If you are developing a multi-threaded console application targeting either Windows 95 or Windows NT, you must set up a control handler routine to handle a potential CTRL-C keystroke. In this control handler routine you must clean up all of your Btrieve clients by issuing either of the following Btrieve operations: B_RESET(28) or B_STOP(25). The cleanup process must complete before the application passes on the event to the operating system. If there are still active clients (of that application) when the system terminates the threads, the MKDE cannot clean up its connection with the application and is forced to allocate more system resources. This causes performance degradation and significantly increases the time needed for the engine to shut down. For more information about control handler routines, refer to the Microsoft WIN32 Reference Guide. * The Btrieve utilities Roll Forward and File Manager do not fully support long filenames. These will be addressed in a future release. The following limitations are in effect for this release: Roll Forward Utility - The pathname is limited to 120 bytes. File Manager Utility - The FILE|OPEN and FILE|SAVE AS menu options are limited to 64 bytes. - The file specifications for the SET/CLEAR OWNER and CREATE/DROP INDEX are limited to 120 bytes. - The file specifications for the LOAD, COPY, and SAVE DATA operations are limited to 8.3 filenames. * In this release, the maximum length of a filename supported by the MicroKernel Database Engine is 255 characters. ====================================================================== 6. Customer Support =================== Pervasive Software Inc. provides Customer Support to assist you with your Btrieve product. Refer to your documentation for details and contact information on Pervasive Software's Customer Support programs. ====================================================================== 7. Disclaimer ============= PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. ====================================================================== (c) Copyright 1982-1997, Pervasive Software Inc. All Rights Reserved Worldwide **End of READCE.TXT**