RBIL61 - Microsoft

86 Bugs List {#idx176344}

Bibliography {#idx166719}{#idx166773}{#idx166837}{#idx166884}{#idx166941}{#idx166946}{#idx166949}{#idx166958}{#idx166959}{#idx166986}{#idx166992}{#idx167027}{#idx167033}{#idx167126}{#idx167129}{#idx167131}{#idx167195}{#idx167200}{#idx167417}

CALL xxxxh:xxxxh - Microsoft EMM386.EXE {#idx159442}

CALL xxxxh:xxxxh - Microsoft Mouse Driver - Alternate Entry Point {#idx159450}

CALL xxxxh:xxxxh - Microsoft Real-Time Compression Interface (MRCI) {#idx159464}

CALL xxxxh:xxxxh - Microsoft Workgroup Connection - WORKGRP.SYS {#idx159471}

CALL xxxxh:xxxxh - Plug-and-Play 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. v1.0A {#idx160432}

INT 09 - IRQ1 - KEYBOARD DATA READY {callout or callback} {#idx720}{#idx739}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - DEFINE DEFAULT REGISTER TABLE {#idx7324}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - INTERROGATE DRIVER {#idx7333}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - READ ONE REGISTER {#idx7154}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - READ REGISTER RANGE {#idx7216}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - READ REGISTER SET {#idx7251}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - REVERT TO DEFAULT REGISTERS {#idx7298}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - WRITE ONE REGISTER {#idx7195}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - WRITE REGISTER RANGE {#idx7234}

INT 10 - EGAEnhanced Graphics Adapter(Enhanced Graphics Adapter) IBMInternational Busiuness Machines's second color video board for the IBMInternational Busiuness Machines PCIBM PC family, capable of a maximum resolution of 640x350 pixels in 16 simultaneous colors of a total of 64 possible colors. Register Interface Library - WRITE REGISTER SET {#idx7279}

INT 10 - VIDEO - GET CURRENT VIDEO MODE {#idx2253}{#idx2255}

INT 10 - VIDEO - MSHERC.COM - GET VIDEO ADAPTER TYPE AND MODE {#idx7138}

INT 13 - DISK - GET DRIVE PARAMETERS (PCIBM PC,XT286IBM PC XT/286,CONVIBM Convertible,PSIBM PS/2, any model,ESDI(Enhanced Small Device Interface) A disk drive interface type which was briefly popular before IDE took over. An ESDI drive can transfer data between the drive and controller at 10, 15, or 20 megabits per second, which is faster than an MFM or RLL controller but slower than what is possible with an IDE or SCSI drive. See also IDE.,SCSI(Small Computer Systems Interface) A system-independent expansion bus typically used to connect hard disks, tape drives, and CD-ROMs to a computer. A host adapter connects the SCSI bus to the computer's own bus. See also ESDI, IDE.) {#idx8636}

INT 13 - DISK - READ SECTOR(S) INTO MEMORY {#idx8074}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - CLEAR THE RECEIVE BUFFER {#idx12070}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - CLEAR THE TRANSMIT BUFFER {#idx12085}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - EXTENDED INITIALIZE {#idx12057}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - GET RECEIVE BUFFER COUNT {#idx12077}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - GET TRANSMIT BUFFER COUNT {#idx12093}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - INITIALIZE MODE {#idx12050}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - INSTALLATION CHECK {#idx12043}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - SET TIMEOUT {#idx12062}

INT 14 - Microsoft Systems Journal TSRCOMM INT14 - UNINSTALL {#idx12100}

INT 15 - Microsoft TSR(Terminate and Stay Resident) A program which remains in memory after terminating in order to provide services to other programs or the user. The name comes from the name of the DOS function call used to remain in memory after termination. Specification {#idx15377}

INT 15 - SYSTEM - GET CONFIGURATION (XTIBM PC XT >1986/1/10,ATIBM PC AT mdl 3x9,CONVIBM Convertible,XT286IBM PC XT/286,PSIBM PS/2, any model) {#idx21674}

INT 16 - Microsoft QBASIC internal - MICROSOFT COOPERATION WITH TSR(Terminate and Stay Resident) A program which remains in memory after terminating in order to provide services to other programs or the user. The name comes from the name of the DOS function call used to remain in memory after termination. {callout or callback, 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.} {#idx25850}

INT 16 - Microsoft Word - TSR(Terminate and Stay Resident) A program which remains in memory after terminating in order to provide services to other programs or the user. The name comes from the name of the DOS function call used to remain in memory after termination. COOPERATION??? {callout or callback} {#idx25873}{#idx25875}{#idx25882}

INT 16 - Microsoft Word internal - MICROSOFT WORD COOPERATION WITH TSR(Terminate and Stay Resident) A program which remains in memory after terminating in order to provide services to other programs or the user. The name comes from the name of the DOS function call used to remain in memory after termination. {callout or callback} {#idx25831}{#idx25838}

INT 1A - Microsoft Real-Time Compression Interface (MRCI) - ROM-BASED SERVER {#idx32146}{#idx32161}

INT 1A - PCI 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. v2.0c+ - FIND PCI DEVICE {#idx32361}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

INT 21 - DOS 2+ - "CWD" - GET CURRENT DIRECTORY {#idx50237}

INT 21 - DOS 2+ - "EXEC" - LOAD AND/OR EXECUTE PROGRAM {#idx50456}

INT 21 - DOS 2+ - GET DOS VERSION {#idx44092}{#idx44183}{#idx44185}{#idx44188}

INT 21 - DOS 2+ internal - SET CURRENT PROCESS ID (SET PSPsee Program Segment Prefix ADDRESS) {#idx51040}

INT 21 - DOS 3.0+ - GET EXTENDED ERROR INFORMATION {#idx52785}

INT 21 - DOS 3.1+ - IOCTL - CHECK IF BLOCK DEVICE REMOTE {#idx48729}

INT 21 - DOS 3.2+ - IOCTL - GENERIC BLOCK DEVICE REQUEST {#idx48953}

INT 21 - DOS 3.2+ - IOCTL - GENERIC CHARACTER DEVICE REQUEST {#idx48828}

INT 21 - European MS-DOS 4.0 - SLEEP {#idx56975}

INT 21 - IFSHLP.SYS - GET 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.} {#idx45444}

INT 21 - LAN Manager Enhanced DOS - LOCAL NetServiceEnum {partially documented} {#idx54219}

INT 21 - LASTBYTE.SYS v1.19 - IOCTL - GET ??? 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.} {#idx47426}

INT 21 - Memory Managers - 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.} {#idx47288}

INT 21 - Memory Managers - GET EMM IMPORT STRUCTURE ADDRESS {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.} {#idx47338}

INT 21 - Memory Managers - GET MEMORY MANAGER VERSION {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.} {#idx47414}

INT 21 - Network Driver Interface Specification (NDIS(Network Driver Interface Specification) A hardware-independent network interface developed by Microsoft and 3com. See also Packet Driver, TCP/IP.) 2.0.1 - PROTOCOL MANAGER {#idx47021}

INT 21 - PCIBM PC/TCP(Transmission Control Protocol) A higher level (session layer) of the TCP/IP protocol suite. See also IP, TCP/IP. IPCUST.SYS - READ CONFIGURATION DATA {#idx45331}

INT 21 - Windows95 - LONG FILENAME - GET VOLUME INFORMATION {#idx56336}

INT 2A - NETWORK (Microsoft) - SET NET PRINTER MODE {#idx72647}

INT 2A - NETWORK (Microsoft,LANtastic) - EXECUTE NETBIOS REQUEST,NO ERROR RETRY {#idx72632}

INT 2F - ??? {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.} {#idx84065}

INT 2F - DOS 5+ - COMMAND.COM INTERFACE {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.} {#idx85706}

INT 2F - DR DOS 6.0+ DELWATCH.EXE - 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.} {#idx76113}

INT 2F - DRIVER.SYS support - EXECUTE DEVICE DRIVER REQUEST {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.} {#idx75500}

INT 2F - INTERLNK - CHECK IF REDIRECTED DRIVE {#idx85818}

INT 2F - INTERLNK - INSTALLATION CHECK {#idx85768}

INT 2F - License Service 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. - INSTALLATION CHECK {#idx86034}

INT 2F - MICRO.EXE - INSTALLATION CHECK {#idx88841}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - "ProfFinish" {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.} {#idx83923}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - "ProfFlush" {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.} {#idx83917}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - ALTERNATE SEGDEBUG IFACE {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.} {#idx83930}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - CLEAR PROFILING DATA {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.} {#idx83910}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - 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.} {#idx83864}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - SET SAMPLING RATE {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.} {#idx83880}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - SETUP PROFILER {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.} {#idx83874}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - START PROFILING {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.} {#idx83888}

INT 2F - Microsoft Profiler (PROF.COM/VPROD.386) - STOP PROFILING {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.} {#idx83899}

INT 2F - Microsoft Realtime Compression Interface (MRCI) - RAM-BASED SERVER {#idx84752}

INT 2F - MS Windows "WINOLDAP" - IDENTIFY WinOldAp VERSION {#idx81658}

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 {#idx79936}{#idx79973}{#idx80025}{#idx80100}{#idx80109}{#idx80110}{#idx80113}{#idx80119}{#idx80122}

INT 2F - MS Windows - WINDOWS ENHANCED MODE & 286 DOSX EXIT BROADCAST {callout or callback} {#idx79276}

INT 2F - MS Windows - WINDOWS ENHANCED MODE & 286 DOSX INIT BROADCAST {callout or callback} {#idx79201}{#idx79216}{#idx79248}

INT 2F - MS Windows - WINDOWS ENHANCED MODE INSTALLATION CHECK {#idx79161}

INT 2F - MS Windows 3.1 - SET FOCUS TO SPECIFIED VIRTUAL MACHINE {#idx81535}

INT 2F - Multiplex - NOTES {#idx74838}

INT 2F - NETWORK - LANtastic, NetWare Lite - GET VERSION {#idx90387}{#idx90398}

INT 2F - Network Courier E-Mail - 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. {#idx88567}

INT 2F - Network Courier E-Mail OPERATOR.EXE - 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. {#idx88985}

INT 2F - Novell NetWare Lite - CLIENT.EXE - 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.} {#idx93675}

INT 33 - LOGITECH MOUSE - SET PARAMETERS - SET EMULATION (SERIAL MOUSE ONLY) {#idx99572}

INT 33 - MS MOUSE - GET VERSION STRING {#idx99313}{#idx99317}{#idx99322}{#idx99329}{#idx99330}{#idx99331}

INT 33 - MS MOUSE - RETURN POINTER TO COPYRIGHT STRING {#idx99186}

INT 33 - MS MOUSE v1.0+ - DEFINE INTERRUPT SUBROUTINE PARAMETERS {#idx98645}{#idx98649}

INT 33 - MS MOUSE v1.0+ - DEFINE SCREEN REGION FOR UPDATING {#idx98682}

INT 33 - MS MOUSE v1.0+ - POSITION MOUSE CURSOR {#idx98560}

INT 33 - MS MOUSE v3.0+ - DEFINE GRAPHICS CURSOR {#idx98610}

INT 33 - MS MOUSE v6.0+ - ENABLE MOUSE DRIVER {#idx98831}

INT 33 - MS MOUSE v6.0+ - RESTORE DRIVER STATE {#idx98734}

INT 33 - MS MOUSE v6.0+ - SAVE DRIVER STATE {#idx98724}

INT 33 - MS MOUSE v6.26+ - GET SOFTWARE VERSION, MOUSE TYPE, AND IRQ(Interrupt ReQuest) A hardware line connected to the interrupt controller chip which signals that a CPU interrupt should be generated. NUMBER {#idx98879}

INT 33 - MS MOUSE v7.05+ - GET SWITCH SETTINGS AND ACCELERATION PROFILE DATA {#idx99066}

INT 34 - FLOATING POINT EMULATION - OPCODE D8h {#idx99764}

INT 35 - FLOATING POINT EMULATION - OPCODE D9h {#idx99772}

INT 36 - FLOATING POINT EMULATION - OPCODE DAh {#idx99780}

INT 37 - FLOATING POINT EMULATION - OPCODE DBh {#idx99788}

INT 38 - FLOATING POINT EMULATION - OPCODE DCh {#idx99796}

INT 39 - FLOATING POINT EMULATION - OPCODE DDh {#idx99814}

INT 3A - FLOATING POINT EMULATION - OPCODE DEh {#idx99822}

INT 3B - FLOATING POINT EMULATION - OPCODE DFh {#idx99830}

INT 3C - FLOATING POINT EMULATION - INSTRUCTIONS WITH SEGMENT OVERRIDE {#idx99838}

INT 3D - FLOATING POINT EMULATION - STANDALONE FWAIT {#idx99847}

INT 3F - Overlay manager interrupt (Microsoft LINK.EXE, Borland TLINK VROOMM) {#idx99876}{#idx99883}

INT 4B - Virtual DMA SpecificationA set of interrupt calls which permit the use of DMA even on systems running in protected or Virtual-86 mode with their address remapping, or systems such as Micro Channel PSIBM PS/2, any model/2s with multiple bus masters independently performing DMA operations. (VDSsee Virtual DMA Specification) - GET VERSION {#idx101509}{#idx101520}

INT 4B - Virtual DMA SpecificationA set of interrupt calls which permit the use of DMA even on systems running in protected or Virtual-86 mode with their address remapping, or systems such as Micro Channel PSIBM PS/2, any model/2s with multiple bus masters independently performing DMA operations. - SCATTER/GATHER UNLOCK REGION {#idx101597}

INT 5B - PCIBM PC cluster adapter - RELOCATED INT 19 {#idx103170}

INT 66 - Microsoft Windows VITD.386 Virtual Interval Timer {#idx114992}

INT 67 - Compaq CEMM v5.10+ - PRIVATE 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. {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.} {#idx117205}

INT 67 - Microsoft EMM386.EXE v4.20+ - INSTALLATION CHECK {#idx117162}{#idx117170}

MEM 80C0h:0000h - COMPAQ DIAGNOSTICS REGISTER {#idx162930}

MEM F000h:C000h - Tandy ROM(Read-Only Memory) A memory for program storage which may not be changed by the program as it runs. 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. ID BYTE {#idx163902}

Ralf Brown Programs {#idx176931}