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.
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.
mkdir /usr/local/MuPAD ; cd /usr/local/MuPADYou 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.
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
cd /usr/local/MuPAD ; sh unpack.shPlease 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.
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 .
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/libIf 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)"
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.xxxxwhen starting xmupad, is a known bug, but causes no problems within the actual MuPAD session. The next release of MuPAD will fix this bug.
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)
Standard configuration: ~ 3.3 MB binaries -- ~ 1.1 MB share -- ~ 2.2 MBYou 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/
xview.fonts -- ~ 3 MB
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/pk300for 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)
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
xmodmap - << EOF keysym F8 = Help EOF
xmodmap - << EOF keysym Alt_L = Meta_L keysym Alt_R = Meta_R EOF
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