[<<Previous Entry]
[^^Up^^]
[Next Entry>>]
[Menu]
[About The Guide]
BLINKER EXECUTABLE CLIPPER (Clipper)
------------------------------------------------------------------------------
Purpose : Specify default CLIPPER environment settings
Syntax : BLINKER EXECUTABLE CLIPPER <environment string>
Example : BLINKER EXECUTABLE CLIPPER F35;
This command is used to burn default values for the Clipper runtime
environment variables into the executable file.
Those settings set using the BLINKER EXECUTABLE CLIPPER command take
precedence over those set with the SET CLIPPER command. Parameters not
specified with the BLINKER EXECUTABLE CLIPPER command will retain values
originally assigned by the SET CLIPPER command. However, if you want
the values in the SET CLIPPER command to take precedence, use the
command BLINKER ENVIRONMENT OVERRIDE.
Note for Clipper 5.01
The maximum string length that can be burned into a 5.01 application is
128 bytes, and Blinker will ignore all but the LAST environment burn-in
command encountered, so all parameters that are to be burned in should
be specified in a single BLINKER EXECUTABLE CLIPPER command.
PLEASE NOTE THAT THIS AND OTHER BLINKER COMMANDS TAKE EFFECT ONLY WHEN A
FULL LINK IS EXECUTED.
The burned-in environment values are not returned by the Clipper
functions GETE() / GETENV().
The Clipper runtime parameters listed here are applicable to Clipper
5.01. Check the latest Clipper documentation for a complete list of
these parameters, correct syntax and default values.
E:nnnn Expanded Memory (kb)
F:nnn Number of files
X:nn eXclude memory
BADCACHE protect the EMS pageframe
CGACURS disable EGA cursor
DYNF:nn number of handles for dynamic
paging
NOIDLE disable background garbage
collection
SWAPK:nnnn size of disk swap file
SWAPPATH:'path' path for swap file
TEMPPATH:'path' path for temporary files
Clipper 5.01 environment settings can always be overridden (regardless
of the BLINKER ENVIRONMENT OVERRIDE setting) on the application command
line, using the command line switch '//' as in:
MYAPP //SWAPPATH:D:\;
which would cause Clipper to create the VMM swapfile in the root of
drive D.
There is usually no reason to disable expanded memory support (E0) for
Clipper 5.01 applications.
Note for Clipper Summer'87
The Clipper runtime settings are detailed in Chapter 9 - The Runtime
Environment - of the Clipper Summer '87 manual.
They consist of 6 values:
Ennn Expanded memory (kb)
Fnnn Number of open files
Rnnn Run command / index memory (kb)
Sn Snow indicator
Vnnn Variable table area (kb)
Xnnn eXclude memory (kb)
For example, to ensure that 41 files are available to Clipper and that
100kb will be available to run external commands, use the following
command:
BLINKER EXECUTABLE CLIPPER F41;R100
Remember that for the application to be able to use 41 file handles,
corresponding values have to be set in the CONFIG.SYS, and, if
necessary, in the appropriate network configuration.
At runtime, using the above burned-in settings, the 'F' and 'R'
parameters in the CLIPPER environment will be ignored, but all the other
parameters will be used in the normal way. It should be noted that the
CLIPPER environment variable should be used to disable expanded memory
usage by Clipper Summer '87. If this is not done index files may be
corrupted when Clipper Summer '87 uses this memory in conjunction with
certain expanded memory drivers, or RUN errors may occur. To disable
Clipper Summer '87 usage of expanded memory set the CLIPPER environment
variable 'E' to 0 as follows (this may be used in conjunction with the
other settings for number of files etc.):
SET CLIPPER=E0
Alternatively, the E0 may be burned into the application using:
BLINKER EXECUTABLE CLIPPER E0
See Also:
BLINKER ENVIRONMENT CLIPPER
BLINKER ENVIRONMENT OVERRIDE
This page created by ng2html v1.05, the Norton guide to HTML conversion utility.
Written by Dave Pearson