home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: OtherApp
/
OtherApp.zip
/
maul123.zip
/
MAULINST.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
2000-03-27
|
13KB
|
307 lines
ΓòÉΓòÉΓòÉ 1. Maul Installation ΓòÉΓòÉΓòÉ
Welcome to the installation utility for Maul Publisher.
IMPORTANT INFORMATION
In case of difficulties getting either this install utility, or the main
program to run, please read the following
If the install utility won't run
If Maul Publisher won't run
Requirements
Maul must be installed on an HPFS partition, or better. The program
requires long filename support.
You must also have multimedia installed. The multimedia extensions are
used to import various bitmap formats, and should be installed even if
you don't have a soundcard. Without them, Maul will not run.
You must have a printer of some kind installed, even if it's only the
'IBMNULL' printer.
You must have a screen resolution of at least 1024x768, or you will not
see some of the status messages.
Notes
If you are reinstalling over an earlier version, and you wish to change the
installed path, or help path, you should uninstall the previous version before
performing an install. If you are a registered customer, you will need to
re-enter your registration information.
If you do not wish to change the installed path, use the advanced
installation, and make sure that the help path is correct before installing.
This install program logs the installation process in a file called
'install.log'. This file is found in the path where this installer was run. If
Maul Publisher does not run, have a look to see if a file called 'error.log'
was generated in the path where Maul was installed. Both log files may be
required if you have trouble installing Maul Publisher. No 'error.log' file
will be created if Maul runs correctly.
For more information about Maul's error logging system, have a look at the
'Using Maul Publisher' manual after the installation has finished.
This program can uninstall as well as install or maintain Maul Publisher. You
should therefore keep this program available, and not delete it. You can run
this program from within the Publisher's own directory. Please make sure that
this help file (maulinst.hlp) is kept in the same path as this program.
Additional release notes
Additional release notes are contained in readme.1st. This file is found in
the original zip file.
Close this help panel to continue...
Created by Peter Koller, Maison des Anglais, Trebuon, 29530 Plonevez du Faou,
France.
Maul Support <maul@manglais.com>
Γòò Peter Koller 1999 - 2000, All Rights Reserved
ΓòÉΓòÉΓòÉ 1.1. If the install utility won't run ΓòÉΓòÉΓòÉ
Known problems
On some OS/2 systems, the utility 'unpack.exe' can get destroyed or altered.
You either can use the 'Seek and scan files' utility supplied with OS/2 or
'Find...' on a popup menu to look for unpack.exe. You should not have, under
any circumstances, a version of unpack containing anything other than 72048
bytes. Some versions of Netfinity use a version of unpack.exe containing
something like 77200 bytes. If this file is in the path before the system
supplied path, this install will fail with 'Failed install:01 id = 70 rc = 2'.
The Warp4 distribution has a working version of unpack in the path
'?:\OS2IMAGE\DISK_3' where the ? is your cd rom drive with Warp4 in it. On
Warp3 the same file is found on '?:\OS2IMAGE\DISK_2'.
The correct 'unpack.exe' should be in the \os2 subdirectory of your boot drive,
and nowhere else. It's size should be 72048 bytes, and nothing else.
Other problems
The uninstall path may not be able to uninstall everything correctly. This is
particularly true if you have used the product, and created files that the
uninstaller does not know about. Once the uninstall has run, you may wish to :-
Delete the path added to the 'path=' statement in config.sys, although
this has no detrimental effect.
Delete the directory to which maul was installed, along with all the
subdirectories.
Getting Help
This install program logs the installation process in a file called
'install.log'. This file is found in the path where this installer was run.
If you cannot find the help required here, please email Maul Support
<maul@manglais.com>, with a copy of the 'install.log' file.
See also:- If Maul Publisher won't run
ΓòÉΓòÉΓòÉ 1.2. If Maul Publisher won't run ΓòÉΓòÉΓòÉ
The program won't run
First, make sure that multimedia is installed, even if you don't have a
soundcard. The multimedia extensions are used to import various graphics file
formats, including GIF and JPEG. Installing multimedia has the added advantage
that the operation system recognises the graphics file types, and opens them
with a double click. If you don't have multimedia installed, the program will
fail with an '@DosLoadModule' error.
There is a problem on some OS/2 systems with a corrupted printer list. Once
Maul opens a printer device context, the runtime library gets corrupted, and
the program fails. The failure always occurs when loading a handler list.
The most common messages for this error are:-
@fopen("maul_dll.lst", "r")
@LoadHandlerList
You may get the program to start up correctly by opening the properties
notebook of the 'Maul Publisher' icon, and adding the optional parameter
/nopdc on the Program page, but be aware that this may cause the program to
fail elsewhere, such as when printing, or when attempting to load or save a
stylesheet or master page.
Please note also, that you may have tried a number of other programs, and
found them unreliable, particularly when printing. A surprising number of
people have a corrupted printer list, and are unaware of the problem (Me too,
for a while...). Maul Publisher is by no means the only program affected.
The correct solution is to set all your printers to 'IBMNULL' and to delete,
and then re-install the latest correct printer drivers. To find out more about
how to do this correctly please note the item below.
Other problems
A number of items are listed in the main user manual, 'Using Maul Publisher'.
Have a look at the section called 'Known problems and bugs'. In particular,
read the section on network printing, even if you are not on a network.
Getting Help
If Maul Publisher still does not run, have a look to see if a file called
'error.log' was generated in the path where Maul was installed. No 'error.log'
file will be created if Maul runs correctly.
If you cannot find the help required here, please email Maul Support
<maul@manglais.com>, with a copy of the 'error.log' file.
See also:- If the install utility won't run
ΓòÉΓòÉΓòÉ 2. Choosing an installation mode ΓòÉΓòÉΓòÉ
Basic installation
Unless you wish to update an existing installation, it's probably easier to use
the basic install mode. This mode will update the CONFIG.SYS file where
required. If CONFIG.SYS is updated, you will be asked if you wish to reboot
your machine.
Advanced installation
If you wish to update an existing installation, or you wish to choose what is
installed or where, you can use the advanced installation. In this mode you can
select what to install, and where to install it. You must be careful however,
as this mode is capable of creating an incomplete or non-functional
installation.
Uninstall
If you wish to remove Maul Publisher from your system, select the uninstall
mode. You will be prompted for each category to be uninstalled, so that you can
leave your templates intact, for example. Please take the time to read the
confirmations properly to avoid deleting something you might wish to keep!
ΓòÉΓòÉΓòÉ 3. Basic Installation ΓòÉΓòÉΓòÉ
This mode will perform a complete installation. If there is not enough room on
the current drive, you must change the installation path. Just change the drive
letter to the required drive. The 'Install' button will be disabled until
sufficient space is available.
This mode installs files based on the main installation path. If the main
installation path is 'C:\MAUL' this mode will install files as follows:-
Main program files into C:\MAUL.
Library files into C:\MAUL\BIN.
Additional data files into C:\MAUL\ETC.
Operating manuals into C:\MAUL\INF.
Help files into C:\MAUL\HELP.
This mode automatically creates or updates the desktop objects, and also
updates CONFIG.SYS. If the system requires re-booting, you will be asked to
perform a shutdown when you exit the installer. After the basic install is
finished, you will be returned to the installers main dialog.
ΓòÉΓòÉΓòÉ 4. Advanced Installation ΓòÉΓòÉΓòÉ
This mode will perform a managed installation. If there is not enough room on
the current drive, you must change the installation path. Just change the drive
letter to the required drive. The 'Install' button will be disabled until
sufficient space is available.
In this mode you can choose to use an existing help path for your help files,
as well as for you main istallation path. If you wish to review Maul Publisher,
and then uninstall it, this modification avoids the need to alter the
CONFIG.SYS file. Do not do this unless you are sure of what you are doing.
This mode installs files based on the main installation path. If the main
installation path is 'C:\MAUL' this mode will install files as follows:-
Install Main Program
The installer will always update the main program files, and help files. This
would default to 'C:\MAUL' and 'C:\MAUL\HELP'
Install DLL Libraries
If the item is checked, this installs all the handlers and DLL's in
'C:\MAUL\BIN'. Maul will do nothing if these DLL's are not installed.
Install additional data
If the item is checked, this installs the dictionary and internationalisation
files in 'C:\MAUL\ETC'. These file are required to allow Maul to use a spell
checker and create date and time strings. The path is also used to hold style
sheets and master pages.
Install operation manuals
If the item is checked, this installs the operating manuals in 'C:\MAUL\INF'.
The manuals are the reference works for Maul and Maul's handlers.
Create Desktop Folder
If the item is checked, this creates the necessary desktop objects for Maul
Publisher. Objects are created for all items, even if these items are not
actually installed. If the objects already exist, this mode will simply refresh
the existing objects without changing their current place on the desktop.
Update CONFIG.SYS
If the item is checked, this updates CONFIG.SYS. If the system requires
re-booting, you will be asked to perform a shutdown when you exit the
installer. After the advanced install is finished, you will be returned to the
installers main dialog.
If the item is not checked, the necessary changes are saved to
'C:\MAUL\CONFIG.NEW'. You will then have to manually apply the changes.
Normally the only changes to make are the 'set path=' statement, and the 'set
helppath=' statement.
ΓòÉΓòÉΓòÉ 5. Uninstalling Maul Publisher ΓòÉΓòÉΓòÉ
If you choose to uninstall Maul Publisher, this mode will remove all the files
based on the current configuration.
You will be prompted for each category to be uninstalled, so that you can leave
your templates intact, for example. Please take the time to read the
confirmations properly to avoid deleting something you might wish to keep!
The uninstall mode is not capable of removing entries in CONFIG.SYS. This does
not normally cause a problem, but if you wish to can manually apply the
changes. Normally the only changes to make are the 'set path=' statement, and
the 'set helppath=' statement. Carefully remove the entries pointing to the
installation path.
ΓòÉΓòÉΓòÉ 6. Setting the Installation Path ΓòÉΓòÉΓòÉ
Normally Maul Publisher is installed into '<bootdrive>:\MAUL'. If OS/2 is
installed in C: this will be 'C:\MAUL'. You can alter the installation path to
be anything you like. Please make sure however, that you set a fully qualified
drive and single path, such as 'd:\fred'. In addition, it is probably not a
good idea to install Maul into an existing path, because this can cause files
from other programs to become overwritten. It is safe to install Maul over an
older version.
ΓòÉΓòÉΓòÉ 7. Setting the Help Path ΓòÉΓòÉΓòÉ
This dialog allows you to choose from a limited selection of help paths. The
selection is either an existing help path, or the 'help' subdirectory to the
installation path. If you choose the 'help' subdirectory to the installation
path, the installer may need to update the 'set helppath=' statement in your
CONFIG.SYS file. This will occur automatically unless you have disabled the
option.