Web Site Login
^ November: PSQL on Mac? ^
October Results: Insufficient Data
[See All Surveys]
|
|
 |
Determining Your Btrieve Engine Version
Last Updated: 02/09/2003
It is very common for people to know that they are using Btrieve, but to not know exactly which version they
are using. Moreover, the list of related files often becomes a question, especially for Btrieve 6.15 versions,
and some users are simply without a clue.
This paper was created so that someone could locate the Btrieve files on their workstation or server and determine
the exact version, including user count, where appropriate.
Table of Contents:
NetWare Server Engines
With NetWare servers, it is possible to have any version of Btrieve from 5.x all the way through Pervasive.SQL
V8. Many users see the version reported from BREQUEST and assume that this is their Btrieve version -- it just
isn't so! You must query the server to determine exactly which version of BTRIEVE.NLM you have.
On older versions of NetWare, you can do this with the "MODULES" command, which lists all the loaded
modules on the server. Then, watch for the BTRIEVE.NLM to scroll by. For NetWare 4.11 and above, you can use the
command "MODULES BTR*" to list only those modules that start with "BTR", which will
save some searching.
Btrieve 5.x
If you get a version of Btrieve that is 5.x, it may be hard to tell exactly which patch you have. If this is
the case, contact Goldstar Software for help in identifying the exact release.
Btrieve 6.10
If you have Btrieve 6.10, it is also important to know the subrelease. Btrieve 6.10 supports DOS applications
and Win16 applications (through the DOS hooks) only. You cannot run Win32 applications to this engine! Here's a
list of releases from this version:
- 6.0 (in the NetWare SQL 3 box): May 1992
- 6.10a (in the NetWare 3.12 box, a very unstable release): Jan 1993
- 6.10c: (in the NetWare 4.01+ box, a very STABLE release!): Nov 1993
- 6.10f: (in the NetWare 4.1x and NetWare 5.0 box, with 4 bug fixes from 6.10c): October 1994
Btrieve 6.15
With Btrieve 6.15, it is also important to note the subrelease, but they started using numbers instead of letters.
It is interesting to note that the DOS requester started reporting itself as 6.16 throughout these releases, and
eventually 7.00.xxx, but the engine was still 6.15. The following list shows the Btrieve 6.15 releases in order:
- 6.15.1 was released with SSQL 3.01 in 11/1994. First release of Btrieve.nlm v6.15.x (there was never a "plain"
6.15)
- 6.15.2 started the "Btrieve for NetWare" releases in 03/1995
- 6.15.525 patch update released in 06/1995
- 6.15.1208 patch update released in 12/1995
- 6.15.430 patch update released in 08/1996
- 6.15.431 patch update released in 09/1996 (only change was a fix to bad DOS requester from .430 release)
- 6.15.435 patch update released in 12/1996 (TCP/IP support for NT added via requester changes; no updates to
Btrieve.NLM)
- 6.15.440 patch update released in 03/1997 (more requester updates; no engine change)
- 6.15.445 patch update released in 08/1997 (engine & requester updates)
- 6.15.451 patch update released in 03/1998 (engine updates) [GS Recommended Version!]
Pervasive.SQL (All Releases)
With the release of Pervasive.SQL 7, Pervasive Software started including the SQL engine "in the box"
with the Btrieve engine. As a result, there are many more components in these releases. They also completed a split
between the Btrieve component (BTRIEVE.NLM) and the MicroKernel Database Engine (NWMKDE.NLM). Because of this,
if you find a version of BTRIEVE.NLM that is v7 or above, you must also check the version of the module NWMKDE.NLM.
As mentioned above, you can find this quickly on newer operating systems with the command "MODULES NWMK*".
Pervasive.SQL 7
Depending on the Build number you find on NWMKDE.NLM, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 7.00.200 (FCS) Build 76, Feb 1998
- 7.00.300 (SP1) Build 91, Jun 1998
- 7.00.400 (SP2) Build 104, Sep 1998
- 7.00.500 (SP3) Build 112, Jan 1999
- 7.00.600 (SP4) Build 132, Apr 1999
- 7.00.700 (SP5) Build 152, Sep 1999
- 7.16.810 (SP6) Build 201, Sep 2001
To properly patch Pervasive.SQL 7, you must first patch to SP3, then to SP5, and then to SP6. You cannot go
direct from SP2 to SP5, for example!
Pervasive.SQL 2000/Pervasive.SQL 2000i
Depending on the Build number you find on NWMKDE.NLM, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 7.50 (FCS) Build 146, Jun 1999
- 7.51 (SP1) Build 154, Sep 1999
- 7.80 (SP2) Build 192, Jun 2000 (This was a defective release! Do not use!)
- 7.82 (SP2a) Build 198, Aug 2000
- 7.90 (SP3) Build 230, Mar 2001 (Also called Pervasive.SQL 2000i)
- 7.94 (SP4) Build 251, Dec 2001
To properly patch Pervasive.SQL 2000, your best bet is to download the evaluation software for the current version
and simply install it. It will detect the existing installation and archive the old pieces or it, as needed.
Pervasive.SQL V8
Depending on the Build number you find on NWMKDE.NLM, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 8.00 (FCS) Build 114, Dec 2002
- 8.?? (SP1) Build ???, ??? 2003
The SP1 release for Pervasive.SQL V8 has not yet been announced, but this info has been added here to save space
for it!.
Linux Server Engines
Linux users have it real easy, since the Linux engine is new with Pervasive.SQL 2000, so you already know that
you do not have any older engines than this. However, there is still the question of the exact release, or if you
have Pervasive.SQL V8 or not. Luckily, the following command will query the Package Manager to determine which
release you have:
$ rpm -qa | grep Pervasive
Pervasive.SQL-server-2000.SP3.225.001-RedHat60
If the command does not include a build number, then you have the original release of Pervasive.SQL 2000.
Windows NT Server Engines
There was no Btrieve 5.x or 6.10 for Windows NT Server -- the first release was Btrieve 6.15! The easiest way
to determine the version of the database on a Windows NT Server is to look to the Services applet on the control
panel:
Once you know the main version, you can find out the sub-release by checking the information below.
Btrieve 6.15
With Btrieve 6.15, sub-releases were denoted by numbers. You can locate the exact version by checking the dates
and embedded version information from various files. The core engine module is called NTMKDE.DLL and is a good
place to start. The following list shows the Btrieve 6.15 for Windows NT Server releases in order:
- First release of 6.15 was in 05/1995.
- 6.15.1208 patch update released in 03/1996
- 6.15.430 patch update released in 08/1996
- 6.15.435 patch update released in 11/1996 (TCP/IP support for NT added via requester changes)
- 6.15.440 patch update released in 03/1997 (more requester updates; no engine change)
- 6.15.445 patch update released in 08/1997 (engine & requester updates)
- 6.15.451 patch update released in 03/1998 (engine updates) [GS Recommended Version!]
Pervasive.SQL (All Releases)
With the release of Pervasive.SQL 7, Pervasive Software started including the SQL engine "in the box"
with the Btrieve engine. As a result, there are many more components in these releases. To quickly check your version,
right-click on NTMKDE.DLL and go to the "Version" tab.
Pervasive.SQL 7
Depending on the Build number you find on NTMKDE.DLL, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 7.00.200 (FCS) Build 76, Feb 1998
- 7.00.300 (SP1) Build 91, Jun 1998
- 7.00.400 (SP2) Build 104, Sep 1998
- 7.00.500 (SP3) Build 112, Jan 1999
- 7.00.600 (SP4) Build 132, Apr 1999
- 7.00.700 (SP5) Build 152, Sep 1999
- 7.16.810 (SP6) Build 201, Sep 2001
To properly patch Pervasive.SQL 7, you must first patch to SP3, then to SP5, and then to SP6. You cannot go
direct from SP2 to SP5, for example!
Pervasive.SQL 2000/Pervasive.SQL 2000i
Depending on the Build number you find on NTMKDE.DLL, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 7.50 (FCS) Build 146, Jun 1999
- 7.51 (SP1) Build 154, Sep 1999
- 7.80 (SP2) Build 192, Jun 2000 (This was a defective release! Do not use!)
- 7.82 (SP2a) Build 198, Aug 2000
- 7.90 (SP3) Build 230, Mar 2001 (Also called Pervasive.SQL 2000i)
- 7.94 (SP4) Build 251, Dec 2001
To properly patch Pervasive.SQL 2000, your best bet is to download the evaluation software for the current version
and simply install it. It will detect the existing installation and archive the old pieces or it, as needed.
Pervasive.SQL V8
Depending on the Build number you find on NTMKDE.DLL, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 8.00 (FCS) Build 114, Dec 2002
- 8.?? (SP1) Build ???, ??? 2003
The SP1 release for Pervasive.SQL V8 has not yet been announced, but this info has been added here to save space
for it!.
Btrieve for OS/2
There was a brief time where Pervasive Software supported an OS/2 database engine. The first engines were available
for Btrieve 6.15, and a later version (actually, a predecessor to Pervasive.SQL 7) was available for a short time
and called Btrieve v6.30 for Warp Server. This was in 1996, and as we all know, IBM lost the Battle of the Operating
Systems, so the OS/2 stuff is only a footnote in history now.
Btrieve for DOS
Btrieve for DOS was a very simply database. The earlier versions were compiled in a single file, called BTRIEVE.EXE.
Running this program gave you a header screen with the exact database version. This helps you identify all of the
older Btrieve 4.x and 5.x engines.
For Btrieve 6.15, there were several sub-releases:
- 6.15 First release in 07/1994
- 6.15.1 patch update released in 10/1994
- 6.15.321 patch update released in 03/1995 (also released in SSQL for DOS v3.01)
- 6.15.525 patch update released in 06/1995
- 6.15.925 patch update released in 10/1995
- 6.15.430 patch update released in 03/1997 [GS Recommended Version!]
There is no Pervasive.SQL engine for DOS.
Btrieve for Windows (16-bit)
There were two versions of Btrieve for Windows, supporting 16-bit applications, Btrieve 5.x and Btrieve 6.15.
Btrieve 5.x
The core interface module for Btrieve 5.x was called WBTRCALL.DLL, and some of these versions, usually those
50K+ in size and dated prior to 1993, are the Btrieve 5.x workstation engine.
Btrieve 6.15
Starting with Btrieve 6.15, the new engine module was called WBTR32.EXE. Like with the Windows NT server engines,
you can locate this file and determine which version you have:
- First release of 6.15 in 05/1994 (first product release after the spin-off from Novell!)
- 6.15.1 patch update released in 09/1994 (6.15.1 also released with SSQL for Windows 3.01 in 8/94)
- 6.15.2 patch update released in 11/1994
- 6.15.306 patch update released in 03/1995
- 6.15.525 patch update released in 06/1995
- 6.15.824 patch update released in 08/1995
- 6.15.925 patch update released in 10/1995
- 6.15.430 patch update released in 03/1997
Other files related to 16-bit Btrieve requesters and engines include:
- WBTRCALL.DLL
- WBTRVRES.DLL
- WBTICOMM.DLL
- WBTRLOCL.DLL
There is no 16-bit Windows engine of Pervasive.SQL.
Btrieve for Windows 95/NT (32-bit)
In the 32-bit world, the first database engine was Btrieve 6.15, but newer engines for Pervasive.SQL and above
exist as well!
Btrieve 6.15
Btrieve 6.15's engine is W32MKDE.EXE. Locate this file to determine which version you have:
- First release of 6.15 in 10/1995
- 6.15.430 patch update released in 3/1997
- 6.15.451 patch update NEVER released (engine updates)
Other files related to 32-bit Btrieve requesters and engines include:
- WBTRV32.DLL
- W32MKRC.DLL
- W32BTICM.DLL
- W32NR.DLL
- W16NR.DLL
- WBTRTHNK.DLL
Pervasive.SQL 7
Depending on the Build number you find on W3DBSMGR.EXE, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 7.00.200 (FCS) Build 76, Feb 1998
- 7.00.300 (SP1) Build 91, Jun 1998
- 7.00.400 (SP2) Build 104, Sep 1998
- 7.00.500 (SP3) Build 112, Jan 1999
- 7.00.600 (SP4) Build 132, Apr 1999
- 7.00.700 (SP5) Build 152, Sep 1999
- 7.16.810 (SP6) Build 201, Sep 2001
To properly patch Pervasive.SQL 7, you must first patch to SP3, then to SP5, and then to SP6. You cannot go
direct from SP2 to SP5, for example!
Pervasive.SQL 2000/Pervasive.SQL 2000i
Depending on the Build number you find on W3DBSMGR.EXE, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 7.50 (FCS) Build 146, Jun 1999
- 7.51 (SP1) Build 154, Sep 1999
- 7.80 (SP2) Build 192, Jun 2000 (This was a defective release! Do not use!)
- 7.82 (SP2a) Build 198, Aug 2000
- 7.90 (SP3) Build 230, Mar 2001 (Also called Pervasive.SQL 2000i)
- 7.94 (SP4) Build 251, Dec 2001
To properly patch Pervasive.SQL 2000, your best bet is to download the evaluation software for the current version
and simply install it. It will detect the existing installation and archive the old pieces or it, as needed.
Pervasive.SQL V8
Depending on the Build number you find on W3DBSMGR.EXE, you can relate this directly back to the Pervasive.SQL
Service Pack Level:
- 8.00 (FCS) Build 114, Dec 2002
- 8.?? (SP1) Build ???, ??? 2003
The SP1 release for Pervasive.SQL V8 has not yet been announced, but this info has been added here to save space
for it!.
If you've tried & still can't figure it out, contact Goldstar Software and let
us work with you to help!
|
|
|