This directory contains the Solaris code for GRASS 4.3 in gzipped tar format. This distribution is based on GRASS 4.2.1 with further features. New 3/2000: bugfix for m.in.e00, new v.in.shape, new v.out.shape, bugfix for tcltkgrass (i.smap, i.gensigset) Installation: 1. get the large (18 mb) file grass4.3_solarisbin_3_2000.tar.gz which is the whole binary in a single file. 2. get the installation script grass43install.sh Then you only need to type the following after you ftp it (example!): sh grass43install.sh grass4.3_solarisbin_3_2000.tar.gz This will create the necessary directories and files for you to run GRASS. The default install path is /usr/local/grass43/ Start GRASS with grass4.3 The user interface is started within GRASS: tcltkgrass& Note: If you are starting from beginning, you have to define your project area within GRASS before accessing the "tcltkgrass" user interface. *************************************************** Paint driver notes: 1) If you have local paint devices, you will need move the appropriate files from $GISBASE/etc/paint/driver.uninst to the driver.sh in the same directory. In addition, you must create a symbolic link (using the 'ln -s' command) from /dev/[paint driver name] to /dev/ttya or /dev/ttyb (or whichenver system device your print device is plugged in too). For example, if you have a xerox4020 connected to /dev/ttya, use % cd $GISBASE/etc/paint/driver.uninst % mv xerox4020 ../driver.sh % ln -s /dev/ttya /dev/xerox4020 % chmod 0666 /dev/xerox4020 You will have to be root to create the symbolic link in /dev. 2) If you have a paint device which exists on a remote host whose GISBASE is difference from the local GISBASE you will need to update the value of GISBASE in etc/paint/driver.rsh. 3) If you plan to use v.digspline and have any digitizers copy the file etc/digcap.sampl to etc/digcap and edit it accordingly. USING THE BINARY VERSION ------------------------ The binary version does not come with any data or documentation (except for on-line man pages). You will need to acquire whatever documents you like from the GRASS Development Team FTP server. Sample data is also available from the FTP site, or you may use data from previous versions of GRASS if you have it available. *********************************************** If you experience any problems, please email us at: grass@baylor.edu