Installation & Use
Copyright: All products on this CD-ROM are Copyright 1992..1999
© multisoft Datentechnik GmbH, 82031 Gruenwald/Munich, Germany. All
rights reserved worldwide. No part of this media may be copied or distributed,
transmitted, transcripted, or published in any form or by any means without
the express written permission of multisoft Datentechnik GmbH.
Made in Germany. Printed in Germany.
License: The License Agreement & Warranty is available in
the /cdrom/doc_engl/license.html
or license.doc resp., or /cdrom/doc_germ/lizenz.doc
ASCII files and in the FlagShip printed or on-line manual in chapter
GEN.2. By installing the package you will read this document and acknowledge
that you agree to be bound by its terms and subjects to its conditions.
Trademarks: FlagShip and FS2 Toolbox are trademarks
of multisoft Datentechnik GmbH. Other products named herein may be trademarks
of their respective manufacturers or trademark holders.
Contents of this Installation
Booklet
Contact address
Introduction
Contents of this CD-ROM
Products and Licenses
Installation from this CD-ROM
Deinstallation
Support
Using FlagShip
Additional Infos and Ports
Postal address:
multisoft Datentechnik
GmbH
Postfach 1312
D-82027 Gruenwald/Muenchen
Germany
Delivery address:
multisoft Datentechnik GmbH
Auf der Eierwiese 1
D-82031 Gruenwald/Muenchen
Germany
Telephone:
(++49 - 89) 649 0040
Fax:
(++49 - 89) 641 2974
E-mail:
sales:
sales@fship.com or sales@multisoft.de
support:
support@fship.com or support@multisoft.de
Internet:
Web:
http://www.fship.com
Ftp: ftp://fship.com/pub/multisoft
Call for address of your local distributor.
Introduction
FlagShip is an independent Database Development system, perfectly suited
also to migrate xBase based applications to UNIX. It is a superset of CA/Clipper
5.3 and therefore fully source and data compatible to it, including macros,
code blocks, objects, user defined OOP classes etc.
-
FlagShip produces native executables by means of .prg to .c translation;
but C knowledge is not required.
-
No royalty or licensing for software you create and distribute.
-
Common source code and data for all operating systems (including DOS).
Millions of well trained Xbase (dBASE, Clipper, Fox) programmers exist.
-
A great rapid prototyping language strong enough to build industrial strength
business applications very quickly. An active third party market creating
applications & libraries.
Contents of
this CD-ROM
FlagShip is ported to all standard Unix systems, from PC-Unix to workstations
and mainframes. On this CD-ROM, you will find
-
a free FlagShip test drive (fully working Demo version),
-
a full release of FlagShip (requires licensing), and
-
a full release of FS2 Toolbox for FlagShip (requires licensing)
for the following operating systems (in alphabetical order; additional
systems are available upon request):
-
AT&T Unix SVR4 x86
for Intel x86 based AT&T Unix SVR4 (rel. 4.1 and newer). Produces
statically or dynamically linked executables in ELF format.
-
Data General AViiON
for the DG AViiON DG/UX (rel. 5.4.3.10 and up) operating system. Produces
statically or dynamically linked executables in ELF format.
-
Digital Equipment DEC-Unix 3.x
for DEC Alpha with Digital Unix (OSF1 V3.2-D1) operating system. Produces
statically or dynamically linked executables in ELF format.
-
Digital Equipment DEC-Unix 4.0D
for DEC Alpha with Digital Unix V4.0D operating system. Produces statically
or dynamically linked executables in ELF format.
-
HP UX 9.x
for HP Risc with HP-UX (rel. 9.01 and up) operating system. Produces
statically linked executables in XCOFF format.
-
HP UX 10.x
for HP Risc with HP-UX (rel. 10.01 and up) operating system. Produces
statically or dynamically linked executables in ELF format.
-
HP UX 11.x
for HP Risc with HP-UX (rel. 11.0 and up) operating system on 32bit
or 64bit PA-RISC 1.1 or 2.0 processors. Produces statically or dynamically
linked.
-
IBM AIX 3.2
for IBM Risc 6000 or PowerPC based systems with AIX rel. 3.2.x. Produces
statically linked executables in XCOFF format.
-
IBM AIX 4.x
for IBM Risc 6000 or PowerPC based systems with AIX rel. 4.1, 4.2 and
newer. Produces statically linked executables in XCOFF format.
-
ICL DRS 6000 & Fujitsu
for ICL and Fujitsu Sparc systems with SVR4.2 rel. 7.7.2. Produces
statically or dynamically linked executables in ELF format.
-
Interactive Unix V/386
for x86 based Interactive Unix V/386 rel. 3.2.2 (and newer). Produces
statically linked executables.
-
Linux (a.out format) with kernel release 0.99 to 2.0.30
usable on Linux 1.0 and all newer releases for Intel x86 based processors.
Produces statically linked executables in the Linux binary format called
"aout". Don't use for kernels newer than 2.0.31
-
Linux (ELF format and Libc) with kernel release 1.2.13 up to 2.0.3x
usable with the Linux ELF kernel and Libc (/usr/libc.so.5), e.g. RedHat
4.x, SuSE 5.x, Caldera 1.x distributions. Produces statically or dynamically
linked executables in ELF format.
-
Linux (ELF format and Glibc) with kernel release 2.0.30 and newer
usable with the Linux ELF kernel and Glibc based system (i.e. the /usr/libc.so.6
file is available), i.e RedHat 5.x, SuSE 6.x, Debian 2.x distributions.
Produces statically or dynamically linked executables in ELF format.
-
Linux (ELF format and Glibc-2.1) with kernel release 2.2.x and newer
usable with the Linux ELF kernel and Glibc-2.1 based system (i.e. the
/usr/libc.so.6 file is available and is a link to /lib/libc-2.1.1.so),
i.e RedHat 6.x, SuSE 6.2+ etc. distributions. Produces statically or dynamically
linked executables in ELF format.
-
NCR 6000
for x86 based NCR with SVR4.2 Unix. Produces statically or dynamically
linked executables in ELF format.
-
SCO Unix 3.2.2 trough 3.2.4.2
for x86 based SCO Unix 3.2.2, 3.2.4 or 3.2.5. Produces statically linked
executables in iAPX 386 COFF format.
-
SCO Unix OS-5
for x86 based SCO Unix OS-5 rel. 3.2.5. Produces statically or dynamically
linked executables in ELF format.
-
SCO UnixWare 7
for x86 based SCO UnixWare 7. Produces statically or dynamically linked
executables in ELF format. For older UnixWare systems, use the UnixWare
4 port.
-
SCO Xenix
for x86 based SCO Xenix 2.3.2 and newer. Produces statically linked
executables in Xenix 386 format.
-
Siemens RM 5.42
for Mips 4000 based Siemens RM with Sinix-N (rel. 5.42 and newer).
Produces statically or dynamically linked executables in ELF format.
-
Siemens RM 5.45
for Mips 4000 based Siemens RM with Sinix-N (rel. 5.45 and newer).
Produces statically or dynamically linked executables in ELF format.
-
Siemens MX
for x86 based Siemens MX with Sinix (rel. 5.4 and newer). Produces
statically or dynamically linked executables in ELF format.
-
Sun SPARC Solaris
for SPARC based Sun Solaris (rel. 2.5, usable also on 2.3 and 2.4).
Produces statically or dynamically linked executables in ELF format.
-
Sun Solaris for X86
for Intel x86 based Sun Solaris x86 (rel. 2.5) system. Produces statically
or dynamically linked executables in ELF format.
-
UnixWare 2.x, 4.x (Novell, SCO)
for x86 based UnixWare rel 4.2 and newer. Produces statically or dynamically
linked executables in ELF format.
The system specific release notes for the
above systems are available on this CD-ROM in overview and after the FlagShip installation in
section REL of the on-line manual fsman.
Products and
Licenses
The complete License Agreement in English is available in html format or ascii file
/cdrom/doc_engl/license.doc
(and LICENSE.DOS for MS-DOS). Here in short:
-
FlagShip Pro is intended as the regular license kit for software
developers who will resell their executables, and for large in-house systems,
accessed simultaneously by any number of users. Therefore,
- The application supports an unlimited number of simultaneous processes
or users,
- The developer/licensee may sell the application compiled by FlagShip
Pro as often as he/she likes, since
- No run-times fees or royalties exist.
- Discounted additional licenses for other platforms are available.
Of course, neither the FlagShip compiler, nor cc is required
on the customer's site, but the executable only. You will need to obtain
a license (Activation Key) from your dealer, distributor or from multisoft
Datentechnik GmbH to be able to install and run this full version.
-
The Personal FlagShip is intended as a low cost Starter Kit for
personal, company internal/in-house and software developer use, as well
as the presentation of applications. Personal FlagShip has all the features
of FlagShip Pro, except:
- Personal FlagShip supports the execution of the same application
or allows access to the same shared database by two different users (or
processes) simultaneously.
- Since used "personally" or in-house, executables need to run on the
system where the compiler resides, but are usable also for presentation
purposes.
There are no run-time licenses or other limitations.
You may upgrade to FlagShip Pro at any time. You will need to obtain an
Activation Key to be able to install and run the Personal FlagShip.
-
With the "Free Personal FlagShip", we support the effort of Linux
community for a free software for personal use. It is similar and compatible
to the licensed "Personal FlagShip", but this free version may be used
strictly for personal, non-commercial purposes or education. You cannot
use it for company purposes where the commercial Personal/Pro license is
required. You may not sell the produced executable(s) but may pass it to
anyone for free (see para 5.c of the FlagShip License Agreement for details).
There are no run-time licenses or other limitations. You may upgrade to
the commercial "Personal FlagShip" or "FlagShip Pro" at any time.
-
The free FlagShip Demo/Test Drive is fully functional, and lets
you evaluate FlagShip with your applications without any risk. Compared
to the full FlagShip license, it is only limited as follows:
- The compiler and with it produced executables run for 30 days, but
may be freely reinstalled again.
- The produced executable has a 1 hour run-time limit and supports
four users simultaneously.
- Any number of records are supported, but only the first hundred records
are writable.
The executable produced by this Demo cannot be distributed. The Test
Drive is also available for a free download on Internet or CompuServe.
You may directly install and run the Test Drive from the CD-ROM without
any additional activation.
-
The FS2 Toolbox is an optional extension of the FlagShip package.
The FS2 library includes hundreds of additional functions, call-compatible
to the NT2/CA3 Toolbox of CA. It includes i.e. windowing, various data
manipulation, communication etc. You will need to obtain an Activation
Key of the same class (Pro, Personal) as your FlagShip license to be able
to install the FS2 Toolbox.
Installation
from this CD-ROM
FlagShip may easily be installed. You will need superuser (or root) privileges
to perform the installation. Requirements:
-
approx. 20-60 Mbyte of free hard disk capacity (system dependent, will
be reported and checked during the installation process),
-
an installed C development system (cc, linker, libraries) for developing
with FlagShip. Not required for executing the produced applications.
With the CD-ROM distribution, the "FSinstCD" script does it all automatically
and interactively for you. If you are in hurry, just cd to
the CD-ROM directory and type ./FSinstCD - that's all.
Here the detailed description:
1. |
Before installing the FlagShip full release (FlagShip Pro, Personal
FlagShip or the FS2 Toolbox), call your dealer or multisoft GmbH for your
Activation Key, you will not be able to install it otherwise. The activation
key for the "Free Personal FlagShip is available for free on http://www.fship.com/register.html
The installation of the Trial/Demo FlagShip version does NOT require such
an Activation Key. |
2. |
Log into your computer system as super-user or root:
$ su
(Unix shell prompt)
Password: john_miller (not displayed)
#
(Unix prompt)
Note: in an emergency, you may perform the installation
(at least partially) also without the 'su' permissions. You will be prompted
accordingly.
Caution: Before installing the DEMO version of FlagShip,
make sure that the date and time are correctly set on your
system. Check this or set it by using:
# date -or-
# date mmddHHMMyy - e.g. date 0321154898 for the
21-Mar-98 at 3:48pm
|
3. |
Insert the CD-ROM into the drive and mount the CD-ROM to any mount
point (directory) of your choice (here referred as /cdrom), if not already
mounted
# mount [-v]
(check the output)
# cd ; umount /cdrom
(to insert the CD-ROM)
# mount /cdrom
Note: some systems, like Sun, use the "volume manager" for
an automatic handling of mounts, and a command "eject cdrom" to open the
CD-ROM drive. On other systems, you may use e.g. the "storage manager",
"Smit", "disk manager" etc, or mount the CD-ROM manually with:
# [/etc/]mount -r <type> <device> <mountPoint>
whereby <type is the name designator for the standard
ISO9660 (HSFS, Rockridge) file system, <device> is the CD-ROM
driver e.g. "/dev/cd0" and <mountPoint> is an available, empty
directory with sufficient permissions, e.g. "/cdrom". See the respective
parameters in the system documentation "man mount" or consult your system
administrator. Some examples for mounting a SCSI CD-ROM drive:
mount -r -v cdrfs /dev/cd0 /cdrom
# on IBM AIX
mount -r -F cdfs /dev/cdrom/c1t4l0 /cdrom
# on AT&T, UnixWare
mount -r -F hsfs /dev/dsk/2s0 /cdrom
# on HP UX
mount -r -F cdfs /dev/cd/0 /cdrom
# on ICL Sparc
mount -r -t iso9660 /dev/scd0 /cdrom
# on Linux ELF
mount -r -t iso9660 /dev/sr0 /cdrom
# on Linux a.out
mount -r -F hs /dev/ios0/sdisk005s0 /cdrom
# on Siemens RM
mount -r -t hsfs /dev/sr0 /cdrom
# on Sun w/o filemangr
eject cd0 ; mount -r -F hsfs /dev/cdrom /cdrom
# on Sun x86
mount -r -f ISO9660 /dev/cd0 /cdrom
# on SCO OS5
# cd /cdrom (or your mount point)
|
4. |
Read the documentation in the /cdrom/doc_engl or /cdrom/doc_germ directory,
e.g.
# pg ./doc_engl/*.doc -or-
# more ./doc_engl/*.doc -or-
# less ./doc_engl/*.doc (for Linux)
Note: type ':n' for next file, 'q' to quit
the browser. File movement with 'space/b' or with '+/-/return'. You may
read it also durimng the installation process.
Read carefully at least the License Agreement & Warranty (the /cdrom/
doc_engl/license.doc or /cdrom/doc_germ/lizenz.doc file). Note: some files
are available also in DOS format, check for the *.DOS extension.
|
5. |
Check, if your CD-ROM drive support mixed case and long file names.
When invoking "ls -l ." you should see the file "FSinstCD"
instead of "fsinstcd" or "FSINSTCD". If you see it in
lower or upper case only, you will not be able to install FlagShip directly
from the CD-ROM, but may install it from your harddisk. To do so,
cd to the /cdrom/tar directory and follow the instruction in README
there. If you see it correctly, invoke the CD-ROM installation script in
the /cdrom directory
# ./FSinstCD -or-
# ./FSinstCD -e (for English messages) -or-
# ./FSinstCD -d (for German messages)
The full syntax with optional arguments is:
# ./FSinstCD [-e|-d] [-help|-h] [-nocheck] [-t nn] [system]
whereby -e : English messages (the default)
-d : German messages
-nocheck : suppress check for important Unix tools
-t <nn> : terminal lines (default = 24 or environment LINES)
<system> : path of the system to be installed (e.g. sco325)
The installation script will communicate with you and ask the system and
product to install.
|
6. |
During the installation of a FULL version (FlagShip Pro, Personal FlagShip
or FS2toolbox), you will be asked to enter the unique serial number and
the activation key. Please get your Activation-Key Document and give the
required entry exactly as printed in the Document, including the
special characters (like colon, period etc.). The entry may be done without
regard to the case of the letters. When the entry was wrong three times,
the installation is aborted and has to be restarted again.
Note: The FlagShip package is tailored to the developer's needs: the
economic "Personal FlagShip" is used personally or internally in the company
and supports two users, whereas the Demo supports four users at a time;
and the FlagShip Pro package supports an unlimited number of users. The
license type limits the accessibility of executable applications and databases.
Normally, if more than the maximum allowed number of users/processes
try to execute an application, the message "...sorry, user limits exceeded,
try later..." occurs and the next execution becomes possible when one of
the current users finishes his session. Only a certain maximum number of
users may access shared databases at any one time, otherwise a run-time
warning occurs and the NETERROR() function returns .T. An application can
check the user limit before database access by using the FlagShip functions
USERCHECK(), USERSMAX() and USERSACTIVE().
Of course, applications created by the usual FlagShip (FlagShip Pro)
do not have any limitations, full access is available at any time.
When installing the FlagShip full license (Personal or Pro) after the DEMO,
uninstall the DEMO version first by using "FSuninstall" or upon request
during the installation (the FSinstCD script will ask you to do this, when
another FlagShip version is detected). All your prg sources must
be recompiled with the full license thereafter.
|
7. |
The FlagShip installation is now finished. Remove the distribution
media from the disk drive and keep it safe. Log into your computer as an
ordinary user:
# exit (leave the su mode now)
$ (std. UNIX shell prompt)
|
Now, you are ready to use the FlagShip development system. Please invoke
the FlagShip on-line manual first by e.g.
$ newfscons fsman
-or-
$ fsman
see details in the Unix manual pages
$ man flagship
$ man fsman
Of the most important sections are the REL (Release Notes) and FSC (compiler).
The Release Notes are available also in
html format in the root CD-ROM directory in relnotes.html,
or in ASCII format in the system specific CD-ROM directory and on your hard disk
in the /usr/FSsrc/manual/relnotes.asc file.
If you are not very familiar with Xbase programming yet, read carefully
the section LNG (Language) and study the complete programming examples
there. For an advanced programmer, the chapter QRF (quick reference) gives
you a quick overview and the reference part (CMD and FUN) describes in
detail all commands or functions, including the differences (if any) to
other Xbase dialects.
Note for Linux users: For your convenience, a printed manual (over 1500
pages) is available for purchase from your dealer.
The printed manual is included in the distribution (except of the Demo)
for all other Unix systems.
Deinstallation
All of the files installed by 'FSinstCD' (or via rpm on Linux) may be removed
selectively at any time by entering
$ su
# FSuninstall -e
(using English messages, the default)
# FSuninstall -d
(using German messages)
Support
The tech support is for free during the initial period for
all registered users. To join it, fill in and return the
registration card (the REGCARD file available in the installation
directory or in /usr/FSsrc), applicable also for the Demo. You
may contact your local distributor or multisoft by e-mail, phone
or fax. Preferably use the Support Request form, available in the appendix
of the on-line manual or on the CD-ROM in /cdrom/doc_engl/suppreq.doc
or on the Web.
Using
FlagShip
The handling of the FlagShip package is very similar to the handling of
any other compiler package like Clipper, cc etc. Please see details in
the printed manual or in the FlagShip on-line manual (see "man fsman"
for its invocation). The most important chapters are REL, FSC and LNG.
An example:
$ cd ~/ (or simple cd )
$ cp /usr/FSsrc/fsadr* .
(a small example)
$ FlagShip fsadr*.prg -omytest (see section FSC)
$ newfscons ./mytest
(or newfswin, newfsterm instd.)
There are also many additional hints in /usr/FSsrc/docu directory,
e.g. the howto* files.
Before starting your application, you should check the actual environment
settings (stty, TERM, ttymap etc.) according to chapter Runtime Requirements
in sections FSC and REL, and the configuration file /etc/ FSconfig. If
the colors or special keys work other than expected, check section SYS
or use the semi-automatic checking program fscheck.prg stored in the /usr/FSsrc
directory. Copy it into your working directory, compile and run it. It
will check and display the input and output mappings, the default settings
and so on:
$ cd /usr/home/john
(or simple cd )
$ cp /usr/FSsrc/fscheck.prg .
$ FlagShip fscheck.prg
(see section FSC)
$ TERM=FSansi ; export TERM
(see release notes, section REL)
$ export FSTERM=fslinux
(for Linux, see release notes)
$ ./a.out
-or to do it automatically, use:
$ newfscons ./a.out
(sets the terminal for you)
Additional
Infos and Ports
For other Unix systems not available on this CD-ROM, FlagShip demos/test
drives are available on floppies or tape for a nominal fee. Ask your distributor
or contact:
http://www.fship.com
ftp://fship.com/pub/multisoft
e-mail: info@fship.com
fax: (++49-89)
6412974
phone : (++49-89) 649-0040
We suggest to frequently check the faqsupp.txt file on Internet
(via the Support button on the home page, or by ftp
in the /pub/multisoft/flagship/support directory) for actual hints from
the support department.
Enjoy !