SE> The bug is Warp's, not Watcom's. The fix is to simply put the watcom
 SE> paths at the end of the LIBPATH= statement.

 JdBP>   Wrong.  The bug is Watcom's.  It's installation routine is not
 JdBP> well designed.

Neither is Warp when it is that fragile in an area that is critical to
simply booting up.

 
 JdBP>   It should check that the DLLs that it is blithely adding to the  
 JdBP> beginning of LIBPATH actually have a later date than the DLLs
 JdBP> already   on LIBPATH.

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.
The folks at IBM that I have spoken to about this think that it is a
problem with Warp. You may disagree.


 JdBP>   Not many install programs do check that they are obseleting older
 JdBP> DLLs   and not newer DLLs, but that is what they *should* do.

And an operating system of the scope and power of Warp should be smart
enough 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.

Cheers,
Simon

---