home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Windoware
/
WINDOWARE_1_6.iso
/
calendar
/
alm095
/
almsetup.doc
< prev
next >
Wrap
Text File
|
1990-07-17
|
6KB
|
120 lines
Almanac for Windows
Version 0.95
INSTALLATION
------------
The program ALMSETUP.EXE is provided to allow easily installation and
initial configuration of Almanac in your Windows system. If you are a
registered user, and are installing Almanac into a NEW windows system
(like Windows 3.0, you should run ALMSETUP twice; once to install and
register, and a second time with the '/C' option (see item #1.C. below)
just to convert any existing support files. Sorry for the inconvenience,
I will update the program to do the convert AFTER registration on the
next release.
WINDOWS 2.x USERS: You must change the current Windows directory to
the directory containing the setup files before
running ALMSETUP.
WINDOW 3.0 USERS: Simply select 'File' from the Program Manager
and then select 'Run...'. Enter the command line
for ALMSETUP using the directory the setup files
are located in.
Examples> A:\ALMSETUP or D:\TEMP\ALMSETUP
1. Start ALMSETUP from Windows from within the same directory
as the rest of the Almanac files. If you perform the setup
from a hard disk, files are relocated to other directories
if necessary. If your setup files are on a floppy disk, the
files will be copied (and not removed) from the floppy.
Besides starting ALMSETUP for normal installation, you
may also activate two other features by using the 'Run...'
command from the 'File' menu:
A. Entering 'ALMSETUP C:\mywindir' tells the program
where to find your Windows directory if it is not
WINDOWS or WIN386 or is on a drive higher than 'F:'.
B. Entering 'ALMSETUP /C' will skip the installation
process and go immediately to the support file
conversion phase (available only to registered users).
2. You will be presented with a dialog box allowing selection of
the sub-directories for Almanac's files. To accept the default
installation paths simply select 'Install'. The installation
paths are described in detail below. Select 'Install' after
selecting your desired directories.
3. If ALMSETUP detects a previous Almanac installation and you are
a registered user, you will be provided with an opportunity to
convert any existing support files you may have created (except
the location data base). You will be prompted to select the
disk drive(s) you would like scanned. ALMSETUP will locate all
overlay, auto-load module, and desk files that will require
conversion. You may select any or all of these files for
processing. All current files will be renamed by changing the
'A' in their extensions to a tilde '~' when they are converted
so the old files are still available should they be required.
You should delete these files after determining the new files
work correctly and that you are comfortable with version .95.
4. After installation has completed, ALMSETUP will continue with
options for entering registration information or viewing the
Almanac documentation.
INSTALLATION PATHS
------------------
A suggested directory structure:
----------------
| WINDOWS |
----------------
| ALMANAC.EXE |
----------------
|
----------------
| ALMANAC |
----------------
| ALMANAC.MST |
| ALMLOCN.DAT |
| ALMFONTx.FON |
| ALMANAC.ALM |
| other *.ALMs |
----------------
|
-------------------------------
| |
---------------- ----------------
| ALO | | ALD |
---------------- ----------------
| overlays | | desk files |
| ( *.ALO ) | | ( *.ALD ) |
---------------- ----------------
In the above diagram, ALMANAC.EXE is installed in the main Windows
directory. ALMANAC's system files are contained in the ALMANAC
sub-directory located below. In addition to the location data file
and font files provided with ALMANAC, all auto-load modules (*.ALM)
are maintained in this sub-directory.
Below the ALMANAC sub-directory are the ALO and ALD directories.
These are the initial directories to store calendar overlay files
and where ALMANAC maintains desk data information. You may later
create other overlay and desk sub-directories, if you desire, and
select them in auto-load modules that you create.
You may select directories however you like. The above example is
only a suggested approach. It is not neccessary to place the
directories under your WINDOWS directory, nor do you have to keep the
files separated into different directories.