RBIL61 - INT 20 P

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} {#idx41401}{#idx41415}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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