Contents of the READ.ME file
Every Program Needs a Read.me file. This is the Read.me for BLINKER
This demonstration is provided for information only, without any warranties
or guarantees of any kind. Blink, Inc. assumes absolutely no liability for
its content or subsequent use. Blink, Inc. reserves the right to change
or modify the commercial product without obligation to anyone. PLEASE NOTE
THAT THE ONLY C & ASM LIBRARY WHICH CAN BE OVERLAID IN THIS DEMONSTRATION
VERSION IS EXTEND.LIB. WE ARE UNABLE TO PROVIDE TECHNICAL SUPPORT ON THIS
This is a functional demonstration copy of BLINKER. You may use it to
dynamically link your own programs. There is a limitation placed into
the demo. The executable file you create will only run for 5 minutes.
We feel that this will be ample time for you to test the abilities of
BLINKER. After the expiration of 5 minutes, your program will cease to
run and will exit to DOS. This ability to create limited demonstration
versions of your application is one of the features of BLINKER that will
be available to registered users. This function has been disabled in
the demo for obvious reasons.
Please note - because this is a demonstration program and generates
applications which are restricted to five minutes of execution,
the error handler for the application will be called once the 5
minutes have expired. Since NO more procedures or functions may be
executed the error handler should NOT attempt to call any other
Clipper functions or overlaid functions or the program will go into
an endless loop.
THIS IS A LIMITATION OF THE DEMONSTRATION VERSION ONLY !!
You may run your program as many times as you like, however it will only
operate for 5 minutes at a time. We highly recommend that you do not
use the demo.exe program on live data. Please use dummy data or be sure
you have backed up your data before running the demo program. We do not
anticipate any problems with lost or corrupted data files, but just by
the fact that your program may hit the 5 minute limitation and fail at a
crucial time would indicate that proper data back up would be prudent.
BLINK, Inc. will not be liable in any way for loss of or damage to your
There are other features in this demo which have not been activated.
One of the reasons for this is that we are unable to provide technical
support for a demonstration copy. The primary feature that has been
disabled is the ability to overlay C & Assembler functions other than
EXTEND.LIB. The very nature of overlaying these types of functions is
complicated. We have however provided you with the abilty to dynamically
overlay your EXTEND.LIB. This should give you a substantial saving on
memory which will demonstrate the power of BLINKER and the tremendous
technological breakthrough which BLINKER represents.
A new function which was added after the documentation was prepared is
BLIDISFRG(). This function, "BLINKER DISPLAY FRAGMENTATION" will show
you graphically what your memory looks like. To test the efficiency of
the BLINKER MEMORY PACK command or BLIMEMPAK() function, use BLIDISFRG()
to display a memory map. Then run a program which fragments memory (we
have provided a small file called BLIFRG.PRG which should sufficiently
show the effects). Then call BLIDISFRG again to see how badly it is
fragmented. Call BLIMEMPAK() to de-fragment the memory. If you then
call the BLIDISFRG() once again you will clearly see the results. Now
go tell all your friends!
The graphic image you will see generated by BLIDISPRG() deserves a little
explanation. There are 4 different characters used to represent blocks of
memory. They are ,,*,o The first two represent contiguous blocks of
USED memory. The block could be any size up to and including 512 bytes.
This means that a "marked block" could only be 10 bytes or it could be 512
bytes. The second two symbols represent free blocks. The same size
criteria apply. The reason we used 4 different characters instead of two
is so that you could see where contiguous blocks start and end, and see
how big each contiguous area is.
To overlay EXTEND.LIB, simply change the line LIBRARY EXTEND, in your
.lnk file to read ALLOCATE EXTEND, then move that command from
the root module to a place between the beginarea and endarea statements.
( see commands marked with ** )
Old Link file New Blinker Link File
Output junk.exe Output junk.exe
file junk file junk
library c:\clipper\clipper library c:\clipper\clipper
library c:\clipper\extend ** beginarea
beginarea section into junk
section into junk
file junk1 file junk1
file junk2 file junk2
file junk3 file junk3
file junk4 file junk4
endarea allocate c:\clipper\extend **
NOTE: BLINKER searches files/libs in the following order:
Occasionally you may get "UNRESOLVED EXTERNALS" because some
library indexes are incomplete (not our fault ). The solution
to this dilemma is to change the ALLOCATE or LIBRARY command to a
SEARCH command on the offending library. Please see section 3.19
of the manual, the SEARCH command, for a more complete explanation
of the reasons for this.
Remaining items not enabled
See Manual Section 6.6 BLINKER ENVIRONMENT OVERRIDE
See Manual Section 6.6 BLINKER ENVIRONMENT NAME
See Manual Section 6.12 BLINKER MESSAGE WINK
BLINKER environment variable for /OO and /DH.
Use of PATH, OBJ and LIB environment variables to find files
not in the current directory. If the OBJs and LIBs are not in the
current directory, you must explicitly declare the path to
For ordering information see ORDER.DOC
BLINKER - copyright (c) 1990 BLINK, Inc. All Rights Reserved