RBIL61 - MS Windows

INT 20 - Microsoft Windows - VMM - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - DEBUG - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VPICD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VDMAD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VTD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - V86MMGR - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - PageSwap - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - REBOOT - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VDD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VSD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VMD / VMOUSE - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VKD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VCD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - BlockDev / IOS - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VMCPD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - EBIOS - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VNETBIOS - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - DOSMGR - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - SHELL - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VMPoll - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - DOSNET - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VFD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - LoadHi - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - Int13 - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - PAGEFILE - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VPOWERD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VXDLDR - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NDIS(Network Driver Interface Specification) A hardware-independent network interface developed by Microsoft and 3com. See also Packet Driver, TCP/IP. - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VWIN32 - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VCOMM - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - SPOOLER - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VSERVER - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - CONFIGMG - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - DWCFGMG.SYS - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VFBACKUP - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VMINI / ENABLE - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VCOND - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - BIOS(Basic Input/Output System) A set of standardized calls giving low-level access to the hardware. The BIOS is the lowest software layer above the actual hardware and serves to insulate programs (and operating systems) which use it from the details of accessing the hardware directly. - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - WSOCK - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - IFSMgr - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VCDFSD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - PERF - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - MTRR - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NTKERN - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VFLATD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - vjoyd - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - mmdevldr - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VNetSup - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VREDIR - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VSHARE - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NWLINK - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VTDI - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VIP - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - MSTCP - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VCACHE - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NWREDIR - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - FILESEC - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NWSERVER - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - MSSP / NWSP - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NSCL - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - AFVXD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - NDIS2SUP - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - Splitter - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - PPPMAC - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VDHCP - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VNBT - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - LOGGER - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - PCCARD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - QEMM - VstlthD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - WSVV - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - ASPIENUM - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - DSOUND - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - A3D - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - CWCPROXY - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 20 - Microsoft Windows - VGARTD - VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. SERVICES {protected mode}
INT 2F - MS Windows - WINDOWS ENHANCED MODE INSTALLATION CHECK
INT 2F - MS Windows/386 2.x - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows/386 - GET INSTANCE DATA {callout or callback}
INT 2F - MS Windows - WINDOWS ENHANCED MODE & 286 DOSX INIT BROADCAST {callout or callback}
INT 2F - MS Windows - WINDOWS ENHANCED MODE & 286 DOSX EXIT BROADCAST {callout or callback}
INT 2F - MS Windows - VIRTUAL DEVICE CALL OUT API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. {callout or callback}
INT 2F - MS Windows - "V86MMGR" VIRTUAL DEVICE API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. {callout or callback}
INT 2F - MS Windows - "VMD" VIRTUAL MOUSE DEVICE API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. {callout or callback}
INT 2F - MS Windows95 - "VKD" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows 3.1 - "BLOCKDEV" VIRTUAL HARD DISK DEVICE API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. {callout or callback}
INT 2F - MS Windows - "VNETBIOS" VIRTUAL DEVICE API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. {callout or callback}
INT 2F - MS Windows - "VMPoll" VIRTUAL DEVICE - IDLE CALLOUT {callout or callback}
INT 2F - MS Windows - "PageFile" VIRTUAL DEVICE - GET LOCK BYTE {callout or callback}
INT 2F - MS Windows - "W32S" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - "IFSMgr" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - "VADLIBD" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - "IFSMgr" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - "NWSUP" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - "PharLap" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - "SIWVID" VIRTUAL DEVICE - ??? CALLOUT {callout or callback}
INT 2F - MS Windows - WINDOWS ENHANCED MODE INIT COMPLETE BROADCAST {callout or callback}
INT 2F - MS Windows - WINDOWS ENHANCED MODE BEGIN EXIT BROADCAST {callout or callback}
INT 2F - MS Windows 3.1 - IDENTIFY WINDOWS VERSION AND TYPE
INT 2F - MS Windows 3.1 - IDENTIFY TSRs
INT 2F - MS Windows 3.1 - DETECT ROMs
INT 2F - MS Windows, DPMIsee DOS Protected-Mode Interface, various - RELEASE CURRENT VIRTUAL MACHINE TIME-SLICE
INT 2F - MS Windows 3+ - BEGIN CRITICAL SECTION
INT 2F - MS Windows 3+ - END CRITICAL SECTION
INT 2F - MS Windows 3+ - GET CURRENT VIRTUAL MACHINE ID
INT 2F - MS Windows - GET DEVICE API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows95 - VMM - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VPICD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VTD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows95 - V86MMGR - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - REBOOT - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VDD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VMD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VKD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VCD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VPD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - IOS - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VMCPD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - DOSMGR - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - SHELL - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {undocumentedInformation about a product which is not publicly available from the manufacturer, and must be determined by reverse-engineering (disassembly, trial-and-error, etc.). Undocumented information tends to change -- often dramatically -- between successive revisions of a product, since the manufacturer has no obligation to maintain compatibility in behavior which is not explicitly stated.}
INT 2F - MS Windows - VNETWARE - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - WINDEBUG - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - PAGEFILE - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode, undocumentedInformation about a product which is not publicly available from the manufacturer, and must be determined by reverse-engineering (disassembly, trial-and-error, etc.). Undocumented information tends to change -- often dramatically -- between successive revisions of a product, since the manufacturer has no obligation to maintain compatibility in behavior which is not explicitly stated.}
INT 2F - MS Windows - APIX - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VPOWERD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows95 - VXDLDR - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - NDIS(Network Driver Interface Specification) A hardware-independent network interface developed by Microsoft and 3com. See also Packet Driver, TCP/IP. - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VWIN32 - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VCOMM - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - W32S - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - MACH32 - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - SERVER / VSERVER - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - CONFIGMG - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VFBACKUP - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - ENABLE.VXD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VCOND - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - DSVXD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - BIOS(Basic Input/Output System) A set of standardized calls giving low-level access to the hardware. The BIOS is the lowest software layer above the actual hardware and serves to insulate programs (and operating systems) which use it from the details of accessing the hardware directly. VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - WSOCK - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VFLATD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VIPX - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - WINICE - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VCLIENT - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - BCW - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - DPMSsee DOS Protected-Mode Services VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {real mode}
INT 2F - MS Windows - VCOMMUTE - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VTDAPI - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VADMAD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VSBD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VADLIBD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - vjoyd - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - mmdevldr - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VflatD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - azt16 - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - UNIMODEM - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VNetSup - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VBrowse - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VSHARE - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - IFSMgr - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - VFAT - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - NWLINK - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VIP - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {real mode}
INT 2F - MS Windows 3.11 - VXDLDR - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - RASMAC - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - NWREDIR - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - NSCL - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - PPPMAC - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VDHCP - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VNBT - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VMB - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - PHARLAPX - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - PharLap VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - EDOS - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VSBPD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - GRVSULTR - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VVidramD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - WSVV - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT {protected mode}
INT 2F - MS Windows - WPS - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VSGLX16.386 - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - STAT.386 - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - QEMM v8.01 - MAGNARAM VxDA virtual device driver for Windows 3.x or 95. So called because nearly all of the Windows 3.0 drivers had names of the form "VdeviceD". See also device driver. - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - DSOUND - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VIWD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - POSTMSG - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VSWITCHD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - VbillD - GET API(Application Program[ming] Interface) The defined set of calls which a program may make to interact with or request services of the operating system or environment under which it is running. Because the inputs and outputs of the calls are well-defined, a program using the API can continue using the identical calls even if the internal organization of the program providing the API changes. ENTRY POINT
INT 2F - MS Windows - SWITCH VMs AND CALLBACK
INT 2F - MS Windows 3.0, 386MAX v6.01 - GET ALIAS SELECTOR TO LDT {undocumentedInformation about a product which is not publicly available from the manufacturer, and must be determined by reverse-engineering (disassembly, trial-and-error, etc.). Undocumented information tends to change -- often dramatically -- between successive revisions of a product, since the manufacturer has no obligation to maintain compatibility in behavior which is not explicitly stated.}
INT 2F - MS Windows 3.0+ - KERNEL IDLE CALL {undocumentedInformation about a product which is not publicly available from the manufacturer, and must be determined by reverse-engineering (disassembly, trial-and-error, etc.). Undocumented information tends to change -- often dramatically -- between successive revisions of a product, since the manufacturer has no obligation to maintain compatibility in behavior which is not explicitly stated.}
INT 2F - MS Windows 3.1 - SET FOCUS TO SPECIFIED VIRTUAL MACHINE
INT 2F - MS Windows 3.1 - RESTART COMMAND
INT 2F - Windows95 - TITLE - SET APPLICATION TITLE
INT 2F - Windows95 - TITLE - SET VIRTUAL MACHINE TITLE
INT 2F - Windows95 - TITLE - GET APPLICATION TITLE
INT 2F - Windows95 - TITLE - GET VIRTUAL MACHINE TITLE
INT 2F - Windows95 - CLOSE-AWARENESS - ENABLE/DISABLE CLOSE COMMAND
INT 2F - Windows95 - CLOSE-AWARENESS - QUERY CLOSE
INT 2F - Windows95 - CLOSE-AWARENESS - ACKNOWLEDGE CLOSE
INT 2F - Windows95 - CLOSE-AWARENESS - CANCEL CLOSE
INT 2F - MS Windows "WINOLDAP" - IDENTIFY WinOldAp VERSION
INT 2F - MS Windows "WINOLDAP" - OPEN CLIPBOARD
INT 2F - MS Windows "WINOLDAP" - EMPTY CLIPBOARD
INT 2F - MS Windows "WINOLDAP" - SET CLIPBOARD DATA
INT 2F - MS Windows "WINOLDAP" - GET CLIPBOARD DATA SIZE
INT 2F - MS Windows "WINOLDAP" - GET CLIPBOARD DATA
INT 2F - MS Windows "WINOLDAP" - CloseClipboard
INT 2F - MS Windows "WINOLDAP" - COMPACT CLIPBOARD
INT 2F - MS Windows "WINOLDAP" - GET DEVICE CAPABILITIES
INT 2F - Windows 3+ (OS/2 2.x???) - GET VIRTUAL DEVICE DRIVER (VDD) CAPABILTIES
INT 2F - Windows 3.x - ENTERING VIDEO DRIVER CRITICAL SECTION
INT 2F - Windows 3.x - EXITING VIDEO DRIVER CRITICAL SECTION
INT 2F - Windows 3.x - SWITCHING DOS TO BACKGROUND {callout or callback}
INT 2F - Windows 3.x - SWITCHING DOS TO FOREGROUND {callout or callback}
INT 2F - Windows 3.x - ENABLE VDD TRAPPING OF VIDEO REGISTERS
INT 2F - MS Windows v3.0 - INSTALLATION CHECK {undocumentedInformation about a product which is not publicly available from the manufacturer, and must be determined by reverse-engineering (disassembly, trial-and-error, etc.). Undocumented information tends to change -- often dramatically -- between successive revisions of a product, since the manufacturer has no obligation to maintain compatibility in behavior which is not explicitly stated.}
INT 2F - MS Windows - WIN.COM - GET ??? POINTER TO WIN.COM
INT 2F - MS Windows 3+ - WIN.COM - SET PROGRAM TO EXECUTE ON EXIT
INT 2F - Windows95 - WIN.COM - GET NESTING LEVEL
INT 2F - MS Windows - WSWAP.EXE - RESET INTERNAL VARIABLES
INT 2F - WINX - INSTALLATION CHECK
INT 2F - WINX - RETURN ADDRESS OF SERVER BUFFER
INT 2F - WINX - SET SERVER'S WORKING DIRECTORY
INT 2F - WINX - EXECUTE COMMAND
INT 30 - MS Windows 3.1+ - PROTECTED-MODE CALLBACK {protected mode}
INT 66 - Microsoft Windows VITD.386 Virtual Interval Timer
INT 68 - MS Windows debugging kernel - OUTPUT STRING
INT 6F - MS Windows 3.0 - DOS APPLICATION SWITCH HOOK {callout or callback}