INSTALLATION NOTES FOR FTS release 1.4.x Starting with release 1.3 patch level 7, the configuration has been simplified; we introduced the concept of "standard installation", i.e. an installation following some default paths and rules, and while leaving the possibility to adopt a complete different structure, the configuration in the standard case is simplified; also, if you are using FTS on a ISPW inside IRCAM, the installation will be perfomed by the FTS developement group. To install the ISPW distribution, you have to do three things: 1- chose a directory and unpack the files. 2- change some permission in the bin directory and run ranlib on the libraries. 3- Install some NextStep Default with the default values, either at the user level or at the site level. 1- CHOSE A DIRECTORY AND UNPACK THE FILES You can use any directory you want to install Max/Fts on your Next machines, but we recomend to use the IRCAM standard installation directory, this will simplify a lot the installation procedure; the IRCAM standard installation directory is /LocalApps/fts.1.3; anyway, any other directory can be used, if you correctly specify the right NextStep defaults; notes that also if this release is numbered 1.4.0, the installation directory stay "fts.1.3"; this will be fixed in a future ISPW only release. The directory structure will not be similar to the Max 0.26 directory structure, and will not include any Max.app directory; to get the Max icon, look in the /LocalApps/fts.1.3/bin/next3 directory and drag it to the desktop. If you want to install the FTS distribution on a different machine and accessing it thru the network you have to create the /LocalApps/Ispw directory (see below) locally on every machine where you will use FTS. To unpack the files, use ungzip to decompress the file, and tar to unpack it in the chosen directory. 2- CHANGE SOME PERMISSION IN THE BIN DIRECTORY AND RUN RANLIB You must go in the /bin/ispw directory, become root, and do the following: > mkdir /LocalApps/Ispw > cp userboot sounddisk hkernel-3.0 dma.lod initdma /LocalApps/Ispw > cd /LocalApps/Ispw > chown root userboot > chown root sounddisk > chmod u+s userboot > chmod ugo+rx userboot > chmod u+s sounddisk Note that you need to perform all this only the first time you install a fts 1.3 directory; the files in /LocalApps/Ispw directory will not change within different patch levels, unless differently stated in the release notes. Then, go to /LocalApps/fts.1.3/lib/ispw and run the command: ranlib libFts.a This is needed if you develop new clients. 3- INSTALL MACHINE DESCRIPTION FILE AND DEFAULT CONFIGURATION FILE If you have one ISPW boards on your Next Cube, copy the file /lib/config/ispw_1/machine.cfg in the /LocalApps/Ispw directory; if you have three boards, do the same with the /lib/config/ispw_3/machine.cfg file; if you have a two board system, copy the file for the three boards machine, and edit it by hand. Also, copy the /lib/config/ispw/default.cfg file in the /LocalApps/Ispw directory; this is the default configuration file loaded by fts if a config file is not specified; feel free to modify your copy according to your hardware installation. 4- INSTALL NEXTSTEP DEFAULTS: STANDARD INSTALLATION Max need to have a number of information about its environment, where to find the fts executable, where to find system files, help files and so on. All these information can be given as command line arguments, or thru the NextStep default system, using the dwrite command; the syntax of the dwrite command is: dwrite From this release of Max/FTS, is always "Max_1_3", also if the release number changed to 1.4. In a standard installation the distribution is installed as it is in a installation directory, without modifying the directory structure; the system assume defaults based on the standard installation root. In a ISPW system, the installation directory (called in the following root directory) default to /LocalApps/fts.1.3; if the FTS installation is installed to a different directory, the user can specify it by declaring the rootDir NextStep default. All the other values have default values oriented to the standard case, i.e. running a local instance of FTS with one single client, running on three ISPW boards As of release 1.3 patch level 7, the are two exceptions to this rule is the following: the first is the resource patchPath, that tell the system where to look for subpatches, do not have a default value; if you want to use subpatches included in the standard library, you need to set it by hand so it include them, like this: dwrite Max_1_3 patchPath /lib/patches:./subpatch The patchPath value is a list of path separated by colons; of course, you can still set the path from inside Max with the standard mechanism, but for the moment you have to specify the standard libs directory by hand because the "use standard libs" button do not work for the moment. The second exception is still the startup configuration file, that must be specified with an absolute path, for exemple like this: dwrite Max_1_3 startupFile /src/config/ispw.cfg The startupFile default to /LocalApps/Ispw/default.cfg rootDir, patchPath and startupFile can also be declared with command line options, see below. 5- INSTALL NEXTSTEP DEFAULTS: CUSTOM INSTALLATION OR NON STANDARD USE A number of configurations variables and command line switches allow to cope with non standard installation, i.e. with installation that do not keep the distribution directory structure, or to run FTS with multiple clients or remotely in an other machine (Unix or ISPW). The following is a complete table of the options and NextStep default you can specify, and their meaning; defaults or values including a (*) are meaningfull only when running fts on a ISPW, either directly or thru a network connection. DEFAULT COMMAND LINE DEFAULT NAME OPTION none -help na Show an help text none -v na Show version and exit linkType -l value pipe Type of link used to connect to fts or the the ftsd daemon; can be sink, socket, ispw (*), pipe, named_pipe linkOptions -lo value empty Link Options (link and architecture dependent) ftsArch -arch name ispw Architecture where FTS is running on; as 1.3.7, can be ispw or sgi. ftsHost -h name empty If the connection type is "socket", i.e. the fts server is remote, this is the name of the host where to look for fts. patchPath -p pathlist empty Search path list for patches. rootDir -r dir /LocalApps/fts.1.3 Root of the FTS installation helpDir -helpDir dir $rootDir/lib/help Help file directory ftsDir -d dir $rootDir/bin/$ftsArch Directory to find the FTS executable sysDir -sys dir /LocalApps/Ispw Directory to find FTS support files (*). ftsName -n name fts Name of the FTS executable nBoards -nb int 3 Number of ISPW board installed/used (*) advances -adv val:val:.. 5:5:5:5:5:5 Colon-separated list of scheduler advances (*) throttle -throttle values 8:8:1 Colon-separated list of 3 throttles (*) stderrCopy -stderr no Copy Max window to stderr fontName -f name Text font name fontSize -s int Text font size startupFile -c filename Startup COnfiguration File (min format) 6- MULTICLIENT OR REMOTE FTS If you run multiple clients, Max or others, or you want to develop your own clients, or use fts from the network, you should use the ftsd network daemon. In this case, read the ftsd.txt and max_and_ftsd.txt documents; about the installation, you need to specify the linkType as socket (see above) and you need to specify the host name in the command line when you run Max. You also need to declare a new TCP service, number 2000, name "ftsd"; the corresponding line in the /etc/services file look like: ftsd 2000/tcp # Ircam ftsd check with your sysop in case of doubts ... Remeber that is possible to use the X/Motif Max with fts running on a ISPW, or, on the contrary, a NextStep Max running on a Next with FTS running on the sgi; in that case you should specify the fts architecture using the -arch option or the ftsArch resource.