(Excerpts from a message dated 12-06-99, Will Honea to Kees Bergwerf:
original topic: not enough disk space):

Hi Will--

WH>Theseus5 is working on multiple machines here with Warp 4, fp9-12,
  >and Warp 3, fp38 or 40.  Better be - I rely on it.  I never got
  >os2memu to work after fp8 or so and agve it up...

     Couple of quick queries, and one not so quick:

    Some Warp 3 FixPak around 10 killed OS20MEMU.  It was revived for
Warp 4 with a patch I got from Hobbes based on advice from
devcon@ibm.net at the time (name of patch not recalled, but the file
OS20MEMU.DLL in my OS2MEMU folder is dated 9/12/96; all the other files
are dated in '94).  I am now running it under Warp 4, FixPak 5.  Are you
saying that os20memu died again on a later Warp 4 FixPak?  If so,
another good reason to not "upgrade" if I don't have to :-).  If its
only death to date was in Warp 3, I have no worry since both of my
machines are running on Warp 4 FixPak 5.

    I am using Theseus 3 (theseus5.sys in config.sys).  Do you really
mean you are using a later version, Theseus 5, or was that a slip of the
fingers?  If you meant it, where did you get it?

    I am also still running OSRM2 Lite, which uses theseus2.sys as a
driver to run a working set analysis.  The output doesn't agree with
that given by Theseus 3; it appears that OSRM2 doesn't show the shared
system memory.  I think I will give up the disk space taken up by OSRM2
since the vendor has apparently vanished and I now have Theseus 3.  The
results shown by OSRM2, OS20MEMU, and THESEUS 3, for "owned memory" are
all different, and I haven't the slightest idea of which one (if any) is
"correct" :-(.  In general, I use OS20MEMU only for quick checks on the
effects of coding changes (mostly for multithreaded programs) on memory
usage.  Any comment?

    Regards,

        --Murray

___
 * MR/2 2.25 #120 * If it ain't broke, don't FixPak it.

--- Maximus/2 2.02