* Original Area: comp.os.os2.programmer.tools
* Original To  : Aglynn{at}Ibm.Net (1:202/1207)

 a> Are you running HPFS386 by any chance?  WF/2 3.0 has
 a> serious problems on my
 a> system if I run HPFS386, returning to standard HPFS
 a> mysteriously solves all the
 a> problems.  This is with Warp Connect and LS 4.0A GA.

After returning to HPFS and finding that all the project settings and
actions that had disappeared suddenly reappeared, I conclude that you are
correct.  Workframe/2 3.0 appears to be incompatible with HPFS386 from LAN
Server 4.0 Advanced.

I installed all of the new VisualAge C++ CSD's, including CTW301 and found
that the incompatibility persists.

I then installed the LAN Server 4.0 ServicePak IP08150 and found that this
appears to correct the incompatibility with HPFS386. Now when I boot up
with HPFS386, project settings and actions are still available. 
Workframe/2 3.0 also doesn't open really slowly like it did with HPFS386
from LS4.0 GA.

 a> I have reported the problems to IBM, but haven't heard
 a> back, other than the
 a> suggestion to try Warp Server Beta instead.

My suggestion is to install LAN Server 4.0 ServicePak IP08150. You can get
it off of ftp.pcco.ibm.com in the pub/corrective_service directory.  Look
for files LS4TOOL1.DSK, LS8150B1.DSK, LS8150B2.DSK,LS8150B3.DSK, and
LS8150B4.DSK.

I found that I had to manually unpack the new CACHE386.EXE
program from the LS8150B3.DSK image.  Use:

    UNPACK A:\FIX\SRV.2\CACHE386.EX_

This will write CACHE386.EXE to the current directory.
The other files appeared to be updated OK, but if you
want to try it manually then you'll need to unpack
the files on disk #4 in the \FIX\HFS.3 directory.

So far I have only had this installed for a few minutes,
but it does appear to have corrected the problem so far.
After using this new HPFS386 version for a few days,
I'll post another message about whether or not it
still appears to correct the incompatibility with WF/2 3.0.

--- Maximus/2 2.02