Pervasive logo

Prev Advanced Operations Guide Next

Win16 Client Configuration Parameters

This section describes the configuration options available for the 16-bit client. These must be changed at each individual client and will be used only when running legacy applications. There is no relational engine access when using 16-bit client applications.

Access

Use Local MicroKernel Engine
Name
Type
Range
Default
Units
Use Local Microkernel Engine
Boolean
On/Off
On
N/A

This setting determines whether a local application tries to connect to a local engine. If set to Off, no attempt is made to connect to a local engine.

Use Remote MicroKernel Engine
Name
Type
Range
Default
Units
Use Remote MicroKernel Engine
Boolean
On/Off
On
N/A

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

Application Characteristics

Splash Screen
Name
Type
Range
Default
Units
Splash screen
Boolean
On/Off
On
N/A

This setting controls whether or not the Btrieve Interface splash screen displays. The splash screen displays the first time a Btrieve requester is loaded.

Use IDS
Name
Type
Range
Default
Units
Use IDS
Boolean
On/Off
Off
N/A

This setting specifies that the MicroKernel Router allows access to a Pervasive.SQL I*net Data server running on a remote server. Make sure this setting is set to On before using any of the IDS configuration options.

Use Thunk
Name
Type
Range
Default
Units
Use Thunk
Boolean
On/Off
On
N/A

This setting specifies whether the Win16 client requester uses thunking to access Win32 components. This option must be turned on when on a Win32 platform (Windows NT/9X/2000) accessing Win16 (Btrieve) applications.

Communication Protocols

Supported Protocols
Name
Type
Range
Default
Units
Supported Protocols
Multiselect
N/A
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 will attempt to use TCP/IP first. If TCP/IP is not available, it uses SPXII. In the case of Linux servers, the only protocol that can be used is TCP/IP; SPX is will not function. The default value varies depending upon the platform; the available options are:

 
Table 5-8 Client 16-bit Supported Protocols
  • Microsoft SPX
  • Microsoft NETBIOS
  • Microsoft TCP/IP
  • NWIPX/SPX SPX

TCP/IP Timeout for Communication Requester
Name
Type
Range
Default
Units
TCP/IP Timeout for Communication Requester
Numeric
1 - 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 (NetWare server access only)

Runtime Server Support
Name
Type
Range
Default
Units
Runtime Server Support
String
Yes
No
user_name:password
Yes
N/A

This setting 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, enter "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.

Configuration Mapping

The following table is a mapping of all the available 16-bit Client configuration options and their settings.

 
Table 5-9 16-bit Client Configuration Settings
Configuration Option
Setting Name
Access
Use Local MicroKernel Engine
Use Remote MicroKernel Engine
Application Characteristics
Splash Screen
Use IDS
Use Thunk
Communication Protocol
Supported Protocols
TCP/IP Timeout for Communication Requester
Security
Runtime Server Support

Prev
Win32 Client Configuration Parameters		 Contents
Up
Check for Revisions 		Next
Linux Client Configuration Parameters