home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
larcos.zip
/
READ.ME
< prev
next >
Wrap
Text File
|
1995-03-03
|
12KB
|
283 lines
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=========================================
LARC Version 3.03 Release Notes
=========================================
Overview
========
This file contains last minute notes and suggestions that did not make
it into the final version of the LARC User's Guide. These notes should
be carefully reviewed before you attempt to use LARC.
Installation Procedure
======================
To install LARC, execute the self extracting file LARCDOS.EXE for
for DOS, or LARCOS2.EXE for OS/2.
To install both the OS/2 and DOS version of LARC on the same system,
you will need to create two full and separate installations using
unique directory names.
Example LARC files are provided in the EXAMPLES.ZIP file. It is
recommended that you unzip the example files in a unique directory
and do not mix the example files with the LARC installation files.
While no damage will occur, placing the example files in the LARC
installation directory could make it difficult to maintain or upgrade
LARC in the future.
The default command and configuration files delivered with LARC
assume an installation directory of C:\LARC3. Assuming you install
into C:\LARC3, then LARC will be ready to run as soon as you complete
the installation process.
You need to print the LARC User's Guide file MANUAL.DOC and read
Chapter 2 for additional steps required to complete the
installation procedure.
Be sure to fully read and understand the LICENSE.DOC file before you
use LARC. Also, review the order form file ORDER.FRM for information
on the benefits of registering LARC.
Redistributing LARC
===================
You MAY NOT redistribute LARC for use in any product you sell or support
without the prior written consent of SouthWind Software Incorporated.
You are allowed to distribute the full LARC download program file to
friends, associates, or to a computer bulletin board system (BBS) only
if you distribute the file LRCS303.EXE in it's complete and original
form.
Using LARC with Microsoft Visual C++
====================================
It is possible to integrate LARC into the Microsoft Visual C++ 1.0 or
1.5 IDE. An example LARC.PIF file is included with this release and
will be installed into the LARC executable directory. To integrate
LARC into the MSVC 1.0 or 1.5 tool bar, you simply:
1. Start Microsoft Windows and select Microsoft Visual C++.
2. Select "Options", then "Tool...".
3. Select "Add" and enter the LARC.PIF file name in the file
dialog box that appears. For example, assuming you installed
LARC into C:\LARC3, enter "C:\LARC3\LARC.PIF".
4. Complete the tool setup by making sure that each prompt is
answered:
Command Line: C:\LARC3\LARC.PIF
Menu Text: &LARC
Arguments: C:\LARC3\LARC.CFG
Initial Directory: $PROJDIR
You may need to adjust the path names depending on the name
you provided to the LARC Installation Program. $PROJDIR is used
to set the initial directory to the current MSVC project directory.
This allows you to use LARC from within MSVC to check files from
LARC to the project directory, and to check files back into LARC
from the project directory.
5. Select OK to save the new tool entry. Select "Tool" from the
menu, then select LARC. LARC should appear as a DOS windowed
application.
Using LARC with Borland C++
===========================
LARC has not been integrated into the Borland C++ IDE. However,
it is assumed that Borland provides the ability to add custom tools
to the IDE menu. If so, then it should be possible to integrate LARC
into the Borland IDE as described above for the Microsoft IDE.
New Features
============
This release allows you to define the programs that LARC will use
to manage compressed libraries. By default, LARC is set up to issue
PKZIP and PKUNZIP (provided by PKWARE, Inc.) commands to manage
compressed libraries. You can override these defaults and use other
compression programs. There are four new LARC Configuration File
commands that tell LARC the names and formats of the four basic
compression routines to use.
To add to a compressed library:
SET COMPRESS ADD "PKZIP -k [LIBRARY] [SOURCE]"
To check-out or copy from a compressed library:
SET COMPRESS OUT "PKUNZIP -o [LIBRARY] [FILE] [DEST]"
To delete a file from a compressed library:
SET COMPRESS DELETE "PKZIP -d [LIBRARY] [FILE]"
To verify a file in a compressed library:
SET COMPRESS VERIFY "PKUNZIP -t [LIBRARY] [FILE]"
To facilitate these user defined commands, LARC uses "substitution"
strings to define the LARC-specific components of the command.
These strings are:
[LIBRARY] Insert the full compressed library name
(ex: C:\EXAMPLE\EXAMPLE.ZIP).
[FILE] Insert just the file name that is to be extracted or
delete from the library (ex: EXAMPLE.C)
[SOURCE] Insert the full source file name (ex: A:\TMP\EXAMPLE.C)
[DEST] Insert the full destination path name (ex: A:\TMP\)
The following notes apply to this new feature:
NOTE 1: The LDIR utility requires that compressed libraries be
created using PKZIP.EXE version 2.04g. LDIR will be unable
to list the contents of compressed libraries that were
created using other compression programs.
NOTE 2: When LARC creates a set of release diskettes, it creates a
list file that shows the contents of the diskette(s).
LARC can expand the contents of compressed files that were
created using PKZIP.EXE version 2.04g. LARC can not
expand the contents of compressed files created using a
different compression program.
Neither of these exceptions should seriously impact your ability
to incorporate your favorite compression utility with LARC.
Revision History Feature
========================
A new revision history management feature has been added. Previously,
LARC only required that you include the embedded control information.
For example, a C file might have included the following embedded control
information:
//
// LARC_S "Library Name Goes Here"
// LARC_D "File Description Goes Here"
// LARC_V "102"
//
// Revision History:
// kbg 03/03/95 100 - Created.
// kbg 03/03/95 101 - Fixed some bugs. This example
// also demonstrates a multi-line
// history comment!
// kbg 03/03/95 102 - Added a new feature.
//
This release of LARC adds new embedded control tokens called the
revision history tokens. These tokens can be define in the LARC.CFG
file using the "SET REVISION" statement and are defaulted to
LARC_REV_ON and LARC_REV_OFF. Here is how the same example C file
would appear using the revision history option:
//
// LARC_S "Library Name Goes Here"
// LARC_D "File Description Goes Here"
// LARC_V "101"
//
// Revision History:
// LARC_REV_ON
// kbg 03/03/95 100 - Created.
// kbg 03/03/95 101 - Fixed some bugs. This example
// also demonstrates a multi-line
// history comment!
// kbg 03/03/95 102 - Added a new feature.
// LARC_REV_OFF
//
The revision history option serves achieves the following:
1. It forces the revision history lines to a uniform format as
shown in the examples. You must start the first revision
history line with "iii mm/dd/yy vvv". iii = user initials,
mm/dd/yy = the edit date and vvv = the edit version.
2. The revision history edit version number will be checked to
ensure that it matches the formal LARC_V edit version number.
This reduces possible confussion created whenever the edit
version number didn't match the LARC_V number.
3. The revision history lines will be written into a Revision
History file. This ASCII file can be used to get a quick
read on all changes that have been made since the last build
of the system. The Revision History file will be created with
a REV extension in the directory specified by the LARC.CFG
"SET SYSTEM DATAFILES" statement.
Using the example shown above, the resulting Revision History
file would appear as follows:
*** Release 3.02h(T) built 01-23-95 at 21:02:30 by KBG ***
EXAMPLE.C kbg 03/03/95 100 - Created.
EXAMPLE.C kbg 03/03/95 101 - Fixed some bugs. This example
EXAMPLE.C also demonstrates a multi-line
EXAMPLE.C history comment!
EXAMPLE.C kbg 03/03/95 102 - Added a new feature.
*** Release 3.03 (F) built 01-25-95 at 21:53:08 by KBG ***
New Display Function Keys
=========================
Two new special function keys have been added. These keys are
supported when displaying library files.
F3: This key toggles the display sort order. By default, the
files are displayed in ascending file name order. Press
the F3 key once and the files will be sorted in ascending
file extension order (i.e. grouped by extension). Press
F3 again and the files will be sorted in ascending date
order.
F4: Pressing this key expands the file display to include (or
hide) the file date and time stamp. This option should be
used when displaying files in date/time order.
New "T" Release Build Type
==========================
A new "T" build type for test builds has been added. "T" builds
function exactly like "F" builds, except they do not automaticaly
execute the LARC Archive Command file (LARCARC.BAT).
Known Software Problems
=======================
The OS/2 version does not provide support for an OS/2-specific
version of PKZIP or PKUNZIP. PKWARE is in the process of providing an
OS/2 version of PKZIP/PKUNZIP that uses the 2.04 compression software
used in the DOS version. This would make the compressed file format
compatible between both DOS and OS/2. Support for the OS/2 version of
PKZIP/PKUNZIP will be provided with that version. Meanwhile, the DOS
versions should be used or you can use alternate OS/2 compression
software as described previously.
Reporting Problems or Recommending Enhancements
===============================================
Refer to the Information section of the file LARC User's Guide for
instructions for reporting any problems you encounter with LARC.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
LARC is a trademark of SouthWind Software Incorporated.
MS-DOS is a registered trademark of Microsoft Corporation.
Windows is a trademark of Microsoft Corporation.
OS/2 is a registered trademark of International Business Machines, Incorporated.
All other product names mentioned in this document may be trademarks
or registered trademarks of their respective companies and are
hereby acknowledged.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Copyright (c) 1995 by SouthWind Software Incorporated
All rights reserved.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=