Answers Database


Foundation F1.x: LMACS, Btrieve and Library Access errors


Record #3395

Product Family: Software

Product Line: Aldec

Product Part: Foundation Project Manager

Problem Title:
Foundation F1.x: LMACS, Btrieve and Library Access errors


Problem Description:
Urgency: Standard

General Description:

You may encounter various LMACS errors when using the
Foundation software. Btrieve errors may also be issued with
these errors.

Most often, these errors are a result of conflicts associated
with the Btrieve software. Btrieve is a Windows database
software program which is used by the Foundation Library
Manager. Btrieve may also be used by other Windows software,
which are unrelated to the Foundation software. If this other
software uses a different version of the Btrieve software than
the Foundation software uses, conflicts may exist, and LMACS
or Btrieve errors may be issued by Foundation. Often, the
errors involve Foundation not being able to locate the proper
library files.




Solution 1:

Foundation 1.5i -- LMACS error -97

For LMACS error -97, a suitable workaround is to reinstall the Foundation
software. In most cases this solves the problem.



Solution 2:

It is possible that there is an incompatible version of Btrieve
being loaded by Windows. An easy way to attempt to resolve
this problem is to copy the Btrieve files directly from the
Foundation CDROM into the Windows directory. It is important
that the system is only able to see one version of the btrieve files
listed below.

F1.3
====
From the Foundation Design Entry Tools CD, go to the
ACTIVE\WINDOWS directory.
Copy the following files into the local Windows directory:
BTI.INI
WBT32RES.DLL
WBTR32.EXE
WBTRCALL.DLL
WBTRLOCL.DLL
WBTRVRES.DLL

F1.4
====
From the Foundation Design Entry Tools CDROM, go to the
FNDTN\ACTIVE\BTRIEVE directory. Copy the file BTI.INI to the
local windows or winnt directory and copy all of the other files in
that directory into the local Windows\system or winnt\system32
directory:
BTI.INI
WBTRV32.EXE
WBTRCALL.DLL
WBTRVRES.DLL
WBTRTHNK.DLL
W32MKRC.DLL
W32MKDE.EXE
NWLOCALE.DLL

F1.5
====
Because the files on the F1.5x	CD have been compressed,
it is not possible to copy the required files directly from the CD.
There are two easy ways to ensure that the correct btrieve files
are on a system:
1) Copy the files from the F1.4 CD.  The files names and versions
did not change between F1.4 and F1.5.
2) Download the file btrieve_.zip from the web page:
ftp://ftp.xilinx.com/pub/swhelp/foundationInternet Link and copy the files into to local windows
and windows\system directory according to the F1.4 instructions.



Solution 3:

Check your WINDOWS directory for any of the following files:
F1.3:
=====
Wbt32res.dll
Wbtrcall.dll
Wbtrlocl.dll
Wbtrvres.dll
Wbtr32.exe

The Foundation v1.3 install program writes the above files
to the c:\windows directory by default.

F1.4, F1.5
=========
WBTRV32.EXE
WBTRCALL.DLL
WBTRVRES.DLL
WBTRTHNK.DLL
W32MKRC.DLL
W32MKDE.EXE
NWLOCALE.DLL

The Foundation v1.4 and later install program writes the above files
to the c:\windows\system directory by default.

Search for the same .dll and/or .exe files in the in other directories
pointed to by the PATH variable. If any of these files are found in
another location there will be a possible conflict between the different
versions of BTRIEVE on your PC. Remove these files from all other
locations pointed to by the PATH variable.



Solution 4:

Libraries which are shared by multiple users over a network
must have the Read Only attribute set, or the entire library
directory must be protected with the Read Only attribute.

If the Read-Only attribute is not set, one user will be able
to access the libraries. Any other users who attempt to use
The libraries at the same time will see the library access error.

In some cases, Novell networks have been found to delete
the wbtrcall.dll when the network sw is invoked if the file is
note set as Read-Only



Solution 5:

This can happen if the user has an IOMEGA ZIP drive and is
using the IOMEGA image icon, which is simply an icon for usage
of the ZIP drive. The user should terminate the icon program by right
clicking on the toolbar, and selecting task manager->process and
then terminating the image icon process.




End of Record #3395 - Last Modified: 07/23/99 10:02

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!