1000 The free memory available is insufficient. Make sure that your workstation meets the system requirements for your environment. If it does, unload some applications to free up memory and try again.
1001 An internal error occurred. Status code is %d.
1002 Setup cannot change trace file name.
1003 Setup cannot access registry.
1004 Setup cannot access registry. Some of the changed settings will not be saved.
1005 No configurable components can be found on the target machine.
1006 The specified setting is invalid.
1007 You cannot run more than one instance of this application at a time. Please close down the other instance and try again.
1008 For SETUP changes to take effect, stop and start the engine(s). This step is not necessary if you changed only TRACE settings and already applied the changes to the current MicroKernel session.
1009 You have not saved your changes.\nDo you want to save them now?
1010 Incomplete Definition: Dictionary location must be specified. Specify a dictionary location and try again.
1011 Add operation not allowed. The maximum number of Data File Locations (8) have been defined. You can specify a maximum of 8 data file locations for a named database reference.
1012 Incomplete Definition: At least one data file location must be specified. Specify at least one data file location for the named database reference definition.
1013 Are you sure you want to delete the following named database reference: %s ?\n\nThe DDF files will not be deleted.
1014 Setup is not able to load the WDBNM32.DLL named database operations cannot be performed.
1015 Setup is not able to load the WDBNAMES.DLL named database operations cannot be performed.
1016 Do you want the changes to setting: %s to apply to the current session of the MicroKernel?
1017 Wrong DLL Version: This is not the current version of WDBUEI32.DLL.
1018 Unable to get the version of %s. status code was: %u.
1019 Incorrect version of %s loaded. Ensure that you do not have an old version of the component loaded, and ensure that the correct version is in your path.
1020 Error checking for availability of component %s. Status code was: %u.
1021 Setup could not get setting infomation for components on the target machine. Ensure that all of the communications and engine components are loaded.
1022 Are you sure you want to bind the following named database reference: %s ?
1023 Are you sure you want to unbind the following named database reference: %s ?
1024 Unable to connect to a remote machine.\n\nThe utility is unable to allocate the resources needed to connect to a remote server. Shut down other applications to free up memory and try again.
1025 Remote connect failed, status code was: %u.\n\nEnsure that all the communications components are current and in the path.
1026 Remote disconnect failed, status code was: %u.\n\nEnsure that all the communications components are current and in the path.
1027 Are you sure you want to disconnect from server: %s?
1028 Client communications component can not be loaded.
1029 A communications error occured between the client communications component and the server communications component. Reloaded the client communications component and the server communications component and try again.
1030 An incorrect version of the client communications component is loaded. Make sure the correct client communications component is loaded and try again.
1031 Unexpected error occurred. Status code was: %u.\n\n Could not get an error message string associated with the reported status code.
1100 Pervasive Software Setup Utility (Win32)
1101 About Pervasive Software Setup Utility (Win32)
1102 Communications Server
1103 MicroKernel Database Engine
1104 Scalable SQL Engine
1105 5.x
1106 6.x
1107 Cursor Stability
1108 Exclusive
1109 On
1110 Off
1111 Pervasive Software Setup Utility (Win32)
1112 Limited by Memory
1113 WSSETUP
1114 NTSSETUP
1115 WMSETUP
1116 NTMSETUP
1117 Modify Database Name
1118 Delete
1119 Workstation only
1120 Local Server only
1121 Multi Engine
1122 Single Engine
1123 Yes
1124 No
1125 LOCAL
1126 &Connect...
1127 &Disconnect...
1128 5.x
1129 6.x
1130 7.x
1131 None
1132 If needed
1133 Always
1134 Error when starting to save settings for component: %s. Status code was: %u.
1135 Error ending setting saves to component: %s. Status code was: %u.
1136 Error saving setting: %s to component: %s. Status code was: %u.\n\nVerify that the correct version of the component identified is loaded.
1137 Unable to gather resources required to connect to a remote server. There could be a shortage of free memory. Shutdown other applications and try again.
1139 Error disconnecting from remote server: %s. Status code was: %u. Ensure that all the correct communications components are loaded.
1140 Some other workstation may be saving settings for component: %s. Another workstation has locked the configuration file. Wait for the other workstation to release this lock, and try to save again
1141 Setting: %s for component: %s has an invalid value. Check the value of the setting and try again.
1143 No
1144 Yes
1145 Auto Detect
1146 Save completed. \n\nYou must shutdown and re-load any components with changed settings in order for those changes to take effect.
1147 Unexpected error occurred. Status code was: %u. Setup could not get an error message string associated with the reported status code.
1148 Could not load the Utilities User Interface DLL. Verify that it is in the path and try again.
1149 Incorrect Utilities User Interface DLL loaded. Verify that the correct DLL is in the path and try again.
1158 Setup has found an unexpected version of %s. Some of the settings displayed by Setup are not supported by this component.\n\nEnsure that the correct version of the component is loaded.
1161 Help for Pervasive Software Setup Utility (Win32)
1162 Named Pipes
1163 Requester
1164 Are you sure you want to delete the following bound named database: %s ?\n\nThe DDF files will be deleted.
1165 Error saving setting: %s to component: %s. The component is not loaded.\n\nVerify that the correct version of the component identified is loaded.
1166 Limited by Available Disk Space
1167 Microsoft SPX
1168 WINSOCK SPXII
1169 Microsoft IPX
1170 WINSOCK TCP/IP
1171 Novell SPX
1172 Novell SPXII
1173 Novell IPX
1174 Novell TCP/IP
1175 TCP/IP
1176 IBM NETBIOS
1177 unknown
1178 WARNING! \n\nThe DDF files in \n\n%s\n\n will be deleted.\n\nAre you sure you want to delete this bound named database?\n\nTo retain the DDF files, first unbind the database, then delete the database.
1179 Named database: %s is consistent with dbnames.cfg.
1180 Database names cannot contain spaces. Enter a name that does not contain a space.
1181 Error saving setting: %s to component: %s. This indicates that an old version of the component is loaded.\n\nEnsure that the correct version of the component identified is loaded.
1182 Try Local Server, then Workstation
1183 Complete Runtime Server Support
1184 Disabled Runtime Server Support
1185 Pre-Authorized Runtime Server Support
1186 NWIPXSPX SPX
1187 Save completed. \n\nYou must shutdown and re-load the following components:
1200 This category contains settings related to files, file handles, record locks, indexes, and log files.
1201 This category contains settings related to the size of buffers the MicroKernel must allocate for various purposes.
1202 This category contains settings related to transactions, including the number supported and how and when they will be logged.
1203 This category contains settings related to the number of clients and threads supported as well as the location of various system files.
1204 This category contains settings related to tracing various Btrieve operations. Tracing is an Advanced feature used mainly for debugging purposes.
1205 This category contains settings available only on NetWare. These include BROUTER and Runtime Server support settings.
1220 The maximum number of unique files that can be open at one time. This value represents the maximum number of physical file handles that the MicroKernel can open.
1221 The maximum number of logical file handles that the MicroKernel uses at one time. Each file can be opened by multiple client instances, resulting in different logical handles for the same physical file handle.
1223 Specifies that the MicroKernel should attempt to balance existing index pages rather than create a new one whenever an index page in a file becomes full.
1225 Controls whether the MicroKernel keeps an archival log of operations executed on selected files. If you turn off this setting, the MicroKernel does not perform archival logging.
1227 Controls file format version of files created by the MicroKernel.
1228 Controls the type of system data stored in files created by the MicroKernel.
1229 Sets the limit for the maximum number of databases this MicroKernel can open. The MicroKernel requires approximately 800 bytes of memory for each open database.
1230 Specifies the size of the cache (in kilobytes) that the MicroKernel allocates. The MicroKernel uses this cache for all Btrieve file accesses. Allocate a cache size no larger than the sum of the sizes of the files you are using.
1231 (Formerly Largest Record Size) Specifies the maximum size of the communication buffer (in kilobytes) that the MicroKernel can submit or return. Each worker thread allocates a memory buffer large enough to accommodate this maximum length of data.
1232 Determines the size of a buffer (in kilobytes) used when accessing files created with the Data Compression file attribute. If you do not use compressed files, set this value to 0.
1233 Advanced: Specifies the size (in kilobytes) of the buffer required to handle extended (multiple record) operations.
1234 Advanced: Specifies the maximum amount of memory (in kilobytes) that the MicroKernel can allocate for sorting purposes during run-time creation of indexes. If set to 0, the MicroKernel allocates as much memory as needed.
1235 Advanced: Controls whether the MicroKernel splits the cache.
1237 You turn this setting on to instruct the MicroKernel that system transactions containing user transactions must be completed when a client issues the End Transaction operation and before the MicroKernel returns the successful status code to the client.
1238 Advanced: Specifies the maximum number of operations (performed on any one file) required to trigger a system transaction. (Transactions are also dependent on the time limit setting.)
1239 Advanced: This setting specifies the time limit (in milliseconds) that triggers a system transaction. (Transactions are also dependent on the bundle limit setting.)
1242 Advanced: This setting specifies the size of the buffer (in kilobytes) the MicroKernel uses when logging. You can enhance performance by increasing the log buffer size, because the MicroKernel writes the log information to disk less frequently.
1243 Advanced: This setting specifies the maximum size (in kilobytes) of a log segment file. When the log file reaches its size limit, the MicroKernel closes the old log segment file and starts a new one.
1244 Each MicroKernel-based application is a client of the MicroKernel. This setting specifies the maximum number of clients that can access the MicroKernel at one time.
1246 Advanced: Specifies how many background I/O threads the MicroKernel spawns. Because the MicroKernel does not spawn additional I/O threads, you should specify the maximum you may need.
1251 Advanced: Specifies the timeout period (in seconds) that the MicroKernel waits when a Btrieve application fetches a record with a wait lock that is already being locked by another application.
1252 Advanced: Specifies the location of the log segment files.
1253 Advanced: Specifies the location of the MicroKernel working directory.
1254 Advanced: Specifies the location of the dbnames.cfg file.
1255 Advanced: Specifies whether to enable the trace feature to trace each API call to a trace file. Developers can use tracing to debug applications. If you turn this option on, you need to specify a trace file.
1256 Advanced: Specifies the file where the MicroKernel should write trace information.
1257 Advanced: Specifies a list of Btrieve Operations which will be traced. Move operations from the Traced list using the Del and Del All buttons. Move operations to the Traced List using the Add and Add All buttons.
1258 Advanced: Specifies the size of the data buffer that the MicroKernel writes to the trace file when you enable the tracing feature.
1259 Advanced: Specifies the size of the key buffer that the MicroKernel writes to the trace file when you enable the tracing feature.
1260 Specifies whether the MicroKernel should use the system cache.
1261 Advanced: Specifies that the MicroKernel allocate resources, including threads and memory buffers, when the MicroKernel is started. By default, the MicroKernel does not allocate any resources until the first operation request.
1262 Advanced: Causes the MicroKernel to free all memory and thread resources to the system and return to a minimal state (no resources allocated) when there are no active clients.
1263 Advanced: Specifies how long the MicroKernel will wait (in seconds) before going into minimal state.
1264 Advanced: Specifies how many worker threads the MicroKernel initially spawns to handle client requests. (The MicroKernel may dynamically spawn additional worker threads as needed.)
1265 Specifies the location the MicroKernel uses to store some system files and is a default location for other items, such as the transaction and trace file.
1266 Advanced: Specifies the thread priority class of MicroKernel threads.
1267 Advanced: Sets the thread priority delta for MicroKernel threads. The MicroKernel threads should have a slightly higher thread priority delta than the client application of the same priority class.
1280 Specifies whether the Microkernel should load Brouter.
1281 Specifies the communications buffer size used by Brouter.
1282 Specifies the level of Runtime Server Support provided by the Microkernel
1340 Settings for the Communications Manager for the MicroKernel Database Engine.
1341 Specifies the maximum number of remote tasks that can access the server at any given time. Approximately 32 kilobytes of memory are required for each session. You cannot improve performance by specifying a value higher than you need.
1342 Advanced: Specifies how many communications threads the Btrieve Communications Manager spawns to handle client requests. These threads are the elements that actually perform file operations on behalf of the requesting client process.
1343 Advanced: Specifies whether to enable the Btrieve Communications Manager to accept remote requests. It advertises the presence of the Engine to remote servers and workstations.
1344 Advanced: Specifies the size of the buffer (in kilobytes) that the engine reads for packets from the OS communication layer (rounds up to nearest multiple of the system page size when allocated).
1345 Specifies the maximum size of the communication buffer (in kilobytes) that the Communications manager can submit or return.
1346 Specifies which communications protocols to enable.
1347 Need help text
1350 Settings for the Communications Manager for the Scalable SQL Engine.
1351 Specifies the maximum number of remote tasks that can access the server at any given time. Approximately 32 kilobytes of memory are required for each session. You cannot improve performance by specifying a value higher than you need.
1352 Advanced: Specifies how many communications threads the Scalable SQL Communications Manager spawns to handle client requests. These threads are the elements that actually perform file operations on behalf of the requesting client process.
1353 Advanced: Specifies whether to enable the Scalable SQL Communications Manager to accept remote requests. It advertises the presence of the Engine to remote servers and workstations.
1354 Advanced: Specifies the size of the buffer (in bytes) that the engine reads for packets from the OS communication layer (rounds up to the nearest multiple of the system page size when allocated).
1355 Specifies the maximum size of the communication buffer (in bytes) that the Communications manager can submit or return.
1356 Specifies which communications protocols to enable.
1357 Need help text
1360 This category contains settings related to the Scalable SQL system configuration.
1361 This category contains settings related to manipulating the Scalable SQL trace or log file.
1380 (Windows NT only, Advanced) Specifies how many worker threads Scalable SQL initially spawns to handle client requests. (Scalable SQL may dynamically spawn additional worker threads as needed.)
1381 (Windows NT only) Specifies the size of the communication buffer (in bytes) that is used by the Scalable SQL engine and the Local Interface DLL to communicate. Each worker thread allocates a memory buffer of this size.
1382 Allows you to specify the maximum number of tables Scalable SQL allows in a single join.
1383 This option allows you to set the isolation level Scalable SQL uses if an application fails to set one. Cursor Stability: row- or page-level locking. Exclusive: file-level locking.
1384 Specifies the directory in which you want Scalable SQL to store the temporary files it creates during certain processes. This directory must exist before Scalable SQL accesses it.
1385 Advanced: Specifies whether to enable the trace feature to record database login and logout activity to a trace file.
1386 Advanced: Specifies whether to enable the trace feature to record failed database login attempts to a trace file.
1387 Advanced: Specifies whether to enable the trace feature to record all data definition and data manipulation activity to a trace file.
1388 Advanced: Specifies the file where Scalable SQL should write trace information.
1389 Advanced: Deletes the Scalable SQL trace file.
1390 Advanced: Specifies whether Scalable SQL will load the Inscribe component.
1391 Advanced: Specifies whether Scalable SQL will check the table definitions stored in the DDFs against the actual data file definitions.
1400 This category contains settings related to files, file handles, record locks, indexes, and log files.
1401 This category contains settings related to the size of buffers the MicroKernel must allocate for various purposes.
1402 This category contains settings related to transactions, including the number supported and how and when they will be logged.
1403 This category contains settings related to the number of clients and threads supported as well as the location of various system files.
1404 This category contains settings related to tracing various Btrieve operations. Tracing is an advanced feature used mainly for debugging purposes.
1420 The maximum number of unique files that can be open at one time. This value represents the maximum number of physical file handles that the MicroKernel can open.
1421 The maximum number of logical file handles that the MicroKernel uses at one time. Each file can be opened by multiple client instances, resulting in different logical handles for the same physical file handle.
1422 The maximum number of records each client instance can lock at one time. This maximum applies to both single and multiple-record read locks.
1423 Specifies that the MicroKernel should attempt to balance existing index pages rather than create a new one whenever an index page in a file becomes full.
1424 Specifies that all new files are created in v5.x file format. Turn on this setting only if you need backward compatibility with a previous version of Btrieve.
1425 Controls whether the MicroKernel keeps a log of operations executed on selected files. If you turn off this setting, the MicroKernel performs no logging.
1426 Advanced: If you turn on the Log Selected Files setting, this setting specifies whether to use the v6.x or v5.x log file format whenever you create a new log file.
1427 Advanced: Tells whether to delete temporary lock files created during multi-engine file sharing. Deleting may cause Status 81 on peer-to-peer networks.
1428 Controls whether the MicroKernel opens files on local disks exclusively (Single Engine), or in shared mode (Multi Engine).
1429 This setting controls whether the MicroKernel opens files on remote disks exclusively (Single Engine), or in shared mode (Multi Engine).
1430 Controls whether applications can open files using a Btrieve operation with a bias that specifies that individual files can be shared.
1431 Advanced: Sets the number of system transactions performed during write operations for shared files.
1432 Specifies the size of the cache (in kilobytes) that the MicroKernel allocates. The MicroKernel uses this cache for all Btrieve file accesses. Allocate a cache size no larger than the sum of the sizes of the files you are using.
1433 Specifies the maximum size of the communication buffer (in kilobytes) that the MicroKernel can submit or return. Each worker thread allocates a memory buffer large enough to accommodate this maximum length.
1434 Determines the size of a buffer (in kilobytes) used when accessing files created with the Data Compression file attribute. If you do not use compressed files, set this value to 0.
1435 Advanced: Specifies the size (in kilobytes) of the buffer required to handle extended (multiple record) operations.
1436 Advanced: Specifies the maximum amount of memory (in kilobytes) that the MicroKernel can allocate for sorting purposes during run-time creation of indexes. If set to 0, the MicroKernel allocates as much memory as needed.
1439 Advanced: Specifies the maximum number of operations (performed on any one file) required to trigger a system transaction. (Transactions are also dependent on the time limit setting.)
1440 Advanced: Specifies the time limit (in milliseconds) that triggers a system transaction. (Transactions are also dependent on the bundle limit setting.)
1443 Each MicroKernel-based application is a client of the MicroKernel. This setting specifies the maximum number of clients that can access the MicroKernel at one time.
1444 Advanced: Specifies how many worker threads the MicroKernel initially spawns to handle client requests. (The MicroKernel may dynamically spawn additional worker threads as needed.)
1445 Advanced: Specifies how many background I/O threads the MicroKernel spawns. Because the MicroKernel does not spawn additional I/O threads, you should specify the maximum you may need.
1446 Advanced: Specifies that the MicroKernel allocate resources, including threads and memory buffers, when the MicroKernel is started. By default, the MicroKernel does not allocate any resources until the first operation request.
1447 Advanced: Causes the MicroKernel to free all memory and thread resources to the system and return to a minimal state (no resources allocated) when there are no active clients.
1448 Specifies the location the MicroKernel uses to store some system files and is a default location for other items, such as the transaction and trace file.
1449 Specifies where the MicroKernel can create temporary work files used for internal operations such as mergesort. If not specified, the MicroKernel uses the directory where the data file is located.
1450 Advanced: Specifies whether to enable the trace feature to trace each API call to a trace file. Developers can use tracing to debug applications. If you turn this option on, you need to specify a trace file.
1451 Advanced: Specifies the file where the MicroKernel should write trace information.
1452 Advanced: Specifies a list of Btrieve Operations which will be traced. Separate each operation number with a comma. For example, to trace the open, close, and get first operations enter 0,1,12
1453 Advanced: Specifies the size of the data buffer that the MicroKernel writes to the trace file when you enable the tracing feature.
1454 Advanced: Specifies the size of the key buffer that the MicroKernel writes to the trace file when you enable the tracing feature.
1500 This category contains settings related to how applications choose which MicroKernel engine to use for Btrieve requests.
1501 This category contains settings related to how applications interface with the Scalable SQL engine.
1502 This category contains settings related to how applications interface with the MicroKernel Database Engine.
1503 This category contains settings related to how Scalable SQL accesses Database Names.
1504 This category contains settings related to how the Pervasive Communications Requester accesses remote server engines.
1505 This category contains settings related to how the Pervasive Btrieve Interface is configured.
1520 (Windows NT only) Tells the MicroKernel Interface where to pass requests when both a workstation and a server engine are available. The Local setting must be On for this setting to have any affect.
1521 Tells the MicroKernel Interface whether the local Workstation Engine or the local Server Engine (on Windows NT) should be used to access a file.
1522 Specifies whether the Btrieve Requester Interface will allow access to a MicroKernel Server Engine running on a remote server.
1530 Tells the Scalable SQL Requester whether the local Workstation Engine or the local Server Engine (on Windows NT) should be used to access a file.
1531 Specifies whether the Scalable SQL Requester will allow access to a Scalable SQL Server Engine running on a remote server. This setting has precedence over the Local Usage setting when dealing with remote files.
1532 Specifies the number of concurrent tasks. For Windows 3.x , this is the number of applications allowed to access Scalable SQL. For Windows NT and Windows 95, this is the number of threads allowed to access Scalable SQL from one application.
1533 Specifies the maximum number of concurrent database sessions available to an application.
1534 (Win16 Requester only) Allow/disallow support for yielding CPU to other applications during a Scalable SQL Callback. Applicable to 16 bit Windows applications only.
1535 Allow/disallow support for the enhanced XQLVersion call added with Scalable SQL 3.01.
1536 Maximum data length transferrable between the application and the Scalable SQL engine.
1537 Load/access the local Scalable SQL Convert and Mask functionality.
1538 (Win32 Requester on Windows NT only) Tells the Scalable SQL Requester where to pass requests when both a workstation and a server engine are available. The Local Usage setting must be On for this setting to have any affect.
1539 (Win16 Requester only) This option activates 16-bit Windows to 32-bit Windows support which allows a 16-bit Windows application to access the 32-bit Windows Scalable SQL Requester. Set to enable 16-bit to 32-bit thunking in Win32 configurations only.
1540 Tells the MicroKernel Router whether the local Workstation Engine or the local Server Engine (on Windows NT) should be used to access a file.
1541 Specifies whether the MicroKernel Router will allow access to a MicroKernel Server Engine running on a remote server. This setting has precedence over the Local setting when dealing with remote files.
1542 This option activates 16-bit Windows to 32-bit Windows support which allows a 16-bit Windows application to access the 32-bit Windows MicroKernel Router.
1543 Enter 'No' to disable RTSS. Enter 'Yes' to enable RTSS using the default username. The default username is described in the User's Guide. To enable RTSS with a different username, enter: 'username,password'.
1544 This options instructs the MicroKernel Router to validate pointers passed to it. Use this option only during development.
1545 Specifies the number of concurrent tasks. For Windows 3.x , this is the number of applications allowed to access the MicroKernel.
1546 Maximum data length transferrable between the application and the MicroKernel.
1547 (Windows NT only) Tells the MicroKernel Router where to pass requests when both a workstation and a server engine are available. The Local setting must be On for this setting to have any affect.
1548 The number of times the MicroKernel Router will try to connect to the target local engine.
1549 Specifies whether the MicroKernel Router will allow access to the Pervasive.SQL I*net Data Server running on a remote server.
1550 Name used by the MicroKernel Router to log into the Pervasive.SQL I*net Data Server.
1551 Password used by the MicroKernel Router to log into the Pervasive.SQL I*net Data Server.
1552 Determines if the MicroKernel Router uses compression with the IDS server. Using compression may allow the data to be transmitted in fewer TCP/IP packets and may improve performance.
1560 Specifies which transport protocols are available to the requester when connecting to a server engine. Server engines can use either TCP/IP or SPX or both. TCP/IP is preferred if client and server support both protocols.
1561 Specifies the number of seconds the requester should wait for a TCP/IP connect request to succeed before timing out.
1562 Enter 'No' to disable RTSS. Enter 'Yes' to enable RTSS using the default username. The default username is described in the User's Guide. To enable RTSS with a different username, enter: 'username,password'.
1570 (Windows 16 bit only) This options instructs the Brieve Interface to validate pointers passed to it. Use this option only during development.
1571 This option controls the Btrieve Splash Screen. Select 'On' to enable the Btrieve Splash Screen. Select 'Off' to disable the Btrieve Splash Screen.
1600 Settings for remote communications to the Btrieve access model.
1601 Specifies the maximum number of remote tasks that can access the server at any given time. Approximately 32 kilobytes of memory are required for each session. You cannot improve performance by specifying a value higher than you need.
1602 Advanced: Specifies how many commuincations threads the Btrieve Communications Manager spawns to handle client requests. Communications threads are the elements that actually perform file operations on behalf of the requesting client process.
1603 Advanced: Specifies the size of the packets received by this component.
1604 Advanced: Specifies the size of the buffer (in bytes) that the engine reads for packets from the OS communication layer (rounds up to nearest multiple of the system page size when allocated).
1605 Specifies whether or not the Btrieve Communications Manager should use SAP.
1606 Specifies TCP/IP port number that the Btrieve Communications Manager should use.
1607 Specifies the maximum number of remote tasks that can access the server at any given time through each of the supported protocols. The same number of sessions are allowed for each protocol.
1608 Advanced: Specifies how many communications threads are spawned to handle client requests. These threads are the elements that actually perform file operations on behalf of the client process. Each supported protocol spawns this number of threads.
1609 Advanced: Specifies the size of the packets received by this component. This setting applies to SPX communications only.
1610 Advanced: Specifies the size of the buffer (in bytes) that the server communications component uses to read packets from the OS communication layer.
1611 Specifies whether or not the Btrieve Communications Manager should use SAP. This setting applies to SPX communications only.
1650 Settings for remote communications to the Scalable SQL access model.
1651 Specifies the maximum number of remote tasks that can access the server at any given time. Approximately 32 kilobytes of memory are required for each session. You cannot improve performance by specifying a value higher than you need.
1652 Advanced: Specifies how many communications threads the Scalable SQL Communications Manager spawns to handle client requests. Communications threads are the elements that actually perform file operations on behalf of the requesting client process.
1653 Advanced: Specifies the size of the packets received by this component.
1654 Advanced: Specifies the size of the buffer (in bytes) that the engine reads for packets from the OS communication layer (rounds up to nearest multiple of the system page size when allocated).
1655 Specifies the maximum number of remote tasks that can access the server at any given time through each of the supported protocols. The same number of sessions are allowed for each protocol.
1656 Advanced: Specifies how many communications threads are spawned to handle client requests. These threads are the elements that actually perform file operations on behalf of the client process. Each supported protocol spawns this number of threads.
1657 Advanced: Specifies the size of the packets received by this component. This setting applies to SPX communications only.
1658 Advanced: Specifies the size of the buffer (in bytes) that the server communications component uses to read packets from the OS communication layer.
1670 Settings for the DBNames Interface.
1671 Advanced: Specifies the path to an alternate infobase. This is a file path, not a directory path.
1672 If any names are added to the Scalable SQL Servers setting, this setting specifies if Microsoft Named Pipes or Pervasive's Communications Requester should be used to connect to the servers listed.
1673 This setting lists the names of Window NT servers that should be queried for Database Names. If the workstation has Novell Client software loaded and a Windows NT server is advertising Database Names using SAP, that server name does not need to be added.
1674 Advanced: If the Transport setting specifies that Microsoft Named Pipes should be used to query a Scalable SQL Server for Database Names, this value specifies the time in milliseconds that a Named Pipe read will wait before timing out.
