home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IBM Presents OS/2 Software Hits 1995
/
OS-2_SW_HITS_2ND_EDITION_1995.ISO
/
i17
/
wf2fix21.dsk
/
READ.ME
< prev
next >
Wrap
Text File
|
1994-06-03
|
25KB
|
600 lines
===============================================================================
IBM* WorkFrame/2* READ.ME file:
IBM WorkFrame/2 Version 2.1, CSD2
(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.
===============================================================================
Note: This CSD only applies to Version 2.1 of the WorkFrame/2 program
CONTENTS
________
0. Fixes contained in CSD1 and CSD2
1. Prerequisites
2. Installation
3. Installing from a CD-ROM
4. Reinstallation
5. Migration from previous versions of IBM WorkFrame/2
6. Tutorial
7. WorkFrame/2 Considerations and Notes
8. Considerations and Notes for Using Other Products
_______________________________________________________________________________
0.1 Fixes contained in CSD2
___________________________
| CSD2 contains all fixes in CSD1, as well as the following:
| Base Projects
| _____________
| * (22297): Base project template does not recognize the changes
| made to its default settings so that when a base project is
| created, settings revert to the default.
|
| * (22302): Base projects lose their icon view settings.
|
| * (22333): Closing the base project Settings notebook on the Target
| page sometimes locks the system.
| Monitor
| _______
| * (23330): Double-clicking on file names to invoke EPM does not
| work as expected when file names are unqualified, or when they
| are mixed- or lower-cased.
| MakeMake
| ________
| * (22300): Start button not disabled while make file is being generated.
| * (22330): MakeMake doesn't have the C Runtime messages bound to it,
| so when it hangs, no register information is shown.
| IBM Library Manager
| ___________________
| * (22218): The IBM Library Manager fails when duplicate object file
| symbols are found while combining extremely large libraries.
| * (22225): The IBM Library Manager outputs an erroneous warning
| "Duplicate symbol...ignored" when an input library contains an
| exported name (EXPDEF) that is an alias for an internal (PUBDEF)
| name.
| Default Options DLL - DDE3DEF2.DLL
| __________________________________
| * (22326) and (22324): When parsing resource files for dependency
| information, DDE3DEF2.DLL does not remove the optional quotes
| from filenames or respect comments prefixed by "//".
| * (22316): When parsing resource files, DDE3DEF2.DLL finds
| include files where it shouldn't.
| Other
| _____
| * (23912): SomMethodDebug calls have not been removed from
| the source.
| * (22314): Mask matching fails in some cases for HPFS file names.
| * (22329): The WorkFrame/2 program makes an invalid assumption
| about variable string formats that causes MakeMake to hang and
| the Monitor to trap when actions are invoked.
0.2 Fixes contained in CSD1
___________________________
Projects and Composite Projects
_______________________________
* (CK01807) and (CK01813): Updates to the actions profile may not
be reflected when you open the Actions page in the Settings
notebook of a project.
Actions Profiles
________________
* (CK01759) and (CK01801): Help for the dialog used to add or
change an action may fail if an error message is displayed as the
dialog is appearing.
IBM Library Manager
___________________
* (CK01772): The IBM Library Manager will lock the system when an
object file is dragged.
* (CK01781): Cannot close the IBM Library Manager after closing
the Errors window from the System Menu icon.
* (CK01839): PMLIB hangs when you cancel the confirmation dialog,
with the help panel active.
MakeMake
________
* (CK01818): Incorrect makefile built if both the "Depend on
project" and "Depend on Makefile" options are selected.
* (CK01815): The MakeMake tool may lock the system if the working
directory of a base project is changed while MakeMake is active.
Monitor
_______
* (CK01822): Invoking the editor from the monitor box highlights
all errors listed, not just those from the most recent action.
Other
_____
* (CK01796): Invoking the DDE3MSGB.EXE tool, (called Message Bind
Plus) in the Toolkit actions profile, on a nonexistent message
file will cause the tool to abnormally end.
* (CK01860): Some vendor (version 1) compiler option DLLs did not
work.
1. PREREQUISITES
________________
A) OS/2* Version 2.1 product.
B) There are several fixes to the OS/2 product that are strongly recommended.
| * Fixes contained in the OS/2 Version 2.1 ServicePak (also known
| as OS/2 Version 2.1.1).
| * If you do not wish to install the OS/2 Version 2.1 ServicePak,
a patch is available that fixes a shutdown problem with OS/2, and
several problems with WorkPlace Shell*. This fix is available
on-line from several networks, and is distributed as 21WPSF.ZIP.
The fix can also be obtained by contacting the IBM support
center, and asking for a fix to APAR PJ08727.
If you do not have this fix installed, please ensure you allow
the shutdown to complete fully, especially during installation of
the WorkFrame/2 product. This may take several minutes to
complete.
|
In North America, you can dial 1-800-237-5511 to contact the
support center.
| C) To install CSD2, you must have WorkFrame/2* Version 2.1 installed.
| You do not have to have CSD1 installed to install CSD2. All fixes
| are cumulative.
2. INSTALLATION
________________
| CSD2 Installation
| _________________
| Installing CSD2 is not a complete install of the WorkFrame/2 product.
| You will not lose any data or settings. Only product files that
| need the fixes are replaced. Do NOT uninstall WorkFrame/2 before
| installing CSD2. To install CSD2:
| 1. Insert the CSD2 diskette in your A: or B: drive.
| 2. Change to the A: or B: drive, then type WFUPDATE to
| run the CSD2 installation program.
Installation Order
__________________
If you are installing the products contained in the IBM C Set ++*
package, the preferred order of installation is:
1. IBM Developer's Toolkit
2. IBM WorkFrame/2 Version 1.1 (optional)
3. IBM WorkFrame/2 Version 2.1
4. IBM C/C++ Tools
5. Other products that are integrated into the WorkFrame/2 product.
If you install the Toolkit after the WorkFrame/2 product, follow
these steps to copy the action for the NMAKE.EXE tool into the
default actions profile. (Do these steps after both products are
installed.)
1. Open the "IBM WorkFrame/2 V2.1" folder.
2. Open the "Actions Profiles" folder.
3. Open the "Default Actions Profile" and the
"IBM Toolkit Profile".
4. In the "IBM Toolkit Profile",
select the action with class MAKE and name NMake.
5. Hold down mouse button 2, press the Ctrl key, and
drag the action to the Actions list in the
"Default Actions Profile".
A copy of the action will appear in the default actions profile.
6. Close both actions profiles and the "Actions Profiles" folder.
WorkFrame/2 Installation
________________________
The installation program consists of two phases, and requires you to
reboot between them. If you are re-installing on top of an existing
copy of WorkFrame/2 version 2.1, you will also be required to reboot
following the installation.
Before installing WorkFrame/2:
1. Close any applications you do not need running.
2. Avoid doing any computer work while the product is installing.
Do not minimize the Setup program while it is running.
Installation Errors
___________________
During phase 2 of installation, you may get errors about objects that
could not be created or about initialization files that could not be
modified. If this happens, 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 bug in the OS/2 WorkPlace Shell.
| You can use an alternate installation program, that attempts to
work-around this problem.
First, select "Undo installation..." from the "Options" pull down.
Next, exit the WFSETUP installation program and start the WF386
program. This program will repeat phase 1 of the installation and
then ask you to reboot your machine. Before you reboot, try to
minimize the number of programs that are running after the machine
is rebooted. Phase 2 will have a better chance of success if other
programs (such as the IBM AntiVirus scanning program) are not running
during the install.
3. INSTALLING FROM A CD-ROM
___________________________
You can install the WorkFrame/2 product from the IBM C Set ++ CD-ROM.
Start the installation by going to the OS2WF21 directory on the
CD-ROM and entering "wfsetup" (or "wf386" if appropriate -- see
"Installation Errors" above).
If you want to create WorkFrame/2 diskettes, you will find the diskette
images in the IMAGE\IBMWF21 directory. DISK1.IMG and DISK2.IMG are the
first and second diskettes respectively. Use the LOADDSKF utility
shipped on the CD-ROM to create the diskettes from the images.
Note that you cannot run the WorkFrame/2 product from the
CD-ROM, only install it.
4. REINSTALLATION
_________________
If you want to reinstall the WorkFrame/2 product, you can start the
Setup program from the WorkFrame/2 folder. Alternatively, to start the
program from the command line, go to the directory where you installed
the WorkFrame/2 product and enter "wfsetup" (or "wf386" if you used that
program to install the first time).
1. Besides updating the CONFIG.SYS and copying files to your machine, the
WorkFrame/2 installation program also registers WorkPlace Shell classes
with the OS/2 Desktop. Before reinstalling the WorkFrame/2 product, you
need to deregister any WorkFrame/2 classes registered in a previous
installation. To do this, select "Undo installation..." from the
"Options" pull-down in the WorkFrame/2 Installation program. Then you
can remove the WorkFrame/2 templates created in the Templates folder by
following the instructions in step 2.
You do not need to remove the WorkFrame/2 entries in CONFIG.SYS;
they will be handled by the installation program when you are
reinstalling.
2. Each installation of the WorkFrame/2 V2.1 product generates a new set of
WorkFrame/2 templates in the Template Folder on the Desktop. By
generating a new set, the WorkFrame/2 product avoids writing over
templates that you customized. However, if you did not customize the
original templates, the new ones will be duplicates. To delete
duplicate templates, complete the following steps before reinstalling
the WorkFrame/2 product:
1. Open the "Templates" folder.
2. Drag the "Folder" template to the Desktop to create a new folder.
3. Open the new folder you just created.
4. Open the pop-up menu of one of the WorkFrame/2 templates
and select the "Move..." item.
5. When the "Move" dialog appears, select "Folder" as the
destination. Then select the "Move" push button.
The template will be moved to the new folder.
6. Move the other WorkFrame/2 templates to the new folder using
| the same steps detailed above. Do not worry about duplicate
| names.
| 7. Close the "Folder" object. From the OS/2 command line, move
| to the \Desktop directory on your boot drive. Remove the
| \Folder subdirectory, first deleting its contents. Ignore
| any warning messages telling you that one or more objects
| could not be deleted.
5. MIGRATING FROM PREVIOUS VERSIONS OF WORKFRAME/2
___________________________________________________
The Setup program has a utility which eases the migration from
projects created by previous versions of the WorkFrame/2 product.
To invoke this utility, select "Migrate" from the "Options" pull-down
in the Setup program.
Note that when projects are migrated along with their associated language
profiles, the names of the compiler and linker Options DLLs are
not changed. Because this version of WorkFrame/2 supports more
powerful interfaces to options DLLs, you may want to replace
the Options DLL used for an action in the migrated project
with a newer version, if one is available.
| If you migrated the C Set/2 compiler and linker, replace the DDE4CSET
| and DDE4ICC options DLL's (for the Compile action) with the new DDE4ICC2
| Options DLL. Replace the old linker Options DLL, DDE4ICL, with DDE4ICL2.
| Set Options DLLs for an action in the action's Settings notebook, on
| the "Options" page, after you have finished migrating your projects.
| Note that when you change to a new DLL for an action, you will have
| to re-enter the options for that action.
| If you are using the IBM C/C++ Tools compiler (bundled with C Set ++),
| these Options DLLs will already have been set for you if you installed
| C/C++ Tools after installing WorkFrame/2 Version 2.1.
6. TUTORIAL
___________
Once you have read the Introduction booklet, you will want to
continue with the IBM WorkFrame/2 Tutorial (found in the WorkFrame/2
Information folder). The first part of the tutorial contains an
on-line version of the Introduction booklet. The last part takes you
step-by-step through a sample software project.
While doing the tutorial, keep in mind the following:
1. The latter part of the tutorial describes using the EPM editor in
conjunction with the Monitor window. Some steps may not work for
the reasons described in the "Error context help in EPM" section below.
2. The CLC sample is only meant to be used in conjunction with the
tutorial. Do not change it in any way other than through the tutorial.
3. The figure in Lesson 12 shows both a make file and a dependency file
in the MakeMake Results window. Typically, no dependency file will
| actually be created using the IBM C Set ++ compiler during the
| lesson.
4. As you do the tutorial, you may run into General Protection Violations
caused by the IBM C Set ++ compiler (in DDE4CPP.EXE). Simply end the
program and continue; the violations do not affect the outcome of the
| tutorial. The problem is corrected in the latest fix level for the
| IBM C Set ++ compiler.
7. WORKFRAME/2 CONSIDERATIONS AND NOTES
________________________________________
General
_______
* Some components of the WorkFrame/2 product may not adopt system-wide
settings, such as colors. (CK00794)
* If you use the "Undo installation..." option of the setup program, you
may encounter messages saying that some objects and folders cannot be
removed. You can ignore these messages. (CK01548)
Setup
_____
* Do not minimize the Setup program when it is running or you may not
be able to maximize it again. (CK01684)
Projects and Composite Projects
_______________________________
* You can use Universal Naming Convention (UNC) names to specify the
locations of files in the Directories list on the Source page of a
base project's Settings notebook. However, the directory specified
as the project's Working Directory must follow the standard FAT or
HPFS naming format.
* Renaming base projects within a composite project and then selecting
an action from the composite project's pop-up menu may cause errors.
Before selecting the action, respecify the contents on the composite
project's Target and Sequence pages to reflect the new project names.
(CK01596)
* In the WorkPlace Shell environment, a common method of creating
duplicate objects with common settings is to make them from a template
with those settings. This technique generally works with WorkFrame/2
objects, except for the setting on the Profile page of a project's
Settings notebook. (CK01783)
* Do not rename or move a base project while the Monitor window is being
used to run an action for that project. (CK01811)
IBM Library Manager
___________________
* Do not drag objects from the IBM Library Manager to the "Drive A:"
icon or folder if there is no diskette in drive A:. Doing so causes
the mouse pointer to change into the "busy" icon until another object
module is moved. (CK01104)
* Selecting Esc on a help panel describing the IBM Library Manager
Settings notebook causes the focus to be misplaced. Click on
the Settings notebook to return the focus to it. (CK01803)
Moving and Renaming WorkFrame/2 Folders
_______________________________________
Different components of the WorkFrame/2 product need to be able to
locate each other as the product is being used. Some of the files are
stored in the operating system's DESKTOP directory and can be renamed
or moved using the WorkPlace Shell interface. If you do use the
WorkPlace Shell interface to move the WorkFrame/2 icon into a folder
or rename the icons that are part of the WorkFrame/2 product, do the
following to avoid errors:
1. Find the Default Actions Profile, open it, and then close it.
Doing this lets the other active WorkFrame/2 components know where
this action profile is located.
2. If you change the Desktop location of an actions profile, the base
projects using that profile may not be able to find it. If this
happens, locate the actions profile on the Desktop and open the
Profile page of the project's Settings notebook. Drag the actions
profile into the field where the Profile is specified on the
notebook page.
MakeMake
________
* The MakeMake utility is intended to create a useful first draft of a
make file that can be used with the Toolkit's NMAKE utility. Not all
subtleties in the build process can be accounted for, so you may
need to change the make file produced by MakeMake.
* When you use MakeMake to build a very large make file, the make file may
not be displayed correctly in the MakeMake Results window. However,
the make file will be saved correctly. (CK01789)
* Do not rename or move a base project while the MakeMake tool is being
used to create a make file for that project. (CK01810)
* When the option "Separate dependency file" is selected, the MakeMake
utility will create a separate dependency file only if there is data
to put into it.
Other
_____
|
* The LINK entry point in the default options DLL (DDE3DEF2.DLL)
truncates some library names to 8 characters. (CK01794)
8. CONSIDERATIONS AND NOTES FOR USING OTHER PRODUCTS
____________________________________________________
IBM C Set ++ Compiler
______________________
* The IBM C Set ++ compiler may cause General Protection Violations
(GPVs) when running in the WorkFrame/2 environment.
| These are caused by preloading the compiler, and is fixed in
| a CSD (CTC0008) of the C Set ++ compiler.
The GVP can be ignored; compilation of your program is not affected.
If you have not installed the latest compiler CSD fix, you can
avoid the GPVs, by specifying the /TL- compiler option to tell
the compiler not to preload itself. To specify this option,
deselect "Preload compiler components" on the "Other" page of
the compiler options dialogs. Alternatively, you can set
AUTOFAIL=YES in your CONFIG.SYS file to not display the GPV screens.
Toolkit Message Bind (MSGBIND)
______________________________
* To bind all the messages in a .MSG file to an executable file,
use the "BIND::Parse and bind messages" action from the Toolkit
actions profile. This is the equivalent to the WorkFrame/2 v1.x
Message Bind action.
If you want to bind only some of the messages, you must create
the MSGBIND response file yourself, and use an extension of .RSP
for this file. You can then run the "BIND::Messages" action
against the .RSP file.
PL/I Support
____________
* If you are using the IBM PL/I product, do not run the PL/I compiler in
more than one Monitor window at a time. Due to a problem in the
IBMWF.DLL file (shipped with the IBM PL/I product), the DLL can cause
either a General Protection Violation or hang the operating system.
Make sure that "Multiple, concurrent monitors" is always
deselected on the Monitor page of the Settings notebook
of PL/I projects.
EPM
____
* Dragging a single error from a Monitor window to the EPM editor may
not always result in the editor's cursor being located at the error.
When this happens, double-click on the error to move the editor's
cursor. (CK01672)
* Dragging more than one file from a base project to the EPM editor will
cause the editor to end abnormally. Instead, select the "Edit -> EPM"
action from the pop-up menu of one of the files. (CK01312)
* Dragging an error line from the Monitor window to the EPM editor's
title bar will cause EPM to end abnormally. (CK01314)
Linking
_______
Temporary response files are created regardless of whether the
WorkFrame/2 product directs the linking to be done in the WorkFrame/2
Monitor, an OS/2 Window, or in OS/2 full-screen mode. If the linking
is done in an OS/2 Window or full screen, the WorkFrame/2 cannot delete
the response files.
SOM
___
If you have SOM Version 2.0 (the SOM Objects Developer's Toolkit)
| installed, make sure you upgrade to SOM Version 2.01 before
| installing WorkFrame/2 Version 2.1.
Using both the SOM Version 2.0 product and WorkFrame/2 Version 2.1
| will cause multiple software errors. There are no restrictions
| on using SOM Version 1.0 (the version included with OS/2 Version 2.1)
| with WorkFrame/2 Version 2.1.
TRADEMARKS AND SERVICE MARKS
____________________________
The following terms, denoted by an asterisk (*) in this README, are
trademarks or registered trademarks of the IBM Corporation in the United
States or other countries:
C Set ++
IBM
OS/2
WorkFrame/2
WorkPlace Shell.