SE>
  > Warp should, IMHO, be clever enough to search through the
  > entire line and not throw up when it doesn't get what it
  > wants at the start of the line.
SE>

  That's exactly the problem, though.  It *does* get what it wants. It
  is looking for a SOM.DLL and it finds it.

  The rule for LIBPATH is that it is searched from left to right.  It is
  the responsibility of any installation program to ensure that when it
  is adding things to the beginning of LIBPATH that it isn't overriding
  newer DLLs with older ones.

  The problem is that Watcom's installation routine hasn't been bright
  enough to realise that it is overriding the newer SOM.DLL in WARP with
  the older SOM.DLL distributed by Watcom.

  The blame is squarely on Watcom's shoulders.

SE>
  >                                 The folks at IBM that I
  > have spoken to about this think that it is a problem with
  > Warp. You may disagree.
SE>

  The "folks at IBM" are allowed to be wrong as well, you know.

  I disagree because it's going to be damn difficult to put the onus on
  the operating system to check that some lazy application developer
  doesn't slip in an outdated DLL when they are installing things.

  If it is an operating system "problem", then how come IBM CSet++
  (which also includes an old version of SOM.DLL) doesn't screw things
  up like Watcom C++ does ?  After all, the operating system hasn't
  changed.

  The answer is that the install routine in IBM CSet++ isn't stupid
  enough to go replacing SOM.DLL without checking.  It leaves that to
  the user.

SE>
  > And an operating system of the scope and power of Warp should be smart enou
  > to check the entire line and validate what it finds when
  > such an action is as critical to simply booting up as this would seem to be
SE>

  Utter rubbish.

  It is *not* critical to booting up.  OS/2 itself runs fine.  After
  all, you get a working command line.  You also get it in a PM window
  (so PM must be working, as well).

  It's only an application (Workplace Shell), which happens to require
  the newer version of this DLL, that has the trouble.

  And Watcom has screwed up this application by making assumptions about
  LIBPATH and who is going to have the latest version of what that are
  simply unwarranted, and wrong.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 2.02