home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 27 Fixes20
/
27-Fixes20.zip
/
wfdesk.zip
/
install.doc
next >
Wrap
Text File
|
1994-07-27
|
10KB
|
210 lines
===============================================================================
IBM* WorkFrame/2* INSTALL.DOC file:
This file provides instructions on how to handle WorkFrame/2
installation errors.
IBM WorkFrame/2 Version 2.x
(C) Copyright IBM Corp., 1991,1993,1994 All Rights Reserved
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
===============================================================================
CONTENTS
________
1. Installation Errors
2. Using WFDESK.CMD
1. INSTALLATION ERRORS
______________________
Just before phase 1 installation ends, or during phase 2, you may
get errors about initialization files that could not be modified,
objects that could not be created, or the install ceases and the
status window shows no activity for a very long period of time.
NOTE: Before you reboot between phase 1 and phase 2 of the install,
it is important to minimize the number of programs that are
running after the machine is rebooted. Phase 2 will have a
better chance of succeeding if other programs (such as an
anti-virus scanning program) are not running during the
install.
Phase 1 Errors
--------------
If you experience an error before the end of phase 1, indicating
that initialization files could not be updated or that the phase 2
startup object could not be created, use the WFDESK.CMD command
file to start phase 2. Follow the instructions under the "Usage"
section in "2. Using WFDESK.CMD" below. Skip steps 2-5 and start
from step 6.
Phase 2 Errors
--------------
If you experience an error in phase 2, wait for all disk activity to
end and then select the Retry push button on the message box.
If after selecting Retry twice, the installation continues to fail,
you may be encountering a known bug in the OS/2* WorkPlace Shell*
(WPS). Select the Cancel pushbutton to abort the installation, then
try the following to correct the problem:
1. First, invoke WFSETUP.EXE from the OS/2 command line.
2. From the "Options" pulldown, select "Selective setup".
3. In the "Source path" entry field, enter the path where
the WorkFrame/2 files are installed.
4. Deselect the "Copy files" and "Update CONFIG.SYS" checkboxes.
5. Ensure that the "Update Desktop" checkbox is selected,
then press "OK".
6. Close down the WFSETUP program, then shutdown your system. When
you reboot, phase 2 of the Setup program should start.
If you still experience failures, try opening the WorkFrame/2 folders
as they are being created (for example, the WorkFrame/2 main folder
and the Actions Profiles folder), as this seems to help the
installation procedure somewhat.
There is an alternate phase 2 install command file you can use if you
still have problems getting WorkFrame/2 installed. For instructions
on how to run this command file, please read the following information
in "2. USING WFDESK.CMD".
2. USING WFDESK.CMD
___________________
The WFDESK.CMD command file was developed as a work-around to an OS/2
problem that occurs when creating Workplace Shell objects. During
the WorkFrame/2 phase 2 installation, many WPS objects are created and
sometimes failures occur on very slow machines.
Description of the problem:
--------------------------
When WPS receives a request for a WPS object to be created, it immediately
indicates that the object has been created, but actually passes the request
onto another thread. Using this object before it has been fully
instantiated will cause errors during WorkFrame/2 phase 2 installation.
To date, there is no known method to determine whether or not the object
has been fully instantiated before updating it. The problem is
particularly noticeable on slow machines with lots of disk activity.
To alleviate the problem, WFDESK.CMD adds an optional timing delay before
each object is updated to make sure that it has been fully created.
Usage:
-----
Before using WFDESK.CMD, it is recommended that you completely remove all
WorkFrame/2 objects and reboot your system. To remove WorkFrame/2 objects
(this procedure is also described in the READ.ME file shipped with the
product):
1) Create a new Desktop folder - Open the Templates folder and create
a folder object on the Desktop (drag and drop); open the new folder.
2) WorkFrame/2 templates - Move all WorkFrame/2 templates to the new
Desktop folder (Action Log, Actions Probile, WorkFrame/2 Composite
Project, WorkFrame/2 Project).
3) WorkFrame/2 folder - Move the WorkFrame/2 folder to the new Desktop
folder.
4) Delete the new Desktop folder. (If this does not delete all the
objects, delete the actual object file from the command line. The
file should be under the Desktop subdirectory on your boot drive and
the file name should be similar to the name of the Desktop object).
Refresh the Desktop. Ignore any warnings indicating that an object
could not be deleted.)
5) Reboot.
Now you are ready to attempt WFDESK.CMD to complete WorkFrame/2 phase 2
installation:
6) Copy both WFDESK.CMD and WFSETOPT.EXE to your WorkFrame/2 installation
directory created during phase 1 (e.g., C:\IBMWF).
7) Stop all unnecessary programs - this is VERY important, particularly
on slow machines.
8) Invoke WFDESK.CMD only from the directory where WorkFrame/2 is
installed, as follows (otherwise it will not work correctly):
WFDESK.CMD boot_drive wf2_directory [pause_time]
where:
boot_drive = drive where OS/2 is installed (e.g., C:).
wf2_directory = full path name where WorkFrame/2 is
installed (e.g., C:\IBMWF).
pause_time = number of seconds to pause between system
commands (e.g., 5).
For example, if OS/2 is installed on drive C: and WorkFrame/2 is
installed on D:\IBMWF and you want a pause time of 7 seconds:
WFDESK.CMD C: D:\IBMWF 7
Important Notes:
---------------
- The pause time is the period of time that the command file will pause
between creating an object and setting its data. A longer pause time
increases the chances of a successful installation.
On very slow machines, a pause time of up to 15 seconds may be required
(5 to 10 seconds will usually work on most machines). The default pause
time is zero seconds; this will usually work on most 486 machines.
- There are two types of errors that could possibly come up: fatal and
non-fatal errors.
- A fatal error will cause WFDESK.CMD to terminate. In this instance,
you should delete any objects already created (as above) and rerun
WFDESK.CMD. Ensure no unnecessary programs are running and increase
your pause time.
If you receive a fatal error while WFDESK.CMD is attempting to write
to the IBMWFV2.INI file, you must reinstall WorkFrame/2 again
starting from phase 1. IBMWFV2.INI is created during phase 1
installation, but is sometimes removed if a failure occurs during
phase 2. To rerun phase 1 so that phase 2 is not run automatically
after a reboot, do the following:
a) Remove any existing WorkFrame/2 objects as described above.
b) Install WorkFrame/2 using WFSETUP.EXE from your installation
medium (CD ROM, diskette, or LAN) and let phase 1 complete,
but do NOT reboot.
c) Delete the "Invoke WF/2 Install Phase 2" object in the
OS/2 System - Startup folder.
d) Reboot.
e) Invoke WFDESK.CMD as described above (WorkFrame/2 phase2
installation).
- A non-fatal error will NOT cause WFDESK.CMD to terminate; WFDESK.CMD
will continue to run, but report an error. Two types of non-fatal
errors are reported:
a) Deregistration of object classes - The classes may not have been
registered and thus do not need to be deregistered. You may ignore
this error.
b) Writing action option settings to the sample projects - The
invocation of WFSETOPT.EXE may fail while trying to write action
option settings to the sample base projects. This error means
that the sample projects have been created, but their options
could not be set. In this case, they will use the default options
settings for their actions.
* IBM, WorkFrame/2, WorkPlace Shell, and OS/2 are registered trademarks of the
IBM Corporation.