Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : MAKELINK.ZIP
Filename : MANUAL.DOC

Output of file : MANUAL.DOC contained in archive : MAKELINK.ZIP


Don't think about your link.
Don't forsake your make.



The following 3 files are included in MAKELINK Version 1.0

MAKELINK.EXE Link and Make file creation program.

ORDER.DOC Registration information and order form.
MANUAL.DOC Reference manual for MAKELINK.


The following features are in MAKELINK Version 1.0.

1. Creates a .MAK file to be used with the Make program
supplied with Clipper.

2. Creates a .LNK file using the TREE.DOC file from
SNAP! MAKELINK when determine which overlay level
the modules of a program belong in, and create the
.LNK file to build internal overlays for PLINK86.

3. Creates a .BAT file to compile and link your program.



A. What is MAKELINK ? . . . . . . . . . . . . . . . . . 4
B. How does MAKELINK work ? . . . . . . . . . . . . . . 5
C. How do you use MAKELINK ?. . . . . . . . . . . . . . 6
D. General MAKELINK information . . . . . . . . . . . . 7

A. Technical Support . . . . . . . . . . . . . . . . . 8
C. Registration Information . . . . . . . . . . . . . . 8
D. Software License . . . . . . . . . . . . . . . . . . 9



MAKELINK was created because I got tired of looking at
tree chart and flowcharts and trying to figure out what
procedure called what in order to make overlay files. Since
everything I write gets documented by SNAP!, I decided to write
a utility that would read the tree chart from SNAP! and creates
my overlay files for me. Thus was the beginning of MAKELINK

Since creating overlay structures is something that most
people don't do every day, I thought a utility would save
the average programmer some 'flipping through the manual' time.
This is really designed for the programmer that sometimes runs
into a situation where a little extra free memory would come in
helpful. If you are the local expert on overlays, you can
probably do a better job yourself; however, for the other
95 % of us, this may be useful.

In order to use this, you must use SNAP! to get a tree
diagram (kind of like a flow chart) of your program. For
those of you who aren't already using SNAP!, what's your
problem? Seriously, you will gain many documentation benefits
by using SNAP! and, if you register your copy of MAKELINK,
I will send you the latest version of SNAP! with the latest
version of MAKELINK.



What MAKELINK does is read a tree chart of your application
created by SNAP! From this tree chart, MAKELINK can determine
which modules call other modules, and can place each module
in its correct overlay area. By creating overlay files,
your system will swap modules in and out of memory as they
are needed. (For more overlay information, please read your
Clipper manual, as Nantucket has a much higher documentation

When MAKELINK determines where everything belongs, it
will create three files. The files are a .MAK file, a .LNK
file, and a batch file to compile and link you application.
The three files will be created in whatever subdirectory
you desire, and with whatever name you want. I STRONGLY
suggest that if you have existing .LNK and .MAK files that
you save these files somewhere. I have tested MAKELINK on
several of my own systems; however, I can't guarantee you
that something might not go wrong.

The .MAK file will run when you use MAKE, supplied
with Clipper. The link file will run with the PLINK86
program supplied with Clipper '87. As far as I have seen,
MAKELINK is a rather safe program; however, if you run
across a bug, or a problem with older versions of
software, please let me know. If you can send me a copy
of the TREE.DOC file created by SNAP!, and a description
of what heppened, I will try my best to correct the bug.



In order to use MAKELINK, you must first run SNAP! on
your application. If you don't have SNAP!, either get a copy
from your local bulletin board, or I will send you one when you
register. You must create the tree diagram, and answer yes to
the following questions in SNAP!

Create tree diagram ? Y
Include procedures ? Y
Include functions ? Y
Include format files ? Y
Include report forms ? Y

Answering yes to any of the other questions concerning
the tree diagram will not affect MAKELINK.

After SNAP! is done, run MAKELINK by having MAKELINK.EXE
somewhere in your path and typing MAKELINK. MAKELINK will
ask you for the directory and name of the tree file created
by SNAP!, TREE.DOC, if you accepted the defaults. MAKELINK
will then ask you for the directory containing your CLIPPER.LIB,
EXTEND.LIB, and OVERlAY.LIB. The next three names are for the
directory and name of the .MAK, .LNK, and batch file to be
used to compile your application. These are the new files
that MAKELINK will create, or overwrite, if they already

MAKELINK will then create the files for you. If you
run across a problem, the first thing to check is if you
entered correct subdirectory names. If you encounter a
mysterious problem, please send me the conditions and the
error message by mail or Compuserve.

MAKELINK will create a file named MAKELINK.CFG in the
subdirectory that MAKELINK has been run from. This file
will save the name of the directories and files that you
used when running MAKELINK.



MAKELINK was creatd using FORCE. It is the first serious
program I have developed in FORCE, and I know it has quite a
bit that can be added to it. Registered users of MAKELINK
will receive updates as I add more features to MAKELINK.

Additional features that I am adding to Version 1.1 are:

* Ability to add in as many additional libraries as you
desire. (Currently you are limited to CLIPPER.LIB,

* Ability to link in other .OBJ files. (For those of you
who have custom routines written in C or assembler)

* And, if I can figure a way to effective way to do it,
eliminate the need to run SNAP! before hand, and have
MAKELINK read your code by itself.

If you, the user, have any additional changes you would
like to see made, please let me know. Shareware software
is only as good as the user feedback.



If you have any further questions or comments about MAKELINK,
please contact:

Mail: Scott Lilly
2448 W. Catalpa
Third Floor
Chicago, IL 60625-275

Compuserve ID: 71160,3606


| |
| |
| If you find MAKELINK fast, easy, and convenient to use, |
| a registration of $25 would be appreciated. |
| |
| Please state the current version number of the software |
| you are presently using. Send check or money order to: |
| |
| Scott Lilly |
| 2448 W. Catalpa |
| Third Floor |
| Chicago, IL 60625-2275 |


(The legal stuff)

MAKELINK Copyright 1990 Scott Lilly All Rights Reserved

You are free to use, copy and distribute MAKELINK for

No fee is charged for use, copying or distribution.

It is not modified in any way.

Clubs and user groups may charge a nominal fee not to exceed
($10) for expenses and handling while distributing MAKELINK.

Site licenses and commercial licenses for MAKELINK are
available. Consult the file ORDER.DOC for more information,
or contact me for more information.

I, Scott Lilly, hereby disclaim all warranties relating
to this software, whether express or implied, including without
limitation any implied warranties of merchantability or fitness
for a particular purpose. I will not be liable for any
special, incidental, consequential, indirect or similar damages
due to loss of data or any other reason, even if I or an
agent of mine has been advised of the possibility of such
damages. In no event shall my liability for any damages
ever exceed the price paid for the license to use software,
regardless of the form of the claim. The person using the
software bears all risk as to the quality and performance of the


  3 Responses to “Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : MAKELINK.ZIP
Filename : MANUAL.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: