MuPAD-FAQ-INSTALLATION

## Installation of MuPAD

All files needed to install MuPAD on your system are available on ftp.uni-paderborn.de:/local/MuPAD. MuPAD is also available on other ftp sites. Before you try to get it, please refer to the list of official MuPAD sites to find one near to you.

Also refer to Installation On Linux , Installation On Macintosh or Installation On Windows for special installation procedures. Note that you have to obtain a license to get the full-featured MuPAD version.

Users of a previous MuPAD version should install the new version in a new directory. Do not mix up different MuPAD releases or you may run into difficulties! Refer to How to run MuPAD. The directory structure of MuPAD may have changed and maybe some environment variables must be changed.

Copyright (C) B. Fuchssteiner, Automath, University of Paderborn, Germany. All rights reserved.

## Contents

- Before you get MuPAD
  - Supported systems
  - Compatibility notes
- How to get MuPAD
  - Files you need
  - Additional files
  - A sample ftp session
- How to install MuPAD
  - Special installing procedures
  - User registration
- How to run MuPAD
  - Environment variables
- Possible warnings when starting MuPAD
- Disc space needed for MuPAD
  - Standard version
  - Terminal version
  - Additional software
- How to reduce disc space
- Differences on IBM RS/6000
  - Editing-, Help- and Meta-Keys
- Remarks on Silicon Graphics

## Before you get MuPAD

You must obtain a password to get the full-featured MuPAD version. Please get your password before you proceed. Without registration you get only a demo version.

### Supported systems

Before you copy MuPAD from the ftp server you should decide which kind of binaries you need. For this please refer to the list of supported systems.

Note: The Sun4 version of MuPAD contains dynamically and statically linked binaries. Those binaries which use dynamic linked libraries are normally prefered as they are much smaller and need less system resources. To use a dynamically linked binary, the shared libraries of the XView-Toolkit must be installed on your system. You can choose the binaries appropriate to your system during unpacking. Linux contains only dynamically linked binaries.

### Compatibility notes

- Sun4 (SunOS 4.1.x) binaries work also with Solaris 2.x (SunOS 5.x)
- SGI (IRIX 4.x) binaries work with IRIX 5.x
- See How to install MuPAD for details.

## How to get MuPAD

Before you copy MuPAD via ftp you should create and change to the directory in which you want to install MuPAD. Say /usr/local/MuPAD for example:

           mkdir /usr/local/MuPAD ; cd /usr/local/MuPAD

You may use any other directory instead of /usr/local/MuPAD. After you have changed to the new MuPAD root directory, you should copy the MuPAD files to this directory. They come as compressed tar-files.

### Files you need

1. README
   - ASCII version of this document, which has always the latest installation informations.
2. unpack.sh
   - shell script to unpack and install MuPAD.
3. share.tar.gz
   - sharable parts of the MuPAD system (libraries, manuals,...).
4. bin.???.tar.gz
   - binaries of MuPAD; Refer to the list of supported systems to check which file you need.

### Additional files

- share-ext.tar.gz
  - extensions of the sharable parts, animation (only available for Sun4)
- doc-ext.tar.gz
  - additional documentation: modules, domains, polynomials, linalg; saved as PostScript files.
- doc-small.tar.gz
  - this manual, tutorial and demo is formated according to a resolution of 600 pixel (height).
- xview.fonts.tar.gz
  - XView fonts, sometimes needed for the X11 version

### A sample ftp session

            ftp ftp.uni-paderborn.de
            [...]
            ftp> cd local/MuPAD/...
            ftp> binary
            ftp> get README
            ftp> get unpack.sh
            ftp> get share.tar.gz
            ftp> get bin.sun4.tar.gz
            ftp> bye

## How to install MuPAD

After you have copied the MuPAD tar-files, you need to unpack them with the script unpack.sh. Change to the MuPAD root directory - where the tar-files are located - and start the script. For example, if your MuPAD root directory is /usr/local/MuPAD the necessary commands are:

            cd /usr/local/MuPAD ; sh unpack.sh

Please stay at the terminal during unpacking because the script may ask for additional information.

That's all you need to install MuPAD. After unpacking has been completed you should try to start MuPAD, following the guidelines in section How to run MuPAD.

### Special installing procedures

Sun4 (SunOS 4.1.x)
  These binaries also work with Solaris 2.x (SunOS 5.x). If you want to run Sun4 binaries with Solaris, create a symbolic link "ln -s sun4 solaris" in the MuPAD root directory. Note: Sun4 binaries runs about 30-50 % slower with Solaris than Solaris binaries and you cannot use MuPAD's module generator.

SGI (IRIX 4.x)
  These binaries also work with IRIX 5.x . If you want to run IRIX 4.x binaries with IRIX 5.x, create a symbolic link "ln -s sgi4 sgi5" in the MuPAD root directory. Note: In this case you cannot use MuPAD's module generator.

Xview fonts
  Running MuPAD on IBM RS/6000 or DECstation you may need the XView fonts too. Copy the file xview.fonts.tar.gz from the ftp server. To unpack these fonts type:

         uncompress xview.fonts.tar.gz ; tar xf xview.fonts.tar ; rm xview.fonts.tar

  To install these fonts on your system, please read the document README which is located in the directory Xview.fonts .

RS6000 (AIX 3.x)
  Also refer to Differences on IBM RS/6000 at the end of this document.

### User registration

If you have a MuPAD registration code, please refer to How to validate your MuPAD version. If you want to register your copy of MuPAD, please refer to About MuPAD licence.

## How to run MuPAD

### Environment variables

In order to run MuPAD, some environment variables must be defined or changed. The most important variable is MuPAD_ROOT_PATH, which defines the MuPAD root directory:

         MuPAD_ROOT_PATH -- root directory of the MuPAD system.
         FONT_PATH       -- directory of the fonts for the help system
         PAGER	     -- pager (ie. less) used to display the help pages in a
                            MuPAD terminal session. If not set, more is used.
         MANPATH	     -- search path for man pages.
         PATH or path    -- command search path.
         LW_PRINTER      -- name of a Postscript-printer.
         PREVIEWER       -- previewer (i.e. xv or xloadimage) used to display
                            GIF-pictures in MuPAD's on-line manual. If not set,
                            /usr/local/X11/bin/xv is used.

In any case you have to specify MuPAD_ROOT_PATH , FONT_PATH and you have to extend the command search path (path or PATH)! Add the following lines to your .cshrc if you use csh or tcsh:

         #
         # MuPAD environment (csh, tcsh)
         #
         setenv MuPAD_ROOT_PATH /usr/local/MuPAD
         setenv FONT_PATH ${MuPAD_ROOT_PATH}/share/doc/hytex/fonts
         setenv MANPATH   ${MuPAD_ROOT_PATH}/share/doc/man:${MANPATH}
         set path = ( ${MuPAD_ROOT_PATH}/share/bin $path )

Add the following lines to your .profile if you use a sh, ksh or bash:

         #
         # MuPAD environment
         #
         MuPAD_ROOT_PATH=/usr/local/MuPAD
         export MuPAD_ROOT_PATH
         FONT_PATH=$MuPAD_ROOT_PATH/share/doc/hytex/fonts
         export FONT_PATH
         MANPATH=$MuPAD_ROOT_PATH/share/doc/man:$MANPATH
         export MANPATH
         PATH=$MuPAD_ROOT_PATH/share/bin:$PATH
         export PATH

Remember that the directory /usr/local/MuPAD serves only as an example and must be substituted by the MuPAD root directory in which the MuPAD system is installed. If you have installed less, you can use this pager instead of more by setting:

         setenv PAGER 'less -C -w -P"<Commands\: f = forward; b = backward; q= quit>"'

respectively

         PAGER='less -C -w -P"<Commands\: f = forward; b = backward; q = quit>"'
         export PAGER

Note: If you don't want users to have to modify their .cshrc or respectively their .profile, use the program setup which is located in share/bin/admin below the MuPAD root directory.

Remember also that the fonts for the MuPAD help system may be located at other places than $MuPAD_ROOT_PATH/share/doc/hytex/fonts if the fonts already exist elsewhere on your system.

If you run the Sun4 binaries which use dynamic link libraries it may be necessary to change the environment variable LD_LIBRARY_PATH (this variable is used to search for dynamic libraries at run time). If you get an error message from ld.so you should extend LD_LIBRARY_PATH by the directories where the necessary libraries are located, for example:

          setenv LD_LIBRARY_PATH /usr/lib:/usr/openwin/lib:/usr/X11/lib

If you don't want to modify your LD_LIBRARY_PATH, you can also use a alias:

          alias xmupad "(setenv LD_LIBRARY_PATH /usr/lib:/usr/openwin/lib; xmupad)"

## Possible warnings when starting MuPAD

If you get the system warning

    	No such file or directory, extras menu file
    	/usr/lib/.text_extras_menu (Textsw package)

when starting xmupad, copy the file text_extras_menu which is located in $MuPAD_ROOT_PATH/share/xview to /usr/lib/.text_extras_menu. Can also be set via environment variable EXTRASMENU, for example setenv EXTRASMENU $MuPAD_ROOT_PATH/share/xview/text_extras_menu

                   ------------------------------

If you get the system warning

    	Warning: make sure that you can write <utmp>

when starting xmupad, please check the access permissions of the file <utmp>. A short extract of the utmp manual page: Some window systems will make entries in utmp for terminal emulation windows running shells, so that library routines such as getlogin will work correctly in that window.

                   ------------------------------

If you get the MuPAD warning

    	Warning: Could not open 'startup.mb', reading system init file.

when starting mupad or xmupad, call rebuild_startup which is located in MuPAD_ROOT_PATH/share/bin/admin.

                   ------------------------------

If you get the XView warning

    	XView warning: Cannot load font '--0' (Font package)

when starting xmupad, please set your LD_LIBRARY_PATH.

                   ------------------------------

If you get the

    	XView warning: Cannot load font set
            '-*-FONT_FAMILY_LUCIDA-medium-r-*-*-*-120-*-*-*-*-*-*'
            (Font package)

when starting xmupad, the X server will automatically choose a font that is available.

                   ------------------------------

If you get the XView warning

    	XView warning: ttysw_sigwinch,
            can't get tty process group: Not a typewriter

when starting mdx within a xterm under Linux or HP-UX, is a known bug, but causes no problems within the actual MuPAD session.

                   ------------------------------

If you get the MuPAD warning

    	Sorry, can't open file: /tmp/xmupad_mupad_connect.xxxx

when starting xmupad, is a known bug, but causes no problems within the actual MuPAD session. The next release of MuPAD will fix this bug.

## Disc space needed for MuPAD

### (1) Standard version

    	Standard configuration: 13 - 23 MB

    	binaries
               SunOS 4.1.x  --      ~  8 MB (a)
               Solaris 2.3  --      ~ 12 MB (b)
               Linux        --      ~  2 MB (c)
               AIX          --      ~  6 MB
               Irix 4       --      ~  8 MB
               Irix 5       --      ~ 11 MB (d)
               Ultrix       --      ~  8 MB
    	share   	--      ~ 11 MB

            (a) Statically linked version : ~ 5 MB
                Dynamically linked version: ~ 2 MB
                Modules                   : ~ 1 MB
            (b) Statically linked version : ~ 9 MB
                Dynamically linked version: ~ 2 MB
                Modules                   : ~ 1 MB
            (c) Only dynamically linked version available.
            (d) Only statically linked version available.

    	Extended configuration: 32 - 42 MB

    	binaries	-- 	see Standard configuration
    	share		-- 	see Standard configuration
    	doc-ext 	--	~  2 MB
    	share-ext	--	~ 17 MB

    	Minimal configuration: 7 - 17 MB

    	binaries	--	see Standard configuration
    	share		--	~  5 MB (see How to reduce disc space)

### (2) Terminal version

The terminal version is completely independent from any window system and therefor all graphical interfaces like xmupad, vcam, mdx and the online hypertext documentation are missing. The terminal version contains all of MuPAD's functionality, inclusive online help, lineeditor, debugger, profiler, modul generator and graphics. The graphics produced by this version are data files. You can use vcam as a standalone tool, or you can convert this data to the format, that is accepted by another renderer.

    	Standard configuration: ~ 3.3 MB

    	binaries	--	~ 1.1 MB
    	share		--	~ 2.2 MB

You need only the directories

              share/bin/  share/lib/   share/doc/ascii/
              share/mmg/  arch/modules

and only the binaries mupad and mmg in the directory

              arch/bin/

where arch is the machine hardware name, for example sun4. If you cannot find the binary mmg and the directory arch/modules/, then MuPAD doesn't support the modul generator for your hardware, and you can remove the directory share/mmg/

### (3) Additional software

    	xview.fonts	-- 	~ 3 MB

## How to reduce disc space

In order to reduce the disc space needed for MuPAD you may further be able to delete some TeX-PK-fonts. These fonts are used for the MuPAD help system and might already be installed on your system.

The fonts for the MuPAD help system are located in the directory

            share/doc/hytex/fonts/			(~ 160 KB)

below the MuPAD root directory. You may delete this font directory if you allready have these fonts in other places, but note that in this case you must change the environment variable FONT_PATH according to the existing font directories. Typical places where such fonts could be located are

    /usr/local/tex/fonts/pk118 and /usr/local/tex/fonts/pk300

for example.

If your system has the shared libraries libxview.so.3.x, libX11.so.4.x and libolgx.so.3.x you can remove all files with the extension .static which are located in sun4/bin, solaris/bin below the MuPAD root directory.

If you do not need the tutorial, you can remove the following files/directories:

    	share/doc/hytex/tutorial.*		(~  600 KB)
    	share/doc/hytex/bsp/tutorial/           (~  500 KB)
    	share/doc/hytex/gif/tutorial/		(~  600 KB)

If you do not need the demo, you can remove the following files/directories:

            share/doc/hytex/demo.*			(~  200 KB)
            share/doc/hytex/bsp/demo/		(~  500 KB)
    	share/demo/				(~ 1500 KB)

If your system does not provide MuPAD's modul generator, or if you do not need the modul generator, you can remove the directory:

    	share/mmg/				(~  600 KB)

## Differences on IBM RS/6000

### Editing Keys

The IBM RS/6000 keyboard does not have a left set of function keys or any usable function keys past F10. The editing keys can be remapped via xmodmap (see below for examples) or the standard keyboard equivalents can be used.

    Sun             IBM
    L2  (Again)     Meta-a
    L4  (Undo)      Meta-u
    L6  (Copy)      Meta-c
    L8  (Paste)     Meta-v
    L9  (Find)      Meta-f
    L10 (Cut)       Meta-x

### Help Key

To use the help functions of XView and OLWM you must bind the Help keysym to some other key. For example, to make the F8 key act like the Help key, type:

    xmodmap - << EOF
    keysym F8 = Help
    EOF

### Meta Key

The AIX Windows keyboard map must first be altered for the Meta key to be noticed by the XView Toolkit. Use the xmodmap command:

    xmodmap - << EOF
    keysym Alt_L = Meta_L
    keysym Alt_R = Meta_R
    EOF

## Remarks on Silicon Graphics

All of MuPAD's graphical interfaces run in 'full-screen-debug' mode, because of a bug in the X11-server Xsgi. This mode slows down the speed of xmupad, hypage (hypertext system), mdx (debugger) and vcam (graphic tool).

Within mdx, user input is repeated in the terminal window. This is a bug in the TERMSW-package of the SGI-XView port.

You have to specify the font for MuPAD's graphical interfaces. Please select a font with a fixed width. xlsfonts lists all available fonts on your server. Make an entry in your .Xdefaults, for example

    Font.name: lucida-normal-10

### Known Bugs

In some cases a window remains empty. Activate a window by clicking the left mouse anywhere on the window background. This will refresh the contents of a window.