Excerpted from message dated 11-25-94, Murray Lesser to David Noon:

  >
ML>    If I weren't so tired of all this, I would attempt to compile and
  >run the REXXUTIL sample that comes with Toolkit 3.0.  I did find out
  >that it wouldn't compile the REXXUTIL sample from Toolkt21 (I ended
  >up with an unresolved external).
  >

Ho, Dave--
    
    This morning, I felt stronger.  So I reinstalled Toolkit 3.0, using
the method that leaves it on the DevCon 5 (special edition) CD-ROM.
(Aside: since I only have a single-speed CD-ROM reader, compiling and
linking is very slow.)  However, by taking a couple of "archives," one
before and one after installing the new toolkit, I can jump back and
forth between the two toolkits at will.

    Before installing WarpTlkt, I compiled the REXXUTIL DLL as written
for WarpTlkt using Toolkt21.  It compiled fine,  Although the prologue
of the C code says to compile and link with MAKE, I only have NMAKE and
NMAKE apparently couldn't read the REXXUTIL.MAK file.  So I did it from
the command line (icc /ge- rexxutil.c rexx.lib rexxutil.def).  Compiled
OK.  REXXUDEM.CMD ran OK.

    Installed WarpTlkt, rebooted (making new archive), compiled and
linked from the command line (WarpTklt's NMAKE couldn't do the job,
either!).  Tried to run REXXUDEM.CMD, which failed on line 50 with error
message to the effect of "improper call statement" (I have forgotten the
exact wording, and I'm not going to go through that process again, just
to find out; I guess my short-term memory is going--must be a sign of
old age!).  Anyhow, line 50 is "call SysLoadFuncs"--not "call
'SysLoadFuncs'."  Note that the same line 50 worked OK when the DLL was
compiled with Toolkt21.  Incidentally, when I copied the WarpTlkt
REXXUDEM.CMD and its associated pre-compiled REXXUTIL.DLL to my hard
drive from the CD-ROM and ran that version, it worked OK; it didn't mind
the missing single quotes.  But then, the DLL I made from their source
code didn't match the DLL furnished on the CD-ROM.

    Of course, none of this has anything to do with why the little test
DLL I posted to you yesterday doesn't run.  But it indicates to me that
there is something very flaky about WarpTlkt as distributed.  Any
suggestions as to where I go from here, except to forget it?

    Thanks, much, for your helping hand.
  
               --Murray
___
 * MR/2 2.13 #120 * Quoth the raven: "Have a Good Day"
                      
---