Installation on Unix

Contents


How to get and install MuPAD

Please read How to get and install MuPAD via ftp first and follow its instructions. Use the shell script unpack.sh to unpack / install MuPAD in the current directory.

sh ./unapck.sh

After unpacking has been completed, on some systems special installing procedures has to be carried out:

Special installing procedures

On some systems unix environment variable must be set to tell MuPAD where to find X11/XView dynamic libraries (LD_LIBRARY_PATH or on HP-UX SHLIB_PATH) and fonts (FONT_PATH).
HP-UX / XView libraries:
It is necessary to change the environment variable SHLIB_PATH. (This is used to search for dynamic libraries at run time.)

setenv SHLIB_PATH ${MuPAD_ROOT_PATH}/hp/xview
or
setenv SHLIB_PATH ${MuPAD_ROOT_PATH}/hp/xview:${SHLIB_PATH}

Insert this line into your file ~/.cshrc.

Be sure that these libraries and also the directories of this path are readable and executable.

Solaris and other systems: / XView libraries
Sometimes it is necessary to change the environment variable LD_LIBRARY_PATH. (This is used to search for dynamic libraries at run time.)

setenv LD_LIBRARY_PATH /XXX/lib
or
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/XXX/lib

Where XXX is the directory in which OpenWindows is installed. This is ususally one of the following: /usr/openwin/ , /opt/openwin/ , /usr/local/openwin/. Insert this line into your file ~/.cshrc.

Some (older) systems: 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 extracted directory Xview.fonts .

After that, you can start MuPAD, following the guidelines in section How to run MuPAD.

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.

[Back To Contents]


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.
     SHLIB_PATH      -- X11/XView libraries on HP-UX
     LD_LIBRARY_PATH -- X11/XView libraries on other systems
     FONT_PATH       -- directory of the fonts for the help system
     LW_PRINTER      -- name of a Postscript-printer. 
     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.
     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. 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.

[Back To Contents]


Possible warnings when starting MuPAD

Textsw package

XView Warning:
	No such file or directory, extras menu file 
	/usr/lib/.text_extras_menu (Textsw package)
Copy the file text_extras_menu which is located in $MuPAD_ROOT_PATH/share/xview to /usr/lib/.text_extras_menu or set the environment variable EXTRASMENU:

setenv EXTRASMENU $MuPAD_ROOT_PATH/share/xview/text_extras_menu

<utmp>

XView Warning:
	Warning: make sure that you can write <utmp>
This is an incompatibility of old XView portations to new SYSV operating systems. Ignore it. Do not change the permissions on this file!!!

Font package

XView Warning:
	XView warning: Cannot load font '--0' (Font package)
Ignore it.

ttysw_sigwinch

XView Warning:
	XView warning: ttysw_sigwinch, 
        can't get tty process group: Not a typewriter
Again an incompatibility of XView. Ignore it.

[Back To Contents]


Remarks on special systems

Remarks 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
[Back To Contents]


Remarks on SGI

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 in the terminal window does not work. This is a problem of the TERMSW-package of the SGI-XView port. If you know any solution, please let us know.

You may have to specify the font for MuPAD's graphical interfaces. 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

Remarks on HP

It is necessary to change the environment variable SHLIB_PATH. Refer to Special installing procedures

[Back To Contents]


Remarks on Sun

It may be necessary to change the environment variable LD_LIBRARY_PATH. Refer to Special installing procedures

Known Bugs

In some cases a window remains empty. Activate a window by clicking the left mouse anywhere on the window background or click the menu item Refresh in the Window popup. This will refresh the contents of a window. For example, if you use the dynamically linked version of MuPAD under Solaris 2.4 you have to do a refresh by hand, because of a bug in the new Solaris XView libraries.

[Back To Contents]


Remarks on other systems

It may be necessary to change the environment variable LD_LIBRARY_PATH. Refer to Special installing procedures

[Back To Contents]


Author: MuPAD-webmaster
Last Update: 13. Dec. 1996