This article was previously published under Q86018
This article has been archived. It is offered "as is" and will no longer be updated.
The "Microsoft Windows Resource Kit" (WRK) guide for Windows 3.1incorrectly states on page 248:
Windows 3.1 supports VCPI in both standard mode and 386 enhanced mode.
Windows 3.1 is a Virtual Control Program Interface (VCPI) client instandard mode (using DOSX.EXE). Windows 3.1 in 386 enhanced mode is aDOS Protected Mode Interface (DPMI) server (using WIN386.EXE); it doesnot support VCPI.
It is possible to run some VCPI applications in standard mode. It isnot possible to run VCPI applications in 386 enhanced mode.
INT15 and Extended Memory Specification (XMS) are two methods forallocating extended memory. INT15 is rarely used anymore. It can beused for data storage or VCPI (early specification). MS-DOS 5.0'sHIMEM.SYS version 2.77 or later has the /INT15=xxxx switch for runningthese older applications. Windows in standard and 386 enhanced modesdoes not use INT15 for itself or MS-DOS applications run from Windows.Some MS-DOS applications that can switch from INT15 VCPI to XMS VCPIbecause INT15 is not available, can run from Windows' standard mode.
XMS can be used for data storage, DPMI calls, and VCPI calls. Windowsstandard mode uses XMS as data storage and VCPI (DOSX.EXE is a VCPIclient). Windows in 386 enhanced mode can use XMS for data storage andDPMI (WIN386.EXE is a DPMI server).
Extended MS-DOS Standard Mode 386 Enhanced ModeMemory Use Windows Windows---------- ------ ------------- -----------------INT15 data Yes, with No No /INT15=INT15 VCPI Yes, with No No /INT15=XMS data Yes Yes YesXMS VCPI Yes Yes NoXMS DPMI Yes N/A Yes
Standard mode can run some VCPI applications because when the MS-DOS-based application is run, Windows, except for DOSX.EXE, is swapped todisk or XMS data. This leaves the MS-DOS application to use any XMScalls or usage it needs. Windows in standard mode understands how toallocate memory from a VCPI provider (server), or a DPMI provider.
3.10 documentation error doc err
Artikelnummer: 86018 – Letzte Überarbeitung: 02/28/2014 00:23:44 – Revision: 2.0
Microsoft Windows 3.1 Standard Edition, Microsoft Windows 3.11 Standard Edition