Unfortunately the
adoption of the DPMI standard has resulted in a confusing situation concerning
what will work with what. The first thing to say is that Windows 3 will not work with any software that is only VCPI compliant but it will work with any software that is DPMI and VCPI compliant. For example, you cannot run an early version of Lotus 1-2-3 Release 3 under Windows or use early 386MAX or QEMM because they are only VCPI compliant, but you can run later versions that are both VCPI and DPMI compliant. In the same way any product that is both DPMI and VCPI compliant will work with software that is only VCPI compliant. In other words, the VCPI and DPMI standards are not compatible but neither are they mutually exclusive-a product can support both.
what will work with what. The first thing to say is that Windows 3 will not work with any software that is only VCPI compliant but it will work with any software that is DPMI and VCPI compliant. For example, you cannot run an early version of Lotus 1-2-3 Release 3 under Windows or use early 386MAX or QEMM because they are only VCPI compliant, but you can run later versions that are both VCPI and DPMI compliant. In the same way any product that is both DPMI and VCPI compliant will work with software that is only VCPI compliant. In other words, the VCPI and DPMI standards are not compatible but neither are they mutually exclusive-a product can support both.
The final
question to be answered is what the continuing existence of two standards-VCPI
and DPMI-means for the user. If you only want to use EMMs, DOS extenders and
DOS multi-taskers then the VCPI standard is quite sufficient and you can live
with old versions of software. If, however, you move to a protected mode
multi-tasker, such as Windows, then DPMI is essential and upgrading to a
version that supports both VCPI and DPMI is necessary. In practice the dual
standard is likely to continue for some time, but with DPMI being certain to be
the long term winner.

0 comments:
Post a Comment