RBIL61 - INT 20

Advertisements {#idx177347}

INT 20 - COMTROL HOSTESS i/ISA(Industry-Standard Architecture) The expansion bus used by the IBMInternational Busiuness Machines PCIBM PC/ATIBM PC AT. See also EISA. DEBUGGER - INVOKE FIRMWARE DEBUGGER {#idx39522}

INT 20 - DOS 1+ - TERMINATE PROGRAM {#idx39513}

INT 20 - Frontier Technologies ??? - 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} {#idx41399}{#idx41402}{#idx41413}{#idx41416}

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} {#idx41468}{#idx41473}

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} {#idx41287}{#idx41292}

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} {#idx41445}{#idx41450}

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} {#idx40853}{#idx40858}

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} {#idx40043}{#idx40048}

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} {#idx40586}{#idx40591}

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} {#idx41479}{#idx41484}

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} {#idx39745}{#idx39750}

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} {#idx40120}{#idx40125}

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} {#idx40218}{#idx40223}

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} {#idx41457}{#idx41462}

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} {#idx40741}{#idx40746}

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} {#idx40093}{#idx40098}

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} {#idx41242}{#idx41247}

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} {#idx40880}{#idx40885}

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} {#idx40253}{#idx40259}

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} {#idx40239}{#idx40245}

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} {#idx41369}{#idx41375}

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} {#idx41091}{#idx41096}

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} {#idx41266}{#idx41272}

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} {#idx41177}{#idx41183}

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} {#idx41048}{#idx41053}

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} {#idx40370}{#idx40375}

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} {#idx41299}{#idx41306}

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} {#idx41277}{#idx41282}

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} {#idx41058}{#idx41064}

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} {#idx41142}{#idx41148}

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} {#idx41229}{#idx41235}

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} {#idx41254}{#idx41260}

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} {#idx40269}{#idx40275}

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} {#idx39909}{#idx39915}

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} {#idx41381}{#idx41388}

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} {#idx41024}{#idx41029}

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} {#idx41336}{#idx41342}

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} {#idx39923}{#idx39929}

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} {#idx40151}{#idx40157}

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} {#idx41314}{#idx41320}

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} {#idx40555}{#idx40561}

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} {#idx39873}{#idx39880}

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} {#idx41189}{#idx41195}

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} {#idx40030}{#idx40035}

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} {#idx41012}{#idx41018}

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} {#idx40499}{#idx40505}

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} {#idx40834}{#idx40840}

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} {#idx39936}{#idx39941}

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} {#idx41348}{#idx41354}

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} {#idx39802}{#idx39809}

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} {#idx40767}{#idx40773}

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} {#idx40229}{#idx40234}

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} {#idx41070}{#idx41076}

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} {#idx41490}{#idx41497}

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} {#idx41166}{#idx41171}

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} {#idx41082}{#idx41087}

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} {#idx40006}{#idx40011}

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} {#idx40061}{#idx40068}

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} {#idx39976}{#idx39983}

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} {#idx40788}{#idx40795}

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} {#idx39526}{#idx39532}

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} {#idx40196}{#idx40203}

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} {#idx41360}{#idx41365}

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} {#idx40106}{#idx40112}

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} {#idx41100}{#idx41106}

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} {#idx39760}{#idx39766}

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} {#idx40284}{#idx40290}

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} {#idx41112}{#idx41118}

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} {#idx39965}{#idx39970}

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} {#idx40568}{#idx40574}

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} {#idx41130}{#idx41136}

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} {#idx39850}{#idx39855}

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} {#idx41155}{#idx41160}

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} {#idx40452}{#idx40458}

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} {#idx40330}{#idx40337}

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} {#idx40863}{#idx40869}

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} {#idx41435}{#idx41440}

INT 20 - Minix - SEND/RECEIVE MESSAGE {#idx39505}

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} {#idx41423}{#idx41427}

INT 21 - COMTROL HOSTESS i/ISA(Industry-Standard Architecture) The expansion bus used by the IBMInternational Busiuness Machines PCIBM PC/ATIBM PC AT. See also EISA. DEBUGGER - GET SEGMENT FOR CONTROL PROGRAM USE {#idx41509}

INT 21 - DOS 1+ - CREATE NEW PROGRAM SEGMENT PREFIX {#idx43442}

INT 21 - DOS 1+ - TERMINATE PROGRAM {#idx41535}

INT 21 - DOS 2+ - "EXIT" - TERMINATE WITH RETURN CODE {#idx50901}

INT 21 - DOS 2+ - GET RETURN CODE (ERRORLEVEL) {#idx50911}

INT 21 - DOS 2+ - TERMINATE AND STAY RESIDENT {#idx44333}

INT 21 - DOS 3.0+ internal - GET ADDRESS OF DOS SWAPPABLE DATA AREA {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.} {#idx53175}

INT 21 - DOS 4.x only - internal - GET DOS SWAPPABLE DATA AREAS {obsolete, 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.} {#idx53422}

INT 21 - DR DOS 5.0+ internal - GET POINTER TO INTERNAL VARIABLE TABLE {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.} {#idx50108}

INT 22 - DOS 1+ - PROGRAM TERMINATION ADDRESS {#idx72017}

INT 24 - DOS 1+ - CRITICAL ERROR HANDLER {callout or callback} {#idx72186}

INT 27 - COMTROL HOSTESS i/ISA(Industry-Standard Architecture) The expansion bus used by the IBMInternational Busiuness Machines PCIBM PC/ATIBM PC AT. See also EISA. DEBUGGER - INVOKE REMOTE TURBO DEBUGGER KERNEL {#idx72519}

INT 29 - DOS 2+ - FAST CONSOLE OUTPUT {callout or callback} {#idx72591}

INT 2F - Intel Plug-and-Play - CONFIGURATION MANAGER - GET ENTRY POINT {#idx80867}

INT 2F - INTMON v2.1 - RESET {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.} {#idx89146}

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} {#idx80662}

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 {#idx81069}

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 {#idx80980}

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 {#idx80934}

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 {#idx80825}{#idx80830}

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 {#idx80494}{#idx80510}

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} {#idx80985}

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 {#idx81471}

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 {#idx80930}

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 {#idx80906}

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 {#idx79868}{#idx80161}

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 {#idx81333}

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} {#idx81123}

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 {#idx80463}{#idx80469}

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} {#idx80804}

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 {#idx81033}

INT 2F - MS Windows - MX1501HAD - 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 {#idx81480}

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 {#idx80740}

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 {#idx81176}

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 {#idx81133}

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 {#idx81169}

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.} {#idx80639}{#idx80651}

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 {#idx81312}

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 {#idx81187}

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 {#idx81163}

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 {#idx80813}

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.} {#idx80519}{#idx80580}{#idx80587}{#idx80591}

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 {#idx81453}

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} {#idx81088}

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 {#idx81023}

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 {#idx81013}

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 {#idx81105}

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} {#idx80405}

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} {#idx80976}

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 {#idx80769}

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 {#idx80993}

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 {#idx80919}

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} {#idx80362}

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 {#idx81193}

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 {#idx81127}

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 {#idx80894}

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} {#idx80952}{#idx81063}

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} {#idx81138}

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 {#idx80963}

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 {#idx81507}

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} {#idx81028}

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} {#idx80395}

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 {#idx81203}

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 {#idx80481}

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 {#idx80372}

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 {#idx81197}

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 {#idx81097}

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 {#idx80623}

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} {#idx80412}

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 {#idx80285}

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} {#idx80672}

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 {#idx81017}

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 {#idx81327}

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 {#idx81436}

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 {#idx81111}

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 {#idx80293}{#idx80302}

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} {#idx81000}

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 {#idx81406}

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} {#idx80749}

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} {#idx80797}

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} {#idx80630}

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 {#idx80969}

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 {#idx81422}

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 {#idx80945}

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} {#idx81415}

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 {#idx81148}{#idx81154}

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} {#idx80313}

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 {#idx80272}

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 {#idx80720}

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 {#idx81460}

INT 30 - MS Windows 3.1+ - PROTECTED-MODE CALLBACK {protected mode} {#idx96509}

INT 60 - Excelan LAN Workplace for DOS 3.5 - 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. {#idx104342}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05 - "net_info" - GET INTERFACE STATISTICS {#idx109132}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05 - "net_sendto" - ??? {#idx109293}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "get_addr" - GET INTERNET ADDRESS OF NET DESCR {#idx109049}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_flush" - FLUSH PENDING DATA {#idx109888}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_peer" - GET DATA ON REMOTE PEER {#idx109629}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_release" - CLOSE A NETWORK DESCRIPTOR {#idx109213}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_releaseall" - CLOSE ALL NON-GLOBAL DESCRS {#idx109248}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_select" - DETECT READINESS OF NETWORK {#idx109435}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_shutdown" - UNINSTALL {#idx109496}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "net_write" - WRITE TO THE NETWORK {#idx109758}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05+ - "nm_prs_addr" - TRANSLATE NUMERICAL IP(Internet Protocol) The lower level (transport layer) of the TCP/IP protocol suite. See also TCP, TCP/IP. ADDRESS {#idx110375}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.05- - "nm_ien116" - RESOLVE HOST NAME USING IEN116 {#idx110427}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.1+ - "get_kernel_info" - GET MISCELLAN LOCAL INFO {partially documented} {#idx109009}

INT 61 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. kernel v2.1+ - "net_config" - CONFIGURE RUNNING KERNEL {partially documented} {#idx108981}

INT 61 - TCPOpen kernel - 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. {#idx107374}