Dec 212017
 
Blinker update v1.10 to v1.20 from BLINK (you must have Blinker v1.10).
File BLI120.ZIP from The Programmer’s Corner in
Category Dbase Source Code
Blinker update v1.10 to v1.20 from BLINK (you must have Blinker v1.10).
File Name File Size Zip Size Zip Type
3RDPARTY 4346 1090 deflated
BLIUPD.EXE 39013 37244 deflated
READ.ME 4821 2054 deflated

Download File BLI120.ZIP Here

Contents of the READ.ME file



READ.ME Blinker 1.20 Update 90.08.10
------- ------------------- --------

This update from Blinker 1.11 to Blinker 1.20 consists of this file
READ.ME, the EXE file BLIUPD.EXE and 3RDPARTY, a compatibility chart
of 3rd party libraries.

Please change directory to the Blinker directory, copy these files
into the directory and then run BLIUPD by typing BLIUPD at the DOS
prompt.

Please ensure that the BLINKER.EXE present in this directory is
version 1.11, and not any other version.

The program will display a message explaining that a new file
BLI120.EXE will be created in the current directory. This file is the
new Blinker 1.20 with the same serial number as the BLINKER.EXE in
the current directory, and should be renamed or copied over the top
of the old BLINKER.EXE

**************************************************************************
* *
* Overlaying of third party libraries has been GREATLY improved. We *
* would like to hear from developers of libraries which do not appear *
* on the enclosed compatibilty chart in order to include them, and also *
* of any corrections for libraries already listed. *
* *
* The overlaying algorithm has also been greatly improved, resulting in *
* significantly faster .EXEs when the OPSIZE is kept small to make as *
* much memory as possible available to the application. *
* *
**************************************************************************

We now have a BBS operational 24 hours a day 7 days a week which may be
used for technical support and to get the up to date news about Blink
Inc. and Blinker. The number is :

804-355-1111 US Robotics 1200 - 9600 N,8,1

Feel free to log on and join in - this is the best way to keep up to
date with what is going on, to get the latest news on overlayable
libraries etc, and the quickest way to get information about YOUR
libraries onto the list !!

Our address and contact details have also changed recently to :

P.O. Box 7154,
Richmond, VA 23221.

Telephone : 804-353-0137/8
FAX : 804-355-1676

Please note that the free upgrade to version 1.5 which will be Clipper
5.0 compatible is still to come, and will be shipped to all registered
users of Blinker once Clipper 5.0 is finalised. The 1.5 update will
also contain a number of new features yet to be announced.

PLEASE ENSURE YOU HAVE RETURNED YOUR REGISTRATION CARD TO PREVENT ANY
DELAY IN THE SHIPPING OF YOUR UPGRADES AND TO FACILITATE TECHNICAL
SUPPORT. WITH OUR PREVIOUS UPDATE A NUMBER OF DISKS SENT TO THE
INVOICE ADDRESS WERE NOT RECEIVED SO WE ARE NOW ONLY USING THE
REGISTRATION ADDRESS.


Other Enhancements
------------------

Clipper X parameter now supported, ensuring compatibility with
libraries such as D123 which require DOS memory for buffers etc.

OVERLAY OPSIZE may now be set to any size up to the limit of
available memory. Previously values greater than 63 KB caused
strange sizes for BLIOVLSIZ and the OVERLAY OPSIZE was always the
remainder when divided by 64 KB.

Blinker now supports a maximum of 15 external overlays. This fixes
a problem where using more than 5 external overlays, ie 5 SECTION
INTOs, could cause BLINKER to terminate with an internal error.

BLINKER @@ now displays an error message 1105.

FILE / LIBRARY names consisting of digits then alphas then digits are
now accepted, as are file and library names containing :

'-' Hyphen
'&' Ampersand
'!' Exclamation mark
'^' Up arrow
'{' Open brace
'}' Close brace


Stack overflow is now detected properly in 99% of all cases to give
error 1206 - maximum procedure depth exceeded.

The error handler ERRORSYS can now be overlaid in the majority of
applications - the only errors which cannot be passed to the overlaid
ERRORSYS are errors 1201 through 1204 as these are overlay errors
which would prevent ERRORSYS from being loaded. This means that the
demonstration restrictions can now be used with an overlaid ERRORSYS.

LIDATA records are now processed correctly. Previously a
processing problem occasionally resulted in the generated .EXE
file hanging on load.



 December 21, 2017  Add comments

Leave a Reply