Environment Variables ===================== The environment variable GMTHOME must to be set for GMT to work properly. In this respect, the OS/2 distribution is the same as the Unix distribution. GMT will look for required data files in the subdirectory share beneath the main GMT directory specified by GMTHOME. I suggest setting GMTHOME in CONFIG.SYS. In addition, the variable HOME should be set to a directory of the user's choice (it could be the same as GMTHOME); GMT stores default parameters in that directory. Remember to use forward slashes rather than backward slashes to indicate the directories (for example, use SET GMTHOME=d:/GMT rather than SET GMTHOME=d:\GMT). Idiosyncracies ============== 1. If you unpack the GMT distribution in a directory g:/GMT, and set the environment variable GMTHOME to g:/GMT, GMT won't find several required files, for unpacking GMT_progs.tar.gz will place them in G:/GMT/GMT3.4/share instead of the expected G:/GMT/share. Moving them to the latter path will solve the problem. 2. To successfully use, e.g. tcsh, for the examples, one has to rename tcsh.exe to csh.exe and place a copy in a directory /bin on the drive on which the examples reside. 3. When creating the examples, the TMP or TEMP environment variables are not honored. Instead one has to ensure that a directory /tmp exists in the root of the drive that the examples reside on. If /tmp doesn't exists, the example will fail. Items 2 and 3 could be solved by using TVFS. Thanks to Christian Hennecke for pointing out the above features. Installation ============ To install, extract the routines from the archive and set the environment variables as discussed above. Install the executables in the directory /GMT/GMT3.4/bin or in any other location in your PATH. Install the DLLs in a location in your LIBPATH, or modify your LIBPATH to include the directory in which you place the DLLs. Obtain and install documentation as you see fit; note that man pages can be viewed online from the GMT site. If you are unfamiliar with GMT, I strongly suggest getting the nice tutorial, available from the main GMT web site. Known Problems ============== Thus far (24 Dec 2001) there is only one known problem with the port. At least one of the routines (sample1d) seems to have a problem accepting piped output from other routines. This is exemplified when example 3 is run. For example, in example 3 (job03.bash, for instance) the command filter1d ship.pg -Fm1 -T$sampr1/$sampr2/1 -E | sample1d -Nsamp.x > samp_ship.pg fails, yet the executing the commands via temporary files, such as filter1d ship.pg -Fm1 -T$sampr1/$sampr2/1 -E > filter1d.tmp sample1d filter1d.tmp -Nsamp.x > samp_ship.pg seems to work perfectly. Until such problems are resolved, you might consider using temporary files with sample1d. Help and Bug Reports ==================== This version of GMT is not directly supported by Paul Wessel and Walter Smith, who are the authors of the Unix verison. If you believe you've found a bug, it may well be a bug that applies to the Unix version as well as to the OS/2 version. Be aware that there are two electronic mailing lists available to users. The first, gmtgroup at soest dot hawaii dot edu, is used primarily to notify users of bug fixes and new versions. The second, gmthelp at soest dot hawaii dor edu, serves as a users forum for idea exchange and questions about GMT usage. To subscribe to either of these lists, send an e-mail message to listserver at soest dot hawaii dot edu containing one or both of the commands subscribe gmtgroup subscribe gmthelp Do not include the angle brackets in the message. Also, if your e-mail client appends a signature file to your outgoing messages, inhibit the sending of the file (or send a blank file). For questions of bug reports that you believe are specific to the OS/2 version, please send bug reports [e-mail only!] to Allen Cogbill, Los Alamos National Laboratory.