Win16 Client Configuration Parameters

This section describes the configuration options available for the 16-bit client. The options must be changed at each individual client and are used only for legacy applications. Relational engine access is not available for 16-bit client applications.

We recommend that you review Using the DOS Requesters in Getting Started With Pervasive PSQL (Server Edition) before configuring a Win16 client. That section explains the types of Win16 clients and how they are typically used.

You manually configure the settings for the Windows 16-bit client requester in the file BTI.INI.

To configure settings in BTI.INI

Open BTI.INI in a text editor. The file is located in the systems directory of your Windows operating system.

Specify the settings under the appropriate section names.

For example, the following is a partial listing of a BTI.INI file that shows all of the configuration settings and the INI section to which they belong. Note that value assignments are case insensitive ("YES" and "yes" are equivalent).

[Btrieve Requester] 
Splash Screen=yes 
Verify Key Length=yes 
[Microkernel Router] 
Local=yes 
Requester=yes 
Thunk=no 
[Communications Requester] 
Runtime server=yes 
Supported protocols=TCPIP 
TCP connect timeout=15 
 
Refer to the following settings for detailed information.

Access

Use Local MicroKernel Engine


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Use Local Microkernel Engine	Local	[Microkernel Router]	Boolean	Yes/No	Yes	N/A

This setting determines whether a local application tries to connect to a local engine. If set to "Yes," the client requester attempts to connect to a local engine.

Use Remote MicroKernel Engine


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Use Remote MicroKernel Engine	Requester	[Microkernel Router]	Boolean	Yes/No	Yes	N/A

This setting specifies whether the client requester allows access to a MicroKernel server engine running on a remote server. If this value is set to "Yes," and Use Local MicroKernel is set to "Yes," the remote server is tried first.

Application Characteristics

Splash Screen


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Splash screen	Splash Screen	[Btrieve Requester]	Boolean	Yes/No	No	N/A

This setting controls whether or not the transactional interface splash screen displays. The splash screen displays the first time a client requester loads.

Use Thunk


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Use Thunk	Thunk	[Microkernel Router]	Boolean	Yes/No	Yes	N/A

This setting specifies whether the Win16 client requester uses thunking to access Win32 components. This option must be turned on (set to "Yes") when a client on a Windows 32-bit platform accesses a Windows 16-bit application.

Verify Key Length


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Verify Key Length	Verify Key Length	[Btrieve Requester]	Boolean	Yes/No	Yes	N/A

This option can be used for legacy Btrieve applications to prevent the requester from verifying that the index key length passed to the client requester is large enough to hold the key. Setting this option to "No" may allow such applications to avoid status 21 errors.

Caution
If set to "No," this option disables the check by the Pervasive requester to prevent memory overwrites. A memory overwrite can cause a general protection fault (GPF) among other undesirable conditions.

Communication Protocols

Supported Protocols


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Supported Protocols	Supported protocols	[Communications Requester]	String	MS_SPX NETBIOS TCP/IP SPX	Varies	N/A

This setting specifies the protocols that are used by the Communications Requester. If more than one protocol is specified, the Communications Requester attempts to use TCP/IP first. If TCP/IP is not available, it uses MS_SPX. In the case of Linux servers, the only protocol that can be used is TCP/IP. The default value varies depending upon the platform.

TCP/IP Timeout for Communication Requester


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
TCP/IP Timeout for Communication Requester	TCP connect timeout	[Communications Requester]	Numeric	1 to 2147483647	15	seconds

This setting specifies the number of seconds the requester should wait for a TCP/IP connect request to succeed before timing out.

Security

Runtime Server Support


Setting Name	Name Value in INI File	Section in INI File	Setting Type	Setting Range	Setting Default	Setting Units
Runtime Server Support	Runtime server	[Communications Requester]	String	Yes No user_name,password	Yes	N/A

This setting applies to NetWare server access only and controls runtime server support. If enabled with the value Yes, the current user name and password for the drive on which you are presently running are used. To enable RTSS with a different username, specify a user name and password in the format user_name,password.

Note
SUPERVISOR and ADMIN are not valid user names, even if supplied with the correct password. If the requester cannot find a login user name other than SUPERVISOR or ADMIN, it does not attempt to login.