##########################################
# MuPAD 1.4.0 beta INSTALLATION FOR OS/2 #
##########################################

Author: Dipl.-Math. Manfred Radimersky
Date: 6.5.98

1. Requirements: OS/2, HPFS, unzip, EMX
=======================================

To run this terminal version of MuPAD for OS/2, you need an OS/2 Warp 3 system
at least, and you must install MuPAD on a HPFS partition. MuPAD will not run
under a FAT partition because of the 8 plus 3 characters file name restriction.
To unpack the zip archives of this distribution, you need Info-ZIP's unzip
program freely available via anonymous ftp at

  ftp://ftp.uni-paderborn.de/os2/muenchen/leo/archiver/unzip532.exe
  ftp://ftp.uni-hannover.de/pub/mirror/os2/util/archiver/unzip532.exe
  ftp://ftp.leo.org/pub/comp/os/os2/leo/archiver/unzip532.exe
  ftp://ftp-os2.cdrom.com/pub/os2/archiver/unzip532.exe

Since this OS/2 port of MuPAD was done using the EMX/GCC compiler system,
this MuPAD version requires the EMX runtime libraries located in the archive
emxrt.zip for EMX version 0.9C or later. Follow the instructions within the
archive emxrt.zip to install the runtime libraries. The archive emxrt.zip is
also freely available via anonymous ftp at

  ftp://ftp.uni-paderborn.de/os2/muenchen/leo/gnu/emx+gcc/emxrt.zip
  ftp://ftp.leo.org/pub/comp/os/os2/leo/gnu/emx+gcc/emxrt.zip
  ftp://ftp-os2.cdrom.com/pub/os2/emx09c/emxrt.zip

It is strongly recommended to install the less pager (famous in the UNIX
world) for viewing the ASCII online help along with MuPAD for OS/2. The
less pager is also freely available via anonymous ftp at

  ftp://ftp.leo.org/pub/comp/os/os2/leo/unix/less321-2.zip
  ftp://ftp-os2.cdrom.com/pub/os2/unix/less3212.zip

Please note that this is an unsupported version of MuPAD, therefore we will
nearly never assist you in installing the Info-ZIP's unzip, the EMX runtime
libraries, the less pager and the OS/2 REXX package. Moreover, we cannot
guarantee that these ftp addresses are correct or will remain available.

2. Unsupported Beta Terminal Version
====================================

This is a terminal version of MuPAD for OS/2. This means it can be run under
the OS/2 shell CMD.EXE. Other shells have not been tested, but they should be
okay as well. This version of MuPAD is NOT a Presentation Manager application,
it therefore does not provide the graphics functionality that is included for
other platforms. If you call MuPAD graphics functions like plot2d and plot3d,
this terminal version will only dump a graphics file with MuPAD's own internal
binary format and you can not make a GIF or PostScript file from it. For the
time being, we do not have the manpower to port the graphical user interface
to OS/2 and to maintain it. Note that this OS/2 version of MuPAD is still a
beta version, there still may be some OS/2 specific bugs remaining. Neither
the MuPAD group nor SciFace GmbH & Co KG provide any guaranteed support for
the OS/2 version. However, you are encouraged to report bugs specific to the
OS/2 version via email to bugs@mupad.de, and if you are lucky, we have the
time to help you and send back an email answer with suggestions how to fix
your problem.

3. Unpacking the ZIP archive
============================

You just need one archive file which contains both the MuPAD kernel executable
and the share library version 1.4.0. This archive is approximately 4 megabytes
in size and is named

  mupad_os2_140.zip

Create a new directory on your HPFS drive as MuPAD base directory. We will use
the path D:\MuPAD in the following text. If you use another directory, you will
have to adapt the following to it. Now change to this new directory and unpack
the zip archives by the following command, assuming the zip archive is in the
root directory of drive D:

  unzip d:\mupad_os2_140.zip

4. Modifying your system files
==============================

Then add the directory D:\MuPAD\bin to your PATH environment variable defined
in your CONFIG.SYS file. If you use another MuPAD base directory, you have to
change the extension of your PATH variable accordingly. Then append the file
mupadpre.cmd in the D:\MuPAD\bin directory to your CONFIG.SYS file. If you
use another base directory than D:\MuPAD, you have to locate mupadpre.cmd
accordingly and change the appended commands from mupadpre.cmd accordingly.
Please note that it is essential that some commands in mupadpre.cmd use
forward slashes and some use backward slashes as path separator character.

Please note that MuPAD uses many megabytes of memory. You have to ensure
that your OS/2 system is set up to support virtual memory via disk swap
space (via MEMMAN=SWAP,PROTECT in your CONFIG.SYS, for instance) or to
have lots of physical memory available. Please refer to your OS/2 User's
Manual for more information if you encounter insufficient memory problems.

Moreover, if you do not have installed the less pager, you must remove
the line SET PAGER=less and replace it with SET PAGER=typemore to view
the ASCII online help. If you use the typemore.cmd pager file, you must
have installed the OS/2 REXX package included in your OS/2 Warp system.
You can change your system configuration according to your OS/2 User's
Manual to add the OS/2 REXX package later on. You can use any other pager
if it can handle forward slashes '/' instead of backward slashes '\' as
path separator characters and if it is included in your PATH variable.
However, it is strongly recommended to install the less pager. At last,
shutdown and reboot your system to put the CONFIG.SYS changes in effect.

5. Have fun with MuPAD
======================

Start MuPAD from the OS/2 shell prompt anywhere via typing "mupad". View
the command line options of MuPAD via "type D:\MuPAD\bin\mupad.man | more",
but change the path if you use another MuPAD base directory. Quit MuPAD
via "quit", online information is available via "?". There is one thing
that you should know before using MuPAD for OS/2: if you access files via
MuPAD commands like "read", you must substitute the backslashes '\' used
as path separator characters either to forward slashes '/' or to double
backslashes '\\'. Then if you want to access the file "C:\TEMP\TEST.MU",
for instance, the code read("C:\TEMP\TEST.MU"); in MuPAD is not working,
but you can use read("C:/TEMP/TEST.MU"); or read("C:\\TEMP\\TEST.MU");
instead. Please contact us via our web interface at

  http://www.sciface.com/download/index.shtml

or via email at 

  info@sciface.com

to get a registration key for MuPAD to remove the memory limitation of the
unregistered version. Then enter the register command at the MuPAD prompt
with the following syntax:

  register("User name", "Key");

If everything worked fine, MuPAD prints that the memory limitation has been
removed. All subsequent starts then print that this is a registered version.
You can even install your own MuPAD initialization file that is executed at
each start of a MuPAD session. Simply set your HOME environment variable to
the directory where the initialization file resides, both forward slashes
and backward slashes are allowed as path separator characters. This should
be done in your CONFIG.SYS file, too. The name of the initialization file
must be .mupadinit without an alternative.

6. Have fun viewing the documents using a DVI previewer
=======================================================

You can view the documents containing technical information if you have
installed a TEX program package including a DVI previewer. I recommend emTEX,
(works on DOS and OS/2) available via anonymous ftp in these directories:

  ftp://ftp.uni-paderborn.de/msdos/emtex/dist
  ftp://ftp.dante.de/pub/tex/systems/msdos/emtex
  ftp://ftp-os2.cdrom.com/pub/os2/tex/emtex

If you have installed emTEX, you can adapt the script file mupaddoc.cmd in
the D:\MuPAD\bin directory to your system to view the documents. This has
to be done differently for different systems. We can give you no advice how
to do that, you must figure it out yourself. The basic facts are that the
DVI documents reside in share/doc/hytex and the needed fonts reside in
share/doc/hytex/fonts relative to the MuPAD base directory.

But if do not have a DVI previewer, you can save lots of disk space by
deleting the files and subdirectories of directory share/doc/hytex
relative to the MuPAD base directory.

7. Known bugs specific to the OS/2 terminal version
===================================================

Very few MuPAD functions like that of the profiler create temporary files,
and they are always created in the /tmp directory of the current drive.
The OS/2 terminal version of MuPAD does not pay attention to the TEMP and
TMP environment variables. If you want to use functions creating temporary
files, you must have a /tmp directory on the actual drive when you start
the OS/2 terminal version of MuPAD, otherwise you will get error messages
telling you that temporary files cannot be created.

END OF DOCUMENT