RBIL61 - INT 30

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} {#idx41406}{#idx41420}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

INT 30 - (NOT A VECTOR!) - DOS 1+ - FAR JMP instruction for CP/M-style calls {#idx96358}

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

INT 30 - QRIP/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. - USED BY GRAPHICS LIBRARY {#idx96368}

INT 31 - overwritten by CP/M(Control Program for Microcomputers) An early operating system for micros based on the 8-bit Intel 8080 CPU (and later the compatible 8085 and Zilog Z80 CPUs). MSDOS version 1.0 was essentially a clone of CP/M for the Intel 8086. jump instruction in INT 30 {#idx96385}

INT 31 - VIRUS - "Vacsina" series - INSTALLATION CHECK (NOT A VECTOR!) {#idx96393}