Didn't even realize that Memsys was distributing it
Sorry, I was probably mixing up versions & products... Too la^b^early...
Regarding the (three) *4.DLLs there shouldn't be a problem? MOZTURBO should use its own, which are located in its BEGINLIBPATH boot drive subdirectory, which isn't a LIBPATH directory (well, "." is).
With a clean boot drive policy FFTURBO xor SMTURBO should use a different copy of those *4.DLLs, which are located in a LIBPATH subdirectory.
Nevertheless I'll append that LIBPATH subdirectory to the BEGINLIBPATH too, just to make sure that it's there. Twice, and once in front.
Current <WP_START>-folder WPProgram settings (typed, errors possible), D:\INTERNET\BIN is the LIBPATH subdirectory where the modern *4.DLLs are saved:
MOZTURBO:
EXENAME=CMD.EXE
PARAMETERS=/c detach C:\PROGRAMS\MOZILLA\MOZTURBO.EXE -l
STARTUPDIR=C:\PROGRAMS\MOZILLA
SET LIBPATHSTRICT=T
SET BEGINLIBPATH=C:\PROGRAMS\MOZILLA
SMTURBO:
EXENAME=CMD.EXE
PARAMATERS=/c detach D:\SEAMONKEY\SMTURBO.EXE -t
STARTUPDIR=D:\SEAMONKEY
SET LIBPATHSTRICT=T
SET BEGINLIBPATH=D:\SEAMONKEY;D:\INTERNET\BIN
So far still no unforced SYS2070s with the "seamonkey.exe" MOZTURBO.EXE (which can be compiled with "ICC MOZTURBO.EXE" too, if I ignore the MAKE.CMD options of GGC; I may insert DosSleep() and DosSetPriority later).