🚀 go-pugleaf

In article <19NOV92.12501962@wl.aecl.ca>,
tranx@wl.aecl.ca writes:
>
>Subj:   Problem with WorkFrame on OS/2
>
>I am using WorkFrame/2 for wirting an application for OS/2. But everytime
>I go to option "Action" and select "Make". I receive the error message like
>"Unable to open message file". I don't know why. I put c:\ibmc\bin,c:\toolkt20\
>os2bin , set include=c:\toolkt20\os2h;c:\ibmc\include in the path. And I also
>run "csetenv.cmd" to make sure the path was set-up right. But it doesn't help.
>Could anybody help me out? Thanks
>

"Unable to open message file" when running what command?  NMAKE itself,
or some command (ICC) started by NMAKE?   If you're not sure your
environment is setup correctly, create a TEST.CMD file, containing only
"SET".  Add that as a background tool, and run it -- it will list
the entire environment.  You should be able to use that information,
together with which tool is actually failing, to narrow down the cause.

One possibility: You say you're running CSETENV to set the environment
up -- are you then starting WorkFrame from the same session (which is
correct), or are you running CSETENV in one window, and then starting
WorkFrame from another, or from the icon (which would be incorrect,
in this case -- you have to start it from where the environment has been
setup).    -tim