DJ> UO> this is time-consuming and error prone. besides, I don't see why WF 2.1
DJ> UO> as installed wouldn't support the common need for both resource and C++
DJ> UO> compiling actions within the same project.
DJ> UO>
DJ> UO> I do believe I remembered to install Workframe before the toolkit
DJ> UO> (otherwise I don't think I'd have the IBM Toolkit actions profile in
DJ> UO> the action profiles folder.) and I _have_ applied the WF21_2 CSD.
DJ>
DJ> did you remember to run addtool?

Do read the subject line.  Addtool was a feature of Work Frame 1.1,
and has nothing to do with WF 2.1 (thank goodness.)  In fact, Work
Frame 2.1 is  so different from 1.1, you wouldn't recognize it as the
same program.  It has been completely reworked to work as a set of
Workplace shell methods.

I have found the answer to my problem:  I create a new actions profile
from the templates folder, drag and drop actions from both the IBM C++
tools actions profile and the IBM Toolkit actions profile (holding down
CTRL for copy.)  And use the new actions profile for my projects.

Now I have another problem: after running make on the project folder,
and editing a few files to fix errors, the system becomes very sluggish
(much more so than using the command line, and even though Resource
Monitor reports 4 meg RAM free.)  Eventually, there is an access
violation trap on a detatched process, and then PM crashes.  I can
never shutdown, but sometimes I can use C-A-D, and sometimes I must
power off.  I have installed all of the latest CSDs for Workframe
(WF21_2), The compiler (CTC0010), and the compiler utilities
(csetu002.)

Any suggestions, anyone?  I'm hooked on WF 2.1, after abandoning 1.1,
but this latest bug makes it nearly unusable.

--Uche

 þ KWQ/2 1.2g þ I write, I wrote, I have rotten.


--- WM v2.04/92-0551