Click above to get retro games delivered to your door ever month!

 Small FAQ
------------------------------------------------------------------------------
 Q: I have just started using Blinker 5.1 with Clip-4-Win and TopClass
    and my program always GPFs at startup.

 A: Unfortunately, TopClass 3.06 and prior are not able to set up or
    handle CA-Clipper memory variables outside of DGROUP.As a service to out
    customers we are providing a replacement .OBJ file to address this
    issue. Click here to download the file BL5TOPCL.ZIP (8Kb).
------------------------------------------------------------------------------
 Q: I have just started using Blinker 5.1 and am getting 'VM Integrity
    failures with CA-Clipper 5.3a.

 A: When using Blinker 5.1 with CA-Clipper 5.3, you must use the 'B'
    patch version - i.e. CA-Clipper 5.3b, and you must also remove all
    references to 5.3 'fix' OBJs (such as DBGAPI.OBJ) from your link script.
------------------------------------------------------------------------------
 Q: I have just started using Blinker 5.1 and am getting a '5.1 requires
    a later version of BLX?????.LIB.

 A: You have the path to the protected mode libraries from a previous
    version of Blinker in your LIB environment variable, or the path is
    hard coded in your link script. Make sure that your LIB path points to
    the Blinker 5.1 supplied libraries, and that your link scripts have
    been modified similarly.
------------------------------------------------------------------------------
 Q: I have just started using Windows 95 and the Blinker SwpRunCmd()
    function appears to keep failing.

 A: The swapper works fine under Windows 95 provided the correct command
    processor is set in the COMSPEC environment variable. As a test try
    swapping to the DOS command line by running COMMAND.COM instead of the
    child program. This test will usually fail as well. In your
    AUTOEXEC.BAT file you should ensure COMSPEC is set to the correct
    COMMAND.COM. For example: SET COMSPEC= C:\WIN95\COMMAND.COM, instead
    of SET COMSPEC=COMMAND.COM.
------------------------------------------------------------------------------
 Q: I have just installed my Blinker and keep getting Error 1109 `Unable
    to open file' on the Blinker libraries. I have checked the LIB
    ubdirectory and there are no library files there.

 A: Occasionally the Blinker library creation utility is not able to
    complete successfully at installation, often due to lack of disk space.
    Change to the Blinker root directory, where you should see BLIBLD.EXE.
    Run this .EXE and the libraries should be created successfully.
------------------------------------------------------------------------------
 Q: I'm getting GPFs on some , but not all DBCOMMIT() and DBUNLOCK()
    calls in my DOS extended CA-Clipper programs. BLIGPF consistently
    reports __BMOVE as the offending function, which is called by a module
    within the DBFMDX database driver.

 A: The problem that you are describing was reported to CA in December
    of 1995. They said that the problem seems to be in the DBFMDX RDD and
    that it exists in versions 5.2e and 5.3 of CA-Clipper. CA development
    is apparently working on the problem.
------------------------------------------------------------------------------
    "There is not a foolproof workaround but on certain files, adding a
    blank deleted record at the beginning of the file prevents the record
    that you are updating from being the first in the index."

    - George A. Oldridge-Compuserve, Clipper Forum/Linkers,
      8/27/96  #581703-Blinker & __BMOVE GPFs