Installing Btrieve 6.15 for Scala 4.1X Or 5.X

Installing Btrieve 6.15 for Scala 4.1x or 5.x

This document assumes that a system administrator or an experienced network technician is reading it. Any comments or suggestions about this document may be directed to [email protected] This document is divided into three sections.

1: Installing Btrieve on the server. 2: Installing Btrieve on the workstation 3: Checking the Btrieve connectivity.

Installing Btrieve On The Server

This section is divided into two subsections. Choose the subsection that applies to your installation and read the whole subsection.

1 Microsoft NT server (3.51 and 4) 2 Novell NETWARE ( 3.x and 4.x)

1.Microsoft NT server (3.51 and 4)

1. The server setup is done at the server console.

2. The first step is to decide which network protocol is to be used (e.g.: TCP/IP).

3. The next step is to ensure that there is connectivity between the workstations and the server, using the chosen protocol.We suggest disabling all protocols that are not to be used as they may cause unnecassary overhead on the workstation as well as the network.

4. Once network connectivity is established, install Btrieve 6.15 on the server.

5. Installing The Database Server If you are using IPX/SPX, see to it that you set the internal network number to a non-zero value. The default in NT is zero. Purchase a Btrieve server licence for the maximum concurrent number of users expected to use the system. Insert disk marked "disk 1" and run install.exe.

The installation is very straightforward. Simply follow the instructions on the screen.When prompted for directories we suggest using the defaults.When prompted for a program group, choose the default group name and select a common program group. This is so that any username that is a member of administrators will be able to use it. Reboot the server and see to it that the Btrieve server starts automatically. To see that the server is running go to control panel – services.

6. Next step is to install the patches.We recommend using the patches found on Pervasive's Web site www.pervasive.com . You can also install the patches that ship with Scala. These will, however not be updated as often as those on the web. The patch is in the form of a self extracting archive, called Btrnt615.exe.

To install the patch, follow the instructions below.

If the Microkernel Engine is running, go to control panel - services and stop the mikrokernel engine

Copy Btrnt615.exe into the directory that you originally installed Btrieve in. This directory will be on your NT server and is normally called C:\BTI\WinNT. Run Btrnt615.exe to extract the files.

Open a DOS window on the server, and change to the Btrieve directory (BTI\WinNT). Run PATBTRNT.BAT v615xx, where xx is the number of user licences of your old Btrieve. E.G.: PATBTRNT v61550 will be the command if you have a 50 user licence. If you are not sure how many licences you have, open the microkernel monitor and view resource usage. The figure under the column maximum on the row licences in use is the number of licences available. If you stopped the Microkernel Engine before installing your patch, don't forget to start it again.

The server is now ready. The following files may be deleted from the Btrieve directory (BTI\WinNT) Patbtrnt.bat

Btrnt.exe

Patch.exe

Btrnt615.exe

8. Configuring The Database Server From the start button choose programs - btrieve technologies database - Microkernel Setup

The following settings should always be made (MKDE Server edition) – file settings – Open files : Maximum number of concurrent users multiplied by 120 (MKDE Server edition) – file settings – handles: Maximum number of concurrent users multiplied by 120 (MKDE Server edition) – System resources/directories – Active clients: Maximum number of concurrent users multiplied by 8 MKDE (Server Edition)-System Resources/Directories-Worker Threads = 4

MKDE (Server Edition)-Memory Resources-Communication Buffer Size = 65135

(MKDE Server edition) – Memory resources – Cache Allocation: 20-25% of available memory after demands for all other running applications are satisfied MKDE (Server Edition)-Memory Resources-Extended Operation Buffer Size = 64

(BTI Communication Server) – Microkernel dB Engine – Sessions: Maximum number of concurrent users multiplied by 4 The following parameters are also worth looking at (MKDE Server edition) – Client System transactions – Operation bundle limit: 2000

(MKDE Server edition) – Client System transactions – Initiation time limit: 1000

9. TIP!! Btrieve MKDE uses double caching by default. This means that the same page can sometimes be found once in the MKDE cache and once in the NT system cache. When the NT system cache gets full, the system will start paging to disk, causing serious performance degradation. This can be avoided by disabling Btrieve use of the system cache. To do this you will have to edit the NT registry. We do not recommend doing this unless you are a very experienced NT system engineer. If the registry is damaged you may not be able to restart your server. The setting is HKEY_LOCAL_MACHINE\SOFTWARE\Btrieve Technologies\Microkernel Engine\version 6.15\Server Edition\Settings\System Cache. Set this value to NO.

10. TCP/IP To install TCP/IP support you have to have btrieve version 6.15.440 or later. To see which version of Btrieve you have got installed, go to Start- Programs- Btrieve Technologies Database-Microkernel monitor. When you have the monitor open, click on help-about. You will now be able to see the exact version number. If the version of Btrieve is 6.15.440 or later, you do not have to make any changes on the server. If it is an earlier version you will have to install the patch available on our web site. The procedure for installing a patch has already been discussed in this subsection. Run BIN\REGUPD to update your NT registry. This command updates the "supported protocols" setting for the microkernel database engine to enable TCP/IP and SPX for the Btrieve server.

11. Click here to proceed to the Installing Btrieve on the workstation section.

2. Novell NETWARE ( 3.x and 4.x)

Remove Read only attributes from Btrieve files in Sys:System ( if you are unsure of which files to remove read only from, remove it from all files in Sys:System). If this is not done the Btrieve installation utility will fail when trying to remove old files. Remember to mark these files read only again after installation!

Btrieve under NETWARE does not support TCP/IP.

BE SURE TO INSTALL NETWARE SERVICE PACK 5 FOR NETWARE 4.11 BEFORE INSTALLING BTRIEVE.

You will need admin or supervisory rights on the server. DOS and Windows workstations must run VLM.EXE v1.2 or higher, or NETX.EXE v3.32 or higher.

1. Log onto your NETWARE server in bindery mode as supervisor or supervisor equivalent.This login must be from a windows based machine.

2. Map F: to the root of the system volume. This is done to simplify the instructions, from this point on we will assume that F: is mapped to the root of the SYS volume.

3. Flag all your NLM and NCF files as read/write.If you do not do this the setup will not work, as NETWARE ships with its own btrieve licence and these files have to be deleted or modified.

4. insert Btrieve for NETWARE disk1 and run install.exe

5. You will be prompted for a Btrieve directory, we recommend always using defaults. The program will also ask you if you wish to write over existing files or back them up, we suggest you back up your old files until you are satisfied that the new software is performing properly.

6. download the patch from our web site support.scala.se under customer/btrieve/updates. If you do not have access to our web you can load the patches from the Scala CD. The patches on the CD will not be as updated as the ones on the web.

7. The patch will be in the form of a self extracting file called btrnw615.exe. Extract the file into a temporary directory. Copy all the files into the directory where Btrieve was originally installed (F:\BTI\NETWARE)

8. Run patbtrnw v615x where x is the number of users you are licensed for. You can see how many user licences you have by looking at the original installations disks or type the modules command at the server console and look at btrieve.nlm.

9. You may need to copy the files Btrieve.nlm and Bspxcom.nlm from F:\system to the current directory (f:\BTI\NETWARE). Remember to copy these files back again after running the patch.

10. When the files are installed, you proceed by setting the parameters for BTRIEVE.NLM. You do this by starting BSETUP from the server console. The following parameters are of interest (use the default setting for all other parameters): Number of open files: 120 multiplied by maximun users.

Number of handles: 120 multiplied by maximun users.

Number of remote sessions: Maximum number of concurrent users multiplied by 4 Cache allocation: 20% of available RAM on the server

BSPXCOM Communication buffer size=65135

Please note that these numbers might be too small if you are running other Btrieve applications together with Scala. To load the Btrieve engine on the server type bstart on the console.Do not run load Btrieve (this will load the Btrieve nlm, but not the necessary support files like bspxcom.nlm). We recommend that you include the bstart command in the server's autoexec.ncf. Under Novell NETWARE, the following files are loaded by entering bstart on the server console: BTRIEVE.NLM

BSPXCOM.NLM

AFTER311.NLM (only on 3.12 and later)

If you are running Scala on Windows 95 and NT workstations, you need to load BSPXCOM with the command line parameter -r=1500 , this parameter sets the maximum SPX receive packet size to 1.500 (Note! The value should be 4.096 if you are running a Token Ring network . Specify the frame lenth when you load your Token ring card, as this could cause problems with windows 95 machines if left on auto.).This parameter can be added by editing the BSTART.NCF file in the SYS\SYSTEM directory on the server. If you are running the backup software Arcserve, it is important that the command bstart is put before astart in the AUTOEXEC.NCF. If you do not load Btrieve using BSTART before loading ASTART, Btrieve will start with incorrect parameters, resulting in Btrieve error messages. If you use the Windows DLL to open a file after installing Btrieve for NETWARE v6.15, you may receive a Status 11, telling you that the file name is invalid. In this case, make sure that you have two Novell files, NWIPXSPX.DLL and NWCALLS.DLL available in your search path. If you do not have NWCALLS.DLL, it is available from Novell. To utilise NDS (Btrieve only supports one NDS context) on the server you should install the patch Btrieve 6.15.430 NETWARE, available from www.Pervasive.com.

That will give you the following NLM’s loaded

File Version Btrieve.NLM 6.15.430 or later Bspxcom.NLM 6.15.824 or later

After loading the patch, register the Btrieve server on NDS.

Installing Btrieve on the workstation

This section is divided into two subsections. Choose the appropriate subsection and read the entire subsection carefully

1 Windows95 and NTWS 2 Dos and win3.x

1 Windows95 and NTWS

Please note that the Btrieve Client installation must be performed on each workstation. Install the Btrieve Workstation Engine from the Scala CD ROM. Start the installation by choosing "Start-Run". The program to run is \btrw32\disk1\setup.exe. When the program stops running, you will be asked to answer a series of questions. The serial number question should be answered with 100009. Copy the following files from the directories \bti\winnt\win32\bin on the server to the \windows\system directory on the windows95 or \winnt\system32 on WinNT respectively (if you are working on a NETWARE server the directory will be sys:\bti\netware\win32\bin) . The files are w32rqcfg.exe

w32nr.dll

w32bticm.dll

wbtrv32.dll

wbtrthnk.dll

Start the program Microkernel Setup (Btrieve Technologies Database - Microkernel Setup) and make the following changes: MKDE (Workstation Edition) - File Settings - Open Files = 80 (default=20)

MKDE Interface - Access Control - Requester = Yes

MKDE Interface - Access Control - local=no

Issues with NT

Enabling TCP/IP. Update the server. Run w32rqcfg.exe with the parameter TCPIP. The command will look like this c:windows\system:>w32rqcfg TCPIP. This will create an entry in the registry. To see the protocol parameters type w32rqcfg at the command prompt. Issues with Novell

NDS. Update the server. The drive mapping to Scala should be done using UNC (\\servername\resource) or using Novell server and volume name method.It should not be a NDS mapping (Although it will look like one if you view the mapping using the map command). We suggest you set this mapping in a login script. The Btrieve client should be the client shipped with Scala 4.1x, that is version 6.15.431 with the following files:

File Version Date W32bticm.DLL 2.0.0.0 26/10/95 W32mkde.exe 2.0.0.0 12/10/95 W32mkrc.DLL 2.0.0.0 12/10/95

The later version (6.15.440) will give you Btrieve error 94 and does not work under NDS.

2. DOS and win3.x

! Note. You can not run the Graphic user interface and the Character user interface on the same workstation because of a conflict between the Borland DPMI extender for Windows, which is used by Scala for DOS (CUI), and Win32s which is used by Scala for Windows (GUI).

CUI - Character interface (DOS) Before running Scala, check that the SYSTEM.INI file in the WINDOWS directory contains the following line in the section [386.Enh]: device=windpmi.386 WINDPMI.386 is supplied with Scala and should be copied into the WINDOWS\SYSTEM directory. With Novell Edit the file BTRIEVE.CFG, located in the Scala root directory, to load the Btrieve requester installed with the Btrieve 6.15 Server package. Example: F:\BTI\NETWARE\DOS\BIN\BREQUEST.EXE /L /D:4096 /C:0 F:\BTI\NETWARE\DOS\BIN\BREQUTIL.EXE -STOP Where F:\BTI\ was chosen as a destination path during installation of Btrieve server.

With NT Server Edit the file BTRIEVE.CFG, located in the Scala root directory, to load the Btrieve requester installed with the Btrieve 6.15 Server package. Example: F:\BTI\WINNT\DOS\BIN\BREQNT.EXE /L /D:4096 /C:0 F:\BTI\WINNT\DOS\BIN\BREQUTIL.EXE -STOP Where F:\BTI\ was chosen as a destination path during installation of the Btrieve server.

The switches for the above requesters do the following. /L tells the requester to load only during the DOS session.

/D:4096 tells the requester that maximum packet length should be 4096 bits. This should be the same as your max packet length setting on the server.

/C:0 disables support for the NETWARE runtime server.

GUI - Graphic User Interface

The graphic interface is only seen in Scala 4.x. This is a 32bit program and is not recommended to be run on a 16bit operating system. This is due to instability experienced in the client server environment when using 32bit programs on 16bit operating systems.

Checking Btrieve Connectivity

Once you have installed Btrieve on both the server and the workstation it is best to test the connectivity before trying to start Scala. To do this, it will be a good idea to install Scala on the server, so that you will have some Btrieve files on the server to test connectivity with.

Testing is a relatively simple process. 1. In a NETWARE enviroment, make sure that you are not logged on as the supervisor or admin user. Supervisor equivalent is OK.

2. Open Btrieve file manager and open the file F:scala\dat\sy\sy150000.dat. Where f: is the drive mapping to the Scala directory.

3. You should receive a message: wbmanage-5 the file was opened successfully.

4. If you receive some other message Btrieve is not working, and you should see the Troubleshooting Btrieve document.

5. If you look at microkernel monitor ( in Btrieve Technologies database group on NT or load btrmon on NETWARE) you should see the users that are using btrieve.

6. There is also a utility called Scacheck (downloadable from this web site) to help you troubleshoot your installation.