home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
C/C++ User's Journal & Wi…eveloper's Journal Tools
/
C-C__Users_Journal_and_Windows_Developers_Journal_Tools_1997.iso
/
prolog
/
readme.txt
< prev
next >
Wrap
Text File
|
1996-09-27
|
8KB
|
214 lines
WIN-PROLOG Version 3.300 - 27 Sep 96
====================================
Welcome to version 3.300 of WIN-PROLOG! Please read the information
below about how to install this software on your system:
If you are installing WIN-PROLOG for the first time, simply place the
master disk into a floppy disk drive, and run the INSTALL program. This
will ask you for various details, before copying the WIN-PROLOG system
to your choice of hard disk directory. INSTALL is a Windows program, so
you will need Windows to be installed before you can install WIN-PROLOG.
Assuming Windows is correctly installed on your system, log on to the
floppy drive you want to use by typing, for example:
C> A: <return>
and then run the install program with the command:
A> win install.exe <return>
Alternately if you are already running windows select the 'File\Run...'
menu option in the Program Manager and enter the following command in
the 'Command Line:' edit box:
A:\INSTALL.EXE
and then click on the 'Ok' button.
PLEASE NOTE!
------------
Due to the behaviour of the Microsoft Windows command line, where .COM
files on the path take precedence over .EXE files (even if the .EXE file
resides in the current directory) when no extension is given, you should
include the extension for the INSTALL.EXE program (as shown in the above
example).
Integrity Checking
------------------
Your new WIN-PROLOG system includes a stand-alone DOS program which can
be used to check your disk for corruption. Normally, you will not need
to use this program, but if you have problems during installation, or
suspect that your disks are damaged in some way, you can use the
checking program to create a print-out which will help LPA to identify
the problem. This is:
CHK386.COM
----------
Creates a screen based report of file date, size and checksum data,
which can be redirected to a file or to the printer for diagnostic
support by LPA. Usage is:
CHK386 [drive]
where:
drive is the name of a drive or directory
The output can be redirected to a disk file, for example:
CHKDSK A: > C:\LPA.TXT
creates a file called LPA.TXT on the C: drive, with a report on all the
files currently on the disk in the A: drive. Further information about
this feature can be obtained by contacting LPA at the addresses shown at
the bottom of this README.TXT file:
File Compression
----------------
A powerful LZSS compression algorithm is built into LPA-PROLOG, and is
used in the stuff/3 and fluff/3 predicates. Because many of the files on
the installation disks are compressed using these, stand-alone
compression utilities have been included in case manual file
installation is needed. The LZSS algorithm has also been incorporated
into four stand-alone programs which can be executed directly from the
DOS command line. These are:
STF386.COM
----------
Stuffs (compresses) a single named input file into a single named output
file, using a default of 11/5 bit LZSS which is configurable on the
command line. Usage is:
STF386 [/n] input output
where:
n is a single digit in the range 0-3 (see stuff/3)
input is a single (raw) input file name
output is a single (compressed) output file name
Files stuffed with either STF386.COM or the stuff/3 predicate can be
fluffed with either FLF386.COM or the fluff/3 predicate.
FLF386.COM
----------
Fluffs (decompresses) a single named input file into a single named
output file, using whichever type of LZSS compression was used to stuff
the file (see above). Usage is:
FLF386 input output
where:
input is a single (compressed) input file name
output is a single (raw) output file name
Files stuffed with either STF386.COM or the stuff/3 predicate can be
fluffed with either FLF386.COM or the fluff/3 predicate.
STS386.COM
----------
Stuffs (compresses) all files matching a given file pattern into a
single named output archive, using a default of 11/5 bit LZSS which is
configurable on the command line. Usage is:
STS386 [/n] pattern archive
where:
n is a single digit in the range 0-3 (see stuff/3)
pattern is any DOS file specification, including wildcards
archive is a single (compressed) archive file name
Files stuffed into an archive with STS386.COM can be retreived and
fluffed with FLS386.COM, but not directly with the fluff/3 predicate.
FLS386.COM
----------
Fluffs (decompresses) all files stored in the single named input
archive, using whichever type of LZSS compression was used to stuff the
file (see above). Usage is:
FLS386 archive
where:
archive is a single (compressed) archive file name
Files stuffed into an archive with STS386.COM can be retreived and
fluffed with FLS386.COM, but not directly with the fluff/3 predicate.
Documentation
========================================================================
The documentation provided with WIN-PROLOG consists of:
User Guide Describes the process of installing
WIN-PROLOG and its various toolkits.
Also described are:
The environment menu options.
Creating stand-alone applications.
The Flex Toolkit.
The Prolog++ Toolkit.
Update Notes Highlights what's new in WIN-PROLOG and
Gives a history of what has changed since
WIN-PROLOG Version 2.6.
Technical Reference Describes the predicates in LPA-PROLOG.
Programming Guide Describes the general programming
aspects of LPA-PROLOG.
LPA-PROLOG for Windows Describes the Windows specific
Programming Guide programming aspects of WIN-PROLOG.
Interfaces and Plug-ins Describes the Intelligence Server external
language interfaces and the various plug-ins
that may be installed with your WIN-PROLOG
system, including:
The DDE interface.
The Dialog Editor.
The Call Graph.
The Cross-Referencer.
Bugs, Problems and Errors
========================================================================
----- Start of List -----
There is a known problem running WIN-PROLOG version 3.3 under Windows NT
The symptoms are that editor control windows run out of space. This means
that when files over a certain size are loaded into a WIN-PROLOG environment
source code window. Only part of the text of the file gets loaded in.
For the time being files must be edited using an external editor and then
loaded into WIN-PROLOG memory using the predicate ensure_loaded/1.
The problem is associated with the memory allocation for the editor control
windows. The next version of WIN-PROLOG, specially designed for the WIN32s
memory model, does not have this problem and in fact should allow edit
controls to be extendable beyond 30k. We will announce the release of this
product as soon as appropriate.
----- End of List -----
Please report any suspected bugs that do not appear in the above list to
LPA at:
Logic Programming Associates Ltd
Studio 4
Royal Victoria Patriotic Building
Trinity Road
London
SW18 3SX
England
Phone: 0181 871 2016 (Int. +44 181 871 2016)
Fax: 0181 874 0449 (Int. +44 181 874 0449)
Email: lpa@cix.compulink.co.uk General Enquiries
Email: djw@cix.compulink.co.uk Technical Support
WWW: http://www.lpa.co.uk Web Home Page