Very Computer

Peter Busser

--
#include <std/disclaimer.h> /* These are MY words, not those of my employer! */

Thanks.
--

Timothy F. Sipples                              Department of Economics
"Keeper of the OS/2 FAQ List."                        University of Chicago

Quote:>The Lotus 1-2-3 Release 3.0 manual recommends inserting an IOPL=YES
>statement in OS/2's CONFIG.SYS.  I prefer not to do this.  Does anyone
>have a list of specific modules that should be listed in this
>statement in lieu of the general "YES"?

Codeview            - IOPL=CVP
Easel               - IOPL=ESLLIB
C Runtime Library   - IOPL=CRTLIB
IBM CAD             - IOPL=VDI,VDIDY011,VDIDY012,VDIDY013,VDIDYEGA
DisplayWrite 5/2    - IOPL=RR$E1,MH

Note, the DW/2 entry RR$E1 changes with the country versions of DW/2.

Run EXEMAP2 against the load module and/or  DLL.

Here's a sample from a CRTLIB.DLL which does need IOPL.

_________________________________________________________________
Segment Table
_________________________________________________________________
  # Offset Length Flag Minimum Attributes
  1 001800  00006 0810  00006  CODE MOVABLE NONSHARED DPL2
  2 001A00  0FDDD 0D00  0FDDD  CODE FIXED NONSHARED RELOC DPL3
  3 012400  0244B 0D00  0244B  CODE FIXED NONSHARED RELOC DPL3
  4 000000  00000 0C01  00834  DATA FIXED NONSHARED DPL3
  5 014A00  00014 0C01  00299  DATA FIXED NONSHARED DPL3
  6 000000  00000 0C01  00200  DATA FIXED NONSHARED DPL3
  7 014C00  02EC8 0D01  03840  DATA FIXED NONSHARED RELOC DPL3

Note that Segment #1 has an attribute of DPL2. This means that the
Descriptor Privilege Level is 2 which is what IOPL means. All other
segments are DPL3 which is the normal application privilege level.
DPL0 is the Kernel privilege level. DPL1 is not used in OS/2.

Any EXE or DLL which has a DPL2 segment needs IOPL authority.

Cheers,