MS>  FS> I recently installed VACPP v3.0 on my system, which has Warp 4 +
FP10,
MS>  FS> Lotus S/S for OS/2, and VA Basic.
MS> 
MS>  FS> In the config.sys there are conflicting SET statements put in by
these
MS>  FS> 3 programs for TMP, SMTMP, SOMBASE, and SOMRUNTIME.
MS> 
MS>  FS> Do I need to consolidate these some how to eliminate the duplication 
MS>  FS> and/or conflicts?  If so, what is the best way to do it?
MS> 
MS> a) do you still know the old statements? if so, please post the
MS> old and the  new ones b) where on you machine have you installed SOM?
MS> there is one version installed  with WAPR4, and one with VACPP. as i
MS> remember, the VACPP version is  incomplete, and older as the OS2
MS> version.  c) do you plan to USE SOM in your apps (dont do it) d)
MS> cursious, you didnt mention SOMIR and all of the other SOM
MS> variables. and  PATH, and libpath. ... VACPP put itself, as i
MS> remember, on the first ,  leading, position of path and libpath
MS> (e.g.) and so SOM references (.DLL,  .EXE) are resolved via VACPP
MS> (but , as i said, VACPP is incomplete and is a  SOM 2.1beta, while
MS> OS2 WARP4 has SOM 2.1.4 installed. so, accepting vacpp in  the
MS> leading position, backgrades your SOM version.
 
Hi Mario-

Thanks for your input.  One of the IBM developers recommended that I
be sure to put the VACPP dll's after the OS/2 dll'l in the LIBPATH, and
also the similar thing for the PATH statement, because the OS/2 stuff is
newer.

No, I do not plan to use SOM in any of my programs.

However, I still have a conflict with the SET SOMRUNTIME statement
which is generated by VACPP and Lotus S/S, and points to different
directories.

Fred Springfield
Plymouth, MN


 þ KWQ/2 1.2i þ If at first you don't succeed, try again--harder.

--- ProBoard v2.16 [Reg]