BTI.INI
Debie
when you are running a 16bit application that is not thunking to 32bit.
The setting for "THUNK=" is checked initially by a 16bit application,
and if 32bit thunking is set to ON then all other configuration settings
are read from the registry. Many of the settings in the bti.ini file are
very old and only remain in the file for legacy reasons in case someone
is using the system to run an old PSQL product also. A current install
of PSQL does not even use many of them. The ones that are still used by
current products are all accessible through the configuration program in
PCC>client-16bit. Also, the [InstallInfo] section is kept up to date
when a Pervasive.SQL 2000i service pack is installed.
--
Debie Quaglino (Pervasive engineering)
Posted via dBforums
http://dbforums.com
Jon Kimball
entries except:
options=/L:200 /F:20 /H:60 /T:15 /M:512 /U:0
From memory, Locks, FileHandles, HIforget, Tcan'teemreb this one tiher, # of
trasncation maybe, M cache size, U turns off an option, R pacekt size
If you run the 16bit setup utility, or change your 16 bit settings you can
easily see which options get changed in the bit.ini file. The setup tool
has descriptions of each option, the min value, default value, max value
etc.etc. Ervything you can change in the bti.ini file is changed through the
setup tool. So simply reading thruogh all teh optiosn ont eh setup tool
will tell you all you need to know about bti.ini options. w32mkset.exe is
the old 32buit tool, I forget the name of the 16bit one.
JON
"Kurt Friis Hansen" <nos...@kfriis.dk> wrote in message
news:1ho3fus65cd09smdd...@4ax.com...
> I'm probably just blind - or not looking the right places - but...
> I've had a hell of a time trying to find descriptions on the
> parameters actually turning up in the bti.ini file.
>
> Does anyone have a link to a document describing the individual
> parameters?
>
> Kind regards
>
> Kurt Friis Hansen - almost: kfriis#kfriis:dk
> ---
> A bribe a day keeps the tax man away.
> Life has a one hundred percent mortality rate.
> One picture kills more bandwidth, than a thousand words.
Bill Bach
Kurt Friis Hansen wrote:
> I need to know, what the parameters mean. Not that some products do
> not use them anymore. I've looked and looked and ... no serious
> documentation seems to exist anywhere - at least none, that I can lay
> my hands on.
At the risk of sucking up a lot of disk space on the news servers....
Please note that this doc is from 1995 and covers the old Btrieve 6.15 params
only. You didn't mention which version you were using and/or interested in,
but didn't seem to like Debie's answer, so I'm assuming you have Btrieve 6.x
still....
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
Bill...@goldstarsoftware.com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: July 15-18, 2002 - See our web site for details!
BTI.INI Configuration Parameters and Values
Filename: BTIINI.WRI
Version: 06/95
BTI.INI File Settings
This document describes the settings in the BTI.INI file for the Microkernel
Database Engine and Scalable SQL. BTI.INI is a configuration file that is
read by the workstation version of the Microkernel and Scalable SQL engines,
and the Btrieve and Scalable SQL requesters for Windows.
Parameters for the engines and the requesters are described in this
document. However, for Scalable SQL for NetWare, only the Btrieve Requester
and Scalable SQL Requester sections are applicable.
The BTI.INI file must reside in the local Windows directory. All parameters
apply only to applications running on that one computer. If you have a copy
of Scalable SQL for Windows v3.01, you may use the SQL Setup utility to set
many of the parameters. If you have a copy of Btrieve for Windows v6.15, you
can use the Database Setup (DBSETUP) utility to set many of the parameters.
You may also use any standard text file editor to edit the parameters in the
BTI.INI. Be sure to save the file as an ASCII text file.
Microkernel Database Engine Settings
The BTI.INI contains three sections for the Microkernel Database Engine
parameters, each of which is described below. For compatibility with
previous versions of Btrieve for Windows, the Microkernel reads the Btrieve
settings in the BTI.INI file. The three sections that the Microkernel
accesses are:
Btrieve Engine [Btrieve] Section
Btrieve Client [Btrieve Client] Section
Btrieve Requester [Btrieve Requester] Section
Btrieve Requester [BrequestDPMI] Section (Now Obsolete)
NOTE: The meaning of the /T parameter in options parameter in the Btrieve
Client section has changed from pre-v6.x Btrieve releases. The new /T
parameter sets the maximum number of Btrieve clients that can simultaneously
have active transactions at the workstation. The old /T parameter specified
the name of the directory where Btrieve placed transaction files. To specify
this directory name now, use "trnfile=<dir-name>". See the discussion in the
Btrieve Client section below.
Btrieve Engine [Btrieve] Section
The Btrieve Engine Section contains those parameters required by the
Microkernel Database Engine (WBTR32.EXE) and the Loader and Requester
interface (WBTRCALL.DLL) in order to set up internal data structures and
values. The section will normally be written by the setup utility by
obtaining values for the various parameters from a user.
[Btrieve]
tasks=30
local=Yes
requester=No
verbose=0
chkparms=No
thunk=No
tasks Entry
The tasks entry specifies the maximum (total) number of applications using
either the local engine or the requester. This entry is directly settable by
using the setup utility.
Range : 1..64,000 tasks
Default : 30
local Entry
The local entry specifies whether the local Windows Microkernel Database
Engine should be loaded. This engine runs on the workstation of a user, not
a NetWare file server. This entry is directly settable by using the setup
utility by selecting the LOCAL Engine Usage button.
Range : [Yes | No]
Default : Yes
requester Entry
The requester entry specifies whether the Btrieve requester interface will
allow user access to a the Microkernel Database Engine, or a Btrieve engine,
running on a NetWare or Windows NT file server. This entry is directly
settable by using the setup utility by selecting the SERVER Engine Usage
button. If you have a copy of the Btrieve Windows Requester v6.15.4 or
later, you do not need to load the Btrieve for DOS Requester before loading
Windows. If you are using an earlier version of WBTRCALL.DLL, and you select
Yes for this entry, you must also load the Btrieve for DOS requester
(BREQUEST.EXE) before loading Windows.
Btrieve Windows Requester v6.15.4 or later is available with Btrieve for
NetWare v6.15 (Server Edition) and Btrieve for Windows NT v6.15 (Server
Edition).
Range : [Yes | No]
Default : No
verbose Entry
The verbose entry determines if errors encountered during the loading of the
Microkernel Database Engine, or Btrieve requester will be displayed
immediately, or detected when an application attempts to execute a Btrieve
operation. When you set this entry to 1, the Microkernel Database Engine
icon will appear when your application accesses the Microkernel. The
possible settings and actions are as follows:
0 Detect error on attempt to execute Btrieve operation.
1 Display an error message immediately.
This entry is not settable by the setup utility.
Range : 0..1
Default : 0
chkparms Entry
The chkparms entry determines if the input parameters for a Btrieve call will
be checked (validated) by the Microkernel Database Engine every time an
engine access occurs. This parameter should be used for debugging only, as
it will cause slight performance degradation on each call. This entry is not
settable by the setup utility.
Range : [Yes | No]
Default : No
thunk Entry
The thunk entry activates 16-bit Windows to 32-bit support. You use this
parameter to use the Windows NT Microkernel Interface (WBTRV32.DLL) to access
Btrieve for Windows NT from a 16-bit Windows application. This configuration
is known as Windows-on-Windows, or WOW. For WOW applications, you use
WBTRCALL.DLL, the dynamic link library that functions as an interface to the
Btrieve for Windows workstation database engine. WBTRCALL.DLL provides
thunking, via WBTRTHNK.DLL, to WBTRV32.DLL, which handles the request as it
would one from a Windows NT application.
If the Thunk entry is set to Yes, then all requests are sent to this
interface, regardless of the settings for the Local and Requester options.
You cannot set the Thunk entry from the Btrieve for Windows Setup utility. To
change this entry, edit the BTI.INI file using an ASCII text editor.
Range : [Yes | No]
Default : No
Btrieve Client [Btrieve Client] Section
The Btrieve Client Section contains those parameters required by the engine
(WBTR32.EXE) in order to set up internal data structures and values. The
section will normally be written by the Database Setup Utility (DBSETUP) by
obtaining values for the various parameters from a user.
[Btrieve Client]
options=/f:20 /h:60 /l:20 /t:15 /m:512 /u:0
trnfile=
desktopicon=No
SharingOnLocalFiles=SingleEngine
SharingOnRemoteFiles=MultiEngine
EnableSharingBias=Yes
echoargs=No
trace=No
tracefile=
traceops=
datalist=32
keylist=32
deletelockfile=Yes
options Entry
The options entry details the load parameters for the local Microkernel
Database Engine. The entry is a sequence of load parameters of the form
/<option>:<value>. All the default options are settable using the setup
utility.
Range : Not Applicable (N/A)
Default : /f:20 /h:60 /l:20 /t:15 /m:512 /u:0
Other options may also be set. These options, /a, /b, /e, /g, /i, /o, and /q
are described in the following paragraphs.
/a option
The /a option controls whether the Microkernel keeps a log of operations
executed on specified files. The Microkernel Database Engine v6.15
introduces an enhanced log file format. However, for compatibility with
existing Btrieve v5.x clients, the Microkernel can also write the pre v6.x
log format. If a log file already exists, the existing format of the log
file overrides any parameter setting. For any log files that do not exist,
you can specify the desired format by setting /a:5 or /a:6 on the options
entry. If /a:5 is selected, the Microkernel creates a log file in the format
specified by the Btrieve file version. If /a:6 is selected and no log file
exists, all log files are created in the v6.x format.
/b option
The /b option allows you to specify a buffer size that is allocated for
temporary use by three different features: extended get/step, get chunk, and
create index operations. The buffer size is specified in KB. The valid
range for this value is 0 to 64,000 KB. The default value is 16KB. For
extended get/step operations, the buffer size must be large enough to hold
the largest record in uncompressed format, plus the filter expression and the
field extraction information. For the get chunk operations, the buffer size
must be large enough for the chunk descriptors. For the create index
operation, the buffer is only used for autoincrement indexes, and any size
(except 0) is sufficient. For example, to allocate a 4 KB buffer, you would
specify /b:4.
/e option
This option enables transaction durability when your Btrieve application
issues an End Transaction operation. When this option is set, the
Microkernel will ensure that all updates within a single transaction are
completed before returning the status code. A status code of 0 implies that
the transaction was successfully written to disk.
/g option
The /g option can be configured to specify transaction bundling for system
transactions. The format is as follows:
/g:<bundle limit>:<system transaction time limit>
bundle limit refers to the number of explicit Microkernel transactions or
implicit transactions that are combined or bundled into one system
transaction. An explicit transaction involves the use of the Begin and End
Transaction operations; an implicit transaction is a single insert, update,
or delete operation.
system transaction time limit refers to the number of milliseconds that
elapses while the Microkernel collects operations into a system transaction.
When either the bundle limit or the system transaction time limit is reached
(whichever happens first), the Microkernel initiates the writing of the
system transaction to the operating system.
The default setting is /g:100:1000 meaning that the Microkernel will bundle
100 transactions or wait one second (1000 milliseconds) before it initiates a
write to the operating system. In changing these settings, the following
guidelines should be observed:
If running in SEFS mode, your performance will be better if you set both
values high.
If running in MEFS mode, you should set both values low to increase
concurrency between Microkernel engines running on the network.
There is a third factor that can trigger the Microkernel to write a system
transaction to the operating system; that is, if the ratio of bundled pages
and all memory cache pages exceeds the maximum amount of cache available.
The higher the values you choose for bundle limit and system transaction
limit, the more cache you will need in order to fully take advantage of these
settings. You may increase the cache size by specifying a larger value for
the /m option.
/i option
The /i option specifies a drive letter other than the drive where your
Btrieve files are located for storing pre-image files for pre v6.x files.
For v6.x formatted files, this drive letter specifies the location of the
file sharing lock files. The file sharing feature of the Microkernel
Database Engine creates a lock file to control access to the Btrieve files
from different workstations. The lock file is a temporary file with the same
name as the Btrieve file that is opened, but with a .LCK extension. One
lock file is created for each Btrieve file that is updated when file sharing
is enabled.
By default, this lock file resides in the same directory as the actual
Btrieve file that it is locking. To redirect the pre-image and lock files
to drive F:, for example, you would specify /i:F. The specified drive must
contain a directory with the same name at each level as the directory
containing your Btrieve file.
IMPORTANT: If you are using multi-engine file sharing (MEFS), described
below, the lock file drive must be the same drive for all Microkernel engines
and this drive must be one that is accessible to all of the Microkernel
engines on the network.
/o option
The /o option specifies the way the Microkernel responds to DOS critical
errors, such as "Drive Not Ready". This option does not require an
argument. If you specify the /o option and a DOS critical error occurs
during a Btrieve operation, the Microkernel returns a status code, usually
Status 2 (I/O Error) or 12 (File not found), to your application. If you do
not specify the /o option, the Microkernel routes the error to the standard
DOS critical error handler, which usually results in a DOS error message
being written to the screen. You can then either abort or retry the
operation in response to the error.
/q option
The /q option is used in conjunction with the Btrieve create index
operation. This option allows you to set an upper bound on the amount of
memory (in KB) that the Microkernel will allocate for sort/merge buffers. If
an upper bound value is not set, the Microkernel will attempt to allocate as
much memory as it needs for sort/merge operations to complete the create
index operation. This could cause conflicts for other applications that may
also be attempting to allocate memory. This is especially true if your
application is using the callback function, and other applications may run
while an index is being created on a Btrieve file.
trnfile Entry
The trnfile entry identifies the location (path) of the transaction file used
by the local Microkernel engine to manage transactions for applications on
that workstation. If transactions will not be used on a particular
workstation, then this entry may be left blank (NULL). This entry is
settable using the setup utility. Each workstation should define a unique
location for this file. If the Microkernel terminates abnormally during a
transaction, then upon reactivation, the Microkernel uses this file to
determine which incomplete transactions should be rolled back.
Range : Any valid and existing directory path.
Default : NULL( use default path, the Windows installation directory )
desktopicon Entry
The desktopicon entry informs the local Microkernel engine to display the
icon representing the engine upon the Windows desktop. The icon can then be
accessed by a user. This entry is not settable using the setup utility. If
you set verbose=1 in the Btrieve section, the Microkernel engine icon will
appear when the engine is accessed, regardless of the current desktopicon
setting. Also, if you are running the developer kit version, the Microkernel
desktop icon will always appear.
Range : [Yes | No]
Default : No
SharingOnLocalFiles Entry
The SharingOnLocalFiles entry is utilized by the local Microkernel engine to
determine if a Btrieve file located on client disk drives (floppy and hard)
may be accessed by other Microkernel engines located on different
workstations. The SingleEngine value indicates only Microkernel clients on
this workstation may access local Btrieve files (SEFS). The MultiEngine
value allows Microkernel clients on other workstations in a peer-to-peer
network to access local Btrieve files (MEFS). See Chapter 2 of the Scalable
SQL for Windows Installation and Operations manual for more information on
SEFS and MEFS concepts.
Range : [SingleEngine|MultiEngine]
Default : SingleEngine
SharingOnRemoteFiles Entry
The SharingOnRemoteFiles entry is utilized by the local Microkernel engine to
determine if a Btrieve file located on a file server or on a remote drive in
a peer to peer network may be accessed by single or multiple Microkernel
engines. The SingleEngine value indicates the Btrieve files cannot be
accessed by other Microkernel engines, that is, only users on this
workstation can access remote Btrieve files in a sharing mode (SEFS). The
MultiEngine value allows users on other workstations to simultaneously access
remote Btrieve files that are in use by this engine (MEFS). See Chapter 2 of
the Scalable SQL for Windows Installation and Operations manual for more
information on SEFS and MEFS concepts.
Range : [SingleEngine|MultiEngine]
Default : MultiEngine
EnableSharingBias Entry
The EnableSharingBias entry is utilized by the local Microkernel engine to
determine if an application is allowed to override the file sharing modes
defined in the BTI.INI file. When this parameter is set to Yes, the
application may specify a bias on the Btrieve OPEN call to override the
current configuration setting.
Range : [Yes | No]
Default : Yes
echoargs Entry
The echoargs entry causes the Microkernel engine to display information
before and after each API call. This information is written to the
Microkernel's window. The last 30K bytes of output is kept and can be
scrolled. Also, the information can be saved as plain text using the
File|Save menu options. The desktopicon entry must be set to Yes when this
option is enabled. This parameter should be used for debugging only.
Range : [Yes | No]
Default : No
tracefile Entry
The tracefile entry enables the Microkernel to write trace information for
each API call. The information is written to the file specified. This
parameter should be used for debugging only, as it will cause the performance
of the Microkernel to degrade. The information is written to the file using
the 'forced write' mode to ensure that the data is written in the event that
the Microkernel abends or terminates abnormally while running.
Range : Any valid file path
Default : None
trace Entry
The trace entry is used to enable or disable the trace capability. If set to
yes, then the tracefile entry should specify a valid file name. To disable
the trace, you simply set trace=No.
Range : [Yes | No]
Default : No
traceops Entry
The traceops entry allows you to specify the set of Btrieve operations that
you wish to trace. By default, the Microkernel will write trace information
for all Btrieve operations. You can specify the list of operations separated
by blanks or commas, for example:
traceops=0,1,2,3
You can also specify that you want to trace operations that have a lock bias
applied. For example, if you wanted to trace only the Get Equal with single
record wait locks, you would enter 105.
Range : N/A
Default: All Btrieve operations
datalist Entry
The datalist entry allows you change the size of the data buffer that is
written when the trace is enabled. The default value is 32 bytes.
Range : 0..64000
Default : 32
keylist Entry
The keylist entry allows you change the size of the key buffer that is
written when the trace is enabled. The default value is 32 bytes.
Range : 0..255
Default : 32
deletelockfile Entry
The deletelockfile entry is used to instruct the Microkernel to delete
temporary files in multi-engine file sharing mode (MEFS). The Microkernel
uses temporary files to control access between multiple engines. The
temporary files are created with the data filename extension replaced with an
.LCK extension. On some peer-to-peer networks, deleting the .LCK file in a
multi-engine sharing causes the application to receive a return code of Lock
Error (81). If this occurs, set the Delete Lock File to No.
Range : [Yes | No]
Default : Yes
Btrieve Requester Section
Windows Requester DLL [Btrieve Requester]: The Btrieve Requester Section will
contain those parameters needed by the Loader and Requester interface
(WBTRCALL.DLL v6.15.4 or later) in order to communicate with a Novell NetWare
Server or Windows NT Server and transfer data between the workstation and the
server. Currently, this section is not created or maintained by any existing
utility, this task must be performed by the user.
[Btrieve Requester]
datalength=4096
runtime server support = yes
datalength Entry
The datalength entry is the maximum number of bytes the Requester can send to
or receive from the Btrieve server on any single Btrieve Requester. This
value represents an initial setting. The Requester automatically increases
the size if needed.
Range : 4096 to 57500
Default : 4096
runtime server support Entry
The runtime server support entry enables you to enable or disable NetWare
Runtime server support.
Range : no | yes | username, password
Default : yes
Windows/DOS Requester [BrequestDPMI]:
Note: The [BrequestDPMI] is obsolete. It is documented here for completeness
only.
The Btrieve Requester Section will contain those parameters needed by the
Loader and Requester interface (WBTRCALL.DLL v6.15.1) in order to communicate
with a Novell NetWare Server and transfer data between the workstation and
the server. Currently, this section is not created or maintained by any
existing utility, this task must be performed by the user.
[BrequestDPMI]
freememory=No
freememory Entry
The freememory entry instructs the requester to allocate and free real-mode
memory upon each request. For any application executing strictly in a
Windows environment, the setting should be No. For those applications
running in conventional memory, a setting of Yes may be appropriate, however,
performance will suffer due to the overhead of allocation and free
operations. This entry is not settable using the DBSETUP utility.
Range : [Yes | No]
Default : No
Scalable SQL [Scalable SQL] Section
The Scalable SQL Section lists those options needed by the Scalable SQL
Loader and Requester interface (WXQLCALL.DLL). These options are set
directly and indirectly, by a user through the setup utility.
[Scalable SQL]
local=Yes
requester=No
tasks=2
logins=2
allow callbacks=Yes
local Entry
The local entry specifies whether the local Scalable SQL engine should be
loaded. This engine runs on the workstation of a user, not a NetWare file
server. This entry is directly settable by using the setup utility by
selecting the LOCAL Engine Usage button.
Range : [Yes | No]
Default : Yes
requester Entry
The requester entry specifies whether the Scalable SQL requester interface
will allow user access to a Scalable SQL engine running on a NetWare file
server. This entry is directly settable by using the setup utility by
selecting the SERVER Engine Usage button.
Range : [Yes | No]
Default : No
tasks Entry
The tasks entry specifies the maximum (total) number of applications using
either the local engine or the requester. This entry is directly settable by
using the setup utility.
Range : 1..250 tasks
Default : 2
logins Entry
The logins entry specifies the maximum number of database logins (sessions)
allowed per task for either the local engine or the requester. This entry is
directly settable by using the setup utility.
Range : 1..250 tasks
Default : 2
verbose Entry
The verbose entry determines if errors encountered during the loading of the
Scalable SQL engine, or Scalable SQL requester will be displayed immediately,
or detected when an application attempts to execute a Scalable SQL
operation. The possible settings and actions are as follows:
0 Detect error on attempt to execute Scalable SQL operation.
1 Display an error message immediately.
This entry is not settable by the setup utility.
Range : 0..1
Default : 1
allow callbacks Entry
The allow callbacks entry determines if the local Scalable SQL engine and the
Scalable SQL requester will relinquish control of the CPU during processing.
If the entry is set to Yes, then control will be released by invoking a user
registered callback function. Otherwise, the CPU will not be shared with
other applications. This entry is not settable using the setup utility.
Range : [Yes | No]
Default : Yes
Scalable SQL Engine [Scalable SQL Engine] Section
The Scalable SQL Engine Section will provide the load parameters for the
Scalable SQL engine (WXQL32.DLL) when it is loaded. These parameters are set
directly and indirectly, with the setup utility.
[Scalable SQL Engine]
isolation level=cs
external sort path=
files in join=8
isolation level Entry
The isolation level entry determines the extent to which an application's
transaction is isolated from other transactions' update operations. The CS
option implements record-level locking on a file and the EX option implements
file-level locking. This entry is settable using the setup utility.
Range : [CS | EX]
Default : CS
external sort path Entry
The external sort path entry is the location of the current external sort
file directory. Scalable SQL uses the directory for temporary files which
are deleted when an application logs out of the dictionary. This entry is
settable using the setup utility.
Range : Any valid and existing directory path
Default : NULL, ( use default path, C:\TMP )
files in join Entry
The files in join entry sets the maximum number of tables that can be joined
together. This entry is settable using the setup utility.
Range : 2 - 20
Default : 8
Scalable SQL Requester [Scalable SQL Requester] Section
The Scalable SQL Requester Section contains those parameters needed by the
Loader and Requester interface (WXQLCALL.DLL) in order to communicate with a
Novell NetWare Server and transfer data between the workstation and the
server for Scalable SQL. The section is set directly and indirectly by the
setup utility after obtaining values for the various parameters from a user.
[Scalable SQL Requester]
datalength=4096
views=8
datalength Entry
The datalength entry specifies the length (in bytes) of the longest message
that may be accessed through the Scalable SQL requester. This value
represents an initial setting; the requester will increase the size if needed
automatically. This entry is not settable using the setup utility.
Range : 1024..57500 bytes
Default : 4096 bytes
views Entry
The views entry specifies the initial maximum number of views that may be
active at any given time on the workstation. This value represents an
initial setting; the requester will increase the size if needed
automatically. This entry is settable using the setup utility.
Range : 1..255 views
Default : 8 views
Database Names [Database Names] Section
The Database Names Section contains those parameters required by Btrieve
Technologies' database products when accessing a database by name rather than
pathname. Currently there is only one entry defined.
[Database Names]
DBNamesDirectory=
DBNamesDirectory Entry
The DBNamesDirectory entry specifies the directory from which you want the
Microkernel to access the database names configuration files (DBNAMES.CFG).
If you are running on a network, you can specify a directory on the network.
Workstations on the network can share the same copy of the database names
configuration file if the applications have the same drive letters mapped to
the directory locations of the files.
Range : Any valid and existing directory path.
Default : The root directory of your drive C