On Tuesday, 98/01/13, Ludovic Braun wrote to Jim Gitzen about "Msvc &
win-os2" as follows:
LB> JG> However, MMD.386 *is* listed in my system.ini.  Is there a way to
LB> JG> get this running under WIN-OS/2?  What is the MMD.386 VDD?
LB> 
LB> VDDs are not allowed to run under Win-OS/2. Your program is then
LB> incompatible with Win-OS/2, thanks to MS :-(
Hi Jim,
Ludovic is partly correct here. If the code were truly dependent on MMD.386
it would not be compatible with WIN-OS/2.
But in this case it isn't necessarily so. The MMD.386 driver was a kludge
that used the ring 0 execution of a VxD (not a VDD) to support VCPI under
Windows. It was replaced by MS in 1994.
The product you are using is, I would infer, MS Visual C++ 1.0. The ideal
solution for this is to replace it with Watcom C/C++, a much better compiler
all around. The next best thing for using it under OS/2 is Build-a-rama, a
shareware IDE for Visual C++ under OS/2; this is on Hobbes and Pete Norloff's
BBS.
The last one, which I am obliged to use at work, is to apply the MS patch to
make the compiler use DPMI memory instead of VCPI memory, and then run
compiles in a VDM with DPMI_DOS_API set to ENABLED. This precludes compiling
from within WIN-OS/2. I can still use the App Studio and such, but to compile
my code I use a separate VDM session and run NMAKE.EXE from the command line
on the .MAK file. E.g.
  D:\PROJ\SYNRPTMG> nmake /f synrptmg.mak
It isn't difficult and is only a minor inconvenience.
Regards
Dave

 * KWQ/2 1.2i * I use Windows...on my car, on my house, but not on my ...
--- Maximus/2 3.01
---------------