|
| |
Knowledgebase
>>ITEM : R00010
>>DATE: 11/10/98
>>TYPE: Bug
>>TITLE: Btrieve MicroKernel and Blinker
Extended Mode Incompatibility
>>PRODUCT(S):
RaSQL/B for Clipper (all versions)
>>PLATFORMS(S):
Btrieve 6.1x Microkernel Engine for DOS
Clipper 5.2, 5.3
>>SUMMARY:
Incompatibilty between Blinker Extended
(protected) mode programs and Btrieve
Microkernel engine causes GPF when ending
program and/or unloading Btrieve.exe.
>>MORE INFORMATION:
This is due to the fact that the Btrieve
MicroKernel Engine and Blinker use
different DPMI Dos Extenders. Btrieve uses
Tenberry's DOS-4G Extender, while Blinker
uses their own Extender. You cannot run
two different DPMI Extenders at the same
time under DOS (nor in a Dos Window).
>>RESOLUTION/FIX:
There is no "fix" for this since it is a
known "feature" of the DPMI specifications.
However, there are several things you can
try:
1) The best solution is to use RTLink or
Blinker real mode with overlays. RaSQL/B is
100% overlayable in real mode.
2) If the Btrieve files are on a NetWare or
Windows NT Server volume, you can try using
Btrieve-for-NetWare or Btrieve-for-NT
Server, respectively. In both these cases
you do not load Btrieve.exe, but a special
requestor instead (Brequest.exe or
Breqnt.exe, respectively). The requestor
programs do not use DPMI services.
3) If you are using Clipper 5.2 (not
applicable to Clipper 5.3), you can try
linking with Exospace 1.0G instead of
Blinker. Exospace 1.0G and Btrieve use
different Dos Extenders. However, they
were both originally developed by the same
company (Rational Systems) and seem to be
more "friendly" to each other. This is the
least desirable solution, however, since
there may be other, unknown issues
involved.
>>SEE ALSO:
>>COPYRIGHT 1998 Communication Horizons
All rights reserved worldwide.
No distribution without specific consent of publisher.
| | |
|
