Jump to content

CONFIG.SYS - DEVICE Statements: Difference between revisions

From EDM2
Ak120 (talk | contribs)
No edit summary
Ak120 (talk | contribs)
muck out
Line 8: Line 8:


==Chipset Support==
==Chipset Support==
===$ICPMOS2.SYS===
===PC Card/CardBus===
Power Management Driver for PCMCIA
*[[$ICPMOS2.SYS]] - PC Card Power Management
DEVICE=$ICPMOS2.SYS


'''ATTENTION:''' Must be after all other listed drivers in the CONFIG.SYS.
===Power Management===
 
*[[APM.SYS]] - Advanced Power Management
{| class="wikitable"
*[[APM_NH.SYS]] - APM NH
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|?
|Yes
|Yes
|Yes
|}


==Network Adapters==
==Network Adapters==
Line 36: Line 24:
*[[DLKFET.OS2]] - D-Link DFE-530TX
*[[DLKFET.OS2]] - D-Link DFE-530TX
*[[DLKPCI.OS2]] - D-Link Fast Ethernet PCI
*[[DLKPCI.OS2]] - D-Link Fast Ethernet PCI
*[[DLKRTS.OS2]] - D-Link DFE-530TX+
*[[DP83820.OS2]] - NS DP83820 Gigabit
*[[DP83820.OS2]] - NS DP83820 Gigabit
*[[HPFEND.OS2]] - HP DeskDirect
*[[HPFEND.OS2]] - HP DeskDirect
*[[IBMGE.OS2]] - IBM 1000BaseSX Gigabit Ethernet
*[[USBETHR.OS2]] - Kawasaki USB Ethernet 10Mbit
*[[USBETHR.OS2]] - Kawasaki USB Ethernet 10Mbit
*[[W840ND.OS2]] - Winbond W89C840
*[[W840ND.OS2]] - Winbond W89C840
Line 59: Line 49:


===ODI===
===ODI===
====CBEODI.OS2====
*[[CBEODI.OS2]] - Xircom CardBus
Xircom CardBus Ethernet 10/100 Adapter OS/2 Netware ODI driver.
*[[CPQNF3.SYS]] - Compaq NETFLEX-3
  DEVICE=CBEODI.OS2
*[[NTR2000.SYS]] - Novell NTR2000
*[[PCIOS2.SYS]] - Realtek RTL8029
*[[RTSOS2.SYS]] - Realtek RTL8139
*[[SMC8000.SYS]] - SMC/WD EtherCard
 
==Input Devices==
*[[ACECAD.SYS]] - ACECAT III digitiser
 
 
==Multimedia Devices==
===Audio Adapter===
*[[AD1816DD.SYS]] - AD1816 SoundPort
*[[ALC.SYS]] - Realtek ALC AC97
 
==Misc==
===ADSMSDIS.SYS===
Personally Safe'n'Sound tape backup driver that from Warp Server for e-Business
  DEVICE=ADSMSDIS.SYS


{|class="wikitable"
{|class="wikitable"
Line 70: Line 77:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 76: Line 83:
|}
|}


====CPQNF3.SYS====
===ADSMTAPE.SYS===
OS/2 ODI Driver for Compaq NETFLEX-3/NETELLIGENT Controllers.
Personally Safe'n'Sound tape backup driver that from Warp Server for e-Business.
  DEVICE=CPQNF3.SYS
  DEVICE=ADSMTAPE.SYS


{|class="wikitable"
{|class="wikitable"
Line 87: Line 94:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|No
|Yes
|Yes
|}
|}


====NTR2000.SYS====
==Protocol==
ODI (Netware) driver for Token Ring network adapter cards.
===AFINET.SYS===
  DEVICE=C:\Netware\NTR2000.SYS
Part of the TCP/IP Protocol Drivers.
  DEVICE=x:\MPTN\PROTOCOL\AFINET.SYS


{| class="wikitable"
{| class="wikitable" style="text-align:center"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 110: Line 118:
|}
|}


====PCIOS2.SYS====
===AFINETK.SYS===
ODI driver for RealTek RTL-8029 based NE2000-combatible cards.
32-bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak 13 for Warp 4
  DEVICE=PCIOS2.SYS
Part of the TCP/IP Ver. 4.x firewall
  DEVICE=AFINETK.SYS
 
'''Parameter:'''
* /V
Verbose, shows version-number


{| class="wikitable"
{| class="wikitable"
Line 121: Line 134:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|No
|FP13
|Yes
|Yes
|Yes
|}
|Yes
|Yes
|}


====RTSOS2.SYS====
===AFNB.SYS===
ODI MAC for RTL8139 Fast Ethernet Adapter.
Basic-NetBIOS-Socket-Support Driver.
  DEVICE=RTSOS2.SYS
  DEVICE=AFNB.SYS


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 138: Line 151:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 144: Line 157:
|}
|}


====SMC8000.SYS====
===AFOS2.SYS===
SMC Ethernet Adapter Family (SMC 8003, SMC 8013, SMC 8216, SMC 8416) ODI driver.
Part of the TCP/IP Protocol Drivers
  DEVICE=SMC8000.SYS
  DEVICE=C:\Mptn\Potocol\Afos2.sys


{|class="wikitable"
'''Parameter:'''
* /V
Verbose, shows version-number
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 155: Line 172:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 161: Line 178:
|}
|}


==Input Devices==
==Unsorted==
===ACECAD.SYS===
===AMOUSE.SYS===
Driver for the ACECATIII digitizing board.
Mouse Driver for Wheel Mice. like e.g. the:
  DEVICE=ACECAD.SYS
* Logitech Pilot Mouse+
for working DEVICE=x:\OS2\BOOT\MOUSE.SYS STYPE=ACECAD$ must be added
* Logitech Mouse Man+
* Logitech Optical Wheel Mouse
* Microsoft Intellimouse
* IBM Scrollpoint Mouse
* Typhoon 40159
* Trust 250S
 
  DEVICE=AMOUSE.SYS
 
'''NOTE:''' With Amouse installed XFree86 refuses to work
Available for FREE at http://home.t-online.de/home/klaus.breining/


{| class="wikitable"
{| class="wikitable"
Line 180: Line 207:
|}
|}


==Multimedia Devices==
==ANSI.SYS==
===AD1816DD.SYS===
This driver installs the ANSI support for DOS windows.
Analog Devices AD1816 Soundport Driver
  DEVICE=x:\OS2\MDOS\ANSI.SYS <parameters>
  DEVICE=AD1816DD.SYS


'''Parameter:'''
Parameters:
* /N:$strng$
* /X - Enables the redefinition of keys.
Device driver name assigned by MINSTALL
* /K - Prevents the use of extended keyboards. Extended keyboards work as standard keyboards.
* /3:y
3D Phase expansion (0-31)


'''NOTE:''' The Aztech SC16-3D sound card has an Analog Devices AD1816 chip whose drivers should work, in theory. The problem is that this card does not report itself as a standard AD1816 based board, so even though the PnP-Manager correctly initializes the card, the
{| class="wikitable"
driver can neither recognize the board nor pick up the IRQ, I/O, and DMA values from the PnP-Manager. Martin Schaffoener (martin.schaffoener@student.uni-magdeburg.de) patched the driver so it will work also with this card. Search for azsc163d.zip
 
==Misc==
===ADSMSDIS.SYS===
Personally Safe'n'Sound tape backup driver that from Warp Server for e-Business
DEVICE=ADSMSDIS.SYS
 
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 206: Line 222:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 212: Line 228:
|}
|}


===ADSMTAPE.SYS===
==APPOINT.SYS==
Personally Safe'n'Sound tape backup driver that from Warp Server for e-Business.
Pen for OS/2 Device Driver for Kurta PenMouse/APT Gliffic Plus.
  DEVICE=ADSMTAPE.SYS
  DEVICE=APPOINT.SYS


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 224: Line 240:
|-
|-
|No
|No
|No
|Yes
|No
|Yes
|Yes
|Yes
|}
|}


==Protocol==
==ARTPAD.SYS==
===AFINET.SYS===
Device Driver for Wacom Artpad used with Pen for OS/2
Part of the TCP/IP Protocol Drivers.
  DEVICE=ARTPAD.SYS
  DEVICE=x:\MPTN\PROTOCOL\AFINET.SYS
IRQ=4 COMPORT=1 ADRESS=3F8 is used for Com1
IRQ=3 COMPORT=2 ADRESS=2F8 is used for Com2


{| class="wikitable" style="text-align:center"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 241: Line 258:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 247: Line 264:
|}
|}


===AFINETK.SYS===
==ARTZ.SYS==
32-bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak 13 for Warp 4
Pen for OS/2 Device Driver for Wacom UD-0608.
Part of the TCP/IP Ver. 4.x firewall
  DEVICE=ARTZ.SYS
  DEVICE=AFINETK.SYS
 
'''Parameter:'''
* /V
Verbose, shows version-number


{| class="wikitable"
{| class="wikitable"
Line 264: Line 276:
|-
|-
|No
|No
|No
|Yes
|FP13
|Yes
|Yes
|Yes
|}
|}


===AFNB.SYS===
==ASNPCI.OS2==
Basic-NetBIOS-Socket-Support Driver.
AsanteFast 10/100 PCI Ethernet driver.
  DEVICE=AFNB.SYS
  DEVICE=ASNPCI.OS2


{| class="wikitable"
{| class="wikitable"
Line 286: Line 298:
|}
|}


===AFOS2.SYS===
==ASP4CORE.SYS==
Part of the TCP/IP Protocol Drivers
Vortex AU8820 Core OS/2 driver.
  DEVICE=C:\Mptn\Potocol\Afos2.sys
  DEVICE=ASP4CORE.SYS


'''Parameter:'''
{| class="wikitable"
* /V
Verbose, shows version-number
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 307: Line 315:
|}
|}


=OTHERS=
==ASP4JOY.SYS==
==ALC.SYS==
Vortex AU8820 OS/2 Joystick driver.
ALC* AC97 Audio Codec OS/2 Device Driver.
  DEVICE=ASP4JOY.SYS
http://www.realtek.com.tw/htm/download/driver.asp
  DEVICE=ALC.SYS
 
'''Parameter:'''
* I5
The 'I' means interrupt, the available interrupts are 5, 7, 9, 10, 11, 12 and 15
 
* N:ALC1$
Physical Device Driver name


{| class="wikitable"
{| class="wikitable"
Line 333: Line 332:
|}
|}


==AMOUSE.SYS==
==ASP4OS2.SYS==
Mouse Driver for Wheel Mice. like e.g. the:
Vortex AU8820 OS/2 MMPM/2 driver.
* Logitech Pilot Mouse+
  DEVICE=ASP4OS2.SYS
* Logitech Mouse Man+
* Logitech Optical Wheel Mouse
* Microsoft Intellimouse
* IBM Scrollpoint Mouse
* Typhoon 40159
* Trust 250S
 
  DEVICE=AMOUSE.SYS
 
'''NOTE:''' With Amouse installed XFree86 refuses to work
Available for FREE at http://home.t-online.de/home/klaus.breining/


{| class="wikitable"
{| class="wikitable"
Line 361: Line 349:
|}
|}


==ANSI.SYS==
==ASP4VDD.SYS==
This driver installs the ANSI support for DOS windows.
Vortex AU8820 Virtual DOS driver.
  DEVICE=x:\OS2\MDOS\ANSI.SYS <parameters>
  DEVICE=ASP4VDD.SYS


Parameters:
{|class="wikitable"
* /X - Enables the redefinition of keys.
* /K - Prevents the use of extended keyboards. Extended keyboards work as standard keyboards.
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 376: Line 360:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 382: Line 366:
|}
|}


==APM.SYS==
==ASPIDRV.SYS==
Advanced Power Management (APM) device driver. Provides support for your APM BIOS on your motherboard.
ASPI Driver supplied by Solution Technology Inc. (STI)
  DEVICE=x:\OS2\BOOT\APM.SYS <parameter>
  DEVICE=ASPIDRV.SYS


'''Parameter:'''
{|class="wikitable"
* /B - favorizes the direct connection to the APM-BIOS support
* /D - favorizes the device-driver connection of the APM support
* /V - x.y forces the compatibility to APM Version x.y (e.g. 1.0)
 
Together with the APMDAEMN.SYS these settings can also be done by using the Power-Symbol in your System Setup Folder.
 
'''TIP:''' To work correctly you have 1. to change your Warp-Center properties to 'Show only when Mouse is over Center's position' and 2. enable in 'Power Properties' in your System folder on the 'Performance' page 'Automaticall change performance when the power source changes'. (Only tested with Warp4 fixpak 13).
 
'''TIP:''' When OS/2 fails to install in ACPI only Systems REM this driver (has to be done on the Installation disks too) or give APM_NH.SYS a try, it is rported to work on Intel based Motherborads too.
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 410: Line 383:
|}
|}


==APM_NH.SYS==
==ASPIPFA.SYS==
Replacement APM driver (APM_NH.SYS)
Device driver used to distinguish between IDE drives and SCSI drives when using Hard Disk Drive Monitor.
APM_NH.SYS is based on 10.037 level of IBM's APM.SYS (same as XR_D002 but probably outdated with respect to OS/2 v 4.52 G.A.). Its purpose is to honor the APM hooks installed by VIAAPM.SYS while allowing usual APM tasks such as power-down or suspend mode. It is therefore essential that one installs APM_NH.SYS rather than APM.SYS, so the KT266A idle hook would not be taken out by IBM's driver.
DEVICE=APM_NH.SYS


'''Tip:''' In System which only have ACPI it is reported that APM-NH.SYS works even it is a Intel chipset.
The Hard Disk Drive Monitor monitors the status of SMART-compatible harddisk drives in your computer.
available as ftp://ftp.pc.ibm.com/pub/pccbbs/commercial_desktop/zp1t06a.exe
DEVICE=ASPIPFA.SYS


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 430: Line 403:
|}
|}


==APPOINT.SYS==
==ASPIROUT.SYS==
Pen for OS/2 Device Driver for Kurta PenMouse/APT Gliffic Plus.
The interface of ASPI Router merely is an extension of the interface of OS2ASPI.DMD
  DEVICE=APPOINT.SYS
needed e.g. by the free CDRecord/2 from [[Chris Wohlgemuth]] available at: http://www.geocities.com/SiliconValley/Sector/5785/ and SANE (Scanner Access Now Easy) from [[Yuri Dario]] available at http://www.geocities.com/SiliconValley/Peaks/4320.
  DEVICE=ASPIROUT.SYS


{| class="wikitable"
{|class="wikitable" style="text-align:center"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 447: Line 421:
|}
|}


==ARTPAD.SYS==
==ASPITAPE.SYS==
Device Driver for Wacom Artpad used with Pen for OS/2
GTAK Driver for SCSI tape access by GTAR scsitape.dmd and scsitape.sys also belong to the package
  DEVICE=ARTPAD.SYS
By [[Andreas Kaiser]] Andreas.Kaiser@stuttgart.netsurf.de, gtak258.zip gtar258.zip.
IRQ=4 COMPORT=1 ADRESS=3F8 is used for Com1
  DEVICE=ASPITAPE.SYS
IRQ=3 COMPORT=2 ADRESS=2F8 is used for Com2


{| class="wikitable"
{| class="wikitable"
Line 466: Line 439:
|}
|}


==ARTZ.SYS==
==ATALK.SYS==
Pen for OS/2 Device Driver for Wacom UD-0608.
Appletalk driver from IBM LAN Server for Macintosh
  DEVICE=ARTZ.SYS
  DEVICE=ATALK.SYS


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 483: Line 456:
|}
|}


==ASNPCI.OS2==
==ATI0.sys==
AsanteFast 10/100 PCI Ethernet driver.
Used by ATI 3D Rage graphic adapter cards.
  DEVICE=ASNPCI.OS2
  DEVICE=x:\OS2\ATI0.sys


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 494: Line 467:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 500: Line 473:
|}
|}


==ASP4CORE.SYS==
==ATIM64.SYS==
Vortex AU8820 Core OS/2 driver.
Used by ATI 3D Rage graphic adapter cards.
  DEVICE=ASP4CORE.SYS
  DEVICE=x:\OS2\ATIM64.SYS  


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 511: Line 484:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 517: Line 490:
|}
|}


==ASP4JOY.SYS==
==ATKP.SYS==
Vortex AU8820 OS/2 Joystick driver.
Appletalk PAP Port driver from IBM LAN Server for Macintosh.
  DEVICE=ASP4JOY.SYS
  DEVICE=ATKP.SYS


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 528: Line 501:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes*
|}
|}


==ASP4OS2.SYS==
==AUDIOVDD.SYS==
Vortex AU8820 OS/2 MMPM/2 driver.
This is the standard VDD for audio device drivers that prevents DOS sessions from accessing the audio hardware when an OS/2 session is using it and vice versa. The driver comes with OS/2 and is used by a lot of diferent soundcards.
  DEVICE=ASP4OS2.SYS
  DEVICE=C:\MMOS2\AUDIOVDD.SYS
 
'''Parameter:'''


{| class="wikitable"
* PAS161$ for the MediaVision's ProAudio Spectrum Soundcard
|+Platform Support:
* SBAUD1$ for the Sound Blaster 16 sound card
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|Yes
|Yes
|Yes
|}


==ASP4VDD.SYS==
'''NOTE:''' the parameter is the link between the OS2 driver and the DOS driver. The DOS driver inherits it's settings associated with the parameter
Vortex AU8820 Virtual DOS driver.
DEVICE=ASP4VDD.SYS


{|class="wikitable"
{|class="wikitable"
Line 562: Line 525:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 568: Line 531:
|}
|}


==ASPIDRV.SYS==
ASPI Driver supplied by Solution Technology Inc. (STI)
DEVICE=ASPIDRV.SYS


{|class="wikitable"
==BT32.SYS==
|+Platform Support:
Radio/TV driver for BT878 based Cards
!OS/2 2.x
DEVICE=BT32.SYS
!OS/2 3.0
 
!OS/2 4.0
'''Parameters:'''
!OS/2 4.5x
* /V - Verbose: Show Copyright information
* /VM - Verbose modules: Like /V plus module list
* /3 - Execute an INT3 at initialisation (Use kernel debugger!)
* /NOMODULE - Don't load modules at system startup (Use BT32CFG.EXE to load/unload)
* /NOCOREMODULE - Don't load core modules at system startup (Use BT32CFG.EXE to load/unload)
* /MODPARM: - Support Linux insmod parameters for various modules
* /LOADMODULE: - Load module (only with parameter /NOCOREMODULE)
* /NOIRQ - Disable IRQ for BTTV. This is for test purposes only when the driver traps at startup
 
'''NOTE:''' BT32.SYS must reside after LXAPI32.SYS.
 
'''NOTE:''' BT32.SYS contains the following modules:
* bttv
* tvaudio
* tuner
* msp3400
* tda7432
* tda9875
 
'''NOTE:'''
'''Module parameters:'''
BT32.SYS contains a lot of module parameters. See documentation in the DOC directory of the package.
Most important paramers are:
* bttv card=n Specify a specific BTTV card.
* tuner=n Specify a specific BTTV tuner.
Valid numbers for n for both parameters are listed in DOC\CARDLIST
 
See DOC\Insmod-options for all other parameters.
 
'''NOTE:''' If you are using wcast.sys also there may be problems to use the bttv driver after an application has used wcast.sys. (Attention: Multimedia Setup also opens wcast.sys!!!) Known results are: No picture, No sound or both.
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 585: Line 581:
|}
|}


==ASPIPFA.SYS==
Device driver used to distinguish between IDE drives and SCSI drives when using Hard Disk Drive Monitor.


The Hard Disk Drive Monitor monitors the status of SMART-compatible harddisk drives in your computer.
==BUSAUDIO.SYS==
available as ftp://ftp.pc.ibm.com/pub/pccbbs/commercial_desktop/zp1t06a.exe
C-Media CMI 8330 Soundcard driver (AD 8329 Chip).
  DEVICE=ASPIPFA.SYS
  DEVICE=BUSAUDIO.SYS
 
'''Parameters:'''
* /D:n - DMA channel, n=0,1 or 3
* /I:n - Interrupt, n=5,7,9,10,11 or 12


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 599: Line 597:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 605: Line 603:
|}
|}


==ASPIROUT.SYS==
==CCSINIT.SYS==
The interface of ASPI Router merely is an extension of the interface of OS2ASPI.DMD
ChipChat Sound Initializer - only needed with Warp 4
needed e.g. by the free CDRecord/2 from [[Chris Wohlgemuth]] available at: http://www.geocities.com/SiliconValley/Sector/5785/ and SANE (Scanner Access Now Easy) from [[Yuri Dario]] available at http://www.geocities.com/SiliconValley/Peaks/4320.
DEVICE=CCSINIT.SYS
DEVICE=ASPIROUT.SYS
 
The ChipChat is one of the rare available Soundcards for the microchannel, it is based on the ESS1688. For more information see: http://www.ChipChat.com


{|class="wikitable" style="text-align:center"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 617: Line 616:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 623: Line 622:
|}
|}


==ASPITAPE.SYS==
==CD1400.SYS==
GTAK Driver for SCSI tape access by GTAR scsitape.dmd and scsitape.sys also belong to the package
RISC COM CD1400 Device driver by DECISION-COMPUTER INTERNATIONAL Co.,LTD
By [[Andreas Kaiser]] Andreas.Kaiser@stuttgart.netsurf.de, gtak258.zip gtar258.zip.
  DEVICE=CD1400.SYS
  DEVICE=ASPITAPE.SYS
 
'''Parameter:'''
* /Mxxxx
card memory address
 
* /Ixx
IRQ Nø
 
* /Cxx
Assign the port number of the first port on the card ( COM1 to COM96 )
 
'''NOTE:''' The driver will autodetect the number of communication ports on the card ( 4 or 8 ports ).


{| class="wikitable"
{| class="wikitable"
Line 635: Line 645:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 641: Line 651:
|}
|}


==ATALK.SYS==
==CDBASPI.SYS==
Appletalk driver from IBM LAN Server for Macintosh
CD-TEK driver to access easily the PIONEER DRM-1804X autochange CD-ROM device.
  DEVICE=ATALK.SYS
  DEVICE=CDBASPI.SYS


{|class="wikitable"
{|class="wikitable"
Line 652: Line 662:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 658: Line 668:
|}
|}


==ATI0.sys==
*[[CDMF.SYS]] - IBM CDMF
Used by ATI 3D Rage graphic adapter cards.
 
  DEVICE=x:\OS2\ATI0.sys
==CDMGRDRV.SYS==
Driver of the FREE CD-Rom Manager for Plextor SCSI CD-ROM drives. Developed by [[Markus Mueller|Markus]] and [[Christian Mueller]].
  DEVICE=CDMGRDRV.SYS


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 669: Line 681:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 675: Line 687:
|}
|}


==ATIM64.SYS==
*[[CDROMMGR.DMD]] - CD-ROM changer device manager
Used by ATI 3D Rage graphic adapter cards.
 
  DEVICE=x:\OS2\ATIM64.SYS  
==CLEANUP.SYS==
This is a simple device driver that DELETES the specified file. Wild cards are NOT supported. To delete multiple files, add multiple times to config.sys.
Part of the Graham Utilities 2.X available at http://www.warpspeed.com.au/graham.htm
  DEVICE=CLEANUP.SYS


{|class="wikitable"
{|class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 692: Line 707:
|}
|}


==ATKP.SYS==
==CLICHOS2.SYS==
Appletalk PAP Port driver from IBM LAN Server for Macintosh.
Crystal Semiconductor CS4299 AC97 Audio Driver (to be found e.g. on IBM T23 Thinkpad)
  DEVICE=ATKP.SYS
This chip doesn't support Midi, you need Timidity to geht Midi working.
  DEVICE=CLICHOS2.SYS


{|class="wikitable"
{|class="wikitable"
Line 706: Line 722:
|Yes
|Yes
|Yes
|Yes
|Yes*
|Yes
|}
|}


==AUDIOVDD.SYS==
==CMPCI16.SYS==
This is the standard VDD for audio device drivers that prevents DOS sessions from accessing the audio hardware when an OS/2 session is using it and vice versa. The driver comes with OS/2 and is used by a lot of diferent soundcards.
C-Media CMI8738 OS/2 Audio Driver ported from Linux sources, based on the SBLive project.
  DEVICE=C:\MMOS2\AUDIOVDD.SYS
  DEVICE=CMPCI16.SYS
 
'''Parameter:'''
'''Parameter:'''
* /V
verbose (prints copyrights during driver init)
* /C
enable CD audio input
* /M
enable microphone audio input
* /L
enable linein audio input
* /A
enable auxin audioinput (since ver. 0.13)


* PAS161$ for the MediaVision's ProAudio Spectrum Soundcard
{| class="wikitable"
* SBAUD1$ for the Sound Blaster 16 sound card
 
'''NOTE:''' the parameter is the link between the OS2 driver and the DOS driver. The DOS driver inherits it's settings associated with the parameter
 
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 733: Line 753:
|}
|}


==CMPCI32.SYS==
C-Media CMI8738 OS/2 Audio Driver
DEVICE=CMPCI32.SYS


==BT32.SYS==
'''Parameter:'''
Radio/TV driver for BT878 based Cards
DEVICE=BT32.SYS


'''Parameters:'''
* /V:  
* /V - Verbose: Show Copyright information
verbose (prints copyrights during driver init)
* /VM - Verbose modules: Like /V plus module list
* /D:
* /3 - Execute an INT3 at initialisation (Use kernel debugger!)
print start and end address of code (useful to locate the code that causes a trap (CS:EIP in trapscreen))
* /NOMODULE - Don't load modules at system startup (Use BT32CFG.EXE to load/unload)
* /R:  
* /NOCOREMODULE - Don't load core modules at system startup (Use BT32CFG.EXE to load/unload)
use linein jack to output rear channels
* /MODPARM: - Support Linux insmod parameters for various modules
* /LOADMODULE: - Load module (only with parameter /NOCOREMODULE)
* /NOIRQ - Disable IRQ for BTTV. This is for test purposes only when the driver traps at startup


'''NOTE:''' BT32.SYS must reside after LXAPI32.SYS.
{| class="wikitable"
 
'''NOTE:''' BT32.SYS contains the following modules:
* bttv
* tvaudio
* tuner
* msp3400
* tda7432
* tda9875
 
'''NOTE:'''
'''Module parameters:'''
BT32.SYS contains a lot of module parameters. See documentation in the DOC directory of the package.
Most important paramers are:
* bttv card=n Specify a specific BTTV card.
* tuner=n Specify a specific BTTV tuner.
Valid numbers for n for both parameters are listed in DOC\CARDLIST
 
See DOC\Insmod-options for all other parameters.
 
'''NOTE:''' If you are using wcast.sys also there may be problems to use the bttv driver after an application has used wcast.sys. (Attention: Multimedia Setup also opens wcast.sys!!!) Known results are: No picture, No sound or both.
 
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 783: Line 779:
|}
|}


==COM.SYS==
This driver is required for serial communications.
DEVICE=C:\OS2\Boot\COM.SYS <parameters>


==BUSAUDIO.SYS==
'''TIP:''' below. This line MUST appear after any driver that uses a communications port. Older versions of COM.SYS are limited to 57600 Baud, newer ones (e.g. delivered with Warp 4) are able to do 115200 Baud. Beginning with build 10.042 PCI Add-On cards with implemented software interrupt sharing are supported too, beginning with build 10.052 there are 16 com ports available and beginning with build 10.068 Combo Cards are supported.
C-Media CMI 8330 Soundcard driver (AD 8329 Chip).
DEVICE=BUSAUDIO.SYS


'''Parameters:'''
'''TIP:''' There are two very good replacement drivers called SIO.SYS\VSIO.SYS.
* /D:n - DMA channel, n=0,1 or 3
* /I:n - Interrupt, n=5,7,9,10,11 or 12


{| class="wikitable"
'''TIP:''' To add support for COM3 and COM4 at location 3E8 with IRQ 4 and 2E8 with IRQ 3 respectively, add (3,3E8,4) (4,2E8,3) to the DEVICE line, e.g.
|+Platform Support:
DEVICE=drive:\OS2\COM.SYS (3,3E8,4) (4,2E8,3)
!OS/2 2.x
You can also use this method to change a COM ports assigned IRQ. The normal address for COM1 is 3F8 and IRQ 4, for COM2 2F8 and IRQ3.
!OS/2 3.0
 
!OS/2 4.0
'''TIP:''' With ThinkPads should the address be added. e.g:
!OS/2 4.5x
DEVICE=drive:\OS2\BOOT\COM.SYS (1,3F8,4) (2,2F8,3)
|-
|Yes
|Yes
|Yes
|Yes
|}


==CCSINIT.SYS==
'''Parameter:'''
ChipChat Sound Initializer - only needed with Warp 4
DEVICE=CCSINIT.SYS


The ChipChat is one of the rare available Soundcards for the microchannel, it is based on the ESS1688. For more information see: http://www.ChipChat.com
* /V
Verbose (since 10.052)
* /W
Wait verbose mode (since 10.052). Displaying pauses with a "Press Enter to continue..." message.
* /F
Find COM ports on PCI combo (serial/parallel) cards automatically (since 10.068).


{|class="wikitable"
{|class="wikitable"
Line 824: Line 816:
|}
|}


==CD1400.SYS==
==COM02.SYS==
RISC COM CD1400 Device driver by DECISION-COMPUTER INTERNATIONAL Co.,LTD
For IBM PS/2 model 90 & 95 only.
  DEVICE=CD1400.SYS
Lets you use the communications ports COM1 and COM2. See DEVICE COM.SYS.
 
  DEVICE=COM02.SYS
'''Parameter:'''
* /Mxxxx
card memory address
 
* /Ixx
IRQ Nø
 
* /Cxx
Assign the port number of the first port on the card ( COM1 to COM96 )
 
'''NOTE:''' The driver will autodetect the number of communication ports on the card ( 4 or 8 ports ).


{| class="wikitable"
{| class="wikitable"
Line 853: Line 834:
|}
|}


==CDBASPI.SYS==
==CONCERTO.SYS==
CD-TEK driver to access easily the PIONEER DRM-1804X autochange CD-ROM device.  
Pen for OS/2 Device Driver for Compaq Concerto.
  DEVICE=CDBASPI.SYS
  DEVICE=CONCERTO.SYS


{|class="wikitable"
{|class="wikitable"
Line 870: Line 851:
|}
|}


==CDMF.SYS==
==CPPVDD.SYS==
Used by the Firewall built into TCP/IP 4.1 and above. This is IBM's Commerical Data Masking Facility encryption driver. This driver is an early version of the IBM proposed new national standard encryption protocol (US) with a variable key of up to 128-bits. It supports the VPN (Virtual Private Network) built-in to the firewall of TCPIP 4.1 and later. This driver uses a larger data block than DES and is faster than competing protocol drivers. It is a enhanced version of
PU Monitor Plus Virtual DOS Driver.
DES. Many to don't consider it as strong an algorithm as Blowfish or Ideal, widely available competitors to this protocol.
  DEVICE=CPPVDD.SYS
  DEVICE=x:\MPTN\PROTOCOL\CDMF.SYS  


{| class="wikitable"
'''TIP:''' By [[Daryl Sperber]]: CPUMONP was last updated in 1996 (for FP17 of Warp connect) and has worked just fine for Warp 3 and Warp 4 all this time. However it obviously now has a fatal incompatibility with FP14 of Warp 4 that is causing the Trap 000e for me.  
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|Yes
|Yes
|Yes
|}
 
==CDMGRDRV.SYS==
Driver of the FREE CD-Rom Manager for Plextor SCSI CD-ROM drives. Developed by [[Markus Mueller|Markus]] and [[Christian Mueller]].
DEVICE=CDMGRDRV.SYS


{| class="wikitable"
{| class="wikitable"
Line 899: Line 864:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|}
==CDROMMGR.DMD==
CD-ROM device manager which prevents subsequent requests to different slots of a CD changer.
DEVICE=CDROMMGR.DMD
'''NOTE:''' OS2CDROM.DMD must be disabled to work.
'''Parameter:'''
* /T:n
CDROMMGR.DMD has the changer feature enabled by default. It prevents slot changes for 1000ms by returning ERROR_DEVICE_NOT_READY to the caller. The timeout value can be set at load time through option /T: The
valid range is from 1 second up to 60 seconds. If CDROMMGR.DMD does not find a CD Changer device, the feature will automatically be disabled and cannot be activated.
* /C
CDROMMGR.DMD will manage only CD Changers. Normal CD-ROM drives or CD Burners will not get allocated. This option is
useful if you want to use another CD-ROM device manager for special features, like CTCDROM.DMD for Unite CD-Maker. To make sure that CDROMMGR.DMD gets control over the CD Changer devices, it has to be loaded as the first CD-ROM manager.
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|Yes
|Yes
|Yes
|Yes
Line 933: Line 870:
|}
|}


==CLEANUP.SYS==
==CT5880.SYS==
This is a simple device driver that DELETES the specified file. Wild cards are NOT supported. To delete multiple files, add multiple times to config.sys.
Creative Lab Ensoniq CT5880 PCI Audio Device Driver.
Part of the Graham Utilities 2.X available at http://www.warpspeed.com.au/graham.htm
  DEVICE=CT5880.SYS
  DEVICE=CLEANUP.SYS
'''NOTE:''' No MIDI support, no WIN/OS2 support.


{|class="wikitable"
{|class="wikitable"
Line 951: Line 888:
|}
|}


==CLICHOS2.SYS==
==CWAUDIO.SYS==
Crystal Semiconductor CS4299 AC97 Audio Driver (to be found e.g. on IBM T23 Thinkpad)
Sound Drivers for the Crystal CS4231, 4232 (A, B), 4235, 4236 (B, D, E), 4237B, 4238B, 4239.
This chip doesn't support Midi, you need Timidity to geht Midi working.
  DEVICE=CWAUDIO.SYS
  DEVICE=CLICHOS2.SYS
 
'''NOTE:''' for 4231, 4232 and 4236 use 'Mode2' driver version (latest 1.7)


{|class="wikitable"
'''TIP:''' If you have problems with the Yamaha OPL3-SAx chipset: According to a user, instead of using the Yamaha OPL-3 SAx drivers for the same audio chipset, using the driver for Crystal CS4232 works fine without any limitations.
 
A FREE mixer for the crystal cards is LBCSMix V1.0 from http://freebyte.ml.org/~boga/OS2Programs.html
 
'''Parameter for 'mode3' drivers:'''
* /N:
Name of PDD BSAUD1$ (Supplied by install)
* /V
Verbose Display
* /X1:
AUX1 unmute/gain 0..100 (decimal) (*50) (usually "Line-In")
* /X2:
AUX2 unmute/gain 0..100 (decimal) (*50) (usually CD-ROM)
* /L:
LINE unmute/gain 0..100 (decimal) (*100)(FM volume)
* /LCAPT:
Line-In record source X1, X2, *X1X2, L (X1X2 is mixed aux1+aux2)
* /T:
Inactivity power down 1..5 minutes (*1)
* /MBY:<0,1>
Mono bypass *1 (mono-in connected to mono-out)
* /MIM:<0,1>
Mono input mute *1 (mono-in not connected to input mixer)
* /MOM:<0,1>
Mono out mute *0 (audible)
* /XCTRL0:<0,1>
XCTRL0 Pin set System specific. Sometimes used to
* /XCTRL1:<0,1>
XCTRL1 Pin set control power to amplifier. On IBM
Aptiva with Bose speakers, set both to 1
* /P:
Codec Port *534, 608, (530..FF8, divisible by 4)
* /I:
Codec IRQ *5, 7, 9, 11, 15 (decimal)
* /D:
Codec DMA 0, 1, 3 (Default 1,0)
* /C:
Control Port 120, *538, (120..FF8, divisible by 8)
* /J:
Joystick Port *200, 208, NONE
* /S:
Sound Blaster Port *220, 240, 260, 280, NONE
* /M:
MPU Port and IRQ *330, NONE, (300..3E0, divisible by 8)
IRQ: 7, 9, 11, 12, 15, *NONE
* /F:
FM synth port *388, NONE, (388..3F8, divisible by 8)
* /IRQRate:dd
Target interrupt rate *32 Range: 1..64 interrupts per second
* /DMASize:nnnn
DMA Buf size maximum *8192 Range: 256..16384 (2 IRQs/Buffer)
 
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 969: Line 959:
|}
|}


==CMPCI16.SYS==
==CWGUTIL.SYS==
C-Media CMI8738 OS/2 Audio Driver ported from Linux sources, based on the SBLive project.
Crystal DSP manager utility device driver.
  DEVICE=CMPCI16.SYS
  DEVICE=CWGUTIL.SYS
'''Parameter:'''
* /V
verbose (prints copyrights during driver init)
* /C
enable CD audio input
* /M
enable microphone audio input
* /L
enable linein audio input
* /A
enable auxin audioinput (since ver. 0.13)


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 997: Line 976:
|}
|}


==CMPCI32.SYS==
==CWMPU401.SYS==
C-Media CMI8738 OS/2 Audio Driver
Crystal MPU401 driver for a complete discription see MPU401.SYS.
  DEVICE=CMPCI32.SYS
  DEVICE=CWMPU401.SYS


'''Parameter:'''
{|class="wikitable"
 
* /V:
verbose (prints copyrights during driver init)
* /D:
print start and end address of code (useful to locate the code that causes a trap (CS:EIP in trapscreen))
* /R:
use linein jack to output rear channels
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,023: Line 993:
|}
|}


==COM.SYS==
==CWVAUDIO.SYS==
This driver is required for serial communications.
Virtual DOS driver for Crystal Soundcards
  DEVICE=C:\OS2\Boot\COM.SYS <parameters>
  DEVICE=<drive>:\MMOS2\CWVAUDIO.SYS BSAUD1$


'''TIP:''' below. This line MUST appear after any driver that uses a communications port. Older versions of COM.SYS are limited to 57600 Baud, newer ones (e.g. delivered with Warp 4) are able to do 115200 Baud. Beginning with build 10.042 PCI Add-On cards with implemented software interrupt sharing are supported too, beginning with build 10.052 there are 16 com ports available and beginning with build 10.068 Combo Cards are supported.
'''Parameter:'''


'''TIP:''' There are two very good replacement drivers called SIO.SYS\VSIO.SYS.
* /S
The CWVAUDIO.SYS driver will automatically set a 'BLASTER' DOS environment variable to the proper audio hardware settings. This is done by adding a '@SET BLASTER=' line to the beginning of all DOS session's autoexec file. This file is specified in DOS session's DOS_AUTOEXEC property. The /S option for CWVAUDIO.SYS will skip the automatic setting of this environment variable.


'''TIP:''' To add support for COM3 and COM4 at location 3E8 with IRQ 4 and 2E8 with IRQ 3 respectively, add (3,3E8,4) (4,2E8,3) to the DEVICE line, e.g.
{|class="wikitable"
DEVICE=drive:\OS2\COM.SYS (3,3E8,4) (4,2E8,3)
|+Platform Support:
You can also use this method to change a COM ports assigned IRQ. The normal address for COM1 is 3F8 and IRQ 4, for COM2 2F8 and IRQ3.
!OS/2 2.x
 
!OS/2 3.0
'''TIP:''' With ThinkPads should the address be added. e.g:
DEVICE=drive:\OS2\BOOT\COM.SYS (1,3F8,4) (2,2F8,3)
 
'''Parameter:'''
 
* /V
Verbose (since 10.052)
* /W
Wait verbose mode (since 10.052). Displaying pauses with a "Press Enter to continue..." message.
* /F
Find COM ports on PCI combo (serial/parallel) cards automatically (since 10.068).
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
Line 1,060: Line 1,015:
|}
|}


==COM02.SYS==
==CWVOPL3.SYS==
For IBM PS/2 model 90 & 95 only.
Crystal Midi FM Virtual Dos Driver.
Lets you use the communications ports COM1 and COM2. See DEVICE COM.SYS.
  DEVICE=CWVOPL3.SYS
  DEVICE=COM02.SYS


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,078: Line 1,032:
|}
|}


==CONCERTO.SYS==
==CWWINPDD.SYS==
Pen for OS/2 Device Driver for Compaq Concerto.
Crystal WinOS2 Audio PDD.
  DEVICE=CONCERTO.SYS
  DEVICE=CWWINPDD.SYS


{|class="wikitable"
{|class="wikitable"
Line 1,095: Line 1,049:
|}
|}


==CPPVDD.SYS==
==CWWINVDD.SYS==
PU Monitor Plus Virtual DOS Driver.
Crystal VDD supporting WinOS2 audio DRV.
  DEVICE=CPPVDD.SYS
  DEVICE=CWWINVDD.SYS


'''TIP:''' By [[Daryl Sperber]]: CPUMONP was last updated in 1996 (for FP17 of Warp connect) and has worked just fine for Warp 3 and Warp 4 all this time. However it obviously now has a fatal incompatibility with FP14 of Warp 4 that is causing the Trap 000e for me.
{|class="wikitable"
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,114: Line 1,066:
|}
|}


==CT5880.SYS==
==DC21X4.OS2==
Creative Lab Ensoniq CT5880 PCI Audio Device Driver.
Digital Semiconductor DC21X4-based Ethernet Adapter Network driver.  
  DEVICE=CT5880.SYS
  DEVICE=DC21X4.OS2
'''NOTE:''' No MIDI support, no WIN/OS2 support.


{|class="wikitable"
{|class="wikitable"
Line 1,132: Line 1,083:
|}
|}


==CWAUDIO.SYS==
==DCF2CDE.SYS==
Sound Drivers for the Crystal CS4231, 4232 (A, B), 4235, 4236 (B, D, E), 4237B, 4238B, 4239.
This driver is used by the DCF/2 disk compression program.
  DEVICE=CWAUDIO.SYS
  DEVICE=C:\Dcf2\DCF2CDE.SYS
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


'''NOTE:''' for 4231, 4232 and 4236 use 'Mode2' driver version (latest 1.7)
==DCF2PDD.SYS==
This driver is used by the DCF/2 disk compression program.
DEVICE=C:\Dcf2\DCF2PDD.SYS <parameter>


'''TIP:''' If you have problems with the Yamaha OPL3-SAx chipset: According to a user, instead of using the Yamaha OPL-3 SAx drivers for the same audio chipset, using the driver for Crystal CS4232 works fine without any limitations.
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


A FREE mixer for the crystal cards is LBCSMix V1.0 from http://freebyte.ml.org/~boga/OS2Programs.html
==DCF2MGR.SYS==
This driver is used by the DCF/2 disk compression program.
DEVICE=C:\Dcf2\DCF2MGR.SYS <parameter>


'''Parameter for 'mode3' drivers:'''
{|class="wikitable"
* /N:
|+Platform Support:
Name of PDD BSAUD1$ (Supplied by install)
!OS/2 2.x
* /V
!OS/2 3.0
Verbose Display
!OS/2 4.0
* /X1:
!OS/2 4.5x
AUX1 unmute/gain 0..100 (decimal) (*50) (usually "Line-In")
* /X2:
AUX2 unmute/gain 0..100 (decimal) (*50) (usually CD-ROM)
* /L:
LINE unmute/gain 0..100 (decimal) (*100)(FM volume)
* /LCAPT:
Line-In record source X1, X2, *X1X2, L (X1X2 is mixed aux1+aux2)
* /T:
Inactivity power down 1..5 minutes (*1)
* /MBY:<0,1>
Mono bypass *1 (mono-in connected to mono-out)
* /MIM:<0,1>
Mono input mute *1 (mono-in not connected to input mixer)
* /MOM:<0,1>
Mono out mute *0 (audible)
* /XCTRL0:<0,1>
XCTRL0 Pin set System specific. Sometimes used to
* /XCTRL1:<0,1>
XCTRL1 Pin set control power to amplifier. On IBM
Aptiva with Bose speakers, set both to 1
* /P:
Codec Port *534, 608, (530..FF8, divisible by 4)
* /I:
Codec IRQ *5, 7, 9, 11, 15 (decimal)
* /D:
Codec DMA 0, 1, 3 (Default 1,0)
* /C:
Control Port 120, *538, (120..FF8, divisible by 8)
* /J:
Joystick Port *200, 208, NONE
* /S:
Sound Blaster Port *220, 240, 260, 280, NONE
* /M:
MPU Port and IRQ *330, NONE, (300..3E0, divisible by 8)
IRQ: 7, 9, 11, 12, 15, *NONE
* /F:
FM synth port *388, NONE, (388..3F8, divisible by 8)
* /IRQRate:dd
Target interrupt rate *32 Range: 1..64 interrupts per second
* /DMASize:nnnn
DMA Buf size maximum *8192 Range: 256..16384 (2 IRQs/Buffer)
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|-
|Yes
|Yes
Line 1,203: Line 1,134:
|}
|}


==CWGUTIL.SYS==
==DCF77.SYS==
Crystal DSP manager utility device driver.
Driver for DCF77-Radiocontrol Watch.
  DEVICE=CWGUTIL.SYS
Available for FREE at http://www.prog-link.com
  DEVICE=DCF77.SYS


{|class="wikitable"
'''Parameter:'''
* /P:Port
Port, 201 (Gameport), 379 (LPT1),
279 (LPT2), 3BD (LPT3), 3F8 (COM1), 2F8 (COM2), 3E8 (COM3), 2E8 (COM4)
* /IRQ=nn (or /I:nn)
Interrupt, 3, 4, 5, 7, 9, 10, 11, 12, 15 or NONE. With
NONE Polling-Mode is used
* /V
Verbose
* /Q
Quiet, disables displaying informations during start
 
'''NOTE:''' For a complete list of parameters see the documentation deliverd with the driver.
 
==DDE4EXTRA.SYS==
Is used by the IBM C Set++ Compiler.
DEVICE=C:\User\Cset21\DDE4EXTRA.SYS
 
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,220: Line 1,170:
|}
|}


==CWMPU401.SYS==
==DE528.OS2==
Crystal MPU401 driver for a complete discription see MPU401.SYS.
D-Link 528CT Ethernet Adapter Network driver.
  DEVICE=CWMPU401.SYS
  DEVICE=DE528.OS2
 
'''NOTE:''' It is impossible with this driver to execute graphical apps using Exceed.


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,237: Line 1,189:
|}
|}


==CWVAUDIO.SYS==
==DELAY.SYS==
Virtual DOS driver for Crystal Soundcards
Device driver for providing a timed delay during system startup avaliable for FREE at http://www.tavi.co.uk/os2pages/delay.html
  DEVICE=<drive>:\MMOS2\CWVAUDIO.SYS BSAUD1$
  DEVICE=DELAY.SYS <parameters>


'''Parameter:'''
'''Parameter:'''


* /S
* /K /k,
The CWVAUDIO.SYS driver will automatically set a 'BLASTER' DOS environment variable to the proper audio hardware settings. This is done by adding a '@SET BLASTER=' line to the beginning of all DOS session's autoexec file. This file is specified in DOS session's DOS_AUTOEXEC property. The /S option for CWVAUDIO.SYS will skip the automatic setting of this environment variable.
-K and -k are equivalent. exits the delay period immediately by pressing any key (apart shift, ctrl, alt etc.)
* mm:ss
is the intended delay in minutes and seconds.
message is an optional message that will appear during the delay period.


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,259: Line 1,218:
|}
|}


==CWVOPL3.SYS==
==DES.SYS==
Crystal Midi FM Virtual Dos Driver.
This is the current national standard encryption protocol (US) used in triple DES encryption with 128-bit key. It is currently being replaced by a new, but yet not chosen protocol. Use to encrypt user data by the VPN service.
  DEVICE=CWVOPL3.SYS
  DEVICE=DES.SYS


{|class="wikitable"
{|class="wikitable"
Line 1,276: Line 1,235:
|}
|}


==CWWINPDD.SYS==
==DFE650.OS2==
Crystal WinOS2 Audio PDD.
D-Link DFE-650 Fast Ethernet PC Card. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.
  DEVICE=CWWINPDD.SYS
  DEVICE=DFE650.OS2


{|class="wikitable"
{|class="wikitable"
Line 1,293: Line 1,252:
|}
|}


==CWWINVDD.SYS==
==DISKFIT.SYS==
Crystal VDD supporting WinOS2 audio DRV.
Driver for the fault tolerance system. See OS/2 manual for more information.
DEVICE=CWWINVDD.SYS
  DEVICE=DISKFIT.SYS


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,310: Line 1,273:
|}
|}


==DC21X4.OS2==
Digital Semiconductor DC21X4-based Ethernet Adapter Network driver.
DEVICE=DC21X4.OS2


{|class="wikitable"
 
|+Platform Support:
=DM9PCI.OS2=
DAVICOM DM9 PCI Series Fast Ethernet Adapter (e.g., on the SiS530 motherboard). http://www.davicom.com.tw
DEVICE=DM9PCI.OS2
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,327: Line 1,293:
|}
|}


==DCF2CDE.SYS==
=DOS.SYS=
This driver is used by the DCF/2 disk compression program.
Is needed if you want to run DOS or Windows applications.
  DEVICE=C:\Dcf2\DCF2CDE.SYS
  DEVICE=C:\OS2\BOOT\DOS.SYS


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,344: Line 1,311:
|}
|}


==DCF2PDD.SYS==
==DP820A.SYS==
This driver is used by the DCF/2 disk compression program.
National Semiconductor DP83820 Another NDIS 2.0.1 MAC driver.
  DEVICE=C:\Dcf2\DCF2PDD.SYS <parameter>
  DEVICE=DP820A.SYS


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,361: Line 1,329:
|}
|}


==DCF2MGR.SYS==
=DP83815.OS2=
This driver is used by the DCF/2 disk compression program.
National Semiconductor DP83815 10/100 MacPhyter3v PCI Adapter.
  DEVICE=C:\Dcf2\DCF2MGR.SYS <parameter>
  DEVICE=DP83815.OS2


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,378: Line 1,347:
|}
|}


==DCF77.SYS==
==DPROM01.SYS==
Driver for DCF77-Radiocontrol Watch.
This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.
Available for FREE at http://www.prog-link.com
DEVICE=DCF77.SYS


'''Parameter:'''
Examples:  
* /P:Port
DEVICE=X:\XPROSYS\EXE\DPROM01.SYS MAXSPEED=9600
Port, 201 (Gameport), 379 (LPT1),
279 (LPT2), 3BD (LPT3), 3F8 (COM1), 2F8 (COM2), 3E8 (COM3), 2E8 (COM4)
* /IRQ=nn (or /I:nn)
Interrupt, 3, 4, 5, 7, 9, 10, 11, 12, 15 or NONE. With
NONE Polling-Mode is used
* /V
Verbose
* /Q
Quiet, disables displaying informations during start


'''NOTE:''' For a complete list of parameters see the documentation deliverd with the driver.
'''Platform Support:'''
 
{| class="wikitable"
==DDE4EXTRA.SYS==
|-
Is used by the IBM C Set++ Compiler.
DEVICE=C:\User\Cset21\DDE4EXTRA.SYS
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,408: Line 1,361:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 1,414: Line 1,367:
|}
|}


==DE528.OS2==
=DRVOCDB.SYS=
D-Link 528CT Ethernet Adapter Network driver.
Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.
  DEVICE=DE528.OS2
  DEVICE=DRVOCDB.SYS
 
'''NOTE:''' It is impossible with this driver to execute graphical apps using Exceed.


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,433: Line 1,385:
|}
|}


==DELAY.SYS==
=DRVOPPQT.SYS=
Device driver for providing a timed delay during system startup avaliable for FREE at http://www.tavi.co.uk/os2pages/delay.html
Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.
  DEVICE=DELAY.SYS <parameters>
  DEVICE=DRVOPPQT.SYS
 
'''Parameter:'''
 
* /K /k,
-K and -k are equivalent. exits the delay period immediately by pressing any key (apart shift, ctrl, alt etc.)
* mm:ss
is the intended delay in minutes and seconds.
message is an optional message that will appear during the delay period.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 1,452: Line 1,396:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,463: Line 1,403:
|}
|}


==DES.SYS==
=DRVOQ117.SYS=
This is the current national standard encryption protocol (US) used in triple DES encryption with 128-bit key. It is currently being replaced by a new, but yet not chosen protocol. Use to encrypt user data by the VPN service.
Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.
  DEVICE=DES.SYS
  DEVICE=DRVOQ117.SYS


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,480: Line 1,421:
|}
|}


==DFE650.OS2==
===DTA.SYS===
D-Link DFE-650 Fast Ethernet PC Card. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.
Data Transport Agent (DTA) Driver for eComStation.
  DEVICE=DFE650.OS2
It is meant to improve the ability to handle datastreams in eCS, DOS and Win-OS/2 sessions. In addition it will enable virtual DOS sessions to play sound via a generic sounddriver, effectively bypassing the need for soundcard specific DOS drivers.  
  DEVICE=DTA.SYS


{|class="wikitable"
{|class="wikitable"
Line 1,491: Line 1,433:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|
|Yes
|
|Yes
|Yes
|Yes
|Yes
|}
|}


==DISKFIT.SYS==
===DTSXPC01.SYS===
Driver for the fault tolerance system. See OS/2 manual for more information.
This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.
  DEVICE=DISKFIT.SYS
This is the TSXPC01 driver.  
 
Examples:
  DEVICE=X:\XPROSYS\EXE\DTSXPC01.SYS MAXSPEED=19200
 
  DEVICE=X:\XPROSYS\EXE\DTSXPC01.SYS COM=COM2 MAXSPEED=19200


'''Platform Support:'''
{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,519: Line 1,461:
|}
|}


=DEVICE=DLKRTS.OS2=
===DUNTLW01.SYS===
D-Link DFE-530TX+ 10/100 Ethernet NIC.
This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.  
DEVICE=DLKRTS.OS2
This is the UNTLW01 driver.  


'''Platform Support:'''
Examples:
{| class="wikitable" style="text-align:center" border="1"
Ver 5.6 (MINI X-TEL)
|-
DEVICE=X:\XPROSYS\EXE\DUNTLW01.SYS COM=COM1 SPEED=9600 BASE=1 NBR=2 DNS=0 TIMEOUT=0 PARITY=O NB_BIT=8 NBSTOP=1
Ver 6.0
DEVICE=X:\XPROSYS\EXE\DUNTLW01.SYS PROFILE=D:\XPROSYS\EXE\DUNTLW.001
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,531: Line 1,478:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 1,537: Line 1,484:
|}
|}


=DEVICE=DM9PCI.OS2=
===E1000.OS2===
DAVICOM DM9 PCI Series Fast Ethernet Adapter (e.g., on the SiS530 motherboard). http://www.davicom.com.tw
Intel 8254X Based Network Connection Gigabit Ethernet driver.  
  DEVICE=DM9PCI.OS2
  DEVICE=E1000.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{|class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,555: Line 1,502:
|}
|}


=DEVICE=DOS.SYS=
===E100B.OS2===
Is needed if you want to run DOS or Windows applications.
Intel EtherExpress PRO Adapter, Intel InBusiness Ethernet Adapter.  
  DEVICE=C:\OS2\BOOT\DOS.SYS
  DEVICE=E100B.OS2


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable" style="text-align:center" border="1"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,573: Line 1,519:
|}
|}


==DP820A.SYS==
===E10P.OS2===
National Semiconductor DP83820 Another NDIS 2.0.1 MAC driver.
Intel EtherExpress PRO/10 PCI LAN Adapter.
  DEVICE=DP820A.SYS
  DEVICE=E10P.OS2


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,591: Line 1,536:
|}
|}


=DEVICE=DP83815.OS2=
===E21ND.OS2===
National Semiconductor DP83815 10/100 MacPhyter3v PCI Adapter.
Cabletron E21 Ethernet Adapter.  
  DEVICE=DP83815.OS2
  DEVICE=E21ND.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,609: Line 1,554:
|}
|}


==DPROM01.SYS==
===E22ND.OS2===
This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.
Cabletron E22 Ethernet Adapter (SNMP).
 
  DEVICE=E22ND.OS2
Examples:
  DEVICE=X:\XPROSYS\EXE\DPROM01.SYS MAXSPEED=9600


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,623: Line 1,565:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,629: Line 1,571:
|}
|}


=DEVICE=DRVOCDB.SYS=
===EC2T.OS2===
Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.
Linksys Combo PCMCIA EthernetCard (EC2T).
  DEVICE=DRVOCDB.SYS
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.
  DEVICE=EC2T.OS2


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable" style="text-align:center" border="1"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,647: Line 1,589:
|}
|}


=DEVICE=DRVOPPQT.SYS=
===ECRDRV.SYS===
Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.
Provides support for Remote Support for OS/2. Remote Support can be found in the BonusPak and allows IBM Support Centers to log onto your OS/2 Warp 4 workstation.
  DEVICE=DRVOPPQT.SYS
  DEVICE=C:\Bonuspak\RS231B\Ecrdrv.sys


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable" style="text-align:center" border="1"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,665: Line 1,606:
|}
|}


=DEVICE=DRVOQ117.SYS=
===EL59X.OS2===
Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.
3Com Fast EtherLink & EtherLink III Bus Master Family Network driver.
  DEVICE=DRVOQ117.SYS
  DEVICE=EL59X.OS2


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 1,683: Line 1,623:
|}
|}


===DTA.SYS===
===EL90X.OS2===
Data Transport Agent (DTA) Driver for eComStation.
3Com Fast EtherLink/EtherLink XL Family Network driver (e.g. 900 A/B).
It is meant to improve the ability to handle datastreams in eCS, DOS and Win-OS/2 sessions. In addition it will enable virtual DOS sessions to play sound via a generic sounddriver, effectively bypassing the need for soundcard specific DOS drivers.  
  DEVICE=EL90X.OS2
  DEVICE=DTA.SYS


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,695: Line 1,634:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|
|Yes
|
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===DTSXPC01.SYS===
===ELNK3.OS2===
This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.  
3Com Etherlink III Adapter.
This is the TSXPC01 driver.  
DEVICE=ELNK3.OS2


Examples:
{| class="wikitable"
  DEVICE=X:\XPROSYS\EXE\DTSXPC01.SYS MAXSPEED=19200
 
  DEVICE=X:\XPROSYS\EXE\DTSXPC01.SYS COM=COM2 MAXSPEED=19200
 
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,717: Line 1,651:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,723: Line 1,657:
|}
|}


===DUNTLW01.SYS===
===ELPC3.OS2===
This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.  
3Com 3C589 EtherLink III PC Card OS/2 driver.
This is the UNTLW01 driver.  
DEVICE=ELPC3.OS2


Examples:
'''TIP:''' The driver traps on system with more than 500MHz clock rates. To solve the problem get 3c589patch.zip to patch the driver. It includes also a ptach to get the 3net_log utility to work with the drivers V. 1.8.
Ver 5.6 (MINI X-TEL)
DEVICE=X:\XPROSYS\EXE\DUNTLW01.SYS COM=COM1 SPEED=9600 BASE=1 NBR=2 DNS=0 TIMEOUT=0 PARITY=O NB_BIT=8 NBSTOP=1
Ver 6.0
DEVICE=X:\XPROSYS\EXE\DUNTLW01.SYS PROFILE=D:\XPROSYS\EXE\DUNTLW.001


{| class="wikitable"
{| class="wikitable"
Line 1,740: Line 1,670:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 1,746: Line 1,676:
|}
|}


===E1000.OS2===
===ELPC3X.OS2===
Intel 8254X Based Network Connection Gigabit Ethernet driver.  
3Com EtherLink III LAN+Modem PC Card for OS2 V1.5 - Card Services driver.
  DEVICE=E1000.OS2
  DEVICE=ELPC3X.OS2
 
'''TIP:''' If you own a 3COM 3C562D add this setting to your config.sys may get your card working:
BASEDEV=RESERVE.SYS /MEM:CB00,1000.


'''Platform Support:'''
{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,764: Line 1,696:
|}
|}


===E100B.OS2===
===ELSA.SYS===
Intel EtherExpress PRO Adapter, Intel InBusiness Ethernet Adapter.  
Card specific part of GRADD display driver and settings for ELSA WINNER 2000/Office.
  DEVICE=E100B.OS2
  DEVICE=ELSA.SYS


{| class="wikitable"
{| class="wikitable"
Line 1,775: Line 1,707:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|*
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|Yes
|}


===E10P.OS2===
===EMI.SYS===
Intel EtherExpress PRO/10 PCI LAN Adapter.
Pen for OS/2 Mouse Emulation driver.
DEVICE=E10P.OS2


{| class="wikitable"
{| class="wikitable"
Line 1,798: Line 1,729:
|}
|}


===E21ND.OS2===
===EN5251.OS2===
Cabletron E21 Ethernet Adapter.  
Accton EN5251 Based Fast Ethernet Adapter.
  DEVICE=E21ND.OS2
  DEVICE=EN5251.OS2


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
Line 1,816: Line 1,746:
|}
|}


===E22ND.OS2===
===ENDS2ISA.OS2===
Cabletron E22 Ethernet Adapter (SNMP).
Crystal LAN CS8900/CS8920 Ethernet Adapter.
  DEVICE=E22ND.OS2
  DEVICE=ENDS2ISA.OS2


{| class="wikitable"
{| class="wikitable"
Line 1,833: Line 1,763:
|}
|}


===EC2T.OS2===
===EP325.OS2===
Linksys Combo PCMCIA EthernetCard (EC2T).
OS/2 NDIS SURECOM EP-325 PCI Ethernet Adapter (based on Realtek RTL8029).
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.
  DEVICE=EP325.OS2
  DEVICE=EC2T.OS2


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 1,851: Line 1,780:
|}
|}


===ECRDRV.SYS===
===EP427.OS2===
Provides support for Remote Support for OS/2. Remote Support can be found in the BonusPak and allows IBM Support Centers to log onto your OS/2 Warp 4 workstation.
SureCom EtherPerfect-427 PCMCIA Ethernet Card.
  DEVICE=C:\Bonuspak\RS231B\Ecrdrv.sys
  DEVICE=EP427.OS2


{| class="wikitable"
{| class="wikitable"
Line 1,868: Line 1,797:
|}
|}


===EL59X.OS2===
===EQNKRCSH.EXE===
3Com Fast EtherLink & EtherLink III Bus Master Family Network driver.
Driver by Netfinity* Version 5.20.3.
  DEVICE=EL59X.OS2
  DEVICE=EQNKRCSH.EXE


{| class="wikitable"
{| class="wikitable"
Line 1,885: Line 1,814:
|}
|}


===EL90X.OS2===
===EQNKVKBD.SYS===
3Com Fast EtherLink/EtherLink XL Family Network driver (e.g. 900 A/B).
Driver by Netfinity* Version 5.20.3.
  DEVICE=EL90X.OS2
  DEVICE=EQNKVKBD.SYS


{| class="wikitable"
{| class="wikitable"
Line 1,902: Line 1,831:
|}
|}


===ELNK3.OS2===
===EQNRCSH.EXE===
3Com Etherlink III Adapter.
Part of DCAF (Distributed Console Access Facility).
  DEVICE=ELNK3.OS2
  DEVICE=EQNRCSH.EXE
 
'''ATTENTION:''' If you don't have the IBM Internal Y2K fix it won't work after 31.12.1999.


{| class="wikitable"
{| class="wikitable"
Line 1,919: Line 1,850:
|}
|}


===ELPC3.OS2===
===EQNVKBD.SYS===
3Com 3C589 EtherLink III PC Card OS/2 driver.
Part of DCAF (Distributed Console Access Facility).
  DEVICE=ELPC3.OS2
  DEVICE=EQNVKBD.SYS


'''TIP:''' The driver traps on system with more than 500MHz clock rates. To solve the problem get 3c589patch.zip to patch the driver. It includes also a ptach to get the 3net_log utility to work with the drivers V. 1.8.
'''ATTENTION:''' See also DEVICE EQNRCSH.EXE


{| class="wikitable"
{| class="wikitable"
Line 1,938: Line 1,869:
|}
|}


===ELPC3X.OS2===
===ES1371.SYS===
3Com EtherLink III LAN+Modem PC Card for OS2 V1.5 - Card Services driver.
PCI Ensoniq ES1371 Audio Device Driver without Win-OS/2 and Midi support.
  DEVICE=ELPC3X.OS2
  DEVICE=ES1371.SYS
 
'''Note:''' Some users report that the Soundblaster PCI 128 works with this driver. According to the Linux ALSA Project (open-source sound drivers) the ES1371 is built into the PCI 64 and PCI 128. But to complicate things there could also ES1370 chips on the boards
 
There are enhanced drivers (From os2 DDK pciaudio driver sources) with support for ct5880(a,c,d), ev1938(a) based cards developed as a part of Russian Team OS/2 ( OS2.Ru ) projects.


'''TIP:''' If you own a 3COM 3C562D add this setting to your config.sys may get your card working:
See: http://OS2.Ru/index.phtml.en
BASEDEV=RESERVE.SYS /MEM:CB00,1000.


{| class="wikitable"
{| class="wikitable"
Line 1,958: Line 1,892:
|}
|}


===ELSA.SYS===
===ES1688DD.SYS===
Card specific part of GRADD display driver and settings for ELSA WINNER 2000/Office.
Sounddriver for the ESS1688.
  DEVICE=ELSA.SYS
A FREE mixer for this Soundchip is ESSMIX13.ZIP by Oleg Deribas (older@iname.com).
  DEVICE=ES1688DD.SYS


{| class="wikitable"
{| class="wikitable"
Line 1,969: Line 1,904:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|*
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===EMI.SYS===
===ES1868DD.SYS===
Pen for OS/2 Mouse Emulation driver.
Sounddriver for the ESS1868pnp (many soundcards). A FREE Mixer for this soundcard is MINIMIX2.ZIP by Marco G. Salvagno (mgs@whiz.cjb.net) http://whiz.cjb.net.
DEVICE=ES1868DD.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
Line 1,991: Line 1,928:
|}
|}


===EN5251.OS2===
===ES1869DD.SYS===
Accton EN5251 Based Fast Ethernet Adapter.
Driver for the ESS 1869 soundchip.  
  DEVICE=EN5251.OS2
  DEVICE=ES1869DD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,008: Line 1,945:
|}
|}


===ENDS2ISA.OS2===
===ES198X.SYS===
Crystal LAN CS8900/CS8920 Ethernet Adapter.
ESS Allegro-1/Maestro-3 PCI Audio Device Driver.
  DEVICE=ENDS2ISA.OS2
  DEVICE=ES198X.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,025: Line 1,962:
|}
|}


===EP325.OS2===
===ESP.SYS===
OS/2 NDIS SURECOM EP-325 PCI Ethernet Adapter (based on Realtek RTL8029).
Ray Gwinn's Hayes ESP device driver.
  DEVICE=EP325.OS2
  DEVICE=ESP.SYS


{|class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 2,042: Line 1,979:
|}
|}


===EP427.OS2===
===ET32ND.OS2===
SureCom EtherPerfect-427 PCMCIA Ethernet Card.
KTI Networks Inc. base 10 t/tx PCI combo ethernet card.  
  DEVICE=EP427.OS2
  DEVICE=ET32ND.OS2


{| class="wikitable"
{| class="wikitable"
Line 2,059: Line 1,996:
|}
|}


===EQNKRCSH.EXE===
===ET32ND.SYS===
Driver by Netfinity* Version 5.20.3.
Driver for KTI Networks System ethernet card.
  DEVICE=EQNKRCSH.EXE
  DEVICE=ET32ND.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,076: Line 2,013:
|}
|}


===EQNKVKBD.SYS===
===ETHPCI.OS2===
Driver by Netfinity* Version 5.20.3.
Acton EN1207 Ethernet Card.
  DEVICE=EQNKVKBD.SYS
  DEVICE=ETHPCI.OS2


{| class="wikitable"
{| class="wikitable"
Line 2,093: Line 2,030:
|}
|}


===EQNRCSH.EXE===
===EXCPHEAD.SYS===
Part of DCAF (Distributed Console Access Facility).
New with eCS 1.1. This works around a condition in DOSCALL1 when the exception handlers have not yet been initialized during boot, and a failing driver causes a trap. EXCPHEAD.SYS should be loaded before other DEVICE= or IFS= lines in CONFIG.SYS to properly terminate the chain of exception handlers for DOSCALL1.
DEVICE=EQNRCSH.EXE


'''ATTENTION:''' If you don't have the IBM Internal Y2K fix it won't work after 31.12.1999.
This may not be necessary for the 14.104a kernel or above.
DEVICE=EXCPHEAD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,106: Line 2,043:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|
|Yes
|
|Yes
|
|Yes
|eCS
|}
|}


===EQNVKBD.SYS===
===EXMOUSE2.SYS===
Part of DCAF (Distributed Console Access Facility).
Kensington mouse driver for OS/2.
  DEVICE=EQNVKBD.SYS
  DEVICE=EXMOUSE2.SYS


'''ATTENTION:''' See also DEVICE EQNRCSH.EXE
'''NOTE:''' Doesn't work together with the Scitech Display driver


{| class="wikitable"
{| class="wikitable"
Line 2,131: Line 2,068:
|}
|}


===ES1371.SYS===
===EXP16.OS2===
PCI Ensoniq ES1371 Audio Device Driver without Win-OS/2 and Midi support.
Intel EtherExpress 16 Family Adapter Network driver.
  DEVICE=ES1371.SYS
  DEVICE=EXP16.OS2
 
'''Note:''' Some users report that the Soundblaster PCI 128 works with this driver. According to the Linux ALSA Project (open-source sound drivers) the ES1371 is built into the PCI 64 and PCI 128. But to complicate things there could also ES1370 chips on the boards
 
There are enhanced drivers (From os2 DDK pciaudio driver sources) with support for ct5880(a,c,d), ev1938(a) based cards developed as a part of Russian Team OS/2 ( OS2.Ru ) projects.
 
See: http://OS2.Ru/index.phtml.en


{| class="wikitable"
{| class="wikitable"
Line 2,154: Line 2,085:
|}
|}


===ES1688DD.SYS===
===EXTDSKDD.SYS===
Sounddriver for the ESS1688.
EXTDSKDD.SYS supports external disk drives. See your online Command Reference for complete details.
A FREE mixer for this Soundchip is ESSMIX13.ZIP by Oleg Deribas (older@iname.com).
  DEVICE=EXTDSKDD.SYS
  DEVICE=ES1688DD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,172: Line 2,102:
|}
|}


===ES1868DD.SYS===
===FASTNIC.OS2===
Sounddriver for the ESS1868pnp (many soundcards). A FREE Mixer for this soundcard is MINIMIX2.ZIP by Marco G. Salvagno (mgs@whiz.cjb.net) http://whiz.cjb.net.
PCI 10/100 Fast Ethernet Adapter (AN981), PCI 10/100 Fast Ethernet Adapter (AN983), PCI 10/100 Fast Ethernet Adapter (DEC21140), PCI 10/100 Fast Ethernet Adapter (DEC21143) Network Driver.
  DEVICE=ES1868DD.SYS
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/amdtek.zip.
  DEVICE=FASTNIC.OS2


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|+Platform Support:
Line 2,190: Line 2,120:
|}
|}


===ES1869DD.SYS===
===FETND.OS2===
Driver for the ESS 1869 soundchip.  
PCI Fast Ethernet 10M/100M Adapter.
  DEVICE=ES1869DD.SYS
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/via.zip.
  DEVICE=FETND.OS2


{| class="wikitable"
{| class="wikitable"
Line 2,207: Line 2,138:
|}
|}


===ES198X.SYS===
===FIREBIRD.SYS===
ESS Allegro-1/Maestro-3 PCI Audio Device Driver.
Enables the programming of the Gravis Firebird and Thunderbird Joysticks under DOS.
  DEVICE=ES198X.SYS
  DEVICE=FIREBIRD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,224: Line 2,155:
|}
|}


===ESP.SYS===
===FIOAUXDD.SYS===
Ray Gwinn's Hayes ESP device driver.
Device Driver file that contains the device driver that supports mouse port (auxiliary) attachment of both the 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader. [ftp://public.dhe.ibm.com/4700/fiodd/docs/77os2prg.pdf]
  DEVICE=ESP.SYS
  DEVICE=FIOAUXDD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,236: Line 2,167:
|-
|-
|Yes
|Yes
|Yes
|Unknown
|Yes
|Unknown
|Yes
|Unknown
|}
|}


===ET32ND.OS2===
===FIOSERDD.SYS===
KTI Networks Inc. base 10 t/tx PCI combo ethernet card.  
Device Driver for  supports serial attachment of both the 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader. ftp://public.dhe.ibm.com/4700/fiodd/docs/77os2prg.pdf]
  DEVICE=ET32ND.OS2
  DEVICE=FIOSERDD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,253: Line 2,184:
|-
|-
|Yes
|Yes
|Yes
|Unknown
|Yes
|Unknown
|Yes
|Unknown
|}
|}


===ET32ND.SYS===
===FLSH2MTD.SYS===
Driver for KTI Networks System ethernet card.
PCMCIA Storage Driver for OS/2 (FLASH MTD).
  DEVICE=ET32ND.SYS
  DEVICE=FLSH2MTD.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,275: Line 2,206:
|}
|}


===ETHPCI.OS2===
===FMD.SYS===
Acton EN1207 Ethernet Card.
Driver required by Faxworks lite 2.* in Warp 3 or the Pro Versions of Faxworks/PMFax.
  DEVICE=ETHPCI.OS2
  DEVICE=FMD.SYS
 
'''Parameter:'''
* L = disable logo on error free boot
* T = do port tests (default)
* N = no port tests, assume ports exist (PCMCIA default)
* S = allow interrupt sharing (MCA bus only)
* A = get ABIOS LID on port open (MCA bus only)
 
* c = COM number (1-48)
* h = I/O port address (in hex)
* i = interrupt number
(defaults are for the standard COM ports)


{| class="wikitable"
{| class="wikitable"
Line 2,292: Line 2,235:
|}
|}


===EXCPHEAD.SYS===
===FMRADIO.SYS===
New with eCS 1.1. This works around a condition in DOSCALL1 when the exception handlers have not yet been initialized during boot, and a failing driver causes a trap. EXCPHEAD.SYS should be loaded before other DEVICE= or IFS= lines in CONFIG.SYS to properly terminate the chain of exception handlers for DOSCALL1.
Driver for the FREE PMRADIO by [[Paul Ratcliffe]].
OS/2 PM application for driving the Reveal RA300 FM radio card and the old version of the AIMS Labs. RadioTrack card.
DEVICE=FMRADIO.SYS <parameters>
 
'''Parameter:'''
 
* /P:port
port is the RA300 port address (in hex.). The port addresses supported are 30F and 20F. The /P parameter is optional and if not supplied, will default to address 30F.
 
The port address must match that which you have configured on the card itself using jumper JP1. The device driver is Resource Manager compliant and will not install if some other device has already claimed the ports (the hardware actually consumes 4 ports: 30C-30F or 20C-20F).


This may not be necessary for the 14.104a kernel or above.
* /V
DEVICE=EXCPHEAD.SYS
It may be specified if you don't wish the device driver to turn the radio volume down when shutting down OS/2.


{| class="wikitable"
{| class="wikitable"
Line 2,304: Line 2,256:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,315: Line 2,263:
|}
|}


===EXMOUSE2.SYS===
===FWIP.SYS===
Kensington mouse driver for OS/2.
Used by the Firewall built into TCP/IP 4.1 and above. This driver adds IP packet filtering to the Firewall.
  DEVICE=EXMOUSE2.SYS
  DEVICE=C:\Mptn\Potocol\Fwip.sys
 
IP Packet Filter Driver. This component of the VPN security system manages the firewall packet fileter and address translation service. Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall


'''NOTE:''' Doesn't work together with the Scitech Display driver
For configuring the Firewall get the FREE ServerConfig Which can be found at: http://www.ecs.soton.ac.uk/~dm898/soft.html a GUI config util for Apache 1.3.9, InetPowerServer/2 0.85 and the IBM OS/2 TCP/IP Firewall. Author: [[SEHH]] (sehh@altered.com)


{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,334: Line 2,284:
|}
|}


===EXP16.OS2===
===FXWRAP.SYS===
Intel EtherExpress 16 Family Adapter Network driver.
NDIS wrapper for the InJoy Firewall for OS/2
  DEVICE=EXP16.OS2
from: http://www.fx.dk/firewall
  DEVICE=FXWRAP.SYS
 
Designed with Cable Modems and LAN-2-LAN connections in mind, the InJoy Firewall is a complete Internet Gateway, Firewall and IPSec VPN gateway/client in one.
FEATURES: IPSec; PPPoE; Superior performance NDIS Protocol Engine; RFC 1631-NAT support; Direct Internet Access for your LAN PC's; Packet Filtering; Traffic Accounting, Port Redirection; Rule Based Access Control; Identd support; No reconfiguration of software; Great step-by-step docs; YK2; PM & text GUI; DHCP support; On-the-fly updates.


{| class="wikitable"
{| class="wikitable"
Line 2,351: Line 2,305:
|}
|}


===EXTDSKDD.SYS===
===GAMEDD.SYS===
EXTDSKDD.SYS supports external disk drives. See your online Command Reference for complete details.
It is used by many Soundcards. It gives support for the Joystick connector for OS/2 programs.
  DEVICE=EXTDSKDD.SYS
  DEVICE=C:\MMOS2\GAMEDD.sys
 
The following joysticks are supported by this driver:
* Advance Gravis Analog Joystick
* Advance Gravis GamePad
* Advance Gravis Analog Pro
* CH Products Flightstick
* Dexxa Joystick ( Infrared )
* Kraft Thunderstick
* Logitech WingMan Extreme
* Logitech Wingman
* Thrustmaster XL Action Controller
 
There is also an Enhanced Joystick driver by Vesa J„„skel„inen who supports the following joysticks:
* Generic 4 axis and 4 button joystick
* Gravis GamePad Pro (in GrIP mode)
* CH FlightStick Pro


{| class="wikitable"
{| class="wikitable"
Line 2,362: Line 2,332:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 2,368: Line 2,338:
|}
|}


===FASTNIC.OS2===
===GAMEPRT2.SYS===
PCI 10/100 Fast Ethernet Adapter (AN981), PCI 10/100 Fast Ethernet Adapter (AN983), PCI 10/100 Fast Ethernet Adapter (DEC21140), PCI 10/100 Fast Ethernet Adapter (DEC21143) Network Driver.
Joystick interface driver. By Jose DaSilva silva@dowco.com.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/amdtek.zip.
  DEVICE=GAMEPRT2.SYS <parameter>
  DEVICE=FASTNIC.OS2


{| class="wikitable"
'''Parameter:'''
* /VB - displays the gameport header at startup.
* /P:hhhh - Is the joystick port (hhhh=hex address of port)
* /W:hhhh - Is the wait run-a-way counter (hhhh=waiting time).
 
'''NOTE:''' This driver is incompatible with the original IBM GAMEDD.SYS. You must use GAMEDD.SYS from the same author.
 
{| class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 2,380: Line 2,356:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 2,386: Line 2,362:
|}
|}


===FETND.OS2===
===GAMEVDD.SYS===
PCI Fast Ethernet 10M/100M Adapter.  
It is used by many Soundcards. It gives support for the Joystick connector for Dos and Windows programs.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/via.zip.
  DEVICE=C:\MMOS2\GAMEVDD.SYS
  DEVICE=FETND.OS2


{| class="wikitable"
{| class="wikitable"
Line 2,398: Line 2,373:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 2,404: Line 2,379:
|}
|}


===FIREBIRD.SYS===
===GENSCSI.SYS===
Enables the programming of the Gravis Firebird and Thunderbird Joysticks under DOS.
Generic SCSI device driver. The basic function of GENSCSI.SYS is to provide applications with an interface to OS2SCSI.DMD. It only answers 4 commands: Open, Close, IOCtl, and Init. All others cause an Invalid Command error. GENSCSI accepts IOCtl commands in the same format that OS2SCSI does, except GENSCSI expects all addresses to be ring 3 addresses while OS2SCSI expects them to be ring 0 addresses, physical addresses or scatter/gather lists. GENSCSI will convert the ring 3 addresses to the proper form and pass the command on to OS2SCSI. When OS2SCSI is done with the command, it returns the results back to GENSCSI who passes it back to the application. Developed by [[Dennis Rowe]] available for free as part of scsipg.zip.
  DEVICE=FIREBIRD.SYS
  DEVICE=GENSCSI.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,421: Line 2,396:
|}
|}


===FIOAUXDD.SYS===
===GPH2USB.SYS===
Device Driver file that contains the device driver that supports mouse port (auxiliary) attachment of both the 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader. [ftp://public.dhe.ibm.com/4700/fiodd/docs/77os2prg.pdf]
USB driver for GPhoto2
  DEVICE=FIOAUXDD.SYS
  DEVICE=GPH2USB.SYS
 
NOTE: With this driver installed accessing your camera using the USBMSD.ADD or CWUSBMSD.ADD drivers doesn't work.


{| class="wikitable"
{| class="wikitable"
Line 2,432: Line 2,409:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Unknown
|Unknown
|Unknown
|}
|}


===FIOSERDD.SYS===
===GRADD.SYS===
Device Driver for  supports serial attachment of both the 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader. ftp://public.dhe.ibm.com/4700/fiodd/docs/77os2prg.pdf]
Graphic card driver.
  DEVICE=FIOSERDD.SYS
  DEVICE=C:\OS2\Boot\GRADD.SYS  


{| class="wikitable"
{| class="wikitable"
Line 2,449: Line 2,426:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Unknown
|Unknown
|Unknown
|}
|}


===FLSH2MTD.SYS===
===GRAHPIRE.SYS===
PCMCIA Storage Driver for OS/2 (FLASH MTD).
WACOM Graphire Tablet device dependant OS/2 driver (serial model). It supports both Graphire Pen & Mouse and emulates usual 3-button serial mouse.
  DEVICE=FLSH2MTD.SYS
  DEVICE=GRAHPIRE.SYS <parameters>
 
'''Parameter:'''
 
* SERIAL=COMn
Specifies the COM Port, COM1 is used by default


{| class="wikitable"
{| class="wikitable"
Line 2,472: Line 2,454:
|}
|}


===FMD.SYS===
===GWDTA.SYS===
Driver required by Faxworks lite 2.* in Warp 3 or the Pro Versions of Faxworks/PMFax.
Generic Winos2 audio driver. Works under DOS for Winos2 sessions.
  DEVICE=FMD.SYS
http://home.wanadoo.nl/~rwklein/
 
  DEVICE=GWDTA.SYS
'''Parameter:'''
* L = disable logo on error free boot
* T = do port tests (default)
* N = no port tests, assume ports exist (PCMCIA default)
* S = allow interrupt sharing (MCA bus only)
* A = get ABIOS LID on port open (MCA bus only)
 
* c = COM number (1-48)
* h = I/O port address (in hex)
* i = interrupt number
(defaults are for the standard COM ports)


{| class="wikitable"
{| class="wikitable"
Line 2,501: Line 2,472:
|}
|}


===FMRADIO.SYS===
===HRTIMER.SYS===
Driver for the FREE PMRADIO by [[Paul Ratcliffe]].
HRTIMER.SYS is a high resolution timer implemented as a device driver. Shows more accurate reading of e.g. the CPU-Meter in Memsize.
OS/2 PM application for driving the Reveal RA300 FM radio card and the old version of the AIMS Labs. RadioTrack card.
  DEVICE=HRTIMER.SYS
  DEVICE=FMRADIO.SYS <parameters>


'''Parameter:'''
'''NOTE:''' Do not run any Windows session while using HRTIMER.SYS otherwise the output is either much too high or much too low. HRTimer (all versions) requires he time slice be less than 55 milliseconds. This should be the case in all unaltered environments. If you choose to increase the TIMESLICE setting in the CONFIG.SYS you may not be able to use HRTimer (readout too low).
 
* /P:port
port is the RA300 port address (in hex.). The port addresses supported are 30F and 20F. The /P parameter is optional and if not supplied, will default to address 30F.
 
The port address must match that which you have configured on the card itself using jumper JP1. The device driver is Resource Manager compliant and will not install if some other device has already claimed the ports (the hardware actually consumes 4 ports: 30C-30F or 20C-20F).
 
* /V
It may be specified if you don't wish the device driver to turn the radio volume down when shutting down OS/2.


{| class="wikitable"
{| class="wikitable"
Line 2,529: Line 2,491:
|}
|}


===FWIP.SYS===
===I2OLOSM.OS2===
Used by the Firewall built into TCP/IP 4.1 and above. This driver adds IP packet filtering to the Firewall.
IBM I2O Token Ring LAN Driver
  DEVICE=C:\Mptn\Potocol\Fwip.sys
  DEVICE=I2OLOSM.OS2
 
IP Packet Filter Driver. This component of the VPN security system manages the firewall packet fileter and address translation service. Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall
 
For configuring the Firewall get the FREE ServerConfig Which can be found at: http://www.ecs.soton.ac.uk/~dm898/soft.html a GUI config util for Apache 1.3.9, InetPowerServer/2 0.85 and the IBM OS/2 TCP/IP Firewall. Author: [[SEHH]] (sehh@altered.com)


{| class="wikitable"
{| class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,550: Line 2,508:
|}
|}


===FXWRAP.SYS===
===IAS_DD.OS2===
NDIS wrapper for the InJoy Firewall for OS/2
OS/2 IrDA IAS Driver Copyright (C) IBM Corp. These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 770, 770E, 770ED, 770X. They do NOT work on the 560.
from: http://www.fx.dk/firewall
 
  DEVICE=FXWRAP.SYS
The IRCOMM.SYS driver make it possible to assign a virtual COM port to your Infrared attached IrCOMM device (Cellular phone, etc.). You can then use any COM port aware application package to access the device like through a normal COM port, i.e. issue AT commands to a modem, etc.
 
Communication Applications tested with this release are:
* InJoy IP Dialer V2.3
* Opalis BTX decoder (German online service)
 
IrCOMM also supports printing via the infrared port. Just install the right printer driver, then point it to the COM port IrCOMM is using. For Win-OS/2 printing, you can select the same COM port as you Win-OS/2 printer port.
 
Printers tested so far:
* HP LaserJet 6MP
* HP DeskJet 340
 
Whenever the IRCOMM driver detects a device, you will see the red indicator come on and tell you there's an active connection.
  DEVICE=IAS_DD.OS2 <parameter>


Designed with Cable Modems and LAN-2-LAN connections in mind, the InJoy Firewall is a complete Internet Gateway, Firewall and IPSec VPN gateway/client in one.
'''Parameter:'''
FEATURES: IPSec; PPPoE; Superior performance NDIS Protocol Engine; RFC 1631-NAT support; Direct Internet Access for your LAN PC's; Packet Filtering; Traffic Accounting, Port Redirection; Rule Based Access Control; Identd support; No reconfiguration of software; Great step-by-step docs; YK2; PM & text GUI; DHCP support; On-the-fly updates.
* /L - Legacy mode support.


{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,565: Line 2,536:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 2,571: Line 2,542:
|}
|}


===GAMEDD.SYS===
===IBG_DATI.DRV===
It is used by many Soundcards. It gives support for the Joystick connector for OS/2 programs.
Sytos Plus driver for the IBM 2.0G 4mm Tape.
  DEVICE=C:\MMOS2\GAMEDD.sys
  DEVICE=IBG_DATI.DRV
 
The following joysticks are supported by this driver:
* Advance Gravis Analog Joystick
* Advance Gravis GamePad
* Advance Gravis Analog Pro
* CH Products Flightstick
* Dexxa Joystick ( Infrared )
* Kraft Thunderstick
* Logitech WingMan Extreme
* Logitech Wingman
* Thrustmaster XL Action Controller
 
There is also an Enhanced Joystick driver by Vesa J„„skel„inen who supports the following joysticks:
* Generic 4 axis and 4 button joystick
* Gravis GamePad Pro (in GrIP mode)
* CH FlightStick Pro


{| class="wikitable"
{| class="wikitable"
Line 2,598: Line 2,553:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,604: Line 2,559:
|}
|}


===GAMEPRT2.SYS===
===IBM360P.SYS===
Joystick interface driver. By Jose DaSilva silva@dowco.com.
Pen for OS/2 Device Driver for IBM360P.
  DEVICE=GAMEPRT2.SYS <parameter>
  DEVICE=IBM360P.SYS
 
'''Parameter:'''
* /VB - displays the gameport header at startup.
* /P:hhhh - Is the joystick port (hhhh=hex address of port)
* /W:hhhh - Is the wait run-a-way counter (hhhh=waiting time).
 
'''NOTE:''' This driver is incompatible with the original IBM GAMEDD.SYS. You must use GAMEDD.SYS from the same author.


{| class="wikitable"
{| class="wikitable"
Line 2,622: Line 2,570:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,628: Line 2,576:
|}
|}


===GAMEVDD.SYS===
===IBM730T.SYS===
It is used by many Soundcards. It gives support for the Joystick connector for Dos and Windows programs.
Pen for OS/2 Device Driver for IBM730T.
  DEVICE=C:\MMOS2\GAMEVDD.SYS
  DEVICE=IBM730T.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,639: Line 2,587:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,645: Line 2,593:
|}
|}


===GENSCSI.SYS===
===IBM750P.SYS===
Generic SCSI device driver. The basic function of GENSCSI.SYS is to provide applications with an interface to OS2SCSI.DMD. It only answers 4 commands: Open, Close, IOCtl, and Init. All others cause an Invalid Command error. GENSCSI accepts IOCtl commands in the same format that OS2SCSI does, except GENSCSI expects all addresses to be ring 3 addresses while OS2SCSI expects them to be ring 0 addresses, physical addresses or scatter/gather lists. GENSCSI will convert the ring 3 addresses to the proper form and pass the command on to OS2SCSI. When OS2SCSI is done with the command, it returns the results back to GENSCSI who passes it back to the application. Developed by [[Dennis Rowe]] available for free as part of scsipg.zip.
Pen for OS/2 Device Driver for IBM750P.
  DEVICE=GENSCSI.SYS
  DEVICE=IBM750P.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,662: Line 2,610:
|}
|}


===GPH2USB.SYS===
===IBMCOMO.SYS===
USB driver for GPhoto2
Device driver for the IBM Advanced System Mangement service processor hardware.
  DEVICE=GPH2USB.SYS
  DEVICE=IBMCOMO.SYS
 
NOTE: With this driver installed accessing your camera using the USBMSD.ADD or CWUSBMSD.ADD drivers doesn't work.


{| class="wikitable"
{| class="wikitable"
Line 2,675: Line 2,621:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,681: Line 2,627:
|}
|}


===GRADD.SYS===
===IBMCSFLK.SYS===
Graphic card driver.
Driver from Corrective Service Facility (CSF) necessary to exchange locked files. Normally this driver should only appear during the reboot after applying a fixpak. If you have this driver installed installation/exchange of locked files may have failed.
  DEVICE=C:\OS2\Boot\GRADD.SYS  
  DEVICE=IBMCSFLK.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,692: Line 2,638:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,698: Line 2,644:
|}
|}


===GRAHPIRE.SYS===
===IBMFE.OS2===
WACOM Graphire Tablet device dependant OS/2 driver (serial model). It supports both Graphire Pen & Mouse and emulates usual 3-button serial mouse.
IBM 10/100 EtherJet PCI Adapter.
  DEVICE=GRAHPIRE.SYS <parameters>
  DEVICE=IBMFE.OS2


'''Parameter:'''
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* SERIAL=COMn
===IBMLANLK.SYS===
Specifies the COM Port, COM1 is used by default
Driver necessary to exchange locked files. Normally this driver should only appear during the reboot. So if you see it installation/exchange of locked files may have failed.
DEVICE=IBMLANLK.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,720: Line 2,678:
|}
|}


===GWDTA.SYS===
===IBMSPO.SYS===
Generic Winos2 audio driver. Works under DOS for Winos2 sessions.
Device driver for the IBM Advanced System Mangement service processor hardware.
http://home.wanadoo.nl/~rwklein/
  DEVICE=IBMSPO.SYS
  DEVICE=GWDTA.SYS


{| class="wikitable"
{|class="wikitable"
|+Platform Support:
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
Line 2,738: Line 2,695:
|}
|}


===HRTIMER.SYS===
===IBMTOK.OS2===
HRTIMER.SYS is a high resolution timer implemented as a device driver. Shows more accurate reading of e.g. the CPU-Meter in Memsize.
Network adapter driver for IBM Token-Ring cards.
  DEVICE=HRTIMER.SYS
  DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
 
'''NOTE:''' Do not run any Windows session while using HRTIMER.SYS otherwise the output is either much too high or much too low. HRTimer (all versions) requires he time slice be less than 55 milliseconds. This should be the case in all unaltered environments. If you choose to increase the TIMESLICE setting in the CONFIG.SYS you may not be able to use HRTimer (readout too low).


{| class="wikitable"
{| class="wikitable"
Line 2,757: Line 2,712:
|}
|}


===I2OLOSM.OS2===
===IBMTOKCS.OS2===
IBM I2O Token Ring LAN Driver
IBM Turbo 16/4 Token-Ring PC Card.
  DEVICE=I2OLOSM.OS2
  DEVICE=IBMTOKCS.OS2


{| class="wikitable"
{| class="wikitable"
Line 2,774: Line 2,729:
|}
|}


===IAS_DD.OS2===
===IBMTRP.OS2===
OS/2 IrDA IAS Driver Copyright (C) IBM Corp. These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 770, 770E, 770ED, 770X. They do NOT work on the 560.
IBM Token-Ring PCI adapter card.
DEVICE=IBMTRP.OS2


The IRCOMM.SYS driver make it possible to assign a virtual COM port to your Infrared attached IrCOMM device (Cellular phone, etc.). You can then use any COM port aware application package to access the device like through a normal COM port, i.e. issue AT commands to a modem, etc.
{| class="wikitable"
 
|+Platform Support:
Communication Applications tested with this release are:
!OS/2 2.x
* InJoy IP Dialer V2.3
* Opalis BTX decoder (German online service)
 
IrCOMM also supports printing via the infrared port. Just install the right printer driver, then point it to the COM port IrCOMM is using. For Win-OS/2 printing, you can select the same COM port as you Win-OS/2 printer port.
 
Printers tested so far:
* HP LaserJet 6MP
* HP DeskJet 340
 
Whenever the IRCOMM driver detects a device, you will see the red indicator come on and tell you there's an active connection.
DEVICE=IAS_DD.OS2 <parameter>
 
'''Parameter:'''
* /L - Legacy mode support.
 
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 2,808: Line 2,746:
|}
|}


===IBG_DATI.DRV===
===ICHCSND.SYS===
Sytos Plus driver for the IBM 2.0G 4mm Tape.
Analog Devices SoundMax Integrated Digital Audio AD188x/198x OS/2 driver for Intel 82801AA/AB/BA/CA/DB/EB and NVidia MCP2/CK8 chipsets.
  DEVICE=IBG_DATI.DRV
  DEVICE=ICHCSND.SYS


{| class="wikitable"
{| class="wikitable"
Line 2,819: Line 2,757:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
| -
|Yes
|Yes
|Yes
|Yes
Line 2,825: Line 2,763:
|}
|}


===IBM360P.SYS===
===ICHCVDD.SYS===
Pen for OS/2 Device Driver for IBM360P.
AD18xx/19xx virtual DOS driver for Intel 82801AA/AB/BA/CA/DB/EB and NVidia MCP2/CK8 chipset.
  DEVICE=IBM360P.SYS
  DEVICE=ICHCVDD.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,842: Line 2,781:
|}
|}


===IBM730T.SYS===
===ICHSND.SYS===
Pen for OS/2 Device Driver for IBM730T.
Analog Devices SoundMax Integrated Digital Audio AD18xx for Intel 82801AA/AB chipsets.
  DEVICE=IBM730T.SYS
  DEVICE=ICHSND.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,859: Line 2,799:
|}
|}


===IBM750P.SYS===
===ICHVDD.SYS===
Pen for OS/2 Device Driver for IBM750P.
AD1881 virtual DOS driver for Intel 82801AA/AB chipset.
  DEVICE=IBM750P.SYS
  DEVICE=ICHVDD.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,870: Line 2,811:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
| -
|Yes
|Yes
|Yes
|Yes
Line 2,876: Line 2,817:
|}
|}


===IBMCOMO.SYS===
===IDEHDD.SYS===
Device driver for the IBM Advanced System Mangement service processor hardware.
MULTIPORT/Kingbyte Parallel Port hard disk drive device driver.
  DEVICE=IBMCOMO.SYS
http://www.multiport.de
http://www.kingbyte.com
  DEVICE=IDEHDD.SYS
 
'''Parameter:'''
 
* /Sn
Set the starting search port access speed level for printer port. If this parameter is not specified, driver will try from the fastest speed level 0, and then level 1, level 2 until level 9 automatically, n must be 0 ~ 9. Default value is 0 (the fastest level).
 
* /Zn
n is a byte-length value bit1 = 1, suppress bi-direction mode = 0, not suppress bi-direction mode (default) bit2 = 1, suppress uni-direction emulation mode= 0, not suppress uni-direction emulation mode (default) bit3 = 1, suppress epp emulation mode = 0, not suppress epp emulation mode (default)
Ex: /Z8 --> suppress EPP mode
Ex: /Z10 --> suppress EPP & bi-direction mode
Ex: /Z14 --> suppress EPP & bi-direction & uni-direction mode
 
* /!E
Suppress 528MB larger enhanced IDE support Default the driver will use the LBA mode to support 528MB larger enhanced IDE.


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,893: Line 2,851:
|}
|}


===IBMCSFLK.SYS===
===IFNDIS.SYS===
Driver from Corrective Service Facility (CSF) necessary to exchange locked files. Normally this driver should only appear during the reboot after applying a fixpak. If you have this driver installed installation/exchange of locked files may have failed.
Network protocol driver. Used by TCP/IP.
  DEVICE=IBMCSFLK.SYS
  DEVICE=\MPTN\PROTOCOL\IFNDIS.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,910: Line 2,869:
|}
|}


===IBMFE.OS2===
===IFNDISNL.SYS===
IBM 10/100 EtherJet PCI Adapter.
TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2.00 IFNDIS Null Driver from the Warp 3 Internet Access Kit.
  DEVICE=IBMFE.OS2
  DEVICE=IFNDISNL.SYS
 
'''TIP:''' To get PPP (Point-to-Point Protocol) download ftp://ftp.ibm.net/pub/PPP/PPP.ZIP


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,927: Line 2,889:
|}
|}


===IBMGE.OS2===
===INET.SYS===
IBM OS/2 1000Base-SX and 1000Base-T Gigabit Ethernet Adapter Support for Options by IBM 34L0301 1000BaseSX Gigabit Ethernet Adapter (See restrictions), Options by IBM 06P3701 1000BaseSX Gigabit Ethernet Adapter, Intel 82542 Based 1000BaseSX Gigabit Ethernet Adapter (See restrictions), Intel 82543 Based 1000BaseSX Gigabit Ethernet Adapter (PRO1000/F), Intel 82544 Based 1000BaseSX Gigabit Ethernet Adapter (PRO1000/XF)
TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2 from the Warp 3 Internet Access Kit.
  DEVICE=IBMGE.OS2
  DEVICE=INET.SYS


'''NOTE:''' It is designed to work with the 1000BaseSX Fiber Adapter only.
'''TIP:''' For PPP see also DEVICE IFNDISNL.SYS.


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,946: Line 2,909:
|}
|}


===IBMLANLK.SYS===
===INIT931.SYS===
Driver necessary to exchange locked files. Normally this driver should only appear during the reboot. So if you see it installation/exchange of locked files may have failed.
OPTi 82C931 Init Device Driver.
DEVICE=IBMLANLK.SYS
DEVICE=INIT931.SYS
 
'''Parameter:'''
 
'''NOTE:''' Only valid for Warp3, Warp4 uses the PnP Ressource Manager.
 
'''MODE:''' wss, sb (default Windows Sound System)
 
* BASE: 220, 240 (for Sound Blaster mode, default 220) 534, E84, F44, 608 (for Windows Sound System mode, default 534)
* CDTYPE: None, IDE (default None) One character is adequate (e.g. CDTYPE:N CDTYPE:I)
* CDBASE: None, 376 IDE - 376 (fixed)
* CDIRQ: None, 15 IDE - 15 (fixed)
* SBIRQ: 5, 7, 10, 11 (default 7)
* SBDMA: 1, 2, 3 (default 1)
* SSIRQ: 7, 9, 10, 11
* WSSDMA: 0, 1, 3 (default 1)
 
'''NOTE:''' The WSS IRQ and DMA are specified here. The audio PDD will query INIT931.SYS to learn of the device settings.
 
* GAMEPORT: 0,200,201,202,203,204,205,206,207 (0 disabled)


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,963: Line 2,946:
|}
|}


===IBMSPO.SYS===
Device driver for the IBM Advanced System Mangement service processor hardware.
DEVICE=IBMSPO.SYS


{|class="wikitable"
===IPSEC.SYS===
|+Platform Support:
Used by the Firewall built into TCP/IP 4.1 and above. This driver adds IPSEC security to the Firewall.
This driver is the protocol driver for controlling VPN between two or more systems. It starts the key exchange and negotiation of protocols to be used. It then manages the exchange using the agreed items.
DEVICE=C:\MPTN\PROTOCOL\IPSEC.SYS
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,974: Line 2,960:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
| -
|Yes
|Yes
|Yes
|Yes
Line 2,980: Line 2,966:
|}
|}


===IBMTOK.OS2===
===IPX.SYS===
Network adapter driver for IBM Token-Ring cards.
Gives support for the Novell Netware IPX protocol.
  DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
  DEVICE=C:\Netware\IPX.sys


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 2,997: Line 2,984:
|}
|}


===IBMTOKCS.OS2===
===IRCOMM.SYS===
IBM Turbo 16/4 Token-Ring PC Card.
OS/2 IrDA IrCOMM Device Class Driver. These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 770, 770E, 770ED, 770X. They do NOT work on the 560.
  DEVICE=IBMTOKCS.OS2
  DEVICE=IRCOMM.SYS
 
'''Parameter:'''
* /V
Tells you which COM port the driver has assigned to itself
 
* /COMPORT:COMx
Sets the COM port that IrCOMM will use.


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,008: Line 3,003:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 3,014: Line 3,009:
|}
|}


===IBMTRP.OS2===
===IRDA_DD.OS2===
IBM Token-Ring PCI adapter card.
IrDA Stack drivers are designed to work on following IBM Thinkpad Models: 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21, T22, T23. They do NOT work on the 560.
  DEVICE=IBMTRP.OS2
  DEVICE=IRDA_DD.OS2


{| class="wikitable"
'''Parameter:'''
|+Platform Support:
* /Wn
!OS/2 2.x
Packet window size in range 1..7. Default value is 7. Used to calculate physical layer receive buffer size by following formula: 2k * n + 2k
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


===ICHCSND.SYS===
* /Nn
Analog Devices SoundMax Integrated Digital Audio AD188x/198x OS/2 driver for Intel 82801AA/AB/BA/CA/DB/EB and NVidia MCP2/CK8 chipsets.
Number of LSAP clients in range 1..112. Default value is 8.
DEVICE=ICHCSND.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,042: Line 3,028:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
| -
|No
|Yes
|Yes
|Yes
|Yes
Line 3,048: Line 3,034:
|}
|}


===ICHCVDD.SYS===
===IRDA_PHY.OS2===
AD18xx/19xx virtual DOS driver for Intel 82801AA/AB/BA/CA/DB/EB and NVidia MCP2/CK8 chipset.
IrDA Stack drivers are designed to work on following IBM Thinkpad Models: 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21, T22, T23. They do NOT work on the 560.
DEVICE=ICHCVDD.SYS
Tests are performed for following systems:
* Thinkpad 600E, 600X, T20, T21
 
Tests are performed for following adapters:
* ACTiSYS IR-220L+
 
Tests are performed for following printers:
* HP LaserJet 6M/6MP, HP LaserJet 2200
 
Tests are performed for following cell phones:
* Nokia 6210, 7110
* Ericsson R320, SH888
* Siemens S25, S35i, ME45
 
DEVICE=IRDA_PHY.OS2 <parameter>
 
'''Parameter:'''
* /Pn - Hexdecimal port number.
* /In - Interrupt number.
* /Sn - Hexdecimal port number for SDLC.
* /Jn - Interrupt number for SDLC.
* /Dn - Transmit Tx DMA channel
* /En - Receive Rx DMA channel
 
Current code isn't capable to recognize all existing Infrared hardware configurations automatically and therefore driver provides a command line parameters interface which allows user to specify hardware configuration settings manually. If hardware configuration is recognized, command line settings will be ignored.
 
If the driver doesn't recognize the hardware settings, it will serve Infrared adapter at 0x3F8 using IRQ4 (COM1 default settings) using SIR mode.


'''Platform Support:'''
'''Platform Support:'''
Line 3,060: Line 3,072:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 3,066: Line 3,078:
|}
|}


===ICHSND.SYS===
===IRDD.SYS===
Analog Devices SoundMax Integrated Digital Audio AD18xx for Intel 82801AA/AB chipsets.
Installs the Infrared Device Driver at COM2.
  DEVICE=ICHSND.SYS
  DEVICE=IRDD.SYS
 
To print through that port, the driver INFRARED.PDR needs also to be installed.
 
'''TIP:''' For Thinkpads the address and the IRQ should be added.
E.g. Device=C:\OS2\BOOT\IRDD.SYS 2F8 3. This is valid only if IRQ 3 isn't used yet. If it is, another one has to be chosen (with an appropriate I/O address).
To print through that port, the driver INFRARED.PDR needs to be installed by changing the Printer Output Port settings in the Printerdriver Properties.


'''Platform Support:'''
'''Platform Support:'''
Line 3,078: Line 3,096:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 3,084: Line 3,102:
|}
|}


===ICHVDD.SYS===
===IRMAC.OS2===
AD1881 virtual DOS driver for Intel 82801AA/AB chipset.
IBM Wireless LAN PCMCIA Adapter driver.
  DEVICE=ICHVDD.SYS
  DEVICE=IRMAC.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 3,096: Line 3,114:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
| -
|No
|Yes
|Yes
|Yes
|Yes
Line 3,102: Line 3,120:
|}
|}


===IDEHDD.SYS===
===JJSCDROM.DMD===
MULTIPORT/Kingbyte Parallel Port hard disk drive device driver.
Modified CD-ROM device manager with CD-DA digital readout / multisessioning enhancement developed by Takayuki Suwa (jjsuwa@sys3175.com)
http://www.multiport.de
  DEVICE=JJSCDROM.DMD
http://www.kingbyte.com
  DEVICE=IDEHDD.SYS


'''Parameter:'''
'''Parameters:'''
* /Q
quiet; displays no messages if not installed


* /Sn
* /V
Set the starting search port access speed level for printer port. If this parameter is not specified, driver will try from the fastest speed level 0, and then level 1, level 2 until level 9 automatically, n must be 0 ~ 9. Default value is 0 (the fastest level).
verbose; displays CD-ROM unit information


* /Zn
* /VP
n is a byte-length value bit1 = 1, suppress bi-direction mode = 0, not suppress bi-direction mode (default) bit2 = 1, suppress uni-direction emulation mode= 0, not suppress uni-direction emulation mode (default) bit3 = 1, suppress epp emulation mode = 0, not suppress epp emulation mode (default)
same as /V, with pausing (requires PAUSEONERROR=YES)
Ex: /Z8 --> suppress EPP mode
Ex: /Z10 --> suppress EPP & bi-direction mode
Ex: /Z14 --> suppress EPP & bi-direction & uni-direction mode


* /!E
* /R:n
Suppress 528MB larger enhanced IDE support Default the driver will use the LBA mode to support 528MB larger enhanced IDE.
reserves at least n driveletters (driveletter reservation)


'''Platform Support:'''
* /S
{| class="wikitable"
assigns only 1 driveletter to SCSI-3/MMC / ATAPI changer units
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


===IFNDIS.SYS===
* /W
Network protocol driver. Used by TCP/IP.
treats all WORM devices as CD-ROM; in order to not apply this treatment to specific unit(s), use /U:n /I
DEVICE=\MPTN\PROTOCOL\IFNDIS.SYS


'''Platform Support:'''
* /U:n
{| class="wikitable"
specifies unit number for /Fxy and /I, 0 based
|-
 
!OS/2 2.x
* /I
!OS/2 3.0
ignores unit (no driveletter assignment)
!OS/2 4.0
 
!OS/2 4.5x
* /Fxy
|-
enforces CD-DA / CD-XA / multisessioning / UPC treatments; without preceding /U, applies to all units
|Yes
|Yes
|Yes
|Yes
|}


===IFNDISNL.SYS===
* /FC+
TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2.00 IFNDIS Null Driver from the Warp 3 Internet Access Kit.
forces "CD-DA readable" flag on
DEVICE=IFNDISNL.SYS


'''TIP:''' To get PPP (Point-to-Point Protocol) download ftp://ftp.ibm.net/pub/PPP/PPP.ZIP
* /FCS
enforces Sony CDU-561 compatible SCSI CD-DA readout method *


'''Platform Support:'''
* /FCT
{| class="wikitable"
enforces Toshiba XM-3401 compatible SCSI CD-DA readout method *
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


===INET.SYS===
* /FC
TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2 from the Warp 3 Internet Access Kit.
same as /FC+ /FCS
DEVICE=INET.SYS


'''TIP:''' For PPP see also DEVICE IFNDISNL.SYS.
* /FX+
forces "CD-XA readable" flag on


'''Platform Support:'''
* /FXT
{| class="wikitable"
enforces Toshiba XM-3401 compatible SCSI CD-XA readout method *
|-
 
!OS/2 2.x
* /FXS
!OS/2 3.0
enforces Sony CDU-561 compatible SCSI CD-XA readout method *
!OS/2 4.0
 
!OS/2 4.5x
* /FXN
|-
enforces NEC 84-1 compatible SCSI CD-XA readout method *
|Yes
|Yes
|Yes
|Yes
|}


===INIT931.SYS===
* /FX
OPTi 82C931 Init Device Driver.
same as /FX+ /FXS
DEVICE=INIT931.SYS


'''Parameter:'''
* /FM+
forces "multisessioning-aware" flag on


'''NOTE:''' Only valid for Warp3, Warp4 uses the PnP Ressource Manager.
* /FMT
enforces Toshiba XM-3401 compatible SCSI multisessioning method *


'''MODE:''' wss, sb (default Windows Sound System)
* /FMS
enforces Sony CDU-561 compatible SCSI multisessioning method *


* BASE: 220, 240 (for Sound Blaster mode, default 220) 534, E84, F44, 608 (for Windows Sound System mode, default 534)
* /FMC
* CDTYPE: None, IDE (default None) One character is adequate (e.g. CDTYPE:N CDTYPE:I)
enforces Chinon CDS-535 compatible SCSI multisessioning method *
* CDBASE: None, 376 IDE - 376 (fixed)
* CDIRQ: None, 15 IDE - 15 (fixed)
* SBIRQ: 5, 7, 10, 11 (default 7)
* SBDMA: 1, 2, 3 (default 1)
* SSIRQ: 7, 9, 10, 11
* WSSDMA: 0, 1, 3 (default 1)


'''NOTE:''' The WSS IRQ and DMA are specified here. The audio PDD will query INIT931.SYS to learn of the device settings.
* /FMN
enforces NEC 84-1 compatible SCSI multisessioning method *


* GAMEPORT: 0,200,201,202,203,204,205,206,207 (0 disabled)
* /FMH
enforces HP C4324 compatible SCSI multisessioning method *


'''Platform Support:'''
* /FMX
{| class="wikitable"
enforces NEC 46x compatible SCSI multisessioning method *
|-
 
!OS/2 2.x
* /FM
!OS/2 3.0
same as /FM+ /FMS
!OS/2 4.0
 
* /FUU
marks as "UPC readable" and enforces unpacked raw UPC format *
 
* /FUP
marks as "UPC readable" and enforces packed raw UPC format *
 
* /FUA
marks as "UPC readable" and enforces ASCII raw UPC format *
 
* /FU
same as /FUA
 
* /F
same as /FC+ /FCS /FX+ /FXS /FM+ /FMS
 
* because SCSI-3/MMC / ATAPI drives can automatically detect and configure their own capabilities, these options are ignored on such drives.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 3,231: Line 3,233:
|}
|}


===KBLS120.SYS===
Kingbyte LS-120 ATAPI Disk Driver.
http://www.kingbyte.com
DEVICE=KBLS120.SYS


===IPSEC.SYS===
Used by the Firewall built into TCP/IP 4.1 and above. This driver adds IPSEC security to the Firewall.
This driver is the protocol driver for controlling VPN between two or more systems. It starts the key exchange and negotiation of protocols to be used. It then manages the exchange using the agreed items.
DEVICE=C:\MPTN\PROTOCOL\IPSEC.SYS
'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|-
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,245: Line 3,245:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
| -
|No
|Yes
|Yes
|Yes
|Yes
Line 3,251: Line 3,251:
|}
|}


===IPX.SYS===
===KBPD.SYS===
Gives support for the Novell Netware IPX protocol.
Kingbyte OS/2 Parallel PD ATAPI Disk Driver.  
  DEVICE=C:\Netware\IPX.sys
http://www.kingbyte.com
  DEVICE=KBPD.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 3,263: Line 3,264:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 3,269: Line 3,270:
|}
|}


===IRCOMM.SYS===
===KBZIP100.SYS===
OS/2 IrDA IrCOMM Device Class Driver. These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 770, 770E, 770ED, 770X. They do NOT work on the 560.
KingByte Parallel Port IOMEGA ZIP 100 drive.
  DEVICE=IRCOMM.SYS
http://www.kingbyte.com
  DEVICE=KBZIP100.SYS


'''Parameter:'''
'''Parameter:'''
* /V
Tells you which COM port the driver has assigned to itself


* /COMPORT:COMx
* /Sn
Sets the COM port that IrCOMM will use.
Set the starting search port access speed level for printer port. If this parameter is not specified, driver will try from the fastest speed level 0, and then level 1, level 2 until level 9 automatically, n must be 0 ~ 9. Default value is 0 (the fastest level).
 
* /Zn
n is a byte-length value bit1 = 1, suppress bi-direction mode = 0, not suppress bi-direction mode (default) bit2 = 1, suppress uni-direction emulation mode = 0, not suppress uni-direction emulation mode (default) bit3 = 1, suppress epp emulation mode = 0, not suppress epp emulation mode (default)
Ex: /Z8 --> suppress EPP mode
Ex: /Z10 --> suppress EPP & bi-direction mode
Ex: /Z14 --> suppress EPP & bi-direction & uni-direction mode


'''Platform Support:'''
'''Platform Support:'''
Line 3,294: Line 3,300:
|}
|}


===IRDA_DD.OS2===
===KDBNET.SYS===
IrDA Stack drivers are designed to work on following IBM Thinkpad Models: 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21, T22, T23. They do NOT work on the 560.
Kernel Failure Networkprotocol, enables remote Kernel-Failure repair over TCP/IP.
  DEVICE=IRDA_DD.OS2
  DEVICE=KDBNET.SYS
 
'''Parameter:'''
* /Wn
Packet window size in range 1..7. Default value is 7. Used to calculate physical layer receive buffer size by following formula: 2k * n + 2k
 
* /Nn
Number of LSAP clients in range 1..112. Default value is 8.


'''Platform Support:'''
'''Platform Support:'''
Line 3,319: Line 3,318:
|}
|}


===IRDA_PHY.OS2===
===KILLER.SYS===
IrDA Stack drivers are designed to work on following IBM Thinkpad Models: 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21, T22, T23. They do NOT work on the 560.
Used by the Watchcat task killer.
Tests are performed for following systems:
DEVICE=C:\User\Watchcat\KILLER.SYS
* Thinkpad 600E, 600X, T20, T21


Tests are performed for following adapters:
'''Platform Support:'''
* ACTiSYS IR-220L+
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


Tests are performed for following printers:
===KMGAX64.SYS===
* HP LaserJet 6M/6MP, HP LaserJet 2200
It is used by Matrox Graphics cards.
 
  DEVICE=C:\Mga\Os2\KMGAX64.SYS
Tests are performed for following cell phones:
* Nokia 6210, 7110
* Ericsson R320, SH888
* Siemens S25, S35i, ME45
 
  DEVICE=IRDA_PHY.OS2 <parameter>
 
'''Parameter:'''
* /Pn - Hexdecimal port number.
* /In - Interrupt number.
* /Sn - Hexdecimal port number for SDLC.
* /Jn - Interrupt number for SDLC.
* /Dn - Transmit Tx DMA channel
* /En - Receive Rx DMA channel
 
Current code isn't capable to recognize all existing Infrared hardware configurations automatically and therefore driver provides a command line parameters interface which allows user to specify hardware configuration settings manually. If hardware configuration is recognized, command line settings will be ignored.
 
If the driver doesn't recognize the hardware settings, it will serve Infrared adapter at 0x3F8 using IRQ4 (COM1 default settings) using SIR mode.


'''Platform Support:'''
'''Platform Support:'''
Line 3,357: Line 3,348:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,363: Line 3,354:
|}
|}


===IRDD.SYS===
===KTC110.OS2===
Installs the Infrared Device Driver at COM2.
Kingston EtheRX PCI Fast Ethernet Adapter.
  DEVICE=IRDD.SYS
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
  DEVICE=KTC110.OS2


To print through that port, the driver INFRARED.PDR needs also to be installed.
{|class="wikitable"
 
|+Platform Support:
'''TIP:''' For Thinkpads the address and the IRQ should be added.
E.g. Device=C:\OS2\BOOT\IRDD.SYS 2F8 3. This is valid only if IRQ 3 isn't used yet. If it is, another one has to be chosen (with an appropriate I/O address).
To print through that port, the driver INFRARED.PDR needs to be installed by changing the Printer Output Port settings in the Printerdriver Properties.
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,381: Line 3,366:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,387: Line 3,372:
|}
|}


===IRMAC.OS2===
===KTC111.OS2===
IBM Wireless LAN PCMCIA Adapter driver.
Kingston Fast EtheRx KNE111TX PCI Fast Ethernet Adapter.
  DEVICE=IRMAC.OS2
  DEVICE=KTC111.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 3,399: Line 3,384:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,405: Line 3,390:
|}
|}


===JJSCDROM.DMD===
=KTC120.OS2=
Modified CD-ROM device manager with CD-DA digital readout / multisessioning enhancement developed by Takayuki Suwa (jjsuwa@sys3175.com)
Kingston EtheRX PCI Fast Ethernet Adapter.
  DEVICE=JJSCDROM.DMD
  DEVICE=KTC120.OS2


'''Parameters:'''
'''Platform Support:'''
* /Q
{| class="wikitable"
quiet; displays no messages if not installed
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* /V
=KTC40.OS2=
verbose; displays CD-ROM unit information
Kingston EtheRx PCI-Ethernet-Networkadapter driver.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
DEVICE=KTC40.OS2


* /VP
'''Platform Support:'''
same as /V, with pausing (requires PAUSEONERROR=YES)
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* /R:n
===KURTAXGT.SYS===
reserves at least n driveletters (driveletter reservation)
Pen for OS/2 Device Driver for Kurta.
DEVICE=KURTAXGT.SYS


* /S
'''Platform Support:'''
assigns only 1 driveletter to SCSI-3/MMC / ATAPI changer units
{| class="wikitable"
 
|-
* /W
!OS/2 2.x
treats all WORM devices as CD-ROM; in order to not apply this treatment to specific unit(s), use /U:n /I
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* /U:n
===L100.OS2===
specifies unit number for /Fxy and /I, 0 based
PNIC 100 Base FX Fast Ethernet adapter.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
DEVICE=L100.OS2


* /I
'''TIP:''' By [[Jan Swartling]]. To get this driver to work with a Netgaer FA 310TX edeit the L100.NIF as follows:
ignores unit (no driveletter assignment)


* /Fxy
  [Media_Mode]
enforces CD-DA / CD-XA / multisessioning / UPC treatments; without preceding /U, applies to all units
  display = "Serial connection type"
  type = string
  strlength = 14
  optional = yes
  set = TP_10,TP_10_FD,TP_100,TP_100_FD,AUTODETECT
  default = AUTODETECT
  help = "This parameter specifies the serial connection type used on the adapter.


* /FC+
'''Platform Support:'''
forces "CD-DA readable" flag on
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* /FCS
===LANDD.OS2===
enforces Sony CDU-561 compatible SCSI CD-DA readout method *
IBM IEEE 802.2 NDIS protocol driver.
Information passed by [[Sergey I. Yevtushenko]] (evsi@naverex.kiev.ua) http://es.os2.ru/


* /FCT
Author of:
enforces Toshiba XM-3401 compatible SCSI CD-DA readout method *
* Fast Editor Lite (FED) Powerful programmers editor for OS/2.
* PU Monitor System monitoring tool for OS/2 PM
* Cell Toolkit Small library for OS/2 PM


* /FC
In short, that driver allows application to send/receive Ethernet and Token-Ring frames in a NIC-independent way. Format of the frame described in IEEE 802.2 standard. Applications using this protocol driver are e.g.: Lexmark's MarkVision uses it for Lexlink protocol support and Remote IPL.
same as /FC+ /FCS


* /FX+
'''Platform Support:'''
forces "CD-XA readable" flag on
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* /FXT
===LANDD.SYS===
enforces Toshiba XM-3401 compatible SCSI CD-XA readout method *
LAN Manager's user device driver that provides services for MAC frame protocols.
DEVICE=LANDD.SYS


* /FXS
'''NOTE:''' By [[Jeff Summner]]: Looking at the driver, it supplies the driver names \dev\LANDD$ and requires another device, \dev\protman$ to work. In my experience, in OS/2 it is strictly used for SNA, be that Anynet (Netbios over SNA/APPN) or simple Mainframe connectivity. It is also used to configure Bridges and LAM/CAU equipment. It does allow for some pretty cool stuff, like simple Token Ring utilization figures (a la Ringutil, IBM EWS, useless at full duplex, though) and Token Ring Diags (last ring code, upstream neighbor, beaconing MAC, Ring Parameter Server reporting.)
enforces Sony CDU-561 compatible SCSI CD-XA readout method *


* /FXN
'''Platform Support:'''
enforces NEC 84-1 compatible SCSI CD-XA readout method *
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


* /FX
=LANDLLDD.OS2=
same as /FX+ /FXS
LAN Manager interface to LAND.OS2--the 802.2 protocol.
DEVICE=LANDLLDD.OS2


* /FM+
'''Platform Support:'''
forces "multisessioning-aware" flag on
{| class="wikitable"
 
|-
* /FMT
enforces Toshiba XM-3401 compatible SCSI multisessioning method *
 
* /FMS
enforces Sony CDU-561 compatible SCSI multisessioning method *
 
* /FMC
enforces Chinon CDS-535 compatible SCSI multisessioning method *
 
* /FMN
enforces NEC 84-1 compatible SCSI multisessioning method *
 
* /FMH
enforces HP C4324 compatible SCSI multisessioning method *
 
* /FMX
enforces NEC 46x compatible SCSI multisessioning method *
 
* /FM
same as /FM+ /FMS
 
* /FUU
marks as "UPC readable" and enforces unpacked raw UPC format *
 
* /FUP
marks as "UPC readable" and enforces packed raw UPC format *
 
* /FUA
marks as "UPC readable" and enforces ASCII raw UPC format *
 
* /FU
same as /FUA
 
* /F
same as /FC+ /FCS /FX+ /FXS /FM+ /FMS
 
* because SCSI-3/MMC / ATAPI drives can automatically detect and configure their own capabilities, these options are ignored on such drives.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,512: Line 3,532:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,518: Line 3,538:
|}
|}


===KBLS120.SYS===
=LANDLLDD.SYS=
Kingbyte LS-120 ATAPI Disk Driver.
LAN Manager's common dll device driver.
http://www.kingbyte.com
  DEVICE=LANDLLDD.SYS
  DEVICE=KBLS120.SYS


'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|+Platform Support:
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,530: Line 3,550:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,536: Line 3,556:
|}
|}


===KBPD.SYS===
=LANMSGDD.OS2=
Kingbyte OS/2 Parallel PD ATAPI Disk Driver.  
Writes a log named LANTRAG.LOG into drive:\IBMCOM. This file will contain any messages (such as errors) generated via LANMSGDD.OS2.
http://www.kingbyte.com
  DEVICE=C:\IBMCOM\LANMSGDD.OS2 <parameter>
  DEVICE=KBPD.SYS
 
'''Parameters'''
 
* /I:C:\IBMCOM /S


'''Platform Support:'''
'''Platform Support:'''
Line 3,549: Line 3,572:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,555: Line 3,578:
|}
|}


===KBZIP100.SYS===
=LANPDD.OS2=
KingByte Parallel Port IOMEGA ZIP 100 drive.
Part of MPTS. It enables the NetBIOS and the IEEE 802.2 Protocols to OS/2 Programs. It loads also support for the LAN Virtual Device Driver ( Lanvdd.os2 ).
http://www.kingbyte.com
  DEVICE=C:\Ibmcom\Protocol\Lanpdd.OS2
  DEVICE=KBZIP100.SYS


'''Parameter:'''
DEVICE=drive:\IBMCOM\LANMSGDD.OS2 /I:drive:\IBMCOM /S


* /Sn
Writes a log named LANTRAG.LOG into drive:\IBMCOM. This file will contain any messages (such as errors) generated via LANMSGDD.OS2.
Set the starting search port access speed level for printer port. If this parameter is not specified, driver will try from the fastest speed level 0, and then level 1, level 2 until level 9 automatically, n must be 0 ~ 9. Default value is 0 (the fastest level).
 
* /Zn
n is a byte-length value bit1 = 1, suppress bi-direction mode = 0, not suppress bi-direction mode (default) bit2 = 1, suppress uni-direction emulation mode = 0, not suppress uni-direction emulation mode (default) bit3 = 1, suppress epp emulation mode = 0, not suppress epp emulation mode (default)
Ex: /Z8 --> suppress EPP mode
Ex: /Z10 --> suppress EPP & bi-direction mode
Ex: /Z14 --> suppress EPP & bi-direction & uni-direction mode


'''Platform Support:'''
'''Platform Support:'''
Line 3,579: Line 3,594:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,585: Line 3,600:
|}
|}


===KDBNET.SYS===
=LANPDD.SYS=
Kernel Failure Networkprotocol, enables remote Kernel-Failure repair over TCP/IP.
LAN Manager's kernel device driver.
  DEVICE=KDBNET.SYS
  DEVICE=LANPDD.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 3,597: Line 3,612:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,603: Line 3,618:
|}
|}


===KILLER.SYS===
=LANVDD.OS2=
Used by the Watchcat task killer.
Part of MPTS. It is the LAN Virtual Device Driver. It enables the NetBIOS and the IEEE 802.2 Protocols to Dos and Windows Programs.
  DEVICE=C:\User\Watchcat\KILLER.SYS
  DEVICE=C:\Ibmcom\Protocol\LANVDD.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 3,621: Line 3,636:
|}
|}


===KMGAX64.SYS===
===LANVDD.SYS===
It is used by Matrox Graphics cards.
DOS LAN Manager's virtual device driver.  
  DEVICE=C:\Mga\Os2\KMGAX64.SYS
  DEVICE=LANVDD.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 3,639: Line 3,654:
|}
|}


===KTC110.OS2===
===LANVMEM.SYS===
Kingston EtheRX PCI Fast Ethernet Adapter.
LAN Virtual DOS Driver, needed when using an specific DOS to be started.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
  DEVICE=LANVMEM.SYS
  DEVICE=KTC110.OS2


{|class="wikitable"
'''Platform Support:'''
|+Platform Support:
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 3,657: Line 3,672:
|}
|}


===KTC111.OS2===
===LDCOPY.SYS===
Kingston Fast EtheRx KNE111TX PCI Fast Ethernet Adapter.
Simple OS/2 driver for copying files while CONFIG.SYS is being processed by [[Bob Eager]].
  DEVICE=KTC111.OS2
  DEVICE=LDCOPY.SYS


'''Platform Support:'''
'''Parameter:'''
{| class="wikitable" style="text-align:center" border="1"
* sourcefile destinationfile
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


=DEVICE=KTC120.OS2=
'''Note:''' The driver can appear several times in the config.sys, thats not a fault.
Kingston EtheRX PCI Fast Ethernet Adapter.
http://www.tavi.co.uk/os2pages/ldcopy.html
DEVICE=KTC120.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 3,693: Line 3,696:
|}
|}


=DEVICE=KTC40.OS2=
===LNE100.OS2===
Kingston EtheRx PCI-Ethernet-Networkadapter driver.
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4).
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
  DEVICE=KTC40.OS2
  DEVICE=LNE100.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 3,712: Line 3,715:
|}
|}


===KURTAXGT.SYS===
=LNEPCI.OS2=
Pen for OS/2 Device Driver for Kurta.
Linksys LNEPCI/LNE100TX Ethernet Adapter.  
  DEVICE=KURTAXGT.SYS
  DEVICE=LNEPCI.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 3,730: Line 3,733:
|}
|}


===L100.OS2===
=LOG.SYS=
PNIC 100 Base FX Fast Ethernet adapter.
This driver enables logging of system error messages and some application error messages.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
DEVICE=L100.OS2


'''TIP:''' By [[Jan Swartling]]. To get this driver to work with a Netgaer FA 310TX edeit the L100.NIF as follows:
note: You need also logdaem.exe


  [Media_Mode]
DEVICE=C:\OS2\LOG.SYS <parameters>
  display = "Serial connection type"
 
  type = string
'''Parameters:'''
  strlength = 14
 
  optional = yes
* /E:value
  set = TP_10,TP_10_FD,TP_100,TP_100_FD,AUTODETECT
This sets up the log buffer size.
  default = AUTODETECT
Value can be in the range from 4 to 64 .
  help = "This parameter specifies the serial connection type used on the adapter.
Default = 8
This value is expressed in Kbytes.
 
* /A:value
This is the size of the alarm buffer.
Value can be in the range from 4 to 64 .
Default = 8
This value is expressed in Kbytes.
 
* /OFF
If set to OFF the driver is installed but the logging of error messages is turned off. You can turn it on again with the program Syslog.
 
See the examples below.
 
To install the log driver with a log buffer size of 48 Kbytes and an alarm buffer of 16 Kbytes, add this line to your config.sys file:
DEVICE=C:\OS2\LOG.SYS /E:48 /A:16
 
To install the log driver but turn it off after initialization use this line:
DEVICE=C:\OS2\LOG.SYS /OFF
 
'''NOTE:''' LOG.SYS has its limitations. It will not log an application error unless the application has been written to make use of LOG.SYS. Some routine system errors will not log either because OS/2 opens an error message box on screen to report these.


'''Platform Support:'''
'''Platform Support:'''
Line 3,760: Line 3,781:
|}
|}


===LANDD.OS2===
===LPT49.SYS===
IBM IEEE 802.2 NDIS protocol driver.
Devicedriver out of the LPT49.ZIP package available for free at http://www.kellergroup.com.
Information passed by [[Sergey I. Yevtushenko]] (evsi@naverex.kiev.ua) http://es.os2.ru/


Author of:
The LPT49 utility includes a device driver (LPT49.SYS) and command file (LPT49.CMD) for creating additional LPT ports on your system (LPT4 through LPT9). You can then install the fax printer object on any of these LPT ports. You can also create multiple fax printer objects on different LPT ports (set on the Output page of the printer object's Settings notebook), and each printer object can have different job properties (set with the Job properties button on the Printer driver page of the printer object's Settings notebook). Keller Group Inc. is the developer of PMFax and Faxworks.
* Fast Editor Lite (FED) Powerful programmers editor for OS/2.
DEVICE=LPT49.SYS
* PU Monitor System monitoring tool for OS/2 PM
* Cell Toolkit Small library for OS/2 PM
 
In short, that driver allows application to send/receive Ethernet and Token-Ring frames in a NIC-independent way. Format of the frame described in IEEE 802.2 standard. Applications using this protocol driver are e.g.: Lexmark's MarkVision uses it for Lexlink protocol support and Remote IPL.


'''Platform Support:'''
'''Platform Support:'''
Line 3,785: Line 3,801:
|}
|}


===LANDD.SYS===
===LPTDD.SYS===
LAN Manager's user device driver that provides services for MAC frame protocols.
This driver allows a DOS session to print to an LPT port that has been redirected (or captured) to a network printer.
  DEVICE=LANDD.SYS
  DEVICE=C:\OS2\Mdos\Lptdd.sys


'''NOTE:''' By [[Jeff Summner]]: Looking at the driver, it supplies the driver names \dev\LANDD$ and requires another device, \dev\protman$ to work. In my experience, in OS/2 it is strictly used for SNA, be that Anynet (Netbios over SNA/APPN) or simple Mainframe connectivity. It is also used to configure Bridges and LAM/CAU equipment. It does allow for some pretty cool stuff, like simple Token Ring utilization figures (a la Ringutil, IBM EWS, useless at full duplex, though) and Token Ring Diags (last ring code, upstream neighbor, beaconing MAC, Ring Parameter Server reporting.)
'''Parameter:'''
* -T:ss
Specifying the timeout value on send/receive (default 10 seconds). If using slow media (diskette), or when LPTool is used on a very busy system, increase this for reliable operation.
 
* -P:n
Specifying the LPT port-address to use (default is 1 for using 0378). Use LPTDD.CMD to define the correct n.
 
The FREE LPTool is developed by Jan van Wijk available at http://www.fsys.demon.nl
 
'''TIP:''' Together with e.g. the great FileCommander/2 by [[Brian Harvard]] create a user-menue entry that sends the current directory to the connected Computer for an easy use.
 
Example:
  S: Copy to Remote via parallel port
  D:\TOOLS\LPTOOL\LPTOOL send


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 3,805: Line 3,834:
|}
|}


=DEVICE=LANDLLDD.OS2=
===LSL.SYS===
LAN Manager interface to LAND.OS2--the 802.2 protocol.
This is the Link Support Layer driver. It is the lowest layer in the Novell Open Data Link Interface model and is required for the requester.
  DEVICE=LANDLLDD.OS2
  DEVICE=C:\Netware\Lsl.sys


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 3,816: Line 3,845:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 3,823: Line 3,855:
|}
|}


=DEVICE=LANDLLDD.SYS=
===LTMDMOS2.SYS===
LAN Manager's common dll device driver.
Lucent Technologies Modem Driver.
  DEVICE=LANDLLDD.SYS
An older V. 5.55 Beta 3 is available for FREE at http://www.drmartinus.de/notebook2/notebook.htm
  DEVICE=LTMDMOS2.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 3,841: Line 3,874:
|}
|}


=DEVICE=LANMSGDD.OS2=
===LXAPI32.SYS===
Writes a log named LANTRAG.LOG into drive:\IBMCOM. This file will contain any messages (such as errors) generated via LANMSGDD.OS2.
Radio/TV driver for BT878 based cards.
  DEVICE=C:\IBMCOM\LANMSGDD.OS2 <parameter>
The LXAPI32.SYS is a common linux services driver. It provides functions for PCI, I2C, memory, resources with linux function calls.
  DEVICE=LXAPI32.SYS


'''Parameters'''
'''Parameter'''
* /NOPCINAMEDEVICE
necessary if a trap on boot occurs


* /I:C:\IBMCOM /S
'''Parameter:'''


'''Platform Support:'''
* /V
{| class="wikitable" style="text-align:center" border="1"
Verbose: Show Copyright information
|-
* /VM
!OS/2 2.x
Verbose modules: Like /V plus module list
!OS/2 3.0
* /3
!OS/2 4.0
Execute an INT3 at initialisation (Use kernel debugger!)
!OS/2 4.5x
* /NOMODULE
|-
Don't load modules at system startup (Use BT32CFG.EXE to load/unload)
|Yes
* /NOCOREMODULE
|Yes
Don't load core modules at system startup (Use BT32CFG.EXE to load/unload)
|Yes
* /MODPARM:
|Yes
Support Linux insmod parameters for various modules
|}
* /LOADMODULE:
Load module (only with parameter /NOCOREMODULE)
* /NOPCINAMEDEVICE
Don't load and parse PCI.IDS file to prevent a system trap with driver SEG32.SYS (32Bit Security Driver of AVP/2)
 
'''NOTE:'''
This driver is the base linux api layer driver for ported drivers. It must reside before all other drivers that attaches to LXAPI32. Currently there is only BT32.SYS available.
 
'''NOTE:'''
LXAPI32.SYS contains the following modules:
* timer
* pci_core
* i2c_core
* videodev


=DEVICE=LANPDD.OS2=
'''NOTE:'''
Part of MPTS. It enables the NetBIOS and the IEEE 802.2 Protocols to OS/2 Programs. It loads also support for the LAN Virtual Device Driver ( Lanvdd.os2 ).
Module parameters:
  DEVICE=C:\Ibmcom\Protocol\Lanpdd.OS2
timer
pci_core dopcifixups=n disable/enable corresponding
dopcienable=n pci functions in pci_core
dopcisetmaster=n n is 0 or 1
dopcisetpowerstate=n
dopciupdateresource=n
  dopciresourcesurvey=n
i2c_core
videodev


DEVICE=drive:\IBMCOM\LANMSGDD.OS2 /I:drive:\IBMCOM /S
All dopci* parameters defaults to 0 because they aren't really needed in OS/2 and caused some problems.


Writes a log named LANTRAG.LOG into drive:\IBMCOM. This file will contain any messages (such as errors) generated via LANMSGDD.OS2.
Here is an example for using the /MODPARM parameter:
/MODPARM:pci_core:dopcifixups=1;dopcienable=1
This will enable dopcifixups and dopcienable.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 3,885: Line 3,944:
|}
|}


=DEVICE=LANPDD.SYS=
===MACFH.OS2===
LAN Manager's kernel device driver.
Part OS/2 Virtual LAN Kernel.
  DEVICE=LANPDD.SYS
  DEVICE=MACFH.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 3,903: Line 3,962:
|}
|}


=DEVICE=LANVDD.OS2=
===MAESTR2E.SYS===
Part of MPTS. It is the LAN Virtual Device Driver. It enables the NetBIOS and the IEEE 802.2 Protocols to Dos and Windows Programs.
AudioDrive Maestro-2E OS/2 Driver modified by [[Daniela Engert]]
  DEVICE=C:\Ibmcom\Protocol\LANVDD.OS2
  DEVICE=MAESTR2E.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 3,921: Line 3,980:
|}
|}


===LANVDD.SYS===
===MD5.SYS===
DOS LAN Manager's virtual device driver.  
Used by the Firewall built into TCP/IP 4.1 and above. This driver adds MD5 encryption to the Firewall. Device driver used by the IBM TCP/IP Firewall to impliment MD5 encryption. Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall. This is RSA's message digest algorithm used to provide authentication and integrity verification.
  DEVICE=LANVDD.SYS
  DEVICE=x:\MPTN\PROTOCOL\MD5.SYS  
 
There are several tools to configure the firewall:
* Zampa:
* ServerConfig: http://www.michelinakis.gr/Dimitris/sc/index.html


'''Platform Support:'''
'''Platform Support:'''
Line 3,939: Line 4,002:
|}
|}


===LANVMEM.SYS===
===MEDIAOS2.SYS===
LAN Virtual DOS Driver, needed when using an specific DOS to be started.
MediaDrive OS/2 Device Driver. The MediaDrive is an internal PC Card drive for Workstations. Useful e.g. for Digital-Cameras.
  DEVICE=LANVMEM.SYS
Available at http://www.altec-computersysteme.com
  DEVICE=MEDIAOS2.SYS
 
'''Parameter:'''
* /V - Verbose
* /B:XXX - Basisadress at XXX e.g. 170
 
'''Limitations:'''
 
The driver can only read/write FAT formatted ATA & SRAM PC Cards.
With OS/2 only the lower slot can be used.
Must be the only drive attached to the IDE-Controller.


'''Platform Support:'''
'''Platform Support:'''
Line 3,957: Line 4,031:
|}
|}


===LDCOPY.SYS===
===MEIO0437.SYS===
Simple OS/2 driver for copying files while CONFIG.SYS is being processed by [[Bob Eager]].
Driver for the MWAVE Modem for IBM Thinkpads.
  DEVICE=LDCOPY.SYS
  DEVICE=MEIO0437.SYS
 
'''Parameter:'''
* sourcefile destinationfile
 
'''Note:''' The driver can appear several times in the config.sys, thats not a fault.
http://www.tavi.co.uk/os2pages/ldcopy.html


'''Platform Support:'''
'''Platform Support:'''
Line 3,981: Line 4,049:
|}
|}


===LNE100.OS2===
===MEMMAN.OS2===
Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4).
LAN Manager's memory manager for DOS/Windows mode operation. Left over from old code to provide compatibility. Not needed for normal operations.  
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.
  DEVICE=MEMMAN.OS2
  DEVICE=LNE100.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 4,000: Line 4,067:
|}
|}


=DEVICE=LNEPCI.OS2=
===MIDI.SYS===
Linksys LNEPCI/LNE100TX Ethernet Adapter.  
RTMIDI helper driver. Is used by your Soundcard, but RTMIDI will work only if your Soundcard supports RTMIDI with the audio driver.
  DEVICE=LNEPCI.OS2
  DEVICE=C:\OS2\Boot\Midi.sys
 
'''TIP:''' For working with Midi there is the MIDI Station Sequencer: http://www.dinosoft.it/~midistation/index.html


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,012: Line 4,081:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|}
|}


=DEVICE=LOG.SYS=
===MODISK.DMD===
This driver enables logging of system error messages and some application error messages.
MO device driver from Fujitsu.
DEVICE=MODISK.DMD


note: You need also logdaem.exe
'''Parameters'''


DEVICE=C:\OS2\LOG.SYS <parameters>
* /Rn or /R:n
(Number of reserved drives) 'n' is a number between 1 and 10. Default is 1. A series of logical drive names can be reserved for each MO drive for future partitioning. If the number of valid partitions exceeds the number specified /R option, and if /S option is not specified, up to 16 partitions are allowed.
* /S
(Reserved drive priority) No more logical drives than the number of /R option is assigned. When the number of reserved drives specified with the /R option is fewer than the number of valid partitions on a disk, the number of reserved drives takes priority. For example, if there are four valid partitions on the disk and the number of reserved drives is specified at 3, a logical drive name cannot be assigned to the fourth partition, and hence it cannot be accessed.


'''Parameters:'''
* /I {h:} m {[n]} {+-{h:} m {[n]}}+-...
(Specify the drive ID) This parameter specifies the target MO drive by the host adapter number and SCSI-ID number. If this option is not used, all accessible MO drives are used by default. h is the host adapter number (between 0 and 9). The default is 0. m is the SCSI-ID number (0 to 7). n is the number of reserved drives. When 'n' is omitted, the value specified with the /R option is used.


* /E:value
* /U:{IDE adapter name}
This sets up the log buffer size.
(Required, specify IDE adapter driver) This parameter is not optional but required both for ATAPIMO.FLT and MODISK.DMD. You must specify same name for these two drivers. Usually '/U:ST506_HardDrive' works fine if 'IBM1S506.ADD' or 'IBM2S506.ADD' is used as IDE adapter driver.
Value can be in the range from 4 to 64 .
Default = 8
This value is expressed in Kbytes.
 
* /A:value
This is the size of the alarm buffer.
Value can be in the range from 4 to 64 .
Default = 8
This value is expressed in Kbytes.
 
* /OFF
If set to OFF the driver is installed but the logging of error messages is turned off. You can turn it on again with the program Syslog.  
 
See the examples below.
 
To install the log driver with a log buffer size of 48 Kbytes and an alarm buffer of 16 Kbytes, add this line to your config.sys file:
DEVICE=C:\OS2\LOG.SYS /E:48 /A:16
 
To install the log driver but turn it off after initialization use this line:
DEVICE=C:\OS2\LOG.SYS /OFF
 
'''NOTE:''' LOG.SYS has its limitations. It will not log an application error unless the application has been written to make use of LOG.SYS. Some routine system errors will not log either because OS/2 opens an error message box on screen to report these.


'''Platform Support:'''
'''Platform Support:'''
Line 4,060: Line 4,112:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|}
|}


===LPT49.SYS===
===MODISK.SYS===
Devicedriver out of the LPT49.ZIP package available for free at http://www.kellergroup.com.
Magneto Optical Device Driver.
DEVICE=MODISK.SYS
 
Disk Types Supported
* 3.5 inch MO disk
* Sector size: 512 bytes or 2048 bytes
* Capacity: 128 MB, 230 MB, 540 MB or 640 MB
 
'''NOTE:''' When using MODISK.SYS you have to delete or REM OPTICAL.DMD (Warp 4) or OPTICAL.SYS (Warp 3)
'''NOTE:''' There is also a MODISK.SYS for SCSI by Fujitsu who supports also 1.3 GB drives. For Parameters see MODISK.DMD


The LPT49 utility includes a device driver (LPT49.SYS) and command file (LPT49.CMD) for creating additional LPT ports on your system (LPT4 through LPT9). You can then install the fax printer object on any of these LPT ports. You can also create multiple fax printer objects on different LPT ports (set on the Output page of the printer object's Settings notebook), and each printer object can have different job properties (set with the Job properties button on the Printer driver page of the printer object's Settings notebook). Keller Group Inc. is the developer of PMFax and Faxworks.
'''NOTE:''' Better use the /of switch together with OS2DASD.DMD (or DANIDASD.DMD). In this case make shure that the MODISK.SYS is not loaded.
DEVICE=LPT49.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,080: Line 4,140:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|}
|}


===LPTDD.SYS===
===MONMOU01.SYS===
This driver allows a DOS session to print to an LPT port that has been redirected (or captured) to a network printer.
Serial Touchscreen Controller on PC-Bus System
  DEVICE=C:\OS2\Mdos\Lptdd.sys
  DEVICE=MONMOU01.SYS <parameter>


'''Parameter:'''
'''Parameter:'''
* -T:ss
where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.
Specifying the timeout value on send/receive (default 10 seconds). If using slow media (diskette), or when LPTool is used on a very busy system, increase this for reliable operation.


* -P:n
matches the jumper settings on the controller.
Specifying the LPT port-address to use (default is 1 for using 0378). Use LPTDD.CMD to define the correct n.


The FREE LPTool is developed by Jan van Wijk available at http://www.fsys.demon.nl
matches the interrupt jumper on the controller.


'''TIP:''' Together with e.g. the great FileCommander/2 by [[Brian Harvard]] create a user-menue entry that sends the current directory to the connected Computer for an easy use.
'''NOTE:''' Disabling the COM Drivers
If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.


Example:
'''NOTE:''' If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.
  S: Copy to Remote via parallel port
  D:\TOOLS\LPTOOL\LPTOOL send


'''Platform Support:'''
'''Platform Support:'''
Line 4,113: Line 4,170:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|}
|}


===LSL.SYS===
===MONMOU02.SYS===
This is the Link Support Layer driver. It is the lowest layer in the Novell Open Data Link Interface model and is required for the requester.
Serial Touchscreen Controller on PS/2 System
DEVICE=C:\Netware\Lsl.sys
DEVICE=MONMOU02.SYS <parameter>
 
'''Parameter:'''
where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.
 
matches the jumper settings on the controller.
 
matches the interrupt jumper on the controller.
 
'''NOTE:''' Disabling the COM Drivers
If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.
 
'''NOTE:''' If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.


'''Platform Support:'''
'''Platform Support:'''
Line 4,130: Line 4,199:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===LTMDMOS2.SYS===
===MONMOU03.SYS===
Lucent Technologies Modem Driver.
PC-Bus and MicroChannel Touchscreen Controller
An older V. 5.55 Beta 3 is available for FREE at http://www.drmartinus.de/notebook2/notebook.htm
DEVICE=MONMOU03.SYS <parameter>
DEVICE=LTMDMOS2.SYS
 
'''Parameter:'''
where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.
 
matches the jumper settings on the controller.
 
matches the interrupt jumper on the controller.
 
'''NOTE:''' Disabling the COM Drivers
If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.
 
'''NOTE:''' If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.


'''Platform Support:'''
'''Platform Support:'''
Line 4,154: Line 4,230:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|}
|}


===LXAPI32.SYS===
===MOUSE.SYS===
Radio/TV driver for BT878 based cards.
Provides support for your mouse. You need also the Pointdd.sys installed.
The LXAPI32.SYS is a common linux services driver. It provides functions for PCI, I2C, memory, resources with linux function calls.
  DEVICE=C:\Os2\Boot\Mouse.sys <parameter>
  DEVICE=LXAPI32.SYS


'''Parameter'''
Lets you use a mouse or track ball. This line also identifies the device dependent type of mouse you have and which COM port it is on. In this case, the device dependent mouse driver is loaded in your OS/2 CONFIG.SYS through a standard "DEVICE=" line, before the MOUSE.SYS driver is loaded, and then on the MOUSE.SYS line there is the parameter "TYPE=", with a reference to the device name of the device. QSIZE is a number from 1 to 100 which indicates how many mouse actions are to be saved when you execute mouse actions faster than your system can handle them. There is also a RELAXED parameter which you would place after QSIZE. It can be used with any mouse when the pointer is jumping randomly about the screen. IBM does not suggest you use this parameter unless you are experiencing this problem.
* /NOPCINAMEDEVICE
necessary if a trap on boot occurs


'''Parameter:'''
'''ATTENTION:''' Together with an device independent Mouse (e.g. a IBM PS/2 Mouse) NO PARAMETERS are needed.


* /V
The supported device dependent Types are:
Verbose: Show Copyright information
* PCLOGIC$ for Genius, Logitech, PC Mouse Systems, Driver: PCLOGIC.SYS
* /VM
* MSBUS$ for Microsoft Bus-Mouse, Driver: NONE
Verbose modules: Like /V plus module list
* MSINP$ for Microsoft-Inport, Driver: NONE
* /3
* VISION$ for Visi-On: Driver: VISION.SYS
Execute an INT3 at initialisation (Use kernel debugger!)
* ELOMOU$ for ELO Touchscreen Driver:MONMOU0x.SYS (x=1, 2 or 3)
* /NOMODULE
* SUMMA$ for SUMMA Tablet Driver:SUMMA.SYS
Don't load modules at system startup (Use BT32CFG.EXE to load/unload)
* GRAPHIR$ for WACOM Tablet Driver: GRAPHIRE.SYS
* /NOCOREMODULE
Don't load core modules at system startup (Use BT32CFG.EXE to load/unload)
* /MODPARM:  
Support Linux insmod parameters for various modules
* /LOADMODULE:  
Load module (only with parameter /NOCOREMODULE)
* /NOPCINAMEDEVICE
Don't load and parse PCI.IDS file to prevent a system trap with driver SEG32.SYS (32Bit Security Driver of AVP/2)


'''NOTE:'''
'''NOTE:''' The MOUSE.SYS statement must come before COM.SYS, but after POINTDD.SYS, because COM.SYS will take over any unused COM port. If COM.SYS takes over the COM ports before MOUSE.SYS is loaded, MOUSE.SYS will not have any COM ports available, thus no mouse support.
This driver is the base linux api layer driver for ported drivers. It must reside before all other drivers that attaches to LXAPI32. Currently there is only BT32.SYS available.


'''NOTE:'''
'''TIP:''' If you have a so called scroll-mouse (e.g. from IBM, or Logitech) get the scrollms.exe package from the OS/2 Device Driver Pack. Or use the scrollmouse driver from http://os2.ru/projects/scrollmouse, who uses a second wheel horizontal not only vertical.
LXAPI32.SYS contains the following modules:
If you want to have a 'scrolling-feature' with normal mice there is the FREE hots11.zip package by [[Samuel Audet]] from http://WWW.CAM.ORG/~guardia/programs.html. See also AMOUSE.SYS
* timer
* pci_core
* i2c_core
* videodev


'''NOTE:'''
'''TIP:''' If you want to have animated mouse pointers (very nice); [[Christan Langanke]] has developed a FREE Version to get as AMPTR101.ZIP
Module parameters:
timer
pci_core dopcifixups=n disable/enable corresponding
dopcienable=n pci functions in pci_core
dopcisetmaster=n n is 0 or 1
dopcisetpowerstate=n
dopciupdateresource=n
dopciresourcesurvey=n
i2c_core
videodev


All dopci* parameters defaults to 0 because they aren't really needed in OS/2 and caused some problems.


Here is an example for using the /MODPARM parameter:
'''Platform Support:'''
/MODPARM:pci_core:dopcifixups=1;dopcienable=1
{| class="wikitable"
This will enable dopcifixups and dopcienable.
 
'''Platform Support:'''
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,230: Line 4,275:
|}
|}


===MACFH.OS2===
===MOUSE2.SYS===
Part OS/2 Virtual LAN Kernel.
Driver for the Trackpoint of IBM Thinkpads
  DEVICE=MACFH.OS2
  DEVICE=MOUSE2.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,248: Line 4,293:
|}
|}


===MAESTR2E.SYS===
===MPU401.SYS===
AudioDrive Maestro-2E OS/2 Driver modified by [[Daniela Engert]]
Provides support for the MPU401 connector on your soundcard.
  DEVICE=MAESTR2E.SYS
  DEVICE=C:\Os2\Boot\MPU401.SYS <parameter>
 
'''Parameter:'''
 
* /Pn:hhh
Basis I/O (Port) Address.
 
* /In:ddd
Interrupt Level. With the Theta Band driver it can be set to 0 so TIMER0 is used during record.
 
* /N:sss
Name of the driver. Default is MPU401$
 
* /R:ddd
TIMER0 resolution in milliseconds. Default 2.
 
* /V
Verbose
 
* /O:sss
Options
 
* L or LONGNAME - Long RTMIDI Names
* QUIETINI - Ignore Initialization errors
* NORMIO Do not check/register I/O addresses with RM
* SHAREDIO Check/register I/O adresses as shared
* MULTIO Check/register I/O adresses as multiplexed
* NORMIRQ Do not check/register IRQ's with RM
* SHAREDIRQ Check/register IRQ's as shared
* MULTIRQ Check/register IRQ's as multiplexed
* NOCHECKIO Do not verify I/O adresses
* NOCHECKIRQ Do not verify IRQ's
* NOTIMER0 Do not use TIMER0
* 10BITS Use 10-bit address width with RM
* 16BITS Use 16-bit adress width with RM
* ONLYONE Locate only one MPU401 device
* AUDIOVDD Enable DOS sharing (Only for Theta Band driver).


'''Platform Support:'''
'''Platform Support:'''
Line 4,266: Line 4,347:
|}
|}


===MD5.SYS===
===MVPRODD.SYS===
Used by the Firewall built into TCP/IP 4.1 and above. This driver adds MD5 encryption to the Firewall. Device driver used by the IBM TCP/IP Firewall to impliment MD5 encryption. Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall. This is RSA's message digest algorithm used to provide authentication and integrity verification.
Driver for MediaVision's ProAudio Spectrum sound card. The first driver is set for IRQ 11, DMA 3 with Sound Blaster support on IRQ 5 and DMA 1.
DEVICE=x:\MPTN\PROTOCOL\MD5.SYS
  DEVICE=MVPRODD.SYS
'''Warp TIP:''' MediaVison's technical support indicates that the only correct settings for the PAS 16 in Warp is IRQ 11 and DMA 3. If you are experiencing static or white noise during bootup, MediaVison indicates that this is caused by using an IRQ other than 11 and DMA 3. They also indicate that the two device driver lines must be the last lines in your config.sys file. Note that this information didn't solve the static problem for all users, but it did for some. Others have indicated that adding the /T:1 parameter solved their "white noise" problem.


There are several tools to configure the firewall:
'''Warp NOTE:''' There may be a bug in Warp which causes problems in WIN-OS2 "seamless" mode. A solution is contained in SNDWOR.ZIP.
* Zampa:
* ServerConfig: http://www.michelinakis.gr/Dimitris/sc/index.html


'''Platform Support:'''
'''Platform Support:'''
Line 4,288: Line 4,368:
|}
|}


===MEDIAOS2.SYS===
===MWAVEDD.SYS===
MediaDrive OS/2 Device Driver. The MediaDrive is an internal PC Card drive for Workstations. Useful e.g. for Digital-Cameras.
Driver for MWAVE Modem on IBM Thinkpads.
Available at http://www.altec-computersysteme.com
  DEVICE=MWAVEDD.SYS
  DEVICE=MEDIAOS2.SYS
 
'''Parameter:'''
* /V - Verbose
* /B:XXX - Basisadress at XXX e.g. 170
 
'''Limitations:'''
 
The driver can only read/write FAT formatted ATA & SRAM PC Cards.
With OS/2 only the lower slot can be used.
Must be the only drive attached to the IDE-Controller.


'''Platform Support:'''
'''Platform Support:'''
Line 4,317: Line 4,386:
|}
|}


===MEIO0437.SYS===
===MWAVEVDD.SYS===
Driver for the MWAVE Modem for IBM Thinkpads.
Dos Driver for the MWAVE-DSP in Thinkpads.
  DEVICE=MEIO0437.SYS
  DEVICE=MWAVEVDD.SYS
 
'''ATTENTION:''' The MWAVEVDD.SYS must placed before VEMM.SYS.


'''Platform Support:'''
'''Platform Support:'''
Line 4,335: Line 4,406:
|}
|}


===MEMMAN.OS2===
===MXNICF.OS2===
LAN Manager's memory manager for DOS/Windows mode operation. Left over from old code to provide compatibility. Not needed for normal operations.  
Macronix MX987xx Family, Edimax EN9120 Family, DFE-540TX Fast Ethernet PCI Adapters.
  DEVICE=MEMMAN.OS2
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/
  DEVICE=MXNICF.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 4,346: Line 4,418:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,353: Line 4,428:
|}
|}


===MIDI.SYS===
===N100.OS2===
RTMIDI helper driver. Is used by your Soundcard, but RTMIDI will work only if your Soundcard supports RTMIDI with the audio driver.
Compaq Fast Ethernet and Gigabit NDIS driver
  DEVICE=C:\OS2\Boot\Midi.sys
  DEVICE=N100.OS2


'''TIP:''' For working with Midi there is the MIDI Station Sequencer: http://www.dinosoft.it/~midistation/index.html
'''Platform Support:'''
 
'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 4,367: Line 4,440:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===MODISK.DMD===
===NE2000.OS2===
MO device driver from Fujitsu.
Eagle Technology NE2000plus Ethernet Adapter.
  DEVICE=MODISK.DMD
  DEVICE=NE2000.OS2
 
'''Parameters'''
 
* /Rn or /R:n
(Number of reserved drives) 'n' is a number between 1 and 10. Default is 1. A series of logical drive names can be reserved for each MO drive for future partitioning. If the number of valid partitions exceeds the number specified /R option, and if /S option is not specified, up to 16 partitions are allowed.
* /S
(Reserved drive priority) No more logical drives than the number of /R option is assigned. When the number of reserved drives specified with the /R option is fewer than the number of valid partitions on a disk, the number of reserved drives takes priority. For example, if there are four valid partitions on the disk and the number of reserved drives is specified at 3, a logical drive name cannot be assigned to the fourth partition, and hence it cannot be accessed.
 
* /I {h:} m {[n]} {+-{h:} m {[n]}}+-...
(Specify the drive ID) This parameter specifies the target MO drive by the host adapter number and SCSI-ID number. If this option is not used, all accessible MO drives are used by default. h is the host adapter number (between 0 and 9). The default is 0. m is the SCSI-ID number (0 to 7). n is the number of reserved drives. When 'n' is omitted, the value specified with the /R option is used.
 
* /U:{IDE adapter name}
(Required, specify IDE adapter driver) This parameter is not optional but required both for ATAPIMO.FLT and MODISK.DMD. You must specify same name for these two drivers. Usually '/U:ST506_HardDrive' works fine if 'IBM1S506.ADD' or 'IBM2S506.ADD' is used as IDE adapter driver.


'''Platform Support:'''
'''Platform Support:'''
Line 4,398: Line 4,458:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===MODISK.SYS===
===NETBEUI.OS2===
Magneto Optical Device Driver.
This is the NetBIOS protocol driver.
  DEVICE=MODISK.SYS
  DEVICE=C:\Ibmcom\Protocol\NETBEUI.OS2
 
Disk Types Supported
* 3.5 inch MO disk
* Sector size: 512 bytes or 2048 bytes
* Capacity: 128 MB, 230 MB, 540 MB or 640 MB
 
'''NOTE:''' When using MODISK.SYS you have to delete or REM OPTICAL.DMD (Warp 4) or OPTICAL.SYS (Warp 3)
'''NOTE:''' There is also a MODISK.SYS for SCSI by Fujitsu who supports also 1.3 GB drives. For Parameters see MODISK.DMD
 
'''NOTE:''' Better use the /of switch together with OS2DASD.DMD (or DANIDASD.DMD). In this case make shure that the MODISK.SYS is not loaded.


'''Platform Support:'''
'''Platform Support:'''
Line 4,426: Line 4,476:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===MONMOU01.SYS===
===NETBIOS.OS2===
Serial Touchscreen Controller on PC-Bus System
This is the NetBIOS API driver.
  DEVICE=MONMOU01.SYS <parameter>
  DEVICE=C:\Ibmcom\Protocol\NETBIOS.OS2
 
'''TIP:''' By Roland Sambain. The conventions wisdom about IFS statements coming at the beginning of config.sys seems not to apply. i.e. for netbios to load correctly the device statement must comes before the NETWKSTA.200 IFS.


'''Parameter:'''
'''Netbios and Gigsabit adapters'''
where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.


matches the jumper settings on the controller.
Due to the Nature of NetBIOS, it has some limitations to work on Gigabit adapters with requires some adjustments to MPTS settings.


matches the interrupt jumper on the controller.
'''Explanation:'''
NetBIOS can not work with large Ethernet frame sizes which are used by default with Gigabit Ethernet adapters. Both transfer and receive buffer sizes should be set to 1024 bytes and USEMAXDATAGRAM set to "NO". The DIX 2.0 protocol type (ETHERAND_TYPE) should be set to "D".


'''NOTE:''' Disabling the COM Drivers
Procedure to change settings
If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.
# From MPTS select 'Configure'
# In 'Current Configuration' find the "IBM 1000BaseT Gigabit Ethernet Adapter" and press 'Edit'
# Set 'Receive Buffer Size' = 1024
# Set 'Transmit Buffer Size' = 1024
# Select OK
# In 'Current Configuration' find the "IBM OS/2 NETBIOS" and press 'Edit'
# Set 'Type of Ethernet driver support = "D"
# Set 'Full buffer datagrams' = "NO"
# Select OK
# Select 'Exit' MPTS.
# Reboot


'''NOTE:''' If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.
The other possibility is to use "IBM OS/2 NETBIOS OVER TCP/IP". You might want to try this and compare the results to native NetBIOS.  


'''Platform Support:'''
'''Platform Support:'''
Line 4,456: Line 4,518:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===MONMOU02.SYS===
===NETBIOS.SYS===
Serial Touchscreen Controller on PS/2 System
Loads support for the NETBIOS protocol.
  DEVICE=MONMOU02.SYS <parameter>
  DEVICE=NETBIOS.SYS


'''Parameter:'''
'''TIP:''' If you do not use NETBIOS applications, you can remove the NETBIOS driver from the config.sys and the NETBIOS section from the PROTOCOL.INI to remove some of the confusion this creates. You should also remove the virtual netbios drivers at the same time since these bind onto the NETBIOS driver and not the LM10 interface (which is why they appear after the NETWKSTA.SYS driver, so it can "eat" its resources first, then what is left over is assigned to NETBIOS.SYS). [<- Note: this should be NETBIOS.OS2] (The mentioned virtual NETBIOS drivers are \IBMCOM\PROTOCOL\LANPDD.OS2 and LANVDD.OS2)
where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.
 
matches the jumper settings on the controller.
 
matches the interrupt jumper on the controller.
 
'''NOTE:''' Disabling the COM Drivers
If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.
 
'''NOTE:''' If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.


'''Platform Support:'''
'''Platform Support:'''
Line 4,486: Line 4,538:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===MONMOU03.SYS===
=NETFLX3.OS2=
PC-Bus and MicroChannel Touchscreen Controller
OS/2 NDIS 2 Driver for Compaq NetFlex-3/Netelligent Controllers.
DEVICE=MONMOU03.SYS <parameter>
DEVICE=NETFLX3.OS2
 
'''Parameter:'''
where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.
 
matches the jumper settings on the controller.
 
matches the interrupt jumper on the controller.
 
'''NOTE:''' Disabling the COM Drivers
If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.
 
'''NOTE:''' If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.


'''Platform Support:'''
'''Platform Support:'''
Line 4,516: Line 4,556:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|No
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|}


===MOUSE.SYS===
=NGUEST2.SYS=
Provides support for your mouse. You need also the Pointdd.sys installed.
NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.
DEVICE=C:\Os2\Boot\Mouse.sys <parameter>
DEVICE=NGUEST2.SYS
 
Lets you use a mouse or track ball. This line also identifies the device dependent type of mouse you have and which COM port it is on. In this case, the device dependent mouse driver is loaded in your OS/2 CONFIG.SYS through a standard "DEVICE=" line, before the MOUSE.SYS driver is loaded, and then on the MOUSE.SYS line there is the parameter "TYPE=", with a reference to the device name of the device. QSIZE is a number from 1 to 100 which indicates how many mouse actions are to be saved when you execute mouse actions faster than your system can handle them. There is also a RELAXED parameter which you would place after QSIZE. It can be used with any mouse when the pointer is jumping randomly about the screen. IBM does not suggest you use this parameter unless you are experiencing this problem.
 
'''ATTENTION:''' Together with an device independent Mouse (e.g. a IBM PS/2 Mouse) NO PARAMETERS are needed.
 
The supported device dependent Types are:
* PCLOGIC$ for Genius, Logitech, PC Mouse Systems, Driver: PCLOGIC.SYS
* MSBUS$ for Microsoft Bus-Mouse, Driver: NONE
* MSINP$ for Microsoft-Inport, Driver: NONE
* VISION$ for Visi-On: Driver: VISION.SYS
* ELOMOU$ for ELO Touchscreen Driver:MONMOU0x.SYS (x=1, 2 or 3)
* SUMMA$ for SUMMA Tablet Driver:SUMMA.SYS
* GRAPHIR$ for WACOM Tablet Driver: GRAPHIRE.SYS
 
'''NOTE:''' The MOUSE.SYS statement must come before COM.SYS, but after POINTDD.SYS, because COM.SYS will take over any unused COM port. If COM.SYS takes over the COM ports before MOUSE.SYS is loaded, MOUSE.SYS will not have any COM ports available, thus no mouse support.
 
'''TIP:''' If you have a so called scroll-mouse (e.g. from IBM, or Logitech) get the scrollms.exe package from the OS/2 Device Driver Pack. Or use the scrollmouse driver from http://os2.ru/projects/scrollmouse, who uses a second wheel horizontal not only vertical.
If you want to have a 'scrolling-feature' with normal mice there is the FREE hots11.zip package by [[Samuel Audet]] from http://WWW.CAM.ORG/~guardia/programs.html. See also AMOUSE.SYS
 
'''TIP:''' If you want to have animated mouse pointers (very nice); [[Christan Langanke]] has developed a FREE Version to get as AMPTR101.ZIP
 


'''Platform Support:'''
'''Platform Support:'''
Line 4,561: Line 4,580:
|}
|}


===MOUSE2.SYS===
=NHOST2.SYS=
Driver for the Trackpoint of IBM Thinkpads
NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.
  DEVICE=MOUSE2.SYS
  DEVICE=NHOST2.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,579: Line 4,598:
|}
|}


===MPU401.SYS===
=NHOST2W.SYS=
Provides support for the MPU401 connector on your soundcard.
NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.
  DEVICE=C:\Os2\Boot\MPU401.SYS <parameter>
  DEVICE=NHOST2W.SYS
 
'''Parameter:'''
 
* /Pn:hhh
Basis I/O (Port) Address.
 
* /In:ddd
Interrupt Level. With the Theta Band driver it can be set to 0 so TIMER0 is used during record.
 
* /N:sss
Name of the driver. Default is MPU401$
 
* /R:ddd
TIMER0 resolution in milliseconds. Default 2.
 
* /V
Verbose
 
* /O:sss
Options
 
* L or LONGNAME - Long RTMIDI Names
* QUIETINI - Ignore Initialization errors
* NORMIO Do not check/register I/O addresses with RM
* SHAREDIO Check/register I/O adresses as shared
* MULTIO Check/register I/O adresses as multiplexed
* NORMIRQ Do not check/register IRQ's with RM
* SHAREDIRQ Check/register IRQ's as shared
* MULTIRQ Check/register IRQ's as multiplexed
* NOCHECKIO Do not verify I/O adresses
* NOCHECKIRQ Do not verify IRQ's
* NOTIMER0 Do not use TIMER0
* 10BITS Use 10-bit address width with RM
* 16BITS Use 16-bit adress width with RM
* ONLYONE Locate only one MPU401 device
* AUDIOVDD Enable DOS sharing (Only for Theta Band driver).


'''Platform Support:'''
'''Platform Support:'''
Line 4,633: Line 4,616:
|}
|}


===MVPRODD.SYS===
=NMPIPE.SYS=
Driver for MediaVision's ProAudio Spectrum sound card. The first driver is set for IRQ 11, DMA 3 with Sound Blaster support on IRQ 5 and DMA 1.
This driver provides Named Pipes support on the Netware client.
  DEVICE=MVPRODD.SYS
DEVICE=C:\Netware\NMPIPE.SYS  
'''Warp TIP:''' MediaVison's technical support indicates that the only correct settings for the PAS 16 in Warp is IRQ 11 and DMA 3. If you are experiencing static or white noise during bootup, MediaVison indicates that this is caused by using an IRQ other than 11 and DMA 3. They also indicate that the two device driver lines must be the last lines in your config.sys file. Note that this information didn't solve the static problem for all users, but it did for some. Others have indicated that adding the /T:1 parameter solved their "white noise" problem.
 
'''Warp NOTE:''' There may be a bug in Warp which causes problems in WIN-OS2 "seamless" mode. A solution is contained in SNDWOR.ZIP.


'''Platform Support:'''
'''Platform Support:'''
Line 4,654: Line 4,634:
|}
|}


===MWAVEDD.SYS===
=NOVAQOS2.SYS=
Driver for MWAVE Modem on IBM Thinkpads.
Driver for backup-software from NOVABACK.
  DEVICE=MWAVEDD.SYS
  DEVICE=NOVAQOS2.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,672: Line 4,652:
|}
|}


===MWAVEVDD.SYS===
=NOVASPI.SYS=
Dos Driver for the MWAVE-DSP in Thinkpads.
Driver for backup-software from NOVABACK.
DEVICE=MWAVEVDD.SYS


'''ATTENTION:''' The MWAVEVDD.SYS must placed before VEMM.SYS.
  DEVICE=NOVASPI.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,692: Line 4,671:
|}
|}


===MXNICF.OS2===
=NPSERVER.SYS=
Macronix MX987xx Family, Edimax EN9120 Family, DFE-540TX Fast Ethernet PCI Adapters.
This driver allows your workstation to function as a Named Pipes Netware server.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/
 
DEVICE=MXNICF.OS2
  DEVICE=C:\Netware\NPSERVER.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,704: Line 4,683:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|}
=NSIR.SYS=
Part of the Infrared driver for IBM PC300PL computer.
DEVICE=C:\OS2\DLL\NSIR.SYS
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|Yes
|Yes
|Yes
|Yes
Line 4,715: Line 4,709:
|}
|}


===N100.OS2===
=NTRACE.OS2=
Compaq Fast Ethernet and Gigabit NDIS driver
Goldencode Network Trace (http://www.goldencode.com).
  DEVICE=N100.OS2
  DEVICE=NTRACE.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 4,733: Line 4,727:
|}
|}


===NE2000.OS2===
=NULLNDIS.OS2=
Eagle Technology NE2000plus Ethernet Adapter.
IBM NULL MAC-driver. Installed if you have NO Network Adapter.
  DEVICE=NE2000.OS2
  DEVICE=NULLNDIS.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 4,751: Line 4,745:
|}
|}


===NETBEUI.OS2===
=NVC.SYS=
This is the NetBIOS protocol driver.
This is a "Smart Behavior Blocker for DOS" from Norman antivirus.
  DEVICE=C:\Ibmcom\Protocol\NETBEUI.OS2
Basically a shield running in dos-boxes and similar to protect from possible virus "sneak attacks".  
  DEVICE=NVC.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 4,769: Line 4,764:
|}
|}


===NETBIOS.OS2===
=NWREQ.SYS=
This is the NetBIOS API driver.
This is the main Netware requester module and must appear in config.sys after the NmPipe.sys , Ipx.sys and Spx.sys drivers.
  DEVICE=C:\Ibmcom\Protocol\NETBIOS.OS2
  DEVICE=\Netware\Nwreq.sys


'''TIP:''' By Roland Sambain. The conventions wisdom about IFS statements coming at the beginning of config.sys seems not to apply. i.e. for netbios to load correctly the device statement must comes before the NETWKSTA.200 IFS.
<b>Platform Support:</b>
 
{| class="wikitable"
'''Netbios and Gigsabit adapters'''
|-
 
!OS/2 2.x
Due to the Nature of NetBIOS, it has some limitations to work on Gigabit adapters with requires some adjustments to MPTS settings.
!OS/2 3.0
 
!OS/2 4.0
'''Explanation:'''
NetBIOS can not work with large Ethernet frame sizes which are used by default with Gigabit Ethernet adapters. Both transfer and receive buffer sizes should be set to 1024 bytes and USEMAXDATAGRAM set to "NO". The DIX 2.0 protocol type (ETHERAND_TYPE) should be set to "D".
 
Procedure to change settings
# From MPTS select 'Configure'
# In 'Current Configuration' find the "IBM 1000BaseT Gigabit Ethernet Adapter" and press 'Edit'
# Set 'Receive Buffer Size' = 1024
# Set 'Transmit Buffer Size' = 1024
# Select OK
# In 'Current Configuration' find the "IBM OS/2 NETBIOS" and press 'Edit'
# Set 'Type of Ethernet driver support = "D"
# Set 'Full buffer datagrams' = "NO"
# Select OK
# Select 'Exit' MPTS.
# Reboot
 
The other possibility is to use "IBM OS/2 NETBIOS OVER TCP/IP". You might want to try this and compare the results to native NetBIOS.
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
Line 4,811: Line 4,782:
|}
|}


===NETBIOS.SYS===
=ODI2NDI.SYS=
Loads support for the NETBIOS protocol.
This driver allows the Netware client to use MPTS as the interface to a network adapter driver and in turn, the LAN.
DEVICE=NETBIOS.SYS
DEVICE=\Netware\Odi2Ndi.sys
 
'''TIP:''' If you do not use NETBIOS applications, you can remove the NETBIOS driver from the config.sys and the NETBIOS section from the PROTOCOL.INI to remove some of the confusion this creates. You should also remove the virtual netbios drivers at the same time since these bind onto the NETBIOS driver and not the LM10 interface (which is why they appear after the NETWKSTA.SYS driver, so it can "eat" its resources first, then what is left over is assigned to NETBIOS.SYS). [<- Note: this should be NETBIOS.OS2] (The mentioned virtual NETBIOS drivers are \IBMCOM\PROTOCOL\LANPDD.OS2 and LANVDD.OS2)


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,824: Line 4,793:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,835: Line 4,800:
|}
|}


=DEVICE=NETFLX3.OS2=
=OPL3.SYS=
OS/2 NDIS 2 Driver for Compaq NetFlex-3/Netelligent Controllers.
Is used by soundcards with an OPL3 sound chip.
DEVICE=C:\Os2\Boot\Opl3.sys
 
'''Parameter:'''


  DEVICE=NETFLX3.OS2
* /P:nnn
Base I/O: Sets the base I/O address for FM device.
Is almost always, 388 (nnn is in hex)


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,847: Line 4,817:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,858: Line 4,824:
|}
|}


=DEVICE=NGUEST2.SYS=
=OPL3SA.SYS=
NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.
It is used by Soundcards with Yamaha SAx sound chips.
 
DEVICE=C:\Mmos2\Opl3sa.sys
  DEVICE=NGUEST2.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,870: Line 4,835:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,881: Line 4,842:
|}
|}


=DEVICE=NHOST2.SYS=
=OPL3VDD.SYS=
NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.
It is used by Soundcards with Yamaha SAx sound chips. It provides support for DOS sessions.
 
DEVICE=C:\Mmos2\OPL3VDD.SYS
  DEVICE=NHOST2.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,893: Line 4,853:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,904: Line 4,860:
|}
|}


=DEVICE=NHOST2W.SYS=
=OPL4D.SYS=
NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.
Yahama Fm Sythesis OPL4 MIDI Driver.
DEVICE=OPL4D.SYS
 
'''Parameter:'''
* /P:xxx
Midiport Address, 300, 310, 330 or 388 (default)


  DEVICE=NHOST2W.SYS
* /N:OPL41$


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,916: Line 4,877:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,927: Line 4,884:
|}
|}


=OPTICAL.DMD=
New with Warp4 Device Manager for Optical devices like MO.


  DEVICE=OPTICAL.DMD


=DEVICE=NMPIPE.SYS=
'''TIP:''' If you have removable media drives (MO, IOMEGA, SYQUEST and others) look at http://rheooptik.fmf.uni-freiburg.de/www/faq/remmedia.htm for a detailed removable media FAQ.
This driver provides Named Pipes support on the Netware client.
 
  DEVICE=C:\Netware\NMPIPE.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,941: Line 4,898:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,952: Line 4,905:
|}
|}


=DEVICE=NOVAQOS2.SYS=
=OS2CDROM.DMD=
Driver for backup-software from NOVABACK.
Provides support for IDE CDRom drives. It is a device manager driver.
 
'''Note:''' To get CDRom support in OS/2 you must also install Ibm1s506.add and Ibmidecd.flt .
BASEDEV=Os2cdrom.dmd parameters
 
'''Parameters:'''
 
* /V
Displays some information about your CDRom drive during the boot.


  DEVICE=NOVAQOS2.SYS
* /Q
Stops displaying error messages during the boot.  


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,964: Line 4,926:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,975: Line 4,933:
|}
|}


=DEVICE=NOVASPI.SYS=
*[[OS2.SYS]] - Iomega ZIP OAD
Driver for backup-software from NOVABACK.


  DEVICE=NOVASPI.SYS
=OS20MEMU.SYS=
OS20MEMU is a Memory Analyser for OS/2 (IBM EWS).
DEVICE=OS20MEMU.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 4,987: Line 4,946:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 4,998: Line 4,953:
|}
|}


=DEVICE=NPSERVER.SYS=
=OS2EASY.SYS=
This driver allows your workstation to function as a Named Pipes Netware server.
Altec EASY DRIVE. http://www.altec-computersysteme.com
DEVICE=OS2EASY.SYS <parameter>
 
'''Parameter:'''
 
* /V
Set Verbose Mode on
* /B:XXX
Set Base Adress to XXX e.g. 170


  DEVICE=C:\Netware\NPSERVER.SYS
'''NOTE:''' Currently only one slot supported, the standard format command is unsupported, no API to get direct access to the meory media.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,017: Line 4,980:
|}
|}


=OS2OGL.SYS=
Pentium Pro optimised Open GL Driver.


=DEVICE=NSIR.SYS=
  DEVICE=OS2OGL.SYS
Part of the Infrared driver for IBM PC300PL computer.


  DEVICE=C:\OS2\DLL\NSIR.SYS
'''NOTE:''' For OpenGL to utilize the device driver on PentiumPro systems, an environment variable, SET OGL_VIDEO_MEM_SIZE, must be set. The suggested place to set OGL_VIDEO_MEM_SIZE is in the config.sys, alternately, it can be set in an OS/2 Window before an OpenGL program is started. For either method, OGL_VIDEO_MEM_SIZE should be set to the total memory size (in megabytes) of the PCI graphics card. For example, using a graphics card with 4MB of memory, "SET OGL_VIDEO_MEM_SIZE=4" should be used.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,030: Line 4,994:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,041: Line 5,001:
|}
|}


=DEVICE=NTRACE.OS2=
=P6K7MTRR.SYS=
Goldencode Network Trace (http://www.goldencode.com).
A simple interface physical device driver(PDD) that can manage memory Type Range Registers(MTRRs) of Intel P6* / AMD K7** series processors. Programmer can query/modify any MTRR settings via DosDevIOCtl() API, from non-Ring0 privileges. A sample executable, VFBWC.exe, using P6K7MTRR.sys, sets MTRR write-combining strategy to video frame buffer aperture. It can often improve graphic performance, especially DIVE. By [[Takayuki 'January June' Suwa]] (jjsuwa@sys3175.com)  
 
DEVICE=P6K7MTRR.SYS
  DEVICE=NTRACE.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,053: Line 5,012:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,064: Line 5,019:
|}
|}


=P9100.sys=
Is used by graphiccards with a Weitek P9100 chip.


=DEVICE=NULLNDIS.OS2=
   DEVICE=C:\Os2\Boot\P9100.sys
IBM NULL MAC-driver. Installed if you have NO Network Adapter.
 
   DEVICE=NULLNDIS.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,077: Line 5,031:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,088: Line 5,038:
|}
|}


=DEVICE=NVC.SYS=
=PANEL.SYS=
This is a "Smart Behavior Blocker for DOS" from Norman antivirus.
PANEL is a small OS/2 device driver that gives access to the small (eight character) information panel on the front of the PS/2 Model 95 series of systems (and possibly others).
Basically a shield running in dos-boxes and similar to protect from possible virus "sneak attacks".  
Available for FREE at http://www.tavi.co.uk/os2pages/index.html
 
DEVICE=PANEL.SYS
  DEVICE=NVC.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,101: Line 5,050:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,112: Line 5,057:
|}
|}


=DEVICE=NWREQ.SYS=
=PARADISE.SYS=
This is the main Netware requester module and must appear in config.sys after the NmPipe.sys , Ipx.sys and Spx.sys drivers.
Driver for the Paradise mixer for all Crystal CS423x soundcards using a mode-3 driver.
DEVICE=PARADISE.SYS


  DEVICE=C:\Netware\Nwreq.sys
'''Platform Support:'''
 
{| class="wikitable"
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,124: Line 5,068:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,135: Line 5,075:
|}
|}


=DEVICE=ODI2NDI.SYS=
=PAUSE.SYS=
This driver allows the Netware client to use MPTS as the interface to a network adapter driver and in turn, the LAN.
DEVICE=PAUSE.SYS
 
'''Parameter:'''
* /W:NNN
Where: NNN = seconds to wait (default = 30 seconds)
 
Pauses the config.sys for a given time. Useful for maintenance purposes.
The driver can be found at the IBM Device Driver Pak Online site.


  DEVICE=C:\Netware\Odi2Ndi.sys
'''TIP:''' Together with BASEDEV=IBM1S506.ADD the /W parameter does the same.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,147: Line 5,094:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,158: Line 5,101:
|}
|}


=DEVICE=OPL3.SYS=
=PC.SYS=
Is used by soundcards with an OPL3 sound chip.
Driver from Process Commander by Stardock.
DEVICE=PC.SYS


  DEVICE=C:\Os2\Boot\Opl3.sys
'''Platform Support:'''
 
{| class="wikitable"
'''Parameter:'''
 
* /P:nnn
Base I/O: Sets the base I/O address for FM device.
Is almost always, 388 (nnn is in hex)
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,176: Line 5,112:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,187: Line 5,119:
|}
|}


=DEVICE=OPL3SA.SYS=
=PC100.OS2=
It is used by Soundcards with Yamaha SAx sound chips.
Linksys EtherFast 10/100 PC Card. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.
 
DEVICE=PC100.OS2
  DEVICE=C:\Mmos2\Opl3sa.sys


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,199: Line 5,130:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,210: Line 5,137:
|}
|}


=DEVICE=OPL3VDD.SYS=
=PCCOM2.SYS=
It is used by Soundcards with Yamaha SAx sound chips. It provides support for DOS sessions.
PCCOM 2 PORT Card Device driver.
DEVICE=PCCOM2.SYS
 
'''Parameter:'''
* /Axxx,yyy
card I/O address; port1=xxx, port2=yyy
 
* /Imm,nn
IRQ Nø; IRQ1=mm, IRQ2=nn


  DEVICE=C:\Mmos2\OPL3VDD.SYS
* /Cxx
Assign the port number of the first port on the card ( COM1 to COM98 )


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,222: Line 5,158:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,234: Line 5,166:




=DEVICE=OPL4D.SYS=
=PCCOM4.SYS=
Yahama Fm Sythesis OPL4 MIDI Driver.
PCCOM 4 PORT Card Device driver.
DEVICE=PCCOM4.SYS <parameter>
 
'''Parameter:'''
/Axxx : card address


  DEVICE=OPL4D.SYS
/Ixx : IRQ Nø


'''Parameter:'''
/D : compatible mode: COM1 and COM2 ( same as PC COM ). Use COM.SYS ( from IBM) for these 2 ports and PCCOM4.SYS for other ports. This option must be put to the front of all other options.
* /P:xxx
Midiport Address, 300, 310, 330 or 388 (default)


* /N:OPL41$
/Cxx : Assign the port number of the first port on the card ( COM1 to COM96 )


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,252: Line 5,186:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,263: Line 5,193:
|}
|}


=PCCOM8.SYS=
PCCOM 8 PORT Card Device driver.
DEVICE=PCCOM8.SYS


'''Parameter:'''
* /Axxx,xxx
Address of the card, following of vector address( without any space ! )
* /Ixx
IRQ Nø
* /Cxx
Assign the port number of the first port on the card ( COM1 to COM92 )


=DEVICE=OPTICAL.DMD=
'''Platform Support:'''
New with Warp4 Device Manager for Optical devices like MO.
{| class="wikitable"
 
  DEVICE=OPTICAL.DMD
 
'''TIP:''' If you have removable media drives (MO, IOMEGA, SYQUEST and others) look at http://rheooptik.fmf.uni-freiburg.de/www/faq/remmedia.htm for a detailed removable media FAQ.
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,279: Line 5,212:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,290: Line 5,219:
|}
|}


=DEVICE=OS2CDROM.DMD=
===PCIND.OS2===
Provides support for IDE CDRom drives. It is a device manager driver.
NDIS driver for RealTek RTL-8029 based NE2000-combatible cards.
 
DEVICE=PCIND.OS2
'''Note:''' To get CDRom support in OS/2 you must also install Ibm1s506.add and Ibmidecd.flt .
 
  BASEDEV=Os2cdrom.dmd parameters
 
'''Parameters:'''
 
* /V
Displays some information about your CDRom drive during the boot.
 
* /Q
Stops displaying error messages during the boot.  


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,312: Line 5,230:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,323: Line 5,237:
|}
|}


=DEVICE=OS2.SYS=
===PCKBD.SYS===
This is a driver for the Iomega ZIP-100 drives. It works only with the older models.
Process Commander Keyboard driver.
The PCKBD line lets full-screen Process Commander be invoked, even when the customized KBDBASE.SYS is not being used.
DEVICE=PCKBD.SYS <parameter>


  DEVICE=C:\oad\OS2.sys
'''Parameter:'''


These drivers only work for Iomega SCSI adapters and the Parallel Port version of the Zip 100 drive.
* KEYB:CA-A
Attention: Newer Parallel Port Versions of the Zipdrive don't work.
See also BASEDEV PPAOS2.ADD which should work with all parallel port ZIP-drives (100, 100+ and 250)


 
For getting it to work with FP13 and up see:
'''Advantages:'''
http://www.scoug.com/os24u/2001/scoug003.mrkia.html
 
Fast without requiring the disk to be locked into the drive as a fixed disk.
Compatible with the format that the disks come with from the factory.
Currently the only option for PP drive users.
 
 
'''Disadvantages:'''
 
Doesn't work with non-Iomega SCSI adapters.
Only allows one device to be attached to your SCSI adapter.
There have been reports of problems copying files that have large EAs and these drivers.
Drivers must be placed in a subdirectory named drive:\OAD on the boot drive.
 
'''NOTE:''' Iomega SCSI versions of Jaz and Zip Drives can be used as backup devices with Seagate Backup Exec for OS/2 Warp. Cartridges used for backup will be reserved solely for backup use. For these devices, you must format the cartridges with the OS/2 format command from a command prompt. This format may fail if the Iomega drivers are loaded in the config.sys. If so, try commenting out the drivers, reboot, and try the OS/2 format again. Once the OS/2 format is complete, the Iomega drivers can be uncommented and there should be no further problem.
 
'''TIP:''' Together with HPFSREM.ZIP and - if you want a GUI - HPFSPM12.ZIP
the drives can also formatted using HPFS. Both packages are available for FREE at:
http://rheooptik.fmf.uni-freiburg.de/pub/os2/drivers/removables/00-index.html


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,360: Line 5,256:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,371: Line 5,263:
|}
|}


=DEVICE=OS20MEMU.SYS=
===PCLOGIC.SYS===
OS20MEMU is a Memory Analyser for OS/2 (IBM EWS).
Provides mouse support for Genius, Logitech, PC Mouse Systems.
   
  DEVICE=PCLOGIC.SYS
  DEVICE=OS20MEMU.SYS
 
'''ATTENTION:''' Must reside between POINTDD.SYS and MOUSE.SYS.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,383: Line 5,276:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
Line 5,390: Line 5,281:
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|Yes
|}


=DEVICE=OS2EASY.SYS=
===PCM2FLSH.SYS===
Altec EASY DRIVE. http://www.altec-computersysteme.com
PCMCIA Storage Driver for OS/2 (FLASH).
 
DEVICE=PCM2FLSH.SYS
  DEVICE=OS2EASY.SYS <parameter>
 
'''Parameter:'''
 
* /V
Set Verbose Mode on
* /B:XXX
Set Base Adress to XXX e.g. 170
 
'''NOTE:''' Currently only one slot supported, the standard format command is unsupported, no API to get direct access to the meory media.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,415: Line 5,294:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,426: Line 5,301:
|}
|}


=DEVICE=OS2OGL.SYS=
===PCM2SRAM.SYS===
Pentium Pro optimised Open GL Driver.
PCMCIA Storage Driver for OS/2 (SRAM).
 
DEVICE=PCM2SRAM.SYS
  DEVICE=OS2OGL.SYS
 
'''NOTE:''' For OpenGL to utilize the device driver on PentiumPro systems, an environment variable, SET OGL_VIDEO_MEM_SIZE, must be set. The suggested place to set OGL_VIDEO_MEM_SIZE is in the config.sys, alternately, it can be set in an OS/2 Window before an OpenGL program is started. For either method, OGL_VIDEO_MEM_SIZE should be set to the total memory size (in megabytes) of the PCI graphics card. For example, using a graphics card with 4MB of memory, "SET OGL_VIDEO_MEM_SIZE=4" should be used.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,440: Line 5,312:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|?
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,451: Line 5,319:
|}
|}


=DEVICE=P6K7MTRR.SYS=
===PCMNICCS.OS2===
A simple interface physical device driver(PDD) that can manage memory Type Range Registers(MTRRs) of Intel P6* / AMD K7** series processors. Programmer can query/modify any MTRR settings via DosDevIOCtl() API, from non-Ring0 privileges. A sample executable, VFBWC.exe, using P6K7MTRR.sys, sets MTRR write-combining strategy to video frame buffer aperture. It can often improve graphic performance, especially DIVE. By [[Takayuki 'January June' Suwa]] (jjsuwa@sys3175.com)
IBM Ethernet Adapter (PCMCIA) driver.
 
DEVICE=PCMNICCS.OS2
  DEVICE=P6K7MTRR.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,463: Line 5,330:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|2.1
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,474: Line 5,337:
|}
|}


=DEVICE=P9100.sys=
===PCMSSDIF.SYS===
Is used by graphiccards with a Weitek P9100 chip.
PCMCIA Storage Driver for OS/2 (Interface).
 
DEVICE=PCMSSDIF.SYS
  DEVICE=C:\Os2\Boot\P9100.sys


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,486: Line 5,348:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|2.1
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|Yes
|Yes
|}


=DEVICE=PANEL.SYS=
===PCNTND.OS2===
PANEL is a small OS/2 device driver that gives access to the small (eight character) information panel on the front of the PS/2 Model 95 series of systems (and possibly others).
AMD PCNet Ethernet Family Adapter driver.
Available for FREE at http://www.tavi.co.uk/os2pages/index.html
DEVICE=PCNTND.OS2
 
  DEVICE=PANEL.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,510: Line 5,366:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,521: Line 5,373:
|}
|}


 
=PDITOU01.SYS=
=DEVICE=PARADISE.SYS=
See DEVICE TOUCH.SYS.
Driver for the Paradise mixer for all Crystal CS423x soundcards using a mode-3 driver.
DEVICE=PDITOU01.SYS
 
  DEVICE=PARADISE.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,534: Line 5,384:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,545: Line 5,391:
|}
|}


 
===PDITOU02.SYS===
=DEVICE=PAUSE.SYS=
See DEVICE TOUCH.SYS.
 
DEVICE=PDITOU02.SYS
  DEVICE=PAUSE.SYS
 
'''Parameter:'''
* /W:NNN
Where: NNN = seconds to wait (default = 30 seconds)
 
Pauses the config.sys for a given time. Useful for maintenance purposes.
The driver can be found at the IBM Device Driver Pak Online site.
 
'''TIP:''' Together with BASEDEV=IBM1S506.ADD the /W parameter does the same.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,566: Line 5,402:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,577: Line 5,409:
|}
|}


 
=PENCC.SYS=
=DEVICE=PC.SYS=
Pen for OS/2 Device Driver for CalComp 3300.
Driver from Process Commander by Stardock.
DEVICE=PENCC.SYS
 
  DEVICE=PC.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,590: Line 5,420:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,601: Line 5,427:
|}
|}


 
===PENDD.SYS===
=DEVICE=PC100.OS2=
Wacom IV and V Tablet driver by Masami Kitamura.
Linksys EtherFast 10/100 PC Card. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.
DEVICE=PENDD.SYS
 
  DEVICE=PC100.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,614: Line 5,438:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
Line 5,621: Line 5,443:
|Yes
|Yes
|Yes
|Yes
|Yes
|}
|Yes
|}


*[[PMAC.OS2]] - SSW Parallel NDIS


=DEVICE=PCCOM2.SYS=
===PMDD.SYS===
PCCOM 2 PORT Card Device driver.
Installs pointer draw device driver support.
DEVICE=\Os2\Boot\Pmdd.sys


  DEVICE=PCCOM2.SYS
'''WARNING:''' OS/2 will not start without this line in your config.sys file.
 
'''Parameter:'''
* /Axxx,yyy
card I/O address; port1=xxx, port2=yyy
 
* /Imm,nn
IRQ Nø; IRQ1=mm, IRQ2=nn
 
* /Cxx
Assign the port number of the first port on the card ( COM1 to COM98 )


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,648: Line 5,460:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,659: Line 5,467:
|}
|}


 
===PNPND.OS2===
=DEVICE=PCCOM4.SYS=
Device driver for the RTL8019 Ethernet card.  
PCCOM 4 PORT Card Device driver.
   DEVICE=PNPND.OS2
 
   DEVICE=PCCOM4.SYS <parameter>
 
'''Parameter:'''
/Axxx : card address
 
/Ixx : IRQ Nø
 
/D : compatible mode: COM1 and COM2 ( same as PC COM ). Use COM.SYS ( from IBM) for these 2 ports and PCCOM4.SYS for other ports. This option must be put to the front of all other options.
 
/Cxx : Assign the port number of the first port on the card ( COM1 to COM96 )


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 5,681: Line 5,478:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,692: Line 5,485:
|}
|}


==POINTDD.SYS==
Provides mouse pointer draw support. Text modes 0, 1, 2, 3, and 7 and graphic modes D, E, F, and 10 are supported. For graphic modes other than D, E, F, and 10, the correct graphic device driver must also be installed.
DEVICE=\Os2\Boot\Pointdd.sys


=DEVICE=PCCOM8.SYS=
'''WARNING:''' In order for MOUSE.SYS to work effectively, this driver must be loaded by OS/2 before MOUSE.SYS. Do not remove it from your config.sys file.
PCCOM 8 PORT Card Device driver.


  DEVICE=PCCOM8.SYS
'''Platform Support:'''
 
{| class="wikitable"
'''Parameter:'''
|-
* /Axxx,xxx
!OS/2 2.x
Address of the card, following of vector address( without any space ! )
* /Ixx
IRQ Nø
* /Cxx
Assign the port number of the first port on the card ( COM1 to COM92 )
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,724: Line 5,505:
|}
|}


===PCIND.OS2===
===PPPEMYWI.OS2===
NDIS driver for RealTek RTL-8029 based NE2000-combatible cards.
PPP over Ethernet Protocol driver included in ISDNPM 3.x.
DEVICE=PCIND.OS2
 
  DEVICE=PPPEMYWI.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 5,742: Line 5,524:
|}
|}


===PCKBD.SYS===
*[[PRANDIS.OS2]] - Parallel Port NDIS Mac
Process Commander Keyboard driver.
The PCKBD line lets full-screen Process Commander be invoked, even when the customized KBDBASE.SYS is not being used.
DEVICE=PCKBD.SYS <parameter>


'''Parameter:'''
===PROTMAN.OS2===
Network protocol-manager driver. IBM OS/2 LAN Protocol Manager, read PROTOCOL.INI in directory drive:\IBMCOM
DEVICE=C:\IBMCOM\PROTMAN.OS2 <parameter>


* KEYB:CA-A
'''Parameters'''


For getting it to work with FP13 and up see:
* /I:C:\IBMCOM
http://www.scoug.com/os24u/2001/scoug003.mrkia.html


'''Platform Support:'''
'''Platform Support:'''
Line 5,768: Line 5,548:
|}
|}


===PCLOGIC.SYS===
===PRTUTIL.SYS===
Provides mouse support for Genius, Logitech, PC Mouse Systems.
Part of the Infrared driver for IBM PC300PL computer.  
  DEVICE=PCLOGIC.SYS
  DEVICE=C:\OS2\DLL\PRTUTIL.SYS
 
'''ATTENTION:''' Must reside between POINTDD.SYS and MOUSE.SYS.


'''Platform Support:'''
'''Platform Support:'''
Line 5,782: Line 5,560:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|No
|Yes
|Yes
|Yes
|Yes
Line 5,788: Line 5,566:
|}
|}


===PCM2FLSH.SYS===
===PSCOM.SYS===
PCMCIA Storage Driver for OS/2 (FLASH).
This driver is required for serial communications on ACPI systems.
  DEVICE=PCM2FLSH.SYS
  DEVICE=\OS2\Boot\PSCOM.SYS <parameters>
 
'''NOTE:''' This line MUST appear ''after'' any driver that uses a communications port, but ''before'' USB serial drivers (e.g., USBSER.SYS and/or USBCOM.SYS).


'''Platform Support:'''
'''NOTE:''' See other notes related to COM.SYS.
{| class="wikitable"
 
|-
'''TIP:''' To specify address and interrupt manually, use the syntax (port,address,IRQ), e.g.:
 
Set COM3 and COM4 at address 3E8 on IRQ 4 and 2E8 on IRQ 3:
  DEVICE=drive:\OS2\COM.SYS (3,3E8,4) (4,2E8,3)
 
'''Parameter:'''
* /V - Verbose
* /W - Wait verbose mode. Displaying pauses with a "Press Enter to continue..." message.
* /F - Find COM ports on PCI combo (serial/parallel) cards automatically.
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 5,806: Line 5,598:
|}
|}


===PCM2SRAM.SYS===
=PTDVR.SYS=
PCMCIA Storage Driver for OS/2 (SRAM).
Driver of Backmaster tape backup system.
  DEVICE=PCM2SRAM.SYS
  DEVICE=PTDVR.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 5,818: Line 5,610:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|?
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,824: Line 5,616:
|}
|}


===PCMNICCS.OS2===
===QAP2DRVR.SYS===
IBM Ethernet Adapter (PCMCIA) driver.
Driver for QAPlus/2, a PM program for testing system hardware: CDROM, ser/par ports, floppy drives, HD, keyboard, system board, memory, mouse... It can pinpoint failed SIMMs. Makes reports; everything. A bit dated now (1996), but still kinda useful. From DiagSoft, Inc., in Scott's Valley, CA, USA.
  DEVICE=PCMNICCS.OS2
  DEVICE=QAP2DRVR.SYS
 
Information by [[Wm D Loughman]] (wdlkhl@attglobal.net)


'''Platform Support:'''
'''Platform Support:'''
Line 5,836: Line 5,630:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|2.1
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,842: Line 5,636:
|}
|}


===PCMSSDIF.SYS===
===QCAMM.SYS===
PCMCIA Storage Driver for OS/2 (Interface).
Driver for the Connectix Quickcam connected to parallel port.
  DEVICE=PCMSSDIF.SYS
QCammdd01.zip is FREE for personal use.
  DEVICE=QCAMM.SYS <parameter>
 
'''Parameter:'''
* /CB=nnn - Camera Balance 1-254 (varies)
* /CC=nnn - Camera Contrast,nnn=1-255,default 104
* /CE=nnn - Camera Exposure,nnn=1-254,default 210
* /CT=n - Camera Transfer,n=1,2,4, default 1
* /FD=n - Frame Depth,n=4,6,default 6
* /FH=nnn - Frame Height,nnn=1-240,default 240
* /FL=nnn - Frame Left,nnn=1-320,default 1
* /FT=nnn - Frame Top,nnn=1-240,default 1
* /FW=nnn - Frame Width,nnn=1-320,default 320
* /PA=nnn - Port Address,nnn=278,378,3bc
* /PN=n - Port Number,n=1,2,3
* /QM - Quiet Mode


'''Platform Support:'''
'''Platform Support:'''
Line 5,854: Line 5,663:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|2.1
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,860: Line 5,669:
|}
|}


===PCNTND.OS2===
=QCOM.SYS=
AMD PCNet Ethernet Family Adapter driver.
Quatech (www.quatech.com) asynchronous serial device driver for the Quatech ISA and PCI boards High baud rates to 921,600 bits per second, depending on UART type. Support for 16750 UARTs and their 64-byte FIFOs. Up to 32 serial ports.
DEVICE=PCNTND.OS2
 
  DEVICE=QCOM.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 5,878: Line 5,688:
|}
|}


=DEVICE=PDITOU01.SYS=
===QUICKCAM.SYS===
See DEVICE TOUCH.SYS.
Quickcam Viewer driver for Connectix QuickCam (tm) B&W, Colour, ColourII, QuickCam VC or QuickCam Pro
  DEVICE=PDITOU01.SYS
 
'''NOTE:''' It is recommended that you set your parallel port to either AT-mode or EPP-mode for uni-directional or bi-directional modes, respectively. Bi-directional mode will give at least double the throughput compared to uni-directional mode. QuickCam VC and Pro: The parallel-port MUST be set to ECP-mode. Currently, interrupt and DMA settings are not used.
Available at: http://www.cix.co.uk/~elad/qv2.htm
  DEVICE=QUICKCAM.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 5,890: Line 5,703:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|
|Yes
|Yes
|Yes
|Yes
Line 5,896: Line 5,709:
|}
|}


===PDITOU02.SYS===
===QVCOM.SYS===
See DEVICE TOUCH.SYS.
Quatech (www.quatech.com) asynchronous serial device driver for the Quatech ISA and PCI boards for DOS.
  DEVICE=PDITOU02.SYS
  DEVICE=QVCOM.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 5,907: Line 5,720:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,918: Line 5,727:
|}
|}


=DEVICE=PENCC.SYS=
===R0STUB.SYS===
Pen for OS/2 Device Driver for CalComp 3300.
Is somewhere used by MMOS2. R0STUB is the ring-0 half of the sync-stream-manager (SSM) that allows MMPM/2 to synchronize audio and video. Allows audiosh.dll to talk to audio drivers vis IDC entrypoint. In the beginning, all the streaming took place at ring-0. Later (Warp 3?), the audio streaming was moved to ring-3. The API still had to be maintained to audio driver. R0STUB is small piece of code that takes FIFOs buffers to/from MMPM/2 ring-3 audio stream handler and delivers them from/to the hardware vender audio device driver.
  DEVICE=PENCC.SYS
  DEVICE=C:\Mmos2\R0stub.sys


'''Platform Support:'''
'''Platform Support:'''
Line 5,936: Line 5,745:
|}
|}


===PENDD.SYS===
===RAWEMYWI.OS2===
Wacom IV and V Tablet driver by Masami Kitamura.
DSL cable-modem driver from ISDNPM.
  DEVICE=PENDD.SYS
  DEVICE=RAWEMYWI.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 5,947: Line 5,756:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 5,958: Line 5,763:
|}
|}


*[[PMAC.OS2]] - SSW Parallel NDIS
===RCPTRNDS.OS2===
 
Racore Preferred Token Ring Adapter (PCMCIA Support).
===PMDD.SYS===
  DEVICE=RCPTRNDS.OS2
Installs pointer draw device driver support.
  DEVICE=\Os2\Boot\Pmdd.sys
 
'''WARNING:''' OS/2 will not start without this line in your config.sys file.


'''Platform Support:'''
'''Platform Support:'''
Line 5,980: Line 5,781:
|}
|}


===PNPND.OS2===
===RDRHELP.200===
Device driver for the RTL8019 Ethernet card.  
This driver is part of MPTS and is necessary somewhere for the NetBIOS protocol.
  DEVICE=PNPND.OS2
DEVICE=\Ibmcom\Netprog\Rdrhelp.200


'''Platform Support:'''
'''Platform Support:'''
Line 5,998: Line 5,799:
|}
|}


==POINTDD.SYS==
===REFPART.SYS===
Provides mouse pointer draw support. Text modes 0, 1, 2, 3, and 7 and graphic modes D, E, F, and 10 are supported. For graphic modes other than D, E, F, and 10, the correct graphic device driver must also be installed.
Driver for accessing the Refernce Partition on IBM PS/2 Microchannel Machines.
DEVICE=\Os2\Boot\Pointdd.sys
Information by: [[Ralph-Marcus Boenicke]]
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


'''WARNING:''' In order for MOUSE.SYS to work effectively, this driver must be loaded by OS/2 before MOUSE.SYS. Do not remove it from your config.sys file.
=RMAUDIO.SYS=
Reel Magic sound card driver.


'''Platform Support:'''
'''Platform Support:'''
Line 6,018: Line 5,834:
|}
|}


===PPPEMYWI.OS2===
*[[RODENT.SYS]]
PPP over Ethernet Protocol driver included in ISDNPM 3.x.


  DEVICE=PPPEMYWI.OS2
=ROUTE.SYS=
This driver allows a Netware client to see Netware servers on other physical LAN (or segment) across source-routing routers (used by many IBM routers). This is equivalent to Route.nlm for a Netware server.
DEVICE=C:\Netware\Route.sys


'''Platform Support:'''
'''Platform Support:'''
Line 6,037: Line 5,854:
|}
|}


*[[PRANDIS.OS2]] - Parallel Port NDIS Mac
=RSJSCSI.SYS=
The device driver RSJSCSI.SYS provides simplified access to SCSI devices. The CD Writer File System uses this device driver to access the CD Recorder (also needed for ATAPI).
DEVICE=RSJSCSI.SYS <parameter>


===PROTMAN.OS2===
'''Parameter:'''
Network protocol-manager driver. IBM OS/2 LAN Protocol Manager, read PROTOCOL.INI in directory drive:\IBMCOM
DEVICE=C:\IBMCOM\PROTMAN.OS2 <parameter>


'''Parameters'''
* -q
While booting, ask user for confirmation before installing the device driver.


* /I:C:\IBMCOM
* -x
This option allows using memory above the 16MB line. This works together with true 32-bit SCSI adapters, only (e.g. most EISA and PCI adapters).


'''Platform Support:'''
'''Platform Support:'''
Line 6,061: Line 5,880:
|}
|}


===PRTUTIL.SYS===
=RSMVDWO.SYS=
Part of the Infrared driver for IBM PC300PL computer.  
Driver for PolyPM a Remote Service Management Solution. http://www.iss2you.com
  DEVICE=C:\OS2\DLL\PRTUTIL.SYS
  DEVICE=RSMVDWO.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 6,073: Line 5,892:
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|No
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,079: Line 5,898:
|}
|}


===PSCOM.SYS===
=RTFND.OS2=
This driver is required for serial communications on ACPI systems.
RTL8129 Fast Ethernet Adapter.
  DEVICE=\OS2\Boot\PSCOM.SYS <parameters>
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/realtek.zip.
  DEVICE=RTFND.OS2


'''NOTE:''' This line MUST appear ''after'' any driver that uses a communications port, but ''before'' USB serial drivers (e.g., USBSER.SYS and/or USBCOM.SYS).
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


'''NOTE:''' See other notes related to COM.SYS.
=RTGNDA.OS2=
 
New description.
'''TIP:''' To specify address and interrupt manually, use the syntax (port,address,IRQ), e.g.:
DEVICE=RTGNDA.OS2
 
Set COM3 and COM4 at address 3E8 on IRQ 4 and 2E8 on IRQ 3:
  DEVICE=drive:\OS2\COM.SYS (3,3E8,4) (4,2E8,3)
 
'''Parameter:'''
* /V - Verbose
* /W - Wait verbose mode. Displaying pauses with a "Press Enter to continue..." message.
* /F - Find COM ports on PCI combo (serial/parallel) cards automatically.


'''Platform Support:'''
'''Platform Support:'''
Line 6,111: Line 5,935:
|}
|}


=DEVICE=PTDVR.SYS=
=RTR16NDIS.OS2=
Driver of Backmaster tape backup system.
Racore 16/4 Token-Ring Adapter.
  DEVICE=PTDVR.SYS
  DEVICE=RTR16NDIS.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 6,129: Line 5,953:
|}
|}


===QAP2DRVR.SYS===
=RTSND.OS2=
Driver for QAPlus/2, a PM program for testing system hardware: CDROM, ser/par ports, floppy drives, HD, keyboard, system board, memory, mouse... It can pinpoint failed SIMMs. Makes reports; everything. A bit dated now (1996), but still kinda useful. From DiagSoft, Inc., in Scott's Valley, CA, USA.
NDIS MAC for RTL8139 Fast Ethernet Adapter.
DEVICE=QAP2DRVR.SYS
 
  DEVICE=RTSND.OS2 <parameter>


Information by [[Wm D Loughman]] (wdlkhl@attglobal.net)
'''Parameters'''
* /V
Verbose mode
* /Q
Quiet mode
* /2 .. /9
Selecects other Drivername = netry in \ibmcom\protocol.ini used automaticly if you install more than one card.
* /U
Number cards as found. useful if BUSNO, DEVICENO or ETHERID values are not present in protocol.ini


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,142: Line 5,975:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,153: Line 5,982:
|}
|}


===QCAMM.SYS===
===RVGNDIS.OS2===
Driver for the Connectix Quickcam connected to parallel port.
Racore 10/100 AnyLAN Card.  
QCammdd01.zip is FREE for personal use.
  DEVICE=RVGNDIS.OS2
  DEVICE=QCAMM.SYS <parameter>
 
'''Parameter:'''
* /CB=nnn - Camera Balance 1-254 (varies)
* /CC=nnn - Camera Contrast,nnn=1-255,default 104
* /CE=nnn - Camera Exposure,nnn=1-254,default 210
* /CT=n - Camera Transfer,n=1,2,4, default 1
* /FD=n - Frame Depth,n=4,6,default 6
* /FH=nnn - Frame Height,nnn=1-240,default 240
* /FL=nnn - Frame Left,nnn=1-320,default 1
* /FT=nnn - Frame Top,nnn=1-240,default 1
* /FW=nnn - Frame Width,nnn=1-320,default 320
* /PA=nnn - Port Address,nnn=278,378,3bc
* /PN=n - Port Number,n=1,2,3
* /QM - Quiet Mode


'''Platform Support:'''
'''Platform Support:'''
Line 6,179: Line 5,993:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,190: Line 6,000:
|}
|}


=DEVICE=QCOM.SYS=
=RZT2BOOT.SYS=
Quatech (www.quatech.com) asynchronous serial device driver for the Quatech ISA and PCI boards High baud rates to 921,600 bits per second, depending on UART type. Support for 16750 UARTs and their 64-byte FIFOs. Up to 32 serial ports.
This driver is used by the IBM AO-Manager.


   DEVICE=QCOM.SYS
   DEVICE=C:\SMG\Bin\Rzt2boot.sys


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,202: Line 6,012:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,213: Line 6,019:
|}
|}


===QUICKCAM.SYS===
===SB16D2.SYS===
Quickcam Viewer driver for Connectix QuickCam (tm) B&W, Colour, ColourII, QuickCam VC or QuickCam Pro
Driver for Sound Blaster 16 sound card.
DEVICE=SB16D2.SYS <parameter>


'''NOTE:''' It is recommended that you set your parallel port to either AT-mode or EPP-mode for uni-directional or bi-directional modes, respectively. Bi-directional mode will give at least double the throughput compared to uni-directional mode. QuickCam VC and Pro: The parallel-port MUST be set to ECP-mode. Currently, interrupt and DMA settings are not used.
'''Parameter:'''
Available at: http://www.cix.co.uk/~elad/qv2.htm
DEVICE=QUICKCAM.SYS


'''Platform Support:'''
* /C:  
{| class="wikitable"
Card Number, this will be set to 1 in most cases
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}


===QVCOM.SYS===
* /D:
Quatech (www.quatech.com) asynchronous serial device driver for the Quatech ISA and PCI boards for DOS.
8-bit DMA channel, Valid values - 0, 1 & 3 (Sound Blaster cards that use Vibra chipset do not have 0). Default value - 1.
DEVICE=QVCOM.SYS
 
* /H:
16-bit DMA channel, Valid values - 5, 6 & 7 (Sound Blaster cards that use Vibra chipset do not have 6). Default value - 5.
 
* /I:
IRQ number, Valid values - 5, 7, 9, 10 & 11. Default IRQ - 5.
 
* /A:
Base addresss, Valid values - 220, 240, 260, 280 Default value - 220.
 
* /B:
Buffer size in KB, Valid values - 1-24. While any value in this range will work fine, to get the best results don't use this option and let the driver use the default buffer size. Default value - 8KB.
 
* /M:
MPU port address Valid values - 300 & 330 Default value - 330.
 
* /N:
Driver name, set this to SBAUD1$
 
* /Q
Quiet mode flag, OPTIONAL. Setting this option disables initialization messages. If not specified the initialization messages are displayed during boot-up.
 
* /EXT
Use MPU port instead of internal synth for MIDI, OPTIONAL By default the drivers are configured to use the internal synthesizer. But if you have a daughterboard attached to your Sound Blaster card and you want MIDI playback to use the synthesizer in the daughterboard, specify this flag.
 
* /P
Ignore PnP BIOS if it is present. If PnP BIOS is present, the driver usually queries the BIOS for certain PnP port addresses. Specifying this option causes the driver not to access the BIOS and determine these port addresses itself.
 
* /G
Override PnP BIOS, undocumented switch. When used all parameters must be specified.
 
'''TIP:''' Look for the SB163264.ZIP package which contains all drivers for the soundblaster cards including those for the AWE 64.
 
A FREE Mixer for SB 16/32/64 is Mixomat 1.01b by [[Christoph Bratschi]], and the newer Mixomat 2.0 available at http://www.bratschi.net


'''Platform Support:'''
'''Platform Support:'''
Line 6,252: Line 6,079:
|}
|}


===R0STUB.SYS===
===SBAWED2.SYS===
Is somewhere used by MMOS2. R0STUB is the ring-0 half of the sync-stream-manager (SSM) that allows MMPM/2 to synchronize audio and video. Allows audiosh.dll to talk to audio drivers vis IDC entrypoint. In the beginning, all the streaming took place at ring-0. Later (Warp 3?), the audio streaming was moved to ring-3. The API still had to be maintained to audio driver. R0STUB is small piece of code that takes FIFOs buffers to/from MMPM/2 ring-3 audio stream handler and delivers them from/to the hardware vender audio device driver.
It is used by Creative Labs AWE32 soundcards.
DEVICE=C:\Mmos2\R0stub.sys
DEVICE=C:\Sbos2\Sbawed2.sys
 
'''Parameter:'''
See DEVICE SB16D2.SYS
 
'''TIP:''' According to OS/2-Inside the statement can be shortened to:
  SBAWED2.SYS /N:SBAUD1$
 
'''TIP:''' Look for the SB163264.ZIP package which contains all drivers for the soundblaster cards including those for the AWE 64.
According to OS2VOICE for the AWE 64 the entry should look like this:
  DEVICE=drive:\SBOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /B:1 /M:330 /N:SBAUD1$ /G


'''Platform Support:'''
'''Platform Support:'''
Line 6,270: Line 6,107:
|}
|}


===RAWEMYWI.OS2===
 
DSL cable-modem driver from ISDNPM.
===SBLIVE16.SYS===
  DEVICE=RAWEMYWI.OS2
Soundblaster Live 16Bit MMPM/2 Sounddriver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)
  DEVICE=SBLIVE16.SYS <parameter>
 
'''Parameters:'''
 
* /V verbose (prints copyrights during driver init)
* /C enable CD audio input
* /M enable microphone audio input
* /L enable linein audio input
* /A enable aux audio input (since driver 0.80)
 
'''ATTENTION:''' Read the supplied readme.txt to avoid troubles if you have installed the scitech display drivers (SDDHELP.SYS).


'''Platform Support:'''
'''Platform Support:'''
Line 6,288: Line 6,136:
|}
|}


===RCPTRNDS.OS2===
===SBLIVE32.SYS===
Racore Preferred Token Ring Adapter (PCMCIA Support).
Soundblaster Live 32Bit core audio driver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)
  DEVICE=RCPTRNDS.OS2
  DEVICE=SBLIVE32.SYS <parameter>
 
'''Parameter:'''
 
* /D
Print start and end address of code (useful to locate code that causes a trap)
 
'''NOTE:''' The install.cmd copies - if it finds a Warp 4.5 (fixpak 13 or WarpServer for E-Business) an driver according to the new KEE API (32 Bit driver architecture) to this file.
 
A appropiate Mixer is the FREE LBMix by Lesha Bogdanow (boga@inbox.ru)
The lastest version of the mixer can be downloaded from http://www.podolsk.ru/~boga/OS2Programs.html where you can also find a couple of other useful OS/2 programs.


'''Platform Support:'''
'''Platform Support:'''
Line 6,306: Line 6,164:
|}
|}


===RDRHELP.200===
===SBMIX.SYS===
This driver is part of MPTS and is necessary somewhere for the NetBIOS protocol.
Soundblaster-mixer driver.
  DEVICE=\Ibmcom\Netprog\Rdrhelp.200
  DEVICE=SBMIX.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 6,324: Line 6,182:
|}
|}


===REFPART.SYS===
===SCANHP1.SYS===
Driver for accessing the Refernce Partition on IBM PS/2 Microchannel Machines.
SCSISCAN OS/2 Copyright from Danmar Systems Inc. Scanner Driver for use with the propietary SCSI controller included with the HPIIp series.
Information by: [[Ralph-Marcus Boenicke]]
DEVICE=SCANHP1.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 6,342: Line 6,200:
|}
|}


=DEVICE=RMAUDIO.SYS=
===SCANOS2.SYS===
Reel Magic sound card driver.
SCSISCAN OS/2 Version 1.20 from Danmar Systems Inc. ASPI Compatible Scanner Driver.
DEVICE=SCANOS2.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,352: Line 6,211:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,363: Line 6,218:
|}
|}


*[[RODENT.SYS]]
*[[SDDHELP.SYS]]


=DEVICE=ROUTE.SYS=
==SDI_ASPI.SYS==
This driver allows a Netware client to see Netware servers on other physical LAN (or segment) across source-routing routers (used by many IBM routers). This is equivalent to Route.nlm for a Netware server.
PC-BaX ASPI Device Driver. This driver provides PC-BaX with support for SCSI devices, it uses the OS2ASPI.DMD device manager. This is the prefered method of SCSI support for PC-BaX and should be used in almost all cases.
 
DEVICE=SDI_ASPI.SYS
  DEVICE=C:\Netware\Route.sys


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,377: Line 6,231:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,388: Line 6,238:
|}
|}


=DEVICE=RSJSCSI.SYS=
==SDI_CISA.SYS==
The device driver RSJSCSI.SYS provides simplified access to SCSI devices. The CD Writer File System uses this device driver to access the CD Recorder (also needed for ATAPI).
PC-BaX ISA Device Driver. This driver provides PC-BaX with support for a special CRISTIE 8-bit SCSI controller.
 
DEVICE=SDI_CISA.SYS
  DEVICE=RSJSCSI.SYS <parameter>
 
'''Parameter:'''
 
* -q
While booting, ask user for confirmation before installing the device driver.
 
* -x
This option allows using memory above the 16MB line. This works together with true 32-bit SCSI adapters, only (e.g. most EISA and PCI adapters).


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,408: Line 6,249:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,419: Line 6,256:
|}
|}


=DEVICE=RSMVDWO.SYS=
=SDI_IDE.SYS=
Driver for PolyPM a Remote Service Management Solution. http://www.iss2you.com
PC-BaX IDE Device Driver. This driver provides PC-BaX with support for IDE connected devices like Travan backup stations.
 
DEVICE=SDI_IDE.SYS
  DEVICE=RSMVDWO.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,431: Line 6,267:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,442: Line 6,274:
|}
|}


=DEVICE=RTFND.OS2=
=SDI_LPT.SYS=
RTL8129 Fast Ethernet Adapter.
PC-BaX LPT Device Driver. This driver provides PC-BaX with support for Cristie parallel port connect tape drives, it does not need any other OS/2 Devices managers or Drivers.
NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/realtek.zip.
DEVICE=SDI_LPT.SYS
 
  DEVICE=RTFND.OS2


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,455: Line 6,285:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,466: Line 6,292:
|}
|}


=DEVICE=RTGNDA.OS2=
=SDI_SCSI.SYS=
New description.
PC-BaX SCSI Device Driver. This driver provides PC-BaX with support for SCSI devices, it uses the OS2SCSI.DMD device manager. This method of SCSI support is only neccesary when using an IBM MCA type SCSI controller. See common problems by clicking on the support icon within PC-BaX for a full description.
  DEVICE=RTGNDA.OS2
DEVICE=SDI_SCSI.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,477: Line 6,303:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,488: Line 6,310:
|}
|}


=DEVICE=RTR16NDIS.OS2=
=SEAGB24.SYS=
Racore 16/4 Token-Ring Adapter.
Sytos Plus driver for the Seagate 4mm Tape.
DEVICE=SEAGB24.SYS


  DEVICE=RTR16NDIS.OS2
'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,499: Line 6,321:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
 
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,510: Line 6,329:
|}
|}


=DEVICE=RTSND.OS2=
=SESDD32.SYS=
NDIS MAC for RTL8139 Fast Ethernet Adapter.
Security device driver. Part of IBM's security system - enabler driver. Will stop install if by itself. Network Associates has a product called 'VirusScan for OS/2'. In its User Guide's appendix 'C' is a very good description of how to modifiy the config.sys file manually to add SES to the user's machine.
DEVICE=C:\Os2\Boot\Sesdd32.sys


  DEVICE=RTSND.OS2 <parameter>
'''Platform Support:'''
 
{| class="wikitable"
'''Parameters'''
|-
* /V
!OS/2 2.x
Verbose mode
* /Q
Quiet mode
* /2 .. /9
Selecects other Drivername = netry in \ibmcom\protocol.ini used automaticly if you install more than one card.
* /U
Number cards as found. useful if BUSNO, DEVICENO or ETHERID values are not present in protocol.ini
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,543: Line 6,347:
|}
|}


===RVGNDIS.OS2===
=SIO.SYS=
Racore 10/100 AnyLAN Card.  
The Sio.sys driver is a replacement for the com.sys driver. The Sio.sys driver can support up to 16 COM ports.
  DEVICE=RVGNDIS.OS2
  DEVICE=\OS2\BOOT\SIO.SYS <parameters>
DEVICE=\OS2\BOOT\SIO.SYS (Cn, An, In, Ig, Fc)
 
* CN
The number of the Com port or the string COM1 to COMn.
If you use a * in front of the Com port, then the port will be used as a PCMCIA Com port.
 
* AN
A hexnumber to define the I/O address of the Com port.
 
* IN
The IRQ number (0 to 15) or the string IRQ0 to IRQ15. If you don't use this parameter, SIO will search for a IRQ.
 
* IG
This exists only for compatibility with COM.SYS and is ignored by Sio.sys.


'''Platform Support:'''
'''Platform Support:'''
Line 6,554: Line 6,372:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,565: Line 6,379:
|}
|}


=DEVICE=RZT2BOOT.SYS=
This driver is used by the IBM AO-Manager.


  DEVICE=C:\SMG\Bin\Rzt2boot.sys
=SIO2K.SYS=
Excellent replacement driver for COM.SYS. If you utilise communications software on a regular basis at high speeds (e.g. 57,600), then the SIO drivers are the way to go.
DEVICE=SIO2K.SYS
 
'''NOTE:''' REM all other serial drivers like COM.SYS or SIO.SYS
 
The SIO2K set of drivers have some interesting new techniques and implementations.
 
'''Block input and output.''' If the UART is a FIFOed device, the interrupt service routines (there are several) always use block input and output instructions to read and write characters. During high communications activity, this means the 16550 interrupt routine is 5 to 10 times faster (possibly more) than previous implementations. UARTs with larger FIFOs will execute even faster. Now boys and girls, it is the interrupt service routines that are faster. Nothing on Earth can make your modem go faster than it is capable of. However, faster interrupt service routines means less processor overhead.
 
'''Automatic FIFO sizing.''' The SIO2K drivers now support 16650, 16550A, 16750, 16850 and 16950 uarts. However, knowing the chip type does not necessarily mean the FIFO size is know. For example, the 16654 is the equivalent of four (or more) 16650A UARTS on a single chip. The normal 16650 UARTs have a 32 byte FIFO, but the UARTS on the 16654 have 64 byte FIFOs. Only probing will determine this.
 
The first time a UART is touched by an application the SIO2K drivers automatically probe the size of the FIFO and the found size is used. Note that a UART with no FIFOs can be thought of as having a FIFO size of 1 byte. My thanks to Sam Detweiler, of IBM, for the idea of probing for FIFO size.
 
'''Automatic Crystal Frequency.''' Most UARTs are capable of bit rates to 921600bps or more. However, on most serial devices, the bit rate is limited to 115200bps by the crystal oscillator attached to the UART. Many boards, like those from Lava, offer bit rates greater than by using faster crystal oscillator. The down side is one must tell the driver to use a bit rate of 28800 to really get a bit rate of.
 
The first time a UART is touched by an app, the SIO2K drivers probe the UART to determine if it is using a standard crystal oscillator or not. If the frequency is not standard, then the SIO2K drivers automatically adjust so that a request of 115200bps yields an actual bit rate of 115200bps. In addition, the maximum bit rate is adjusted and reported to applications that request the maximum bit rate. Boards like the Blue Heat from CTI use a 12x crystal and its top bit rate is 1382.4kbps.
 
'''Minimum touch during boot.''' The SIO2K drivers do not touch the UART hardware during boot. This was very difficult to do, while maintaining a compatible OS/2 serial driver. The "no touch" practically eliminates the possibility of traps occurring during the boot process when they are difficult to deal with. This does mean that a lot of processing will occur the first time a port is opened.


'''Platform Support:'''
'''Platform Support:'''
Line 6,584: Line 6,414:
|}
|}


===SB16D2.SYS===
=SIS900.OS2=
Driver for Sound Blaster 16 sound card.
SIS 900/7016 PCI Fast Ethernet Adapter.
DEVICE=SB16D2.SYS <parameter>


'''Parameter:'''
  DEVICE=SIS900.OS2
 
* /C:
Card Number, this will be set to 1 in most cases
 
* /D:
8-bit DMA channel, Valid values - 0, 1 & 3 (Sound Blaster cards that use Vibra chipset do not have 0). Default value - 1.
 
* /H:
16-bit DMA channel, Valid values - 5, 6 & 7 (Sound Blaster cards that use Vibra chipset do not have 6). Default value - 5.
 
* /I:
IRQ number, Valid values - 5, 7, 9, 10 & 11. Default IRQ - 5.
 
* /A:
Base addresss, Valid values - 220, 240, 260, 280 Default value - 220.
 
* /B:
Buffer size in KB, Valid values - 1-24. While any value in this range will work fine, to get the best results don't use this option and let the driver use the default buffer size. Default value - 8KB.
 
* /M:
MPU port address Valid values - 300 & 330 Default value - 330.
 
* /N:
Driver name, set this to SBAUD1$
 
* /Q
Quiet mode flag, OPTIONAL. Setting this option disables initialization messages. If not specified the initialization messages are displayed during boot-up.
 
* /EXT
Use MPU port instead of internal synth for MIDI, OPTIONAL By default the drivers are configured to use the internal synthesizer. But if you have a daughterboard attached to your Sound Blaster card and you want MIDI playback to use the synthesizer in the daughterboard, specify this flag.
 
* /P
Ignore PnP BIOS if it is present. If PnP BIOS is present, the driver usually queries the BIOS for certain PnP port addresses. Specifying this option causes the driver not to access the BIOS and determine these port addresses itself.
 
* /G
Override PnP BIOS, undocumented switch. When used all parameters must be specified.
 
'''TIP:''' Look for the SB163264.ZIP package which contains all drivers for the soundblaster cards including those for the AWE 64.
 
A FREE Mixer for SB 16/32/64 is Mixomat 1.01b by [[Christoph Bratschi]], and the newer Mixomat 2.0 available at http://www.bratschi.net


'''Platform Support:'''
'''Platform Support:'''
Line 6,637: Line 6,426:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,644: Line 6,436:
|}
|}


===SBAWED2.SYS===
=SMC1208.OS2=
It is used by Creative Labs AWE32 soundcards.
SMC EZ PCI COMBO Ethernet NIC.
  DEVICE=C:\Sbos2\Sbawed2.sys
  DEVICE=SMC1208.OS2


'''Parameter:'''
'''Platform Support:'''
See DEVICE SB16D2.SYS
 
'''TIP:''' According to OS/2-Inside the statement can be shortened to:
  SBAWED2.SYS /N:SBAUD1$
 
'''TIP:''' Look for the SB163264.ZIP package which contains all drivers for the soundblaster cards including those for the AWE 64.
According to OS2VOICE for the AWE 64 the entry should look like this:
  DEVICE=drive:\SBOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /B:1 /M:330 /N:SBAUD1$ /G
 
'''Platform Support:'''
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 6,665: Line 6,447:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,672: Line 6,457:
|}
|}


 
==SMC8000.OS2==
===SBLIVE16.SYS===
SMC Ethernet Adapter Family (SMC 8003, SMC 8013, SMC 8216, SMC 8416) NDIS driver.
Soundblaster Live 16Bit MMPM/2 Sounddriver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)
  DEVICE=SMC8000.OS2
  DEVICE=SBLIVE16.SYS <parameter>
 
'''Parameters:'''
 
* /V verbose (prints copyrights during driver init)
* /C enable CD audio input
* /M enable microphone audio input
* /L enable linein audio input
* /A enable aux audio input (since driver 0.80)
 
'''ATTENTION:''' Read the supplied readme.txt to avoid troubles if you have installed the scitech display drivers (SDDHELP.SYS).


'''Platform Support:'''
'''Platform Support:'''
Line 6,701: Line 6,475:
|}
|}


===SBLIVE32.SYS===
==SMC9432.OS2==
Soundblaster Live 32Bit core audio driver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)
Network driver for SMC9432/TX (EtherPower II) 10/100 PCI NIC.
  DEVICE=SBLIVE32.SYS <parameter>
  DEVICE=SMC9432.OS2
 
'''Parameter:'''
 
* /D
Print start and end address of code (useful to locate code that causes a trap)
 
'''NOTE:''' The install.cmd copies - if it finds a Warp 4.5 (fixpak 13 or WarpServer for E-Business) an driver according to the new KEE API (32 Bit driver architecture) to this file.
 
A appropiate Mixer is the FREE LBMix by Lesha Bogdanow (boga@inbox.ru)
The lastest version of the mixer can be downloaded from http://www.podolsk.ru/~boga/OS2Programs.html where you can also find a couple of other useful OS/2 programs.


'''Platform Support:'''
'''Platform Support:'''
Line 6,729: Line 6,493:
|}
|}


===SBMIX.SYS===
Soundblaster-mixer driver.
DEVICE=SBMIX.SYS


'''Platform Support:'''
==SMCND.OS2==
{| class="wikitable"
Acctron SMC 1211TX base 10/100 PCI ethernet card.
|-
  DEVICE=SMCND.OS2
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
===SCANHP1.SYS===
SCSISCAN OS/2 Copyright from Danmar Systems Inc. Scanner Driver for use with the propietary SCSI controller included with the HPIIp series.
  DEVICE=SCANHP1.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 6,765: Line 6,512:
|}
|}


===SCANOS2.SYS===
==SMCPWR.OS2==
SCSISCAN OS/2 Version 1.20 from Danmar Systems Inc. ASPI Compatible Scanner Driver.
SMC EtherPower for OS/2. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/dec.zip.
  DEVICE=SCANOS2.SYS
  DEVICE=SMCPWR.OS2


'''Platform Support:'''
'''Platform Support:'''
Line 6,783: Line 6,530:
|}
|}


*[[SDDHELP.SYS]]
==SND16.SYS==
 
The Snd16.sys driver is used by the MAD16 soundcard.
==SDI_ASPI.SYS==
  DEVICE=C:\Os2\Boot\Snd16.sys <parameters>
PC-BaX ASPI Device Driver. This driver provides PC-BaX with support for SCSI devices, it uses the OS2ASPI.DMD device manager. This is the prefered method of SCSI support for PC-BaX and should be used in almost all cases.
  DEVICE=SDI_ASPI.SYS


'''Platform Support:'''
'''Platform Support:'''
Line 6,803: Line 6,548:
|}
|}


==SDI_CISA.SYS==
==SND931.SYS==
PC-BaX ISA Device Driver. This driver provides PC-BaX with support for a special CRISTIE 8-bit SCSI controller.
OPTiSound 82C931 Sound Card Driver.
 
DEVICE=SND931.SYS
  DEVICE=SDI_CISA.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,815: Line 6,559:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,826: Line 6,566:
|}
|}


=DEVICE=SDI_IDE.SYS=
==SNDSCAPE.SYS==
PC-BaX IDE Device Driver. This driver provides PC-BaX with support for IDE connected devices like Travan backup stations.
Ensoniq Soundscape VIVO (SND-ENSVIVO) AD1848 Audio OS/2 Device Driver.
 
DEVICE=SNDSCAPE.SYS
  DEVICE=SDI_IDE.SYS


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,838: Line 6,577:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,849: Line 6,584:
|}
|}


=DEVICE=SDI_LPT.SYS=
===SOCKETS.SYS===
PC-BaX LPT Device Driver. This driver provides PC-BaX with support for Cristie parallel port connect tape drives, it does not need any other OS/2 Devices managers or Drivers.
Network driver.
DEVICE=\Mptn\Potocol\Sockets.sys <parameter>


  DEVICE=SDI_LPT.SYS
'''Parameters:'''
 
* /c:value
Number of the COM port to which debug information should be sent. Value may be any valid COM port number .
Default = 2
 
* /v
Display the banner at boot time.
 
* /uis:0
Turn off unique ID for select().
If this parameter is not set it defaults to ON .
 
* /mem:value
Number of 4kbyte clusters allocated at initialization time.
Value can be in the range from 30 to 32766 . Default = 75
 
* /gdt:value
The maximum number of 64kbyte blocks the stack can allocate.
Default = 80
 
 
'''TIP:''' According to IBM, the undocumented parameter /UIS:0 is for use on the 3172 Offload System to improve performance. This parameter is only intended for use on the 3172 Offload System, and turns off the process id : thread id processing on select() calls in the stack.


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,861: Line 6,619:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,872: Line 6,626:
|}
|}


=DEVICE=SDI_SCSI.SYS=
==SOCKETSK.SYS==
PC-BaX SCSI Device Driver. This driver provides PC-BaX with support for SCSI devices, it uses the OS2SCSI.DMD device manager. This method of SCSI support is only neccesary when using an IBM MCA type SCSI controller. See common problems by clicking on the support icon within PC-BaX for a full description.
32bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak 13 for Warp 4.
Part of the TCP/IP Ver. 4.x firewall.
DEVICE=SOCKETSK.SYS <parameter>
 
'''Parameter:'''
 
* /V
Verbose, shows version-number
 
* /MEM:#
amount of 4KB Clusters. Standard = 75; valid Range = 30 - 32766


  DEVICE=SDI_SCSI.SYS
* /GDT:#
max. amount of 64KB Blocks the Stack can arrange; Standard = 80


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,884: Line 6,649:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,895: Line 6,656:
|}
|}


=DEVICE=SEAGB24.SYS=
==SOLO.SYS==
Sytos Plus driver for the Seagate 4mm Tape.
Driver for ESS SOLO 1 based soundcards or motherboards.
DEVICE=SOLO.SYS <parameter>
 
'''Parameter:'''


  DEVICE=SEAGB24.SYS
* /O:ENABLEWAVETABLE
If your installation includes an ES689 or ES692 WaveTable adding thid parameter to the config.sys line will cause the driver to use the wavetable as the primary midi.


'''Platform Support:'''
* /R:n
{| class="wikitable" style="text-align:center" border="1"
(where n is in milliseconds and between 1 and 32) this parameter allows the user to over ride the default timer resolution (5ms). Increasing this value will cause te driver to get dispatched less often and so use less cpu time, however this can cause the tempo to drag. Decreasing this value below 5 will cause the driver to use more cpu time and can interfere with other timers.
|-
 
The IBM Mixer IOCTLS fully implemented in the Solo driver and this driver can be controlled using IBM's Warp Mixer. Available as Warpmix.zip
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,918: Line 6,684:
|}
|}


=DEVICE=SESDD32.SYS=
==SPCIIRQ.SYS==
Security device driver. Part of IBM's security system - enabler driver. Will stop install if by itself. Network Associates has a product called 'VirusScan for OS/2'. In its User Guide's appendix 'C' is a very good description of how to modifiy the config.sys file manually to add SES to the user's machine.
Change IRQ for PCI cards.
DEVICE=SPCIIRQ.SYS <parameter>


  DEVICE=C:\Os2\Boot\Sesdd32.sys
'''Parameter:'''
* 0..255
* 0..31
* 0..7
* 1..4 fr #A..#B
* 0..15


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,930: Line 6,702:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,941: Line 6,709:
|}
|}


=DEVICE=SIO.SYS=
==SPKRDD.SYS==
The Sio.sys driver is a replacement for the com.sys driver. The Sio.sys driver can support up to 16 COM ports.
The Speaker audio device driver provide support for playing digital audio waveform files on the standard PC speaker by using the MMPM/2 audio system. The speaker driver provides support for PCM waveform files that are (8-bit/16-bit, stereo/mono, 11Khz-44khz).
DEVICE=SPKRDD.SYS


  DEVICE=C:\Os2\Boot\Sio.sys <parameters>
BETTER DON'T USE IT, if you need (or want) sound on a regular base better buy one of those cheap soundcards.
 
* DEVICE=C:bslbootbslSio.Sys (Cn, An, In, Ig, Fc) :hp4. [(Cn, An, In, Ig, Fc)] :ehp4.
 
* CN
The number of the Com port or the string COM1 to COMn.
If you use a * in front of the Com port, then the port will be used as a PCMCIA Com port.
 
* AN
A hexnumber to define the I/O address of the Com port.
 
* IN
The IRQ number (0 to 15) or the string IRQ0 to IRQ15. If you don't use this parameter, SIO will search for a IRQ.
 
* IG
This exists only for compatibility with COM.SYS and is ignored by Sio.sys.  


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x
Line 6,968: Line 6,722:
!OS/2 4.0
!OS/2 4.0
!OS/2 4.5x
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
Line 6,979: Line 6,729:
|}
|}


==SPX.SYS==
Provides support for the Novell Netware SPX protocol.
DEVICE=C:\Netware\Spx.sys


=DEVICE=SIO2K.SYS=
'''Platform Support:'''
Excellent replacement driver for COM.SYS. If you utilise communications software on a regular basis at high speeds (e.g. 57,600), then the SIO drivers are the way to go.
{| class="wikitable"
 
|-
  DEVICE=SIO2K.SYS
 
'''NOTE:''' REM all other serial drivers like COM.SYS or SIO.SYS
 
The SIO2K set of drivers have some interesting new techniques and implementations.
 
'''Block input and output.''' If the UART is a FIFOed device, the interrupt service routines (there are several) always use block input and output instructions to read and write characters. During high communications activity, this means the 16550 interrupt routine is 5 to 10 times faster (possibly more) than previous implementations. UARTs with larger FIFOs will execute even faster. Now boys and girls, it is the interrupt service routines that are faster. Nothing on Earth can make your modem go faster than it is capable of. However, faster interrupt service routines means less processor overhead.
 
'''Automatic FIFO sizing.''' The SIO2K drivers now support 16650, 16550A, 16750, 16850 and 16950 uarts. However, knowing the chip type does not necessarily mean the FIFO size is know. For example, the 16654 is the equivalent of four (or more) 16650A UARTS on a single chip. The normal 16650 UARTs have a 32 byte FIFO, but the UARTS on the 16654 have 64 byte FIFOs. Only probing will determine this.
 
The first time a UART is touched by an application the SIO2K drivers automatically probe the size of the FIFO and the found size is used. Note that a UART with no FIFOs can be thought of as having a FIFO size of 1 byte. My thanks to Sam Detweiler, of IBM, for the idea of probing for FIFO size.
 
'''Automatic Crystal Frequency.''' Most UARTs are capable of bit rates to 921600bps or more. However, on most serial devices, the bit rate is limited to 115200bps by the crystal oscillator attached to the UART. Many boards, like those from Lava, offer bit rates greater than by using faster crystal oscillator. The down side is one must tell the driver to use a bit rate of 28800 to really get a bit rate of.
 
The first time a UART is touched by an app, the SIO2K drivers probe the UART to determine if it is using a standard crystal oscillator or not. If the frequency is not standard, then the SIO2K drivers automatically adjust so that a request of 115200bps yields an actual bit rate of 115200bps. In addition, the maximum bit rate is adjusted and reported to applications that request the maximum bit rate. Boards like the Blue Heat from CTI use a 12x crystal and its top bit rate is 1382.4kbps.
 
'''Minimum touch during boot.''' The SIO2K drivers do not touch the UART hardware during boot. This was very difficult to do, while maintaining a compatible OS/2 serial driver. The "no touch" practically eliminates the possibility of traps occurring during the boot process when they are difficult to deal with. This does mean that a lot of processing will occur the first time a port is opened.
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|}
 
=DEVICE=SIS900.OS2=
SIS 900/7016 PCI Fast Ethernet Adapter.
 
  DEVICE=SIS900.OS2
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|}
 
=DEVICE=SMC1208.OS2=
SMC EZ PCI COMBO Ethernet NIC.
 
  DEVICE=SMC1208.OS2
 
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
!eCS 1.x
!eCs 2.x
|-
|Yes
|Yes
|Yes
|Yes
|Yes
|Yes
|}
 
==SMC8000.OS2==
SMC Ethernet Adapter Family (SMC 8003, SMC 8013, SMC 8216, SMC 8416) NDIS driver.
DEVICE=SMC8000.OS2
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SMC9432.OS2==
Network driver for SMC9432/TX (EtherPower II) 10/100 PCI NIC.
DEVICE=SMC9432.OS2
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
 
==SMCND.OS2==
Acctron SMC 1211TX base 10/100 PCI ethernet card.
DEVICE=SMCND.OS2
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SMCPWR.OS2==
SMC EtherPower for OS/2. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/dec.zip.
DEVICE=SMCPWR.OS2
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SND16.SYS==
The Snd16.sys driver is used by the MAD16 soundcard.
DEVICE=C:\Os2\Boot\Snd16.sys <parameters>
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SND931.SYS==
OPTiSound 82C931 Sound Card Driver.
DEVICE=SND931.SYS
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SNDSCAPE.SYS==
Ensoniq Soundscape VIVO (SND-ENSVIVO) AD1848 Audio OS/2 Device Driver.
DEVICE=SNDSCAPE.SYS
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
===SOCKETS.SYS===
Network driver.
DEVICE=\Mptn\Potocol\Sockets.sys <parameter>
 
'''Parameters:'''
 
* /c:value
Number of the COM port to which debug information should be sent. Value may be any valid COM port number .
Default = 2
 
* /v
Display the banner at boot time.
 
* /uis:0
Turn off unique ID for select().
If this parameter is not set it defaults to ON .
 
* /mem:value
Number of 4kbyte clusters allocated at initialization time.
Value can be in the range from 30 to 32766 . Default = 75
 
* /gdt:value
The maximum number of 64kbyte blocks the stack can allocate.
Default = 80
 
 
'''TIP:''' According to IBM, the undocumented parameter /UIS:0 is for use on the 3172 Offload System to improve performance. This parameter is only intended for use on the 3172 Offload System, and turns off the process id : thread id processing on select() calls in the stack.
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SOCKETSK.SYS==
32bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak 13 for Warp 4.
Part of the TCP/IP Ver. 4.x firewall.
DEVICE=SOCKETSK.SYS <parameter>
 
'''Parameter:'''
 
* /V
Verbose, shows version-number
 
* /MEM:#
amount of 4KB Clusters. Standard = 75; valid Range = 30 - 32766
 
* /GDT:#
max. amount of 64KB Blocks the Stack can arrange; Standard = 80
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SOLO.SYS==
Driver for ESS SOLO 1 based soundcards or motherboards.
DEVICE=SOLO.SYS <parameter>
 
'''Parameter:'''
 
* /O:ENABLEWAVETABLE
If your installation includes an ES689 or ES692 WaveTable adding thid parameter to the config.sys line will cause the driver to use the wavetable as the primary midi.
 
* /R:n
(where n is in milliseconds and between 1 and 32) this parameter allows the user to over ride the default timer resolution (5ms). Increasing this value will cause te driver to get dispatched less often and so use less cpu time, however this can cause the tempo to drag. Decreasing this value below 5 will cause the driver to use more cpu time and can interfere with other timers.
 
The IBM Mixer IOCTLS fully implemented in the Solo driver and this driver can be controlled using IBM's Warp Mixer. Available as Warpmix.zip
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SPCIIRQ.SYS==
Change IRQ for PCI cards.
DEVICE=SPCIIRQ.SYS <parameter>
 
'''Parameter:'''
* 0..255
* 0..31
* 0..7
* 1..4 fr #A..#B
* 0..15
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SPKRDD.SYS==
The Speaker audio device driver provide support for playing digital audio waveform files on the standard PC speaker by using the MMPM/2 audio system. The speaker driver provides support for PCM waveform files that are (8-bit/16-bit, stereo/mono, 11Khz-44khz).
DEVICE=SPKRDD.SYS
 
BETTER DON'T USE IT, if you need (or want) sound on a regular base better buy one of those cheap soundcards.
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==SPX.SYS==
Provides support for the Novell Netware SPX protocol.
DEVICE=C:\Netware\Spx.sys
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 2.x
!OS/2 3.0
!OS/2 3.0
Line 7,389: Line 6,781:


'''Platform Support:'''
'''Platform Support:'''
{| class="wikitable" style="text-align:center" border="1"
{| class="wikitable"
|-
|-
!OS/2 2.x
!OS/2 2.x

Revision as of 14:20, 30 October 2016

Return to The Config.sys Documentation Project Main Page

Device Drivers are needed by OS/2 to work with your installed hardware.

The Device Drivers are loaded after the Base Device Drivers. Unlike them the Device Drivers are loaded in the order they appear in the CONFIG.SYS file.

The following pages describe these entries:

Chipset Support

PC Card/CardBus

Power Management

Network Adapters

NDIS MAC

Ethernet
Infrared
Token-Ring
VG AnyLAN
Wireless

ODI

Input Devices


Multimedia Devices

Audio Adapter

Misc

ADSMSDIS.SYS

Personally Safe'n'Sound tape backup driver that from Warp Server for e-Business

DEVICE=ADSMSDIS.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ADSMTAPE.SYS

Personally Safe'n'Sound tape backup driver that from Warp Server for e-Business.

DEVICE=ADSMTAPE.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No Yes

Protocol

AFINET.SYS

Part of the TCP/IP Protocol Drivers.

DEVICE=x:\MPTN\PROTOCOL\AFINET.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

AFINETK.SYS

32-bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak 13 for Warp 4 Part of the TCP/IP Ver. 4.x firewall

DEVICE=AFINETK.SYS

Parameter:

  • /V

Verbose, shows version-number

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No FP13 Yes

AFNB.SYS

Basic-NetBIOS-Socket-Support Driver.

DEVICE=AFNB.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

AFOS2.SYS

Part of the TCP/IP Protocol Drivers

DEVICE=C:\Mptn\Potocol\Afos2.sys 

Parameter:

  • /V

Verbose, shows version-number

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

Unsorted

AMOUSE.SYS

Mouse Driver for Wheel Mice. like e.g. the:

  • Logitech Pilot Mouse+
  • Logitech Mouse Man+
  • Logitech Optical Wheel Mouse
  • Microsoft Intellimouse
  • IBM Scrollpoint Mouse
  • Typhoon 40159
  • Trust 250S
DEVICE=AMOUSE.SYS

NOTE: With Amouse installed XFree86 refuses to work Available for FREE at http://home.t-online.de/home/klaus.breining/

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ANSI.SYS

This driver installs the ANSI support for DOS windows.

DEVICE=x:\OS2\MDOS\ANSI.SYS <parameters>

Parameters:

  • /X - Enables the redefinition of keys.
  • /K - Prevents the use of extended keyboards. Extended keyboards work as standard keyboards.
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

APPOINT.SYS

Pen for OS/2 Device Driver for Kurta PenMouse/APT Gliffic Plus.

DEVICE=APPOINT.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ARTPAD.SYS

Device Driver for Wacom Artpad used with Pen for OS/2

DEVICE=ARTPAD.SYS

IRQ=4 COMPORT=1 ADRESS=3F8 is used for Com1 IRQ=3 COMPORT=2 ADRESS=2F8 is used for Com2

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ARTZ.SYS

Pen for OS/2 Device Driver for Wacom UD-0608.

DEVICE=ARTZ.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASNPCI.OS2

AsanteFast 10/100 PCI Ethernet driver.

DEVICE=ASNPCI.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASP4CORE.SYS

Vortex AU8820 Core OS/2 driver.

DEVICE=ASP4CORE.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASP4JOY.SYS

Vortex AU8820 OS/2 Joystick driver.

DEVICE=ASP4JOY.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASP4OS2.SYS

Vortex AU8820 OS/2 MMPM/2 driver.

DEVICE=ASP4OS2.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASP4VDD.SYS

Vortex AU8820 Virtual DOS driver.

DEVICE=ASP4VDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASPIDRV.SYS

ASPI Driver supplied by Solution Technology Inc. (STI)

DEVICE=ASPIDRV.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASPIPFA.SYS

Device driver used to distinguish between IDE drives and SCSI drives when using Hard Disk Drive Monitor.

The Hard Disk Drive Monitor monitors the status of SMART-compatible harddisk drives in your computer. available as ftp://ftp.pc.ibm.com/pub/pccbbs/commercial_desktop/zp1t06a.exe

DEVICE=ASPIPFA.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASPIROUT.SYS

The interface of ASPI Router merely is an extension of the interface of OS2ASPI.DMD needed e.g. by the free CDRecord/2 from Chris Wohlgemuth available at: http://www.geocities.com/SiliconValley/Sector/5785/ and SANE (Scanner Access Now Easy) from Yuri Dario available at http://www.geocities.com/SiliconValley/Peaks/4320.

DEVICE=ASPIROUT.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ASPITAPE.SYS

GTAK Driver for SCSI tape access by GTAR scsitape.dmd and scsitape.sys also belong to the package By Andreas Kaiser Andreas.Kaiser@stuttgart.netsurf.de, gtak258.zip gtar258.zip.

DEVICE=ASPITAPE.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ATALK.SYS

Appletalk driver from IBM LAN Server for Macintosh

DEVICE=ATALK.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

ATI0.sys

Used by ATI 3D Rage graphic adapter cards.

DEVICE=x:\OS2\ATI0.sys 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ATIM64.SYS

Used by ATI 3D Rage graphic adapter cards.

DEVICE=x:\OS2\ATIM64.SYS 
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ATKP.SYS

Appletalk PAP Port driver from IBM LAN Server for Macintosh.

DEVICE=ATKP.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes*

AUDIOVDD.SYS

This is the standard VDD for audio device drivers that prevents DOS sessions from accessing the audio hardware when an OS/2 session is using it and vice versa. The driver comes with OS/2 and is used by a lot of diferent soundcards.

DEVICE=C:\MMOS2\AUDIOVDD.SYS

Parameter:

  • PAS161$ for the MediaVision's ProAudio Spectrum Soundcard
  • SBAUD1$ for the Sound Blaster 16 sound card

NOTE: the parameter is the link between the OS2 driver and the DOS driver. The DOS driver inherits it's settings associated with the parameter

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


BT32.SYS

Radio/TV driver for BT878 based Cards

DEVICE=BT32.SYS

Parameters:

  • /V - Verbose: Show Copyright information
  • /VM - Verbose modules: Like /V plus module list
  • /3 - Execute an INT3 at initialisation (Use kernel debugger!)
  • /NOMODULE - Don't load modules at system startup (Use BT32CFG.EXE to load/unload)
  • /NOCOREMODULE - Don't load core modules at system startup (Use BT32CFG.EXE to load/unload)
  • /MODPARM: - Support Linux insmod parameters for various modules
  • /LOADMODULE: - Load module (only with parameter /NOCOREMODULE)
  • /NOIRQ - Disable IRQ for BTTV. This is for test purposes only when the driver traps at startup

NOTE: BT32.SYS must reside after LXAPI32.SYS.

NOTE: BT32.SYS contains the following modules:

  • bttv
  • tvaudio
  • tuner
  • msp3400
  • tda7432
  • tda9875

NOTE: Module parameters: BT32.SYS contains a lot of module parameters. See documentation in the DOC directory of the package. Most important paramers are:

  • bttv card=n Specify a specific BTTV card.
  • tuner=n Specify a specific BTTV tuner.

Valid numbers for n for both parameters are listed in DOC\CARDLIST

See DOC\Insmod-options for all other parameters.

NOTE: If you are using wcast.sys also there may be problems to use the bttv driver after an application has used wcast.sys. (Attention: Multimedia Setup also opens wcast.sys!!!) Known results are: No picture, No sound or both.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


BUSAUDIO.SYS

C-Media CMI 8330 Soundcard driver (AD 8329 Chip).

DEVICE=BUSAUDIO.SYS

Parameters:

  • /D:n - DMA channel, n=0,1 or 3
  • /I:n - Interrupt, n=5,7,9,10,11 or 12
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CCSINIT.SYS

ChipChat Sound Initializer - only needed with Warp 4

DEVICE=CCSINIT.SYS

The ChipChat is one of the rare available Soundcards for the microchannel, it is based on the ESS1688. For more information see: http://www.ChipChat.com

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CD1400.SYS

RISC COM CD1400 Device driver by DECISION-COMPUTER INTERNATIONAL Co.,LTD

DEVICE=CD1400.SYS

Parameter:

  • /Mxxxx

card memory address

  • /Ixx

IRQ Nø

  • /Cxx

Assign the port number of the first port on the card ( COM1 to COM96 )

NOTE: The driver will autodetect the number of communication ports on the card ( 4 or 8 ports ).

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CDBASPI.SYS

CD-TEK driver to access easily the PIONEER DRM-1804X autochange CD-ROM device.

DEVICE=CDBASPI.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CDMGRDRV.SYS

Driver of the FREE CD-Rom Manager for Plextor SCSI CD-ROM drives. Developed by Markus and Christian Mueller.

DEVICE=CDMGRDRV.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

CLEANUP.SYS

This is a simple device driver that DELETES the specified file. Wild cards are NOT supported. To delete multiple files, add multiple times to config.sys. Part of the Graham Utilities 2.X available at http://www.warpspeed.com.au/graham.htm

DEVICE=CLEANUP.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CLICHOS2.SYS

Crystal Semiconductor CS4299 AC97 Audio Driver (to be found e.g. on IBM T23 Thinkpad) This chip doesn't support Midi, you need Timidity to geht Midi working.

DEVICE=CLICHOS2.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CMPCI16.SYS

C-Media CMI8738 OS/2 Audio Driver ported from Linux sources, based on the SBLive project.

DEVICE=CMPCI16.SYS

Parameter:

  • /V

verbose (prints copyrights during driver init)

  • /C

enable CD audio input

  • /M

enable microphone audio input

  • /L

enable linein audio input

  • /A

enable auxin audioinput (since ver. 0.13)

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CMPCI32.SYS

C-Media CMI8738 OS/2 Audio Driver

DEVICE=CMPCI32.SYS

Parameter:

  • /V:

verbose (prints copyrights during driver init)

  • /D:

print start and end address of code (useful to locate the code that causes a trap (CS:EIP in trapscreen))

  • /R:

use linein jack to output rear channels

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

COM.SYS

This driver is required for serial communications.

DEVICE=C:\OS2\Boot\COM.SYS <parameters>

TIP: below. This line MUST appear after any driver that uses a communications port. Older versions of COM.SYS are limited to 57600 Baud, newer ones (e.g. delivered with Warp 4) are able to do 115200 Baud. Beginning with build 10.042 PCI Add-On cards with implemented software interrupt sharing are supported too, beginning with build 10.052 there are 16 com ports available and beginning with build 10.068 Combo Cards are supported.

TIP: There are two very good replacement drivers called SIO.SYS\VSIO.SYS.

TIP: To add support for COM3 and COM4 at location 3E8 with IRQ 4 and 2E8 with IRQ 3 respectively, add (3,3E8,4) (4,2E8,3) to the DEVICE line, e.g.

DEVICE=drive:\OS2\COM.SYS (3,3E8,4) (4,2E8,3)

You can also use this method to change a COM ports assigned IRQ. The normal address for COM1 is 3F8 and IRQ 4, for COM2 2F8 and IRQ3.

TIP: With ThinkPads should the address be added. e.g:

DEVICE=drive:\OS2\BOOT\COM.SYS (1,3F8,4) (2,2F8,3)

Parameter:

  • /V

Verbose (since 10.052)

  • /W

Wait verbose mode (since 10.052). Displaying pauses with a "Press Enter to continue..." message.

  • /F

Find COM ports on PCI combo (serial/parallel) cards automatically (since 10.068).

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

COM02.SYS

For IBM PS/2 model 90 & 95 only. Lets you use the communications ports COM1 and COM2. See DEVICE COM.SYS.

DEVICE=COM02.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CONCERTO.SYS

Pen for OS/2 Device Driver for Compaq Concerto.

DEVICE=CONCERTO.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CPPVDD.SYS

PU Monitor Plus Virtual DOS Driver.

DEVICE=CPPVDD.SYS

TIP: By Daryl Sperber: CPUMONP was last updated in 1996 (for FP17 of Warp connect) and has worked just fine for Warp 3 and Warp 4 all this time. However it obviously now has a fatal incompatibility with FP14 of Warp 4 that is causing the Trap 000e for me.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CT5880.SYS

Creative Lab Ensoniq CT5880 PCI Audio Device Driver.

DEVICE=CT5880.SYS

NOTE: No MIDI support, no WIN/OS2 support.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWAUDIO.SYS

Sound Drivers for the Crystal CS4231, 4232 (A, B), 4235, 4236 (B, D, E), 4237B, 4238B, 4239.

DEVICE=CWAUDIO.SYS

NOTE: for 4231, 4232 and 4236 use 'Mode2' driver version (latest 1.7)

TIP: If you have problems with the Yamaha OPL3-SAx chipset: According to a user, instead of using the Yamaha OPL-3 SAx drivers for the same audio chipset, using the driver for Crystal CS4232 works fine without any limitations.

A FREE mixer for the crystal cards is LBCSMix V1.0 from http://freebyte.ml.org/~boga/OS2Programs.html

Parameter for 'mode3' drivers:

  • /N:

Name of PDD BSAUD1$ (Supplied by install)

  • /V

Verbose Display

  • /X1:

AUX1 unmute/gain 0..100 (decimal) (*50) (usually "Line-In")

  • /X2:

AUX2 unmute/gain 0..100 (decimal) (*50) (usually CD-ROM)

  • /L:

LINE unmute/gain 0..100 (decimal) (*100)(FM volume)

  • /LCAPT:

Line-In record source X1, X2, *X1X2, L (X1X2 is mixed aux1+aux2)

  • /T:

Inactivity power down 1..5 minutes (*1)

  • /MBY:<0,1>

Mono bypass *1 (mono-in connected to mono-out)

  • /MIM:<0,1>

Mono input mute *1 (mono-in not connected to input mixer)

  • /MOM:<0,1>

Mono out mute *0 (audible)

  • /XCTRL0:<0,1>

XCTRL0 Pin set System specific. Sometimes used to

  • /XCTRL1:<0,1>

XCTRL1 Pin set control power to amplifier. On IBM Aptiva with Bose speakers, set both to 1

  • /P:

Codec Port *534, 608, (530..FF8, divisible by 4)

  • /I:

Codec IRQ *5, 7, 9, 11, 15 (decimal)

  • /D:

Codec DMA 0, 1, 3 (Default 1,0)

  • /C:

Control Port 120, *538, (120..FF8, divisible by 8)

  • /J:

Joystick Port *200, 208, NONE

  • /S:

Sound Blaster Port *220, 240, 260, 280, NONE

  • /M:

MPU Port and IRQ *330, NONE, (300..3E0, divisible by 8) IRQ: 7, 9, 11, 12, 15, *NONE

  • /F:

FM synth port *388, NONE, (388..3F8, divisible by 8)

  • /IRQRate:dd

Target interrupt rate *32 Range: 1..64 interrupts per second

  • /DMASize:nnnn

DMA Buf size maximum *8192 Range: 256..16384 (2 IRQs/Buffer)

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWGUTIL.SYS

Crystal DSP manager utility device driver.

DEVICE=CWGUTIL.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWMPU401.SYS

Crystal MPU401 driver for a complete discription see MPU401.SYS.

DEVICE=CWMPU401.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWVAUDIO.SYS

Virtual DOS driver for Crystal Soundcards

DEVICE=<drive>:\MMOS2\CWVAUDIO.SYS BSAUD1$

Parameter:

  • /S

The CWVAUDIO.SYS driver will automatically set a 'BLASTER' DOS environment variable to the proper audio hardware settings. This is done by adding a '@SET BLASTER=' line to the beginning of all DOS session's autoexec file. This file is specified in DOS session's DOS_AUTOEXEC property. The /S option for CWVAUDIO.SYS will skip the automatic setting of this environment variable.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWVOPL3.SYS

Crystal Midi FM Virtual Dos Driver.

DEVICE=CWVOPL3.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWWINPDD.SYS

Crystal WinOS2 Audio PDD.

DEVICE=CWWINPDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

CWWINVDD.SYS

Crystal VDD supporting WinOS2 audio DRV.

DEVICE=CWWINVDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DC21X4.OS2

Digital Semiconductor DC21X4-based Ethernet Adapter Network driver.

DEVICE=DC21X4.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DCF2CDE.SYS

This driver is used by the DCF/2 disk compression program.

DEVICE=C:\Dcf2\DCF2CDE.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DCF2PDD.SYS

This driver is used by the DCF/2 disk compression program.

DEVICE=C:\Dcf2\DCF2PDD.SYS <parameter>
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DCF2MGR.SYS

This driver is used by the DCF/2 disk compression program.

DEVICE=C:\Dcf2\DCF2MGR.SYS <parameter>
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DCF77.SYS

Driver for DCF77-Radiocontrol Watch. Available for FREE at http://www.prog-link.com

DEVICE=DCF77.SYS

Parameter:

  • /P:Port

Port, 201 (Gameport), 379 (LPT1), 279 (LPT2), 3BD (LPT3), 3F8 (COM1), 2F8 (COM2), 3E8 (COM3), 2E8 (COM4)

  • /IRQ=nn (or /I:nn)

Interrupt, 3, 4, 5, 7, 9, 10, 11, 12, 15 or NONE. With NONE Polling-Mode is used

  • /V

Verbose

  • /Q

Quiet, disables displaying informations during start

NOTE: For a complete list of parameters see the documentation deliverd with the driver.

DDE4EXTRA.SYS

Is used by the IBM C Set++ Compiler.

DEVICE=C:\User\Cset21\DDE4EXTRA.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DE528.OS2

D-Link 528CT Ethernet Adapter Network driver.

DEVICE=DE528.OS2

NOTE: It is impossible with this driver to execute graphical apps using Exceed.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DELAY.SYS

Device driver for providing a timed delay during system startup avaliable for FREE at http://www.tavi.co.uk/os2pages/delay.html

DEVICE=DELAY.SYS <parameters>

Parameter:

  • /K /k,

-K and -k are equivalent. exits the delay period immediately by pressing any key (apart shift, ctrl, alt etc.)

  • mm:ss

is the intended delay in minutes and seconds. message is an optional message that will appear during the delay period.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes Yes Yes

DES.SYS

This is the current national standard encryption protocol (US) used in triple DES encryption with 128-bit key. It is currently being replaced by a new, but yet not chosen protocol. Use to encrypt user data by the VPN service.

DEVICE=DES.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DFE650.OS2

D-Link DFE-650 Fast Ethernet PC Card. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.

DEVICE=DFE650.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DISKFIT.SYS

Driver for the fault tolerance system. See OS/2 manual for more information.

  DEVICE=DISKFIT.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes Yes Yes


DM9PCI.OS2

DAVICOM DM9 PCI Series Fast Ethernet Adapter (e.g., on the SiS530 motherboard). http://www.davicom.com.tw

DEVICE=DM9PCI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DOS.SYS

Is needed if you want to run DOS or Windows applications.

DEVICE=C:\OS2\BOOT\DOS.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DP820A.SYS

National Semiconductor DP83820 Another NDIS 2.0.1 MAC driver.

DEVICE=DP820A.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DP83815.OS2

National Semiconductor DP83815 10/100 MacPhyter3v PCI Adapter.

DEVICE=DP83815.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DPROM01.SYS

This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.

Examples:

DEVICE=X:\XPROSYS\EXE\DPROM01.SYS MAXSPEED=9600

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

DRVOCDB.SYS

Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.

DEVICE=DRVOCDB.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DRVOPPQT.SYS

Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.

DEVICE=DRVOPPQT.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DRVOQ117.SYS

Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0.

DEVICE=DRVOQ117.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DTA.SYS

Data Transport Agent (DTA) Driver for eComStation. It is meant to improve the ability to handle datastreams in eCS, DOS and Win-OS/2 sessions. In addition it will enable virtual DOS sessions to play sound via a generic sounddriver, effectively bypassing the need for soundcard specific DOS drivers.

DEVICE=DTA.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes

DTSXPC01.SYS

This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage. This is the TSXPC01 driver.

Examples:

 DEVICE=X:\XPROSYS\EXE\DTSXPC01.SYS MAXSPEED=19200
 DEVICE=X:\XPROSYS\EXE\DTSXPC01.SYS COM=COM2 MAXSPEED=19200
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

DUNTLW01.SYS

This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage. This is the UNTLW01 driver.

Examples: Ver 5.6 (MINI X-TEL)

DEVICE=X:\XPROSYS\EXE\DUNTLW01.SYS COM=COM1 SPEED=9600 BASE=1 NBR=2 DNS=0 TIMEOUT=0 PARITY=O NB_BIT=8 NBSTOP=1 

Ver 6.0

DEVICE=X:\XPROSYS\EXE\DUNTLW01.SYS PROFILE=D:\XPROSYS\EXE\DUNTLW.001
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

E1000.OS2

Intel 8254X Based Network Connection Gigabit Ethernet driver.

DEVICE=E1000.OS2

Platform Support:

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

E100B.OS2

Intel EtherExpress PRO Adapter, Intel InBusiness Ethernet Adapter.

DEVICE=E100B.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

E10P.OS2

Intel EtherExpress PRO/10 PCI LAN Adapter.

DEVICE=E10P.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

E21ND.OS2

Cabletron E21 Ethernet Adapter.

DEVICE=E21ND.OS2

Platform Support:

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

E22ND.OS2

Cabletron E22 Ethernet Adapter (SNMP).

DEVICE=E22ND.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EC2T.OS2

Linksys Combo PCMCIA EthernetCard (EC2T). NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.

DEVICE=EC2T.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ECRDRV.SYS

Provides support for Remote Support for OS/2. Remote Support can be found in the BonusPak and allows IBM Support Centers to log onto your OS/2 Warp 4 workstation.

DEVICE=C:\Bonuspak\RS231B\Ecrdrv.sys 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EL59X.OS2

3Com Fast EtherLink & EtherLink III Bus Master Family Network driver.

DEVICE=EL59X.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EL90X.OS2

3Com Fast EtherLink/EtherLink XL Family Network driver (e.g. 900 A/B).

DEVICE=EL90X.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ELNK3.OS2

3Com Etherlink III Adapter.

DEVICE=ELNK3.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ELPC3.OS2

3Com 3C589 EtherLink III PC Card OS/2 driver.

DEVICE=ELPC3.OS2

TIP: The driver traps on system with more than 500MHz clock rates. To solve the problem get 3c589patch.zip to patch the driver. It includes also a ptach to get the 3net_log utility to work with the drivers V. 1.8.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ELPC3X.OS2

3Com EtherLink III LAN+Modem PC Card for OS2 V1.5 - Card Services driver.

DEVICE=ELPC3X.OS2

TIP: If you own a 3COM 3C562D add this setting to your config.sys may get your card working:

BASEDEV=RESERVE.SYS /MEM:CB00,1000.
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ELSA.SYS

Card specific part of GRADD display driver and settings for ELSA WINNER 2000/Office.

DEVICE=ELSA.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No * Yes Yes

EMI.SYS

Pen for OS/2 Mouse Emulation driver.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EN5251.OS2

Accton EN5251 Based Fast Ethernet Adapter.

DEVICE=EN5251.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ENDS2ISA.OS2

Crystal LAN CS8900/CS8920 Ethernet Adapter.

DEVICE=ENDS2ISA.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EP325.OS2

OS/2 NDIS SURECOM EP-325 PCI Ethernet Adapter (based on Realtek RTL8029).

DEVICE=EP325.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EP427.OS2

SureCom EtherPerfect-427 PCMCIA Ethernet Card.

DEVICE=EP427.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EQNKRCSH.EXE

Driver by Netfinity* Version 5.20.3.

DEVICE=EQNKRCSH.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EQNKVKBD.SYS

Driver by Netfinity* Version 5.20.3.

DEVICE=EQNKVKBD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EQNRCSH.EXE

Part of DCAF (Distributed Console Access Facility).

DEVICE=EQNRCSH.EXE

ATTENTION: If you don't have the IBM Internal Y2K fix it won't work after 31.12.1999.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EQNVKBD.SYS

Part of DCAF (Distributed Console Access Facility).

DEVICE=EQNVKBD.SYS

ATTENTION: See also DEVICE EQNRCSH.EXE

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ES1371.SYS

PCI Ensoniq ES1371 Audio Device Driver without Win-OS/2 and Midi support.

DEVICE=ES1371.SYS

Note: Some users report that the Soundblaster PCI 128 works with this driver. According to the Linux ALSA Project (open-source sound drivers) the ES1371 is built into the PCI 64 and PCI 128. But to complicate things there could also ES1370 chips on the boards

There are enhanced drivers (From os2 DDK pciaudio driver sources) with support for ct5880(a,c,d), ev1938(a) based cards developed as a part of Russian Team OS/2 ( OS2.Ru ) projects.

See: http://OS2.Ru/index.phtml.en

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ES1688DD.SYS

Sounddriver for the ESS1688. A FREE mixer for this Soundchip is ESSMIX13.ZIP by Oleg Deribas (older@iname.com).

DEVICE=ES1688DD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ES1868DD.SYS

Sounddriver for the ESS1868pnp (many soundcards). A FREE Mixer for this soundcard is MINIMIX2.ZIP by Marco G. Salvagno (mgs@whiz.cjb.net) http://whiz.cjb.net.

DEVICE=ES1868DD.SYS

Platform Support:

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ES1869DD.SYS

Driver for the ESS 1869 soundchip.

DEVICE=ES1869DD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ES198X.SYS

ESS Allegro-1/Maestro-3 PCI Audio Device Driver.

DEVICE=ES198X.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ESP.SYS

Ray Gwinn's Hayes ESP device driver.

DEVICE=ESP.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ET32ND.OS2

KTI Networks Inc. base 10 t/tx PCI combo ethernet card.

DEVICE=ET32ND.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ET32ND.SYS

Driver for KTI Networks System ethernet card.

DEVICE=ET32ND.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ETHPCI.OS2

Acton EN1207 Ethernet Card.

DEVICE=ETHPCI.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EXCPHEAD.SYS

New with eCS 1.1. This works around a condition in DOSCALL1 when the exception handlers have not yet been initialized during boot, and a failing driver causes a trap. EXCPHEAD.SYS should be loaded before other DEVICE= or IFS= lines in CONFIG.SYS to properly terminate the chain of exception handlers for DOSCALL1.

This may not be necessary for the 14.104a kernel or above.

DEVICE=EXCPHEAD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
eCS

EXMOUSE2.SYS

Kensington mouse driver for OS/2.

DEVICE=EXMOUSE2.SYS

NOTE: Doesn't work together with the Scitech Display driver

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EXP16.OS2

Intel EtherExpress 16 Family Adapter Network driver.

DEVICE=EXP16.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

EXTDSKDD.SYS

EXTDSKDD.SYS supports external disk drives. See your online Command Reference for complete details.

DEVICE=EXTDSKDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FASTNIC.OS2

PCI 10/100 Fast Ethernet Adapter (AN981), PCI 10/100 Fast Ethernet Adapter (AN983), PCI 10/100 Fast Ethernet Adapter (DEC21140), PCI 10/100 Fast Ethernet Adapter (DEC21143) Network Driver. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/amdtek.zip.

DEVICE=FASTNIC.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FETND.OS2

PCI Fast Ethernet 10M/100M Adapter. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/via.zip.

DEVICE=FETND.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FIREBIRD.SYS

Enables the programming of the Gravis Firebird and Thunderbird Joysticks under DOS.

DEVICE=FIREBIRD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FIOAUXDD.SYS

Device Driver file that contains the device driver that supports mouse port (auxiliary) attachment of both the 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader. [1]

DEVICE=FIOAUXDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Unknown Unknown Unknown

FIOSERDD.SYS

Device Driver for supports serial attachment of both the 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader. ftp://public.dhe.ibm.com/4700/fiodd/docs/77os2prg.pdf]

DEVICE=FIOSERDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Unknown Unknown Unknown

FLSH2MTD.SYS

PCMCIA Storage Driver for OS/2 (FLASH MTD).

DEVICE=FLSH2MTD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FMD.SYS

Driver required by Faxworks lite 2.* in Warp 3 or the Pro Versions of Faxworks/PMFax.

DEVICE=FMD.SYS

Parameter:

  • L = disable logo on error free boot
  • T = do port tests (default)
  • N = no port tests, assume ports exist (PCMCIA default)
  • S = allow interrupt sharing (MCA bus only)
  • A = get ABIOS LID on port open (MCA bus only)
  • c = COM number (1-48)
  • h = I/O port address (in hex)
  • i = interrupt number

(defaults are for the standard COM ports)

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FMRADIO.SYS

Driver for the FREE PMRADIO by Paul Ratcliffe. OS/2 PM application for driving the Reveal RA300 FM radio card and the old version of the AIMS Labs. RadioTrack card.

DEVICE=FMRADIO.SYS <parameters>

Parameter:

  • /P:port

port is the RA300 port address (in hex.). The port addresses supported are 30F and 20F. The /P parameter is optional and if not supplied, will default to address 30F.

The port address must match that which you have configured on the card itself using jumper JP1. The device driver is Resource Manager compliant and will not install if some other device has already claimed the ports (the hardware actually consumes 4 ports: 30C-30F or 20C-20F).

  • /V

It may be specified if you don't wish the device driver to turn the radio volume down when shutting down OS/2.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FWIP.SYS

Used by the Firewall built into TCP/IP 4.1 and above. This driver adds IP packet filtering to the Firewall.

DEVICE=C:\Mptn\Potocol\Fwip.sys 

IP Packet Filter Driver. This component of the VPN security system manages the firewall packet fileter and address translation service. Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall

For configuring the Firewall get the FREE ServerConfig Which can be found at: http://www.ecs.soton.ac.uk/~dm898/soft.html a GUI config util for Apache 1.3.9, InetPowerServer/2 0.85 and the IBM OS/2 TCP/IP Firewall. Author: SEHH (sehh@altered.com)

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

FXWRAP.SYS

NDIS wrapper for the InJoy Firewall for OS/2 from: http://www.fx.dk/firewall

DEVICE=FXWRAP.SYS

Designed with Cable Modems and LAN-2-LAN connections in mind, the InJoy Firewall is a complete Internet Gateway, Firewall and IPSec VPN gateway/client in one. FEATURES: IPSec; PPPoE; Superior performance NDIS Protocol Engine; RFC 1631-NAT support; Direct Internet Access for your LAN PC's; Packet Filtering; Traffic Accounting, Port Redirection; Rule Based Access Control; Identd support; No reconfiguration of software; Great step-by-step docs; YK2; PM & text GUI; DHCP support; On-the-fly updates.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

GAMEDD.SYS

It is used by many Soundcards. It gives support for the Joystick connector for OS/2 programs.

DEVICE=C:\MMOS2\GAMEDD.sys 

The following joysticks are supported by this driver:

  • Advance Gravis Analog Joystick
  • Advance Gravis GamePad
  • Advance Gravis Analog Pro
  • CH Products Flightstick
  • Dexxa Joystick ( Infrared )
  • Kraft Thunderstick
  • Logitech WingMan Extreme
  • Logitech Wingman
  • Thrustmaster XL Action Controller

There is also an Enhanced Joystick driver by Vesa J„„skel„inen who supports the following joysticks:

  • Generic 4 axis and 4 button joystick
  • Gravis GamePad Pro (in GrIP mode)
  • CH FlightStick Pro
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

GAMEPRT2.SYS

Joystick interface driver. By Jose DaSilva silva@dowco.com.

DEVICE=GAMEPRT2.SYS <parameter>

Parameter:

  • /VB - displays the gameport header at startup.
  • /P:hhhh - Is the joystick port (hhhh=hex address of port)
  • /W:hhhh - Is the wait run-a-way counter (hhhh=waiting time).

NOTE: This driver is incompatible with the original IBM GAMEDD.SYS. You must use GAMEDD.SYS from the same author.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

GAMEVDD.SYS

It is used by many Soundcards. It gives support for the Joystick connector for Dos and Windows programs.

DEVICE=C:\MMOS2\GAMEVDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

GENSCSI.SYS

Generic SCSI device driver. The basic function of GENSCSI.SYS is to provide applications with an interface to OS2SCSI.DMD. It only answers 4 commands: Open, Close, IOCtl, and Init. All others cause an Invalid Command error. GENSCSI accepts IOCtl commands in the same format that OS2SCSI does, except GENSCSI expects all addresses to be ring 3 addresses while OS2SCSI expects them to be ring 0 addresses, physical addresses or scatter/gather lists. GENSCSI will convert the ring 3 addresses to the proper form and pass the command on to OS2SCSI. When OS2SCSI is done with the command, it returns the results back to GENSCSI who passes it back to the application. Developed by Dennis Rowe available for free as part of scsipg.zip.

DEVICE=GENSCSI.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

GPH2USB.SYS

USB driver for GPhoto2

DEVICE=GPH2USB.SYS

NOTE: With this driver installed accessing your camera using the USBMSD.ADD or CWUSBMSD.ADD drivers doesn't work.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

GRADD.SYS

Graphic card driver.

DEVICE=C:\OS2\Boot\GRADD.SYS 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

GRAHPIRE.SYS

WACOM Graphire Tablet device dependant OS/2 driver (serial model). It supports both Graphire Pen & Mouse and emulates usual 3-button serial mouse.

DEVICE=GRAHPIRE.SYS <parameters>

Parameter:

  • SERIAL=COMn

Specifies the COM Port, COM1 is used by default

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

GWDTA.SYS

Generic Winos2 audio driver. Works under DOS for Winos2 sessions. http://home.wanadoo.nl/~rwklein/

DEVICE=GWDTA.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

HRTIMER.SYS

HRTIMER.SYS is a high resolution timer implemented as a device driver. Shows more accurate reading of e.g. the CPU-Meter in Memsize.

DEVICE=HRTIMER.SYS

NOTE: Do not run any Windows session while using HRTIMER.SYS otherwise the output is either much too high or much too low. HRTimer (all versions) requires he time slice be less than 55 milliseconds. This should be the case in all unaltered environments. If you choose to increase the TIMESLICE setting in the CONFIG.SYS you may not be able to use HRTimer (readout too low).

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

I2OLOSM.OS2

IBM I2O Token Ring LAN Driver

DEVICE=I2OLOSM.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IAS_DD.OS2

OS/2 IrDA IAS Driver Copyright (C) IBM Corp. These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 770, 770E, 770ED, 770X. They do NOT work on the 560.

The IRCOMM.SYS driver make it possible to assign a virtual COM port to your Infrared attached IrCOMM device (Cellular phone, etc.). You can then use any COM port aware application package to access the device like through a normal COM port, i.e. issue AT commands to a modem, etc.

Communication Applications tested with this release are:

  • InJoy IP Dialer V2.3
  • Opalis BTX decoder (German online service)

IrCOMM also supports printing via the infrared port. Just install the right printer driver, then point it to the COM port IrCOMM is using. For Win-OS/2 printing, you can select the same COM port as you Win-OS/2 printer port.

Printers tested so far:

  • HP LaserJet 6MP
  • HP DeskJet 340

Whenever the IRCOMM driver detects a device, you will see the red indicator come on and tell you there's an active connection.

DEVICE=IAS_DD.OS2 <parameter>

Parameter:

  • /L - Legacy mode support.
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

IBG_DATI.DRV

Sytos Plus driver for the IBM 2.0G 4mm Tape.

DEVICE=IBG_DATI.DRV
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBM360P.SYS

Pen for OS/2 Device Driver for IBM360P.

DEVICE=IBM360P.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBM730T.SYS

Pen for OS/2 Device Driver for IBM730T.

DEVICE=IBM730T.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBM750P.SYS

Pen for OS/2 Device Driver for IBM750P.

DEVICE=IBM750P.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMCOMO.SYS

Device driver for the IBM Advanced System Mangement service processor hardware.

DEVICE=IBMCOMO.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMCSFLK.SYS

Driver from Corrective Service Facility (CSF) necessary to exchange locked files. Normally this driver should only appear during the reboot after applying a fixpak. If you have this driver installed installation/exchange of locked files may have failed.

DEVICE=IBMCSFLK.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMFE.OS2

IBM 10/100 EtherJet PCI Adapter.

DEVICE=IBMFE.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMLANLK.SYS

Driver necessary to exchange locked files. Normally this driver should only appear during the reboot. So if you see it installation/exchange of locked files may have failed.

DEVICE=IBMLANLK.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMSPO.SYS

Device driver for the IBM Advanced System Mangement service processor hardware.

DEVICE=IBMSPO.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMTOK.OS2

Network adapter driver for IBM Token-Ring cards.

DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMTOKCS.OS2

IBM Turbo 16/4 Token-Ring PC Card.

DEVICE=IBMTOKCS.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IBMTRP.OS2

IBM Token-Ring PCI adapter card.

DEVICE=IBMTRP.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ICHCSND.SYS

Analog Devices SoundMax Integrated Digital Audio AD188x/198x OS/2 driver for Intel 82801AA/AB/BA/CA/DB/EB and NVidia MCP2/CK8 chipsets.

DEVICE=ICHCSND.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
- Yes Yes Yes

ICHCVDD.SYS

AD18xx/19xx virtual DOS driver for Intel 82801AA/AB/BA/CA/DB/EB and NVidia MCP2/CK8 chipset.

DEVICE=ICHCVDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ICHSND.SYS

Analog Devices SoundMax Integrated Digital Audio AD18xx for Intel 82801AA/AB chipsets.

DEVICE=ICHSND.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ICHVDD.SYS

AD1881 virtual DOS driver for Intel 82801AA/AB chipset.

DEVICE=ICHVDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
- Yes Yes Yes

IDEHDD.SYS

MULTIPORT/Kingbyte Parallel Port hard disk drive device driver. http://www.multiport.de http://www.kingbyte.com

DEVICE=IDEHDD.SYS

Parameter:

  • /Sn

Set the starting search port access speed level for printer port. If this parameter is not specified, driver will try from the fastest speed level 0, and then level 1, level 2 until level 9 automatically, n must be 0 ~ 9. Default value is 0 (the fastest level).

  • /Zn

n is a byte-length value bit1 = 1, suppress bi-direction mode = 0, not suppress bi-direction mode (default) bit2 = 1, suppress uni-direction emulation mode= 0, not suppress uni-direction emulation mode (default) bit3 = 1, suppress epp emulation mode = 0, not suppress epp emulation mode (default)

Ex: /Z8 --> suppress EPP mode
Ex: /Z10 --> suppress EPP & bi-direction mode
Ex: /Z14 --> suppress EPP & bi-direction & uni-direction mode
  • /!E

Suppress 528MB larger enhanced IDE support Default the driver will use the LBA mode to support 528MB larger enhanced IDE.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IFNDIS.SYS

Network protocol driver. Used by TCP/IP.

DEVICE=\MPTN\PROTOCOL\IFNDIS.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IFNDISNL.SYS

TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2.00 IFNDIS Null Driver from the Warp 3 Internet Access Kit.

DEVICE=IFNDISNL.SYS

TIP: To get PPP (Point-to-Point Protocol) download ftp://ftp.ibm.net/pub/PPP/PPP.ZIP

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

INET.SYS

TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2 from the Warp 3 Internet Access Kit.

DEVICE=INET.SYS

TIP: For PPP see also DEVICE IFNDISNL.SYS.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

INIT931.SYS

OPTi 82C931 Init Device Driver.

DEVICE=INIT931.SYS

Parameter:

NOTE: Only valid for Warp3, Warp4 uses the PnP Ressource Manager.

MODE: wss, sb (default Windows Sound System)

  • BASE: 220, 240 (for Sound Blaster mode, default 220) 534, E84, F44, 608 (for Windows Sound System mode, default 534)
  • CDTYPE: None, IDE (default None) One character is adequate (e.g. CDTYPE:N CDTYPE:I)
  • CDBASE: None, 376 IDE - 376 (fixed)
  • CDIRQ: None, 15 IDE - 15 (fixed)
  • SBIRQ: 5, 7, 10, 11 (default 7)
  • SBDMA: 1, 2, 3 (default 1)
  • SSIRQ: 7, 9, 10, 11
  • WSSDMA: 0, 1, 3 (default 1)

NOTE: The WSS IRQ and DMA are specified here. The audio PDD will query INIT931.SYS to learn of the device settings.

  • GAMEPORT: 0,200,201,202,203,204,205,206,207 (0 disabled)

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


IPSEC.SYS

Used by the Firewall built into TCP/IP 4.1 and above. This driver adds IPSEC security to the Firewall. This driver is the protocol driver for controlling VPN between two or more systems. It starts the key exchange and negotiation of protocols to be used. It then manages the exchange using the agreed items.

DEVICE=C:\MPTN\PROTOCOL\IPSEC.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
- Yes Yes Yes

IPX.SYS

Gives support for the Novell Netware IPX protocol.

DEVICE=C:\Netware\IPX.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IRCOMM.SYS

OS/2 IrDA IrCOMM Device Class Driver. These drivers work on the IBM ThinkPad 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 770, 770E, 770ED, 770X. They do NOT work on the 560.

DEVICE=IRCOMM.SYS

Parameter:

  • /V

Tells you which COM port the driver has assigned to itself

  • /COMPORT:COMx

Sets the COM port that IrCOMM will use.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

IRDA_DD.OS2

IrDA Stack drivers are designed to work on following IBM Thinkpad Models: 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21, T22, T23. They do NOT work on the 560.

DEVICE=IRDA_DD.OS2

Parameter:

  • /Wn

Packet window size in range 1..7. Default value is 7. Used to calculate physical layer receive buffer size by following formula: 2k * n + 2k

  • /Nn

Number of LSAP clients in range 1..112. Default value is 8.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

IRDA_PHY.OS2

IrDA Stack drivers are designed to work on following IBM Thinkpad Models: 380, 380D, 380E, 380ED, 380XD, 380Z, 385D, 385ED, 385XD, 560E, 560X, 560Z, 600, 600E, 600X, 770, 770E, 770ED, 770X, T20, T21, T22, T23. They do NOT work on the 560. Tests are performed for following systems:

  • Thinkpad 600E, 600X, T20, T21

Tests are performed for following adapters:

  • ACTiSYS IR-220L+

Tests are performed for following printers:

  • HP LaserJet 6M/6MP, HP LaserJet 2200

Tests are performed for following cell phones:

  • Nokia 6210, 7110
  • Ericsson R320, SH888
  • Siemens S25, S35i, ME45
DEVICE=IRDA_PHY.OS2 <parameter>

Parameter:

  • /Pn - Hexdecimal port number.
  • /In - Interrupt number.
  • /Sn - Hexdecimal port number for SDLC.
  • /Jn - Interrupt number for SDLC.
  • /Dn - Transmit Tx DMA channel
  • /En - Receive Rx DMA channel

Current code isn't capable to recognize all existing Infrared hardware configurations automatically and therefore driver provides a command line parameters interface which allows user to specify hardware configuration settings manually. If hardware configuration is recognized, command line settings will be ignored.

If the driver doesn't recognize the hardware settings, it will serve Infrared adapter at 0x3F8 using IRQ4 (COM1 default settings) using SIR mode.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

IRDD.SYS

Installs the Infrared Device Driver at COM2.

DEVICE=IRDD.SYS

To print through that port, the driver INFRARED.PDR needs also to be installed.

TIP: For Thinkpads the address and the IRQ should be added. E.g. Device=C:\OS2\BOOT\IRDD.SYS 2F8 3. This is valid only if IRQ 3 isn't used yet. If it is, another one has to be chosen (with an appropriate I/O address). To print through that port, the driver INFRARED.PDR needs to be installed by changing the Printer Output Port settings in the Printerdriver Properties.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

IRMAC.OS2

IBM Wireless LAN PCMCIA Adapter driver.

DEVICE=IRMAC.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

JJSCDROM.DMD

Modified CD-ROM device manager with CD-DA digital readout / multisessioning enhancement developed by Takayuki Suwa (jjsuwa@sys3175.com)

DEVICE=JJSCDROM.DMD

Parameters:

  • /Q

quiet; displays no messages if not installed

  • /V

verbose; displays CD-ROM unit information

  • /VP

same as /V, with pausing (requires PAUSEONERROR=YES)

  • /R:n

reserves at least n driveletters (driveletter reservation)

  • /S

assigns only 1 driveletter to SCSI-3/MMC / ATAPI changer units

  • /W

treats all WORM devices as CD-ROM; in order to not apply this treatment to specific unit(s), use /U:n /I

  • /U:n

specifies unit number for /Fxy and /I, 0 based

  • /I

ignores unit (no driveletter assignment)

  • /Fxy

enforces CD-DA / CD-XA / multisessioning / UPC treatments; without preceding /U, applies to all units

  • /FC+

forces "CD-DA readable" flag on

  • /FCS

enforces Sony CDU-561 compatible SCSI CD-DA readout method *

  • /FCT

enforces Toshiba XM-3401 compatible SCSI CD-DA readout method *

  • /FC

same as /FC+ /FCS

  • /FX+

forces "CD-XA readable" flag on

  • /FXT

enforces Toshiba XM-3401 compatible SCSI CD-XA readout method *

  • /FXS

enforces Sony CDU-561 compatible SCSI CD-XA readout method *

  • /FXN

enforces NEC 84-1 compatible SCSI CD-XA readout method *

  • /FX

same as /FX+ /FXS

  • /FM+

forces "multisessioning-aware" flag on

  • /FMT

enforces Toshiba XM-3401 compatible SCSI multisessioning method *

  • /FMS

enforces Sony CDU-561 compatible SCSI multisessioning method *

  • /FMC

enforces Chinon CDS-535 compatible SCSI multisessioning method *

  • /FMN

enforces NEC 84-1 compatible SCSI multisessioning method *

  • /FMH

enforces HP C4324 compatible SCSI multisessioning method *

  • /FMX

enforces NEC 46x compatible SCSI multisessioning method *

  • /FM

same as /FM+ /FMS

  • /FUU

marks as "UPC readable" and enforces unpacked raw UPC format *

  • /FUP

marks as "UPC readable" and enforces packed raw UPC format *

  • /FUA

marks as "UPC readable" and enforces ASCII raw UPC format *

  • /FU

same as /FUA

  • /F

same as /FC+ /FCS /FX+ /FXS /FM+ /FMS

  • because SCSI-3/MMC / ATAPI drives can automatically detect and configure their own capabilities, these options are ignored on such drives.
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

KBLS120.SYS

Kingbyte LS-120 ATAPI Disk Driver. http://www.kingbyte.com

DEVICE=KBLS120.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

KBPD.SYS

Kingbyte OS/2 Parallel PD ATAPI Disk Driver. http://www.kingbyte.com

DEVICE=KBPD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

KBZIP100.SYS

KingByte Parallel Port IOMEGA ZIP 100 drive. http://www.kingbyte.com

DEVICE=KBZIP100.SYS

Parameter:

  • /Sn

Set the starting search port access speed level for printer port. If this parameter is not specified, driver will try from the fastest speed level 0, and then level 1, level 2 until level 9 automatically, n must be 0 ~ 9. Default value is 0 (the fastest level).

  • /Zn

n is a byte-length value bit1 = 1, suppress bi-direction mode = 0, not suppress bi-direction mode (default) bit2 = 1, suppress uni-direction emulation mode = 0, not suppress uni-direction emulation mode (default) bit3 = 1, suppress epp emulation mode = 0, not suppress epp emulation mode (default)

Ex: /Z8 --> suppress EPP mode
Ex: /Z10 --> suppress EPP & bi-direction mode
Ex: /Z14 --> suppress EPP & bi-direction & uni-direction mode

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

KDBNET.SYS

Kernel Failure Networkprotocol, enables remote Kernel-Failure repair over TCP/IP.

DEVICE=KDBNET.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

KILLER.SYS

Used by the Watchcat task killer.

DEVICE=C:\User\Watchcat\KILLER.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

KMGAX64.SYS

It is used by Matrox Graphics cards.

DEVICE=C:\Mga\Os2\KMGAX64.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

KTC110.OS2

Kingston EtheRX PCI Fast Ethernet Adapter. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.

DEVICE=KTC110.OS2
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

KTC111.OS2

Kingston Fast EtheRx KNE111TX PCI Fast Ethernet Adapter.

DEVICE=KTC111.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

KTC120.OS2

Kingston EtheRX PCI Fast Ethernet Adapter.

DEVICE=KTC120.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

KTC40.OS2

Kingston EtheRx PCI-Ethernet-Networkadapter driver. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.

DEVICE=KTC40.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

KURTAXGT.SYS

Pen for OS/2 Device Driver for Kurta.

DEVICE=KURTAXGT.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

L100.OS2

PNIC 100 Base FX Fast Ethernet adapter. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.

DEVICE=L100.OS2

TIP: By Jan Swartling. To get this driver to work with a Netgaer FA 310TX edeit the L100.NIF as follows:

 [Media_Mode]
 display = "Serial connection type"
 type = string
 strlength = 14
 optional = yes
 set = TP_10,TP_10_FD,TP_100,TP_100_FD,AUTODETECT
 default = AUTODETECT
 help = "This parameter specifies the serial connection type used on the adapter.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANDD.OS2

IBM IEEE 802.2 NDIS protocol driver. Information passed by Sergey I. Yevtushenko (evsi@naverex.kiev.ua) http://es.os2.ru/

Author of:

  • Fast Editor Lite (FED) Powerful programmers editor for OS/2.
  • PU Monitor System monitoring tool for OS/2 PM
  • Cell Toolkit Small library for OS/2 PM

In short, that driver allows application to send/receive Ethernet and Token-Ring frames in a NIC-independent way. Format of the frame described in IEEE 802.2 standard. Applications using this protocol driver are e.g.: Lexmark's MarkVision uses it for Lexlink protocol support and Remote IPL.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANDD.SYS

LAN Manager's user device driver that provides services for MAC frame protocols.

DEVICE=LANDD.SYS

NOTE: By Jeff Summner: Looking at the driver, it supplies the driver names \dev\LANDD$ and requires another device, \dev\protman$ to work. In my experience, in OS/2 it is strictly used for SNA, be that Anynet (Netbios over SNA/APPN) or simple Mainframe connectivity. It is also used to configure Bridges and LAM/CAU equipment. It does allow for some pretty cool stuff, like simple Token Ring utilization figures (a la Ringutil, IBM EWS, useless at full duplex, though) and Token Ring Diags (last ring code, upstream neighbor, beaconing MAC, Ring Parameter Server reporting.)

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANDLLDD.OS2

LAN Manager interface to LAND.OS2--the 802.2 protocol.

DEVICE=LANDLLDD.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANDLLDD.SYS

LAN Manager's common dll device driver.

DEVICE=LANDLLDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANMSGDD.OS2

Writes a log named LANTRAG.LOG into drive:\IBMCOM. This file will contain any messages (such as errors) generated via LANMSGDD.OS2.

DEVICE=C:\IBMCOM\LANMSGDD.OS2 <parameter>

Parameters

  • /I:C:\IBMCOM /S

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANPDD.OS2

Part of MPTS. It enables the NetBIOS and the IEEE 802.2 Protocols to OS/2 Programs. It loads also support for the LAN Virtual Device Driver ( Lanvdd.os2 ).

DEVICE=C:\Ibmcom\Protocol\Lanpdd.OS2
DEVICE=drive:\IBMCOM\LANMSGDD.OS2 /I:drive:\IBMCOM /S

Writes a log named LANTRAG.LOG into drive:\IBMCOM. This file will contain any messages (such as errors) generated via LANMSGDD.OS2.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANPDD.SYS

LAN Manager's kernel device driver.

DEVICE=LANPDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANVDD.OS2

Part of MPTS. It is the LAN Virtual Device Driver. It enables the NetBIOS and the IEEE 802.2 Protocols to Dos and Windows Programs.

DEVICE=C:\Ibmcom\Protocol\LANVDD.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANVDD.SYS

DOS LAN Manager's virtual device driver.

DEVICE=LANVDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANVMEM.SYS

LAN Virtual DOS Driver, needed when using an specific DOS to be started.

DEVICE=LANVMEM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LDCOPY.SYS

Simple OS/2 driver for copying files while CONFIG.SYS is being processed by Bob Eager.

DEVICE=LDCOPY.SYS

Parameter:

  • sourcefile destinationfile

Note: The driver can appear several times in the config.sys, thats not a fault. http://www.tavi.co.uk/os2pages/ldcopy.html

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LNE100.OS2

Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4). NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.

DEVICE=LNE100.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LNEPCI.OS2

Linksys LNEPCI/LNE100TX Ethernet Adapter.

DEVICE=LNEPCI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LOG.SYS

This driver enables logging of system error messages and some application error messages.

note: You need also logdaem.exe

DEVICE=C:\OS2\LOG.SYS <parameters>

Parameters:

  • /E:value

This sets up the log buffer size. Value can be in the range from 4 to 64 . Default = 8 This value is expressed in Kbytes.

  • /A:value

This is the size of the alarm buffer. Value can be in the range from 4 to 64 . Default = 8 This value is expressed in Kbytes.

  • /OFF

If set to OFF the driver is installed but the logging of error messages is turned off. You can turn it on again with the program Syslog.

See the examples below.

To install the log driver with a log buffer size of 48 Kbytes and an alarm buffer of 16 Kbytes, add this line to your config.sys file:

DEVICE=C:\OS2\LOG.SYS /E:48 /A:16

To install the log driver but turn it off after initialization use this line:

DEVICE=C:\OS2\LOG.SYS /OFF

NOTE: LOG.SYS has its limitations. It will not log an application error unless the application has been written to make use of LOG.SYS. Some routine system errors will not log either because OS/2 opens an error message box on screen to report these.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LPT49.SYS

Devicedriver out of the LPT49.ZIP package available for free at http://www.kellergroup.com.

The LPT49 utility includes a device driver (LPT49.SYS) and command file (LPT49.CMD) for creating additional LPT ports on your system (LPT4 through LPT9). You can then install the fax printer object on any of these LPT ports. You can also create multiple fax printer objects on different LPT ports (set on the Output page of the printer object's Settings notebook), and each printer object can have different job properties (set with the Job properties button on the Printer driver page of the printer object's Settings notebook). Keller Group Inc. is the developer of PMFax and Faxworks.

DEVICE=LPT49.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LPTDD.SYS

This driver allows a DOS session to print to an LPT port that has been redirected (or captured) to a network printer.

DEVICE=C:\OS2\Mdos\Lptdd.sys 

Parameter:

  • -T:ss

Specifying the timeout value on send/receive (default 10 seconds). If using slow media (diskette), or when LPTool is used on a very busy system, increase this for reliable operation.

  • -P:n

Specifying the LPT port-address to use (default is 1 for using 0378). Use LPTDD.CMD to define the correct n.

The FREE LPTool is developed by Jan van Wijk available at http://www.fsys.demon.nl

TIP: Together with e.g. the great FileCommander/2 by Brian Harvard create a user-menue entry that sends the current directory to the connected Computer for an easy use.

Example:

  S: Copy to Remote via parallel port
  D:\TOOLS\LPTOOL\LPTOOL send

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LSL.SYS

This is the Link Support Layer driver. It is the lowest layer in the Novell Open Data Link Interface model and is required for the requester.

DEVICE=C:\Netware\Lsl.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes Yes Yes

LTMDMOS2.SYS

Lucent Technologies Modem Driver. An older V. 5.55 Beta 3 is available for FREE at http://www.drmartinus.de/notebook2/notebook.htm

DEVICE=LTMDMOS2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LXAPI32.SYS

Radio/TV driver for BT878 based cards. The LXAPI32.SYS is a common linux services driver. It provides functions for PCI, I2C, memory, resources with linux function calls.

DEVICE=LXAPI32.SYS

Parameter

  • /NOPCINAMEDEVICE

necessary if a trap on boot occurs

Parameter:

  • /V

Verbose: Show Copyright information

  • /VM

Verbose modules: Like /V plus module list

  • /3

Execute an INT3 at initialisation (Use kernel debugger!)

  • /NOMODULE

Don't load modules at system startup (Use BT32CFG.EXE to load/unload)

  • /NOCOREMODULE

Don't load core modules at system startup (Use BT32CFG.EXE to load/unload)

  • /MODPARM:

Support Linux insmod parameters for various modules

  • /LOADMODULE:

Load module (only with parameter /NOCOREMODULE)

  • /NOPCINAMEDEVICE

Don't load and parse PCI.IDS file to prevent a system trap with driver SEG32.SYS (32Bit Security Driver of AVP/2)

NOTE: This driver is the base linux api layer driver for ported drivers. It must reside before all other drivers that attaches to LXAPI32. Currently there is only BT32.SYS available.

NOTE: LXAPI32.SYS contains the following modules:

  • timer
  • pci_core
  • i2c_core
  • videodev

NOTE: Module parameters:

timer
pci_core dopcifixups=n disable/enable corresponding
dopcienable=n pci functions in pci_core
dopcisetmaster=n n is 0 or 1
dopcisetpowerstate=n
dopciupdateresource=n
dopciresourcesurvey=n
i2c_core
videodev

All dopci* parameters defaults to 0 because they aren't really needed in OS/2 and caused some problems.

Here is an example for using the /MODPARM parameter: /MODPARM:pci_core:dopcifixups=1;dopcienable=1 This will enable dopcifixups and dopcienable.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MACFH.OS2

Part OS/2 Virtual LAN Kernel.

DEVICE=MACFH.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MAESTR2E.SYS

AudioDrive Maestro-2E OS/2 Driver modified by Daniela Engert

DEVICE=MAESTR2E.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MD5.SYS

Used by the Firewall built into TCP/IP 4.1 and above. This driver adds MD5 encryption to the Firewall. Device driver used by the IBM TCP/IP Firewall to impliment MD5 encryption. Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall. This is RSA's message digest algorithm used to provide authentication and integrity verification.

DEVICE=x:\MPTN\PROTOCOL\MD5.SYS 

There are several tools to configure the firewall:

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MEDIAOS2.SYS

MediaDrive OS/2 Device Driver. The MediaDrive is an internal PC Card drive for Workstations. Useful e.g. for Digital-Cameras. Available at http://www.altec-computersysteme.com

DEVICE=MEDIAOS2.SYS

Parameter:

  • /V - Verbose
  • /B:XXX - Basisadress at XXX e.g. 170

Limitations:

The driver can only read/write FAT formatted ATA & SRAM PC Cards. With OS/2 only the lower slot can be used. Must be the only drive attached to the IDE-Controller.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MEIO0437.SYS

Driver for the MWAVE Modem for IBM Thinkpads.

DEVICE=MEIO0437.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MEMMAN.OS2

LAN Manager's memory manager for DOS/Windows mode operation. Left over from old code to provide compatibility. Not needed for normal operations.

DEVICE=MEMMAN.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MIDI.SYS

RTMIDI helper driver. Is used by your Soundcard, but RTMIDI will work only if your Soundcard supports RTMIDI with the audio driver.

DEVICE=C:\OS2\Boot\Midi.sys 

TIP: For working with Midi there is the MIDI Station Sequencer: http://www.dinosoft.it/~midistation/index.html

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

MODISK.DMD

MO device driver from Fujitsu.

DEVICE=MODISK.DMD

Parameters

  • /Rn or /R:n

(Number of reserved drives) 'n' is a number between 1 and 10. Default is 1. A series of logical drive names can be reserved for each MO drive for future partitioning. If the number of valid partitions exceeds the number specified /R option, and if /S option is not specified, up to 16 partitions are allowed.

  • /S

(Reserved drive priority) No more logical drives than the number of /R option is assigned. When the number of reserved drives specified with the /R option is fewer than the number of valid partitions on a disk, the number of reserved drives takes priority. For example, if there are four valid partitions on the disk and the number of reserved drives is specified at 3, a logical drive name cannot be assigned to the fourth partition, and hence it cannot be accessed.

  • /I {h:} m {[n]} {+-{h:} m {[n]}}+-...

(Specify the drive ID) This parameter specifies the target MO drive by the host adapter number and SCSI-ID number. If this option is not used, all accessible MO drives are used by default. h is the host adapter number (between 0 and 9). The default is 0. m is the SCSI-ID number (0 to 7). n is the number of reserved drives. When 'n' is omitted, the value specified with the /R option is used.

  • /U:{IDE adapter name}

(Required, specify IDE adapter driver) This parameter is not optional but required both for ATAPIMO.FLT and MODISK.DMD. You must specify same name for these two drivers. Usually '/U:ST506_HardDrive' works fine if 'IBM1S506.ADD' or 'IBM2S506.ADD' is used as IDE adapter driver.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

MODISK.SYS

Magneto Optical Device Driver.

DEVICE=MODISK.SYS

Disk Types Supported

  • 3.5 inch MO disk
  • Sector size: 512 bytes or 2048 bytes
  • Capacity: 128 MB, 230 MB, 540 MB or 640 MB

NOTE: When using MODISK.SYS you have to delete or REM OPTICAL.DMD (Warp 4) or OPTICAL.SYS (Warp 3) NOTE: There is also a MODISK.SYS for SCSI by Fujitsu who supports also 1.3 GB drives. For Parameters see MODISK.DMD

NOTE: Better use the /of switch together with OS2DASD.DMD (or DANIDASD.DMD). In this case make shure that the MODISK.SYS is not loaded.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

MONMOU01.SYS

Serial Touchscreen Controller on PC-Bus System

DEVICE=MONMOU01.SYS <parameter>

Parameter: where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.

matches the jumper settings on the controller.

matches the interrupt jumper on the controller.

NOTE: Disabling the COM Drivers If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.

NOTE: If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

MONMOU02.SYS

Serial Touchscreen Controller on PS/2 System

DEVICE=MONMOU02.SYS <parameter>

Parameter: where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.

matches the jumper settings on the controller.

matches the interrupt jumper on the controller.

NOTE: Disabling the COM Drivers If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.

NOTE: If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

MONMOU03.SYS

PC-Bus and MicroChannel Touchscreen Controller

DEVICE=MONMOU03.SYS <parameter>

Parameter: where is: 4035 for the IntelliTouch E281-4035 PC-Bus controller. 4025 for the IntelliTouch E281{A}-4025 PC-Bus controllers. 2201 for the AccuTouch E271-2201 PC-Bus con troller. 141 for the AccuTouch E271-141 PC-Bus controller.

matches the jumper settings on the controller.

matches the interrupt jumper on the controller.

NOTE: Disabling the COM Drivers If you selected IRQ4 or IRQ3 for the touchscreen controller (the interrupts reserved for COM1 and COM2), move the DEVICE=COM.SYS and DEVICE=VCOM.SYS commands (if present) before the DEVICE= MONMOU03.SYS command in CONFIG.SYS. This prevents the COM drivers from displaying a message saying the COM port is unavailable. Add the flag (,0,0) to COM.SYS, where is 1 for IRQ4 or 2 for IRQ3.

NOTE: If you do not wish to have a mouse connected, change the "stype=elomou$" flag to "type=elomou$" on the DEVICE=MOUSE.SYS command.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

MOUSE.SYS

Provides support for your mouse. You need also the Pointdd.sys installed.

DEVICE=C:\Os2\Boot\Mouse.sys <parameter>

Lets you use a mouse or track ball. This line also identifies the device dependent type of mouse you have and which COM port it is on. In this case, the device dependent mouse driver is loaded in your OS/2 CONFIG.SYS through a standard "DEVICE=" line, before the MOUSE.SYS driver is loaded, and then on the MOUSE.SYS line there is the parameter "TYPE=", with a reference to the device name of the device. QSIZE is a number from 1 to 100 which indicates how many mouse actions are to be saved when you execute mouse actions faster than your system can handle them. There is also a RELAXED parameter which you would place after QSIZE. It can be used with any mouse when the pointer is jumping randomly about the screen. IBM does not suggest you use this parameter unless you are experiencing this problem.

ATTENTION: Together with an device independent Mouse (e.g. a IBM PS/2 Mouse) NO PARAMETERS are needed.

The supported device dependent Types are:

  • PCLOGIC$ for Genius, Logitech, PC Mouse Systems, Driver: PCLOGIC.SYS
  • MSBUS$ for Microsoft Bus-Mouse, Driver: NONE
  • MSINP$ for Microsoft-Inport, Driver: NONE
  • VISION$ for Visi-On: Driver: VISION.SYS
  • ELOMOU$ for ELO Touchscreen Driver:MONMOU0x.SYS (x=1, 2 or 3)
  • SUMMA$ for SUMMA Tablet Driver:SUMMA.SYS
  • GRAPHIR$ for WACOM Tablet Driver: GRAPHIRE.SYS

NOTE: The MOUSE.SYS statement must come before COM.SYS, but after POINTDD.SYS, because COM.SYS will take over any unused COM port. If COM.SYS takes over the COM ports before MOUSE.SYS is loaded, MOUSE.SYS will not have any COM ports available, thus no mouse support.

TIP: If you have a so called scroll-mouse (e.g. from IBM, or Logitech) get the scrollms.exe package from the OS/2 Device Driver Pack. Or use the scrollmouse driver from http://os2.ru/projects/scrollmouse, who uses a second wheel horizontal not only vertical. If you want to have a 'scrolling-feature' with normal mice there is the FREE hots11.zip package by Samuel Audet from http://WWW.CAM.ORG/~guardia/programs.html. See also AMOUSE.SYS

TIP: If you want to have animated mouse pointers (very nice); Christan Langanke has developed a FREE Version to get as AMPTR101.ZIP


Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MOUSE2.SYS

Driver for the Trackpoint of IBM Thinkpads

DEVICE=MOUSE2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MPU401.SYS

Provides support for the MPU401 connector on your soundcard.

DEVICE=C:\Os2\Boot\MPU401.SYS <parameter> 

Parameter:

  • /Pn:hhh

Basis I/O (Port) Address.

  • /In:ddd

Interrupt Level. With the Theta Band driver it can be set to 0 so TIMER0 is used during record.

  • /N:sss

Name of the driver. Default is MPU401$

  • /R:ddd

TIMER0 resolution in milliseconds. Default 2.

  • /V

Verbose

  • /O:sss

Options

* L or LONGNAME - Long RTMIDI Names
* QUIETINI - Ignore Initialization errors
* NORMIO Do not check/register I/O addresses with RM
* SHAREDIO Check/register I/O adresses as shared
* MULTIO Check/register I/O adresses as multiplexed
* NORMIRQ Do not check/register IRQ's with RM
* SHAREDIRQ Check/register IRQ's as shared
* MULTIRQ Check/register IRQ's as multiplexed
* NOCHECKIO Do not verify I/O adresses
* NOCHECKIRQ Do not verify IRQ's
* NOTIMER0 Do not use TIMER0
* 10BITS Use 10-bit address width with RM
* 16BITS Use 16-bit adress width with RM
* ONLYONE Locate only one MPU401 device
* AUDIOVDD Enable DOS sharing (Only for Theta Band driver).

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MVPRODD.SYS

Driver for MediaVision's ProAudio Spectrum sound card. The first driver is set for IRQ 11, DMA 3 with Sound Blaster support on IRQ 5 and DMA 1.

  DEVICE=MVPRODD.SYS

Warp TIP: MediaVison's technical support indicates that the only correct settings for the PAS 16 in Warp is IRQ 11 and DMA 3. If you are experiencing static or white noise during bootup, MediaVison indicates that this is caused by using an IRQ other than 11 and DMA 3. They also indicate that the two device driver lines must be the last lines in your config.sys file. Note that this information didn't solve the static problem for all users, but it did for some. Others have indicated that adding the /T:1 parameter solved their "white noise" problem.

Warp NOTE: There may be a bug in Warp which causes problems in WIN-OS2 "seamless" mode. A solution is contained in SNDWOR.ZIP.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MWAVEDD.SYS

Driver for MWAVE Modem on IBM Thinkpads.

DEVICE=MWAVEDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MWAVEVDD.SYS

Dos Driver for the MWAVE-DSP in Thinkpads.

DEVICE=MWAVEVDD.SYS

ATTENTION: The MWAVEVDD.SYS must placed before VEMM.SYS.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MXNICF.OS2

Macronix MX987xx Family, Edimax EN9120 Family, DFE-540TX Fast Ethernet PCI Adapters. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/

DEVICE=MXNICF.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes Yes Yes

N100.OS2

Compaq Fast Ethernet and Gigabit NDIS driver

DEVICE=N100.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NE2000.OS2

Eagle Technology NE2000plus Ethernet Adapter.

DEVICE=NE2000.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NETBEUI.OS2

This is the NetBIOS protocol driver.

DEVICE=C:\Ibmcom\Protocol\NETBEUI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NETBIOS.OS2

This is the NetBIOS API driver.

DEVICE=C:\Ibmcom\Protocol\NETBIOS.OS2

TIP: By Roland Sambain. The conventions wisdom about IFS statements coming at the beginning of config.sys seems not to apply. i.e. for netbios to load correctly the device statement must comes before the NETWKSTA.200 IFS.

Netbios and Gigsabit adapters

Due to the Nature of NetBIOS, it has some limitations to work on Gigabit adapters with requires some adjustments to MPTS settings.

Explanation: NetBIOS can not work with large Ethernet frame sizes which are used by default with Gigabit Ethernet adapters. Both transfer and receive buffer sizes should be set to 1024 bytes and USEMAXDATAGRAM set to "NO". The DIX 2.0 protocol type (ETHERAND_TYPE) should be set to "D".

Procedure to change settings

  1. From MPTS select 'Configure'
  2. In 'Current Configuration' find the "IBM 1000BaseT Gigabit Ethernet Adapter" and press 'Edit'
  3. Set 'Receive Buffer Size' = 1024
  4. Set 'Transmit Buffer Size' = 1024
  5. Select OK
  6. In 'Current Configuration' find the "IBM OS/2 NETBIOS" and press 'Edit'
  7. Set 'Type of Ethernet driver support = "D"
  8. Set 'Full buffer datagrams' = "NO"
  9. Select OK
  10. Select 'Exit' MPTS.
  11. Reboot

The other possibility is to use "IBM OS/2 NETBIOS OVER TCP/IP". You might want to try this and compare the results to native NetBIOS.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NETBIOS.SYS

Loads support for the NETBIOS protocol.

DEVICE=NETBIOS.SYS

TIP: If you do not use NETBIOS applications, you can remove the NETBIOS driver from the config.sys and the NETBIOS section from the PROTOCOL.INI to remove some of the confusion this creates. You should also remove the virtual netbios drivers at the same time since these bind onto the NETBIOS driver and not the LM10 interface (which is why they appear after the NETWKSTA.SYS driver, so it can "eat" its resources first, then what is left over is assigned to NETBIOS.SYS). [<- Note: this should be NETBIOS.OS2] (The mentioned virtual NETBIOS drivers are \IBMCOM\PROTOCOL\LANPDD.OS2 and LANVDD.OS2)

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NETFLX3.OS2

OS/2 NDIS 2 Driver for Compaq NetFlex-3/Netelligent Controllers.

DEVICE=NETFLX3.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NGUEST2.SYS

NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.

DEVICE=NGUEST2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NHOST2.SYS

NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.

DEVICE=NHOST2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NHOST2W.SYS

NetOp driver. NetOp is a family of remote contral products which support multiple operating systems and various communication interfaces.

DEVICE=NHOST2W.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NMPIPE.SYS

This driver provides Named Pipes support on the Netware client.

DEVICE=C:\Netware\NMPIPE.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NOVAQOS2.SYS

Driver for backup-software from NOVABACK.

DEVICE=NOVAQOS2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NOVASPI.SYS

Driver for backup-software from NOVABACK.

  DEVICE=NOVASPI.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NPSERVER.SYS

This driver allows your workstation to function as a Named Pipes Netware server.

  DEVICE=C:\Netware\NPSERVER.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


NSIR.SYS

Part of the Infrared driver for IBM PC300PL computer.

DEVICE=C:\OS2\DLL\NSIR.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

NTRACE.OS2

Goldencode Network Trace (http://www.goldencode.com).

DEVICE=NTRACE.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NULLNDIS.OS2

IBM NULL MAC-driver. Installed if you have NO Network Adapter.

DEVICE=NULLNDIS.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NVC.SYS

This is a "Smart Behavior Blocker for DOS" from Norman antivirus. Basically a shield running in dos-boxes and similar to protect from possible virus "sneak attacks".

DEVICE=NVC.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NWREQ.SYS

This is the main Netware requester module and must appear in config.sys after the NmPipe.sys , Ipx.sys and Spx.sys drivers.

DEVICE=\Netware\Nwreq.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ODI2NDI.SYS

This driver allows the Netware client to use MPTS as the interface to a network adapter driver and in turn, the LAN.

DEVICE=\Netware\Odi2Ndi.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OPL3.SYS

Is used by soundcards with an OPL3 sound chip.

DEVICE=C:\Os2\Boot\Opl3.sys 

Parameter:

  • /P:nnn

Base I/O: Sets the base I/O address for FM device. Is almost always, 388 (nnn is in hex)

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OPL3SA.SYS

It is used by Soundcards with Yamaha SAx sound chips.

DEVICE=C:\Mmos2\Opl3sa.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OPL3VDD.SYS

It is used by Soundcards with Yamaha SAx sound chips. It provides support for DOS sessions.

DEVICE=C:\Mmos2\OPL3VDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OPL4D.SYS

Yahama Fm Sythesis OPL4 MIDI Driver.

DEVICE=OPL4D.SYS

Parameter:

  • /P:xxx

Midiport Address, 300, 310, 330 or 388 (default)

  • /N:OPL41$

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OPTICAL.DMD

New with Warp4 Device Manager for Optical devices like MO.

 DEVICE=OPTICAL.DMD

TIP: If you have removable media drives (MO, IOMEGA, SYQUEST and others) look at http://rheooptik.fmf.uni-freiburg.de/www/faq/remmedia.htm for a detailed removable media FAQ.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OS2CDROM.DMD

Provides support for IDE CDRom drives. It is a device manager driver.

Note: To get CDRom support in OS/2 you must also install Ibm1s506.add and Ibmidecd.flt .

BASEDEV=Os2cdrom.dmd parameters

Parameters:

  • /V

Displays some information about your CDRom drive during the boot.

  • /Q

Stops displaying error messages during the boot.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OS20MEMU.SYS

OS20MEMU is a Memory Analyser for OS/2 (IBM EWS).

DEVICE=OS20MEMU.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OS2EASY.SYS

Altec EASY DRIVE. http://www.altec-computersysteme.com

DEVICE=OS2EASY.SYS <parameter>

Parameter:

  • /V

Set Verbose Mode on

  • /B:XXX

Set Base Adress to XXX e.g. 170

NOTE: Currently only one slot supported, the standard format command is unsupported, no API to get direct access to the meory media.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

OS2OGL.SYS

Pentium Pro optimised Open GL Driver.

  DEVICE=OS2OGL.SYS

NOTE: For OpenGL to utilize the device driver on PentiumPro systems, an environment variable, SET OGL_VIDEO_MEM_SIZE, must be set. The suggested place to set OGL_VIDEO_MEM_SIZE is in the config.sys, alternately, it can be set in an OS/2 Window before an OpenGL program is started. For either method, OGL_VIDEO_MEM_SIZE should be set to the total memory size (in megabytes) of the PCI graphics card. For example, using a graphics card with 4MB of memory, "SET OGL_VIDEO_MEM_SIZE=4" should be used.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

P6K7MTRR.SYS

A simple interface physical device driver(PDD) that can manage memory Type Range Registers(MTRRs) of Intel P6* / AMD K7** series processors. Programmer can query/modify any MTRR settings via DosDevIOCtl() API, from non-Ring0 privileges. A sample executable, VFBWC.exe, using P6K7MTRR.sys, sets MTRR write-combining strategy to video frame buffer aperture. It can often improve graphic performance, especially DIVE. By Takayuki 'January June' Suwa (jjsuwa@sys3175.com)

DEVICE=P6K7MTRR.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

P9100.sys

Is used by graphiccards with a Weitek P9100 chip.

  DEVICE=C:\Os2\Boot\P9100.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PANEL.SYS

PANEL is a small OS/2 device driver that gives access to the small (eight character) information panel on the front of the PS/2 Model 95 series of systems (and possibly others). Available for FREE at http://www.tavi.co.uk/os2pages/index.html

DEVICE=PANEL.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PARADISE.SYS

Driver for the Paradise mixer for all Crystal CS423x soundcards using a mode-3 driver.

DEVICE=PARADISE.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PAUSE.SYS

DEVICE=PAUSE.SYS

Parameter:

  • /W:NNN

Where: NNN = seconds to wait (default = 30 seconds)

Pauses the config.sys for a given time. Useful for maintenance purposes. The driver can be found at the IBM Device Driver Pak Online site.

TIP: Together with BASEDEV=IBM1S506.ADD the /W parameter does the same.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PC.SYS

Driver from Process Commander by Stardock.

DEVICE=PC.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PC100.OS2

Linksys EtherFast 10/100 PC Card. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.

DEVICE=PC100.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCCOM2.SYS

PCCOM 2 PORT Card Device driver.

DEVICE=PCCOM2.SYS

Parameter:

  • /Axxx,yyy

card I/O address; port1=xxx, port2=yyy

  • /Imm,nn

IRQ Nø; IRQ1=mm, IRQ2=nn

  • /Cxx

Assign the port number of the first port on the card ( COM1 to COM98 )

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


PCCOM4.SYS

PCCOM 4 PORT Card Device driver.

DEVICE=PCCOM4.SYS <parameter>

Parameter: /Axxx : card address

/Ixx : IRQ Nø

/D : compatible mode: COM1 and COM2 ( same as PC COM ). Use COM.SYS ( from IBM) for these 2 ports and PCCOM4.SYS for other ports. This option must be put to the front of all other options.

/Cxx : Assign the port number of the first port on the card ( COM1 to COM96 )

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCCOM8.SYS

PCCOM 8 PORT Card Device driver.

DEVICE=PCCOM8.SYS

Parameter:

  • /Axxx,xxx

Address of the card, following of vector address( without any space ! )

  • /Ixx

IRQ Nø

  • /Cxx

Assign the port number of the first port on the card ( COM1 to COM92 )

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCIND.OS2

NDIS driver for RealTek RTL-8029 based NE2000-combatible cards.

DEVICE=PCIND.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCKBD.SYS

Process Commander Keyboard driver. The PCKBD line lets full-screen Process Commander be invoked, even when the customized KBDBASE.SYS is not being used.

DEVICE=PCKBD.SYS <parameter>

Parameter:

  • KEYB:CA-A

For getting it to work with FP13 and up see: http://www.scoug.com/os24u/2001/scoug003.mrkia.html

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCLOGIC.SYS

Provides mouse support for Genius, Logitech, PC Mouse Systems.

DEVICE=PCLOGIC.SYS

ATTENTION: Must reside between POINTDD.SYS and MOUSE.SYS.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCM2FLSH.SYS

PCMCIA Storage Driver for OS/2 (FLASH).

DEVICE=PCM2FLSH.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PCM2SRAM.SYS

PCMCIA Storage Driver for OS/2 (SRAM).

DEVICE=PCM2SRAM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

PCMNICCS.OS2

IBM Ethernet Adapter (PCMCIA) driver.

DEVICE=PCMNICCS.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
2.1 Yes Yes Yes

PCMSSDIF.SYS

PCMCIA Storage Driver for OS/2 (Interface).

DEVICE=PCMSSDIF.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
2.1 Yes Yes Yes

PCNTND.OS2

AMD PCNet Ethernet Family Adapter driver.

DEVICE=PCNTND.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PDITOU01.SYS

See DEVICE TOUCH.SYS.

DEVICE=PDITOU01.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PDITOU02.SYS

See DEVICE TOUCH.SYS.

DEVICE=PDITOU02.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PENCC.SYS

Pen for OS/2 Device Driver for CalComp 3300.

DEVICE=PENCC.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PENDD.SYS

Wacom IV and V Tablet driver by Masami Kitamura.

DEVICE=PENDD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PMDD.SYS

Installs pointer draw device driver support.

DEVICE=\Os2\Boot\Pmdd.sys 

WARNING: OS/2 will not start without this line in your config.sys file.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PNPND.OS2

Device driver for the RTL8019 Ethernet card.

  DEVICE=PNPND.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

POINTDD.SYS

Provides mouse pointer draw support. Text modes 0, 1, 2, 3, and 7 and graphic modes D, E, F, and 10 are supported. For graphic modes other than D, E, F, and 10, the correct graphic device driver must also be installed.

DEVICE=\Os2\Boot\Pointdd.sys 

WARNING: In order for MOUSE.SYS to work effectively, this driver must be loaded by OS/2 before MOUSE.SYS. Do not remove it from your config.sys file.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PPPEMYWI.OS2

PPP over Ethernet Protocol driver included in ISDNPM 3.x.

 DEVICE=PPPEMYWI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PROTMAN.OS2

Network protocol-manager driver. IBM OS/2 LAN Protocol Manager, read PROTOCOL.INI in directory drive:\IBMCOM

DEVICE=C:\IBMCOM\PROTMAN.OS2 <parameter>

Parameters

  • /I:C:\IBMCOM

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PRTUTIL.SYS

Part of the Infrared driver for IBM PC300PL computer.

DEVICE=C:\OS2\DLL\PRTUTIL.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

PSCOM.SYS

This driver is required for serial communications on ACPI systems.

DEVICE=\OS2\Boot\PSCOM.SYS <parameters>

NOTE: This line MUST appear after any driver that uses a communications port, but before USB serial drivers (e.g., USBSER.SYS and/or USBCOM.SYS).

NOTE: See other notes related to COM.SYS.

TIP: To specify address and interrupt manually, use the syntax (port,address,IRQ), e.g.:

Set COM3 and COM4 at address 3E8 on IRQ 4 and 2E8 on IRQ 3:

  DEVICE=drive:\OS2\COM.SYS (3,3E8,4) (4,2E8,3)

Parameter:

  • /V - Verbose
  • /W - Wait verbose mode. Displaying pauses with a "Press Enter to continue..." message.
  • /F - Find COM ports on PCI combo (serial/parallel) cards automatically.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

PTDVR.SYS

Driver of Backmaster tape backup system.

DEVICE=PTDVR.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

QAP2DRVR.SYS

Driver for QAPlus/2, a PM program for testing system hardware: CDROM, ser/par ports, floppy drives, HD, keyboard, system board, memory, mouse... It can pinpoint failed SIMMs. Makes reports; everything. A bit dated now (1996), but still kinda useful. From DiagSoft, Inc., in Scott's Valley, CA, USA.

DEVICE=QAP2DRVR.SYS

Information by Wm D Loughman (wdlkhl@attglobal.net)

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

QCAMM.SYS

Driver for the Connectix Quickcam connected to parallel port. QCammdd01.zip is FREE for personal use.

DEVICE=QCAMM.SYS <parameter>

Parameter:

  • /CB=nnn - Camera Balance 1-254 (varies)
  • /CC=nnn - Camera Contrast,nnn=1-255,default 104
  • /CE=nnn - Camera Exposure,nnn=1-254,default 210
  • /CT=n - Camera Transfer,n=1,2,4, default 1
  • /FD=n - Frame Depth,n=4,6,default 6
  • /FH=nnn - Frame Height,nnn=1-240,default 240
  • /FL=nnn - Frame Left,nnn=1-320,default 1
  • /FT=nnn - Frame Top,nnn=1-240,default 1
  • /FW=nnn - Frame Width,nnn=1-320,default 320
  • /PA=nnn - Port Address,nnn=278,378,3bc
  • /PN=n - Port Number,n=1,2,3
  • /QM - Quiet Mode

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

QCOM.SYS

Quatech (www.quatech.com) asynchronous serial device driver for the Quatech ISA and PCI boards High baud rates to 921,600 bits per second, depending on UART type. Support for 16750 UARTs and their 64-byte FIFOs. Up to 32 serial ports.

  DEVICE=QCOM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

QUICKCAM.SYS

Quickcam Viewer driver for Connectix QuickCam (tm) B&W, Colour, ColourII, QuickCam VC or QuickCam Pro

NOTE: It is recommended that you set your parallel port to either AT-mode or EPP-mode for uni-directional or bi-directional modes, respectively. Bi-directional mode will give at least double the throughput compared to uni-directional mode. QuickCam VC and Pro: The parallel-port MUST be set to ECP-mode. Currently, interrupt and DMA settings are not used. Available at: http://www.cix.co.uk/~elad/qv2.htm

DEVICE=QUICKCAM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

QVCOM.SYS

Quatech (www.quatech.com) asynchronous serial device driver for the Quatech ISA and PCI boards for DOS.

DEVICE=QVCOM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

R0STUB.SYS

Is somewhere used by MMOS2. R0STUB is the ring-0 half of the sync-stream-manager (SSM) that allows MMPM/2 to synchronize audio and video. Allows audiosh.dll to talk to audio drivers vis IDC entrypoint. In the beginning, all the streaming took place at ring-0. Later (Warp 3?), the audio streaming was moved to ring-3. The API still had to be maintained to audio driver. R0STUB is small piece of code that takes FIFOs buffers to/from MMPM/2 ring-3 audio stream handler and delivers them from/to the hardware vender audio device driver.

DEVICE=C:\Mmos2\R0stub.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RAWEMYWI.OS2

DSL cable-modem driver from ISDNPM.

DEVICE=RAWEMYWI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RCPTRNDS.OS2

Racore Preferred Token Ring Adapter (PCMCIA Support).

DEVICE=RCPTRNDS.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RDRHELP.200

This driver is part of MPTS and is necessary somewhere for the NetBIOS protocol.

DEVICE=\Ibmcom\Netprog\Rdrhelp.200 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

REFPART.SYS

Driver for accessing the Refernce Partition on IBM PS/2 Microchannel Machines. Information by: Ralph-Marcus Boenicke

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RMAUDIO.SYS

Reel Magic sound card driver.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ROUTE.SYS

This driver allows a Netware client to see Netware servers on other physical LAN (or segment) across source-routing routers (used by many IBM routers). This is equivalent to Route.nlm for a Netware server.

DEVICE=C:\Netware\Route.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RSJSCSI.SYS

The device driver RSJSCSI.SYS provides simplified access to SCSI devices. The CD Writer File System uses this device driver to access the CD Recorder (also needed for ATAPI).

DEVICE=RSJSCSI.SYS <parameter>

Parameter:

  • -q

While booting, ask user for confirmation before installing the device driver.

  • -x

This option allows using memory above the 16MB line. This works together with true 32-bit SCSI adapters, only (e.g. most EISA and PCI adapters).

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RSMVDWO.SYS

Driver for PolyPM a Remote Service Management Solution. http://www.iss2you.com

DEVICE=RSMVDWO.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RTFND.OS2

RTL8129 Fast Ethernet Adapter. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/realtek.zip.

DEVICE=RTFND.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RTGNDA.OS2

New description.

DEVICE=RTGNDA.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RTR16NDIS.OS2

Racore 16/4 Token-Ring Adapter.

DEVICE=RTR16NDIS.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RTSND.OS2

NDIS MAC for RTL8139 Fast Ethernet Adapter.

  DEVICE=RTSND.OS2 <parameter>

Parameters

  • /V

Verbose mode

  • /Q

Quiet mode

  • /2 .. /9

Selecects other Drivername = netry in \ibmcom\protocol.ini used automaticly if you install more than one card.

  • /U

Number cards as found. useful if BUSNO, DEVICENO or ETHERID values are not present in protocol.ini

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RVGNDIS.OS2

Racore 10/100 AnyLAN Card.

DEVICE=RVGNDIS.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RZT2BOOT.SYS

This driver is used by the IBM AO-Manager.

  DEVICE=C:\SMG\Bin\Rzt2boot.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SB16D2.SYS

Driver for Sound Blaster 16 sound card.

DEVICE=SB16D2.SYS <parameter>

Parameter:

  • /C:

Card Number, this will be set to 1 in most cases

  • /D:

8-bit DMA channel, Valid values - 0, 1 & 3 (Sound Blaster cards that use Vibra chipset do not have 0). Default value - 1.

  • /H:

16-bit DMA channel, Valid values - 5, 6 & 7 (Sound Blaster cards that use Vibra chipset do not have 6). Default value - 5.

  • /I:

IRQ number, Valid values - 5, 7, 9, 10 & 11. Default IRQ - 5.

  • /A:

Base addresss, Valid values - 220, 240, 260, 280 Default value - 220.

  • /B:

Buffer size in KB, Valid values - 1-24. While any value in this range will work fine, to get the best results don't use this option and let the driver use the default buffer size. Default value - 8KB.

  • /M:

MPU port address Valid values - 300 & 330 Default value - 330.

  • /N:

Driver name, set this to SBAUD1$

  • /Q

Quiet mode flag, OPTIONAL. Setting this option disables initialization messages. If not specified the initialization messages are displayed during boot-up.

  • /EXT

Use MPU port instead of internal synth for MIDI, OPTIONAL By default the drivers are configured to use the internal synthesizer. But if you have a daughterboard attached to your Sound Blaster card and you want MIDI playback to use the synthesizer in the daughterboard, specify this flag.

  • /P

Ignore PnP BIOS if it is present. If PnP BIOS is present, the driver usually queries the BIOS for certain PnP port addresses. Specifying this option causes the driver not to access the BIOS and determine these port addresses itself.

  • /G

Override PnP BIOS, undocumented switch. When used all parameters must be specified.

TIP: Look for the SB163264.ZIP package which contains all drivers for the soundblaster cards including those for the AWE 64.

A FREE Mixer for SB 16/32/64 is Mixomat 1.01b by Christoph Bratschi, and the newer Mixomat 2.0 available at http://www.bratschi.net

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SBAWED2.SYS

It is used by Creative Labs AWE32 soundcards.

DEVICE=C:\Sbos2\Sbawed2.sys 

Parameter: See DEVICE SB16D2.SYS

TIP: According to OS/2-Inside the statement can be shortened to:

  SBAWED2.SYS /N:SBAUD1$

TIP: Look for the SB163264.ZIP package which contains all drivers for the soundblaster cards including those for the AWE 64. According to OS2VOICE for the AWE 64 the entry should look like this:

 DEVICE=drive:\SBOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /B:1 /M:330 /N:SBAUD1$ /G

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


SBLIVE16.SYS

Soundblaster Live 16Bit MMPM/2 Sounddriver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)

DEVICE=SBLIVE16.SYS <parameter>

Parameters:

  • /V verbose (prints copyrights during driver init)
  • /C enable CD audio input
  • /M enable microphone audio input
  • /L enable linein audio input
  • /A enable aux audio input (since driver 0.80)

ATTENTION: Read the supplied readme.txt to avoid troubles if you have installed the scitech display drivers (SDDHELP.SYS).

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SBLIVE32.SYS

Soundblaster Live 32Bit core audio driver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)

DEVICE=SBLIVE32.SYS <parameter>

Parameter:

  • /D

Print start and end address of code (useful to locate code that causes a trap)

NOTE: The install.cmd copies - if it finds a Warp 4.5 (fixpak 13 or WarpServer for E-Business) an driver according to the new KEE API (32 Bit driver architecture) to this file.

A appropiate Mixer is the FREE LBMix by Lesha Bogdanow (boga@inbox.ru) The lastest version of the mixer can be downloaded from http://www.podolsk.ru/~boga/OS2Programs.html where you can also find a couple of other useful OS/2 programs.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SBMIX.SYS

Soundblaster-mixer driver.

DEVICE=SBMIX.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SCANHP1.SYS

SCSISCAN OS/2 Copyright from Danmar Systems Inc. Scanner Driver for use with the propietary SCSI controller included with the HPIIp series.

DEVICE=SCANHP1.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SCANOS2.SYS

SCSISCAN OS/2 Version 1.20 from Danmar Systems Inc. ASPI Compatible Scanner Driver.

DEVICE=SCANOS2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SDI_ASPI.SYS

PC-BaX ASPI Device Driver. This driver provides PC-BaX with support for SCSI devices, it uses the OS2ASPI.DMD device manager. This is the prefered method of SCSI support for PC-BaX and should be used in almost all cases.

DEVICE=SDI_ASPI.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SDI_CISA.SYS

PC-BaX ISA Device Driver. This driver provides PC-BaX with support for a special CRISTIE 8-bit SCSI controller.

DEVICE=SDI_CISA.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SDI_IDE.SYS

PC-BaX IDE Device Driver. This driver provides PC-BaX with support for IDE connected devices like Travan backup stations.

DEVICE=SDI_IDE.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SDI_LPT.SYS

PC-BaX LPT Device Driver. This driver provides PC-BaX with support for Cristie parallel port connect tape drives, it does not need any other OS/2 Devices managers or Drivers.

DEVICE=SDI_LPT.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SDI_SCSI.SYS

PC-BaX SCSI Device Driver. This driver provides PC-BaX with support for SCSI devices, it uses the OS2SCSI.DMD device manager. This method of SCSI support is only neccesary when using an IBM MCA type SCSI controller. See common problems by clicking on the support icon within PC-BaX for a full description.

DEVICE=SDI_SCSI.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SEAGB24.SYS

Sytos Plus driver for the Seagate 4mm Tape.

DEVICE=SEAGB24.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SESDD32.SYS

Security device driver. Part of IBM's security system - enabler driver. Will stop install if by itself. Network Associates has a product called 'VirusScan for OS/2'. In its User Guide's appendix 'C' is a very good description of how to modifiy the config.sys file manually to add SES to the user's machine.

DEVICE=C:\Os2\Boot\Sesdd32.sys

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SIO.SYS

The Sio.sys driver is a replacement for the com.sys driver. The Sio.sys driver can support up to 16 COM ports.

DEVICE=\OS2\BOOT\SIO.SYS <parameters>
DEVICE=\OS2\BOOT\SIO.SYS (Cn, An, In, Ig, Fc)
  • CN

The number of the Com port or the string COM1 to COMn. If you use a * in front of the Com port, then the port will be used as a PCMCIA Com port.

  • AN

A hexnumber to define the I/O address of the Com port.

  • IN

The IRQ number (0 to 15) or the string IRQ0 to IRQ15. If you don't use this parameter, SIO will search for a IRQ.

  • IG

This exists only for compatibility with COM.SYS and is ignored by Sio.sys.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


SIO2K.SYS

Excellent replacement driver for COM.SYS. If you utilise communications software on a regular basis at high speeds (e.g. 57,600), then the SIO drivers are the way to go.

DEVICE=SIO2K.SYS

NOTE: REM all other serial drivers like COM.SYS or SIO.SYS

The SIO2K set of drivers have some interesting new techniques and implementations.

Block input and output. If the UART is a FIFOed device, the interrupt service routines (there are several) always use block input and output instructions to read and write characters. During high communications activity, this means the 16550 interrupt routine is 5 to 10 times faster (possibly more) than previous implementations. UARTs with larger FIFOs will execute even faster. Now boys and girls, it is the interrupt service routines that are faster. Nothing on Earth can make your modem go faster than it is capable of. However, faster interrupt service routines means less processor overhead.

Automatic FIFO sizing. The SIO2K drivers now support 16650, 16550A, 16750, 16850 and 16950 uarts. However, knowing the chip type does not necessarily mean the FIFO size is know. For example, the 16654 is the equivalent of four (or more) 16650A UARTS on a single chip. The normal 16650 UARTs have a 32 byte FIFO, but the UARTS on the 16654 have 64 byte FIFOs. Only probing will determine this.

The first time a UART is touched by an application the SIO2K drivers automatically probe the size of the FIFO and the found size is used. Note that a UART with no FIFOs can be thought of as having a FIFO size of 1 byte. My thanks to Sam Detweiler, of IBM, for the idea of probing for FIFO size.

Automatic Crystal Frequency. Most UARTs are capable of bit rates to 921600bps or more. However, on most serial devices, the bit rate is limited to 115200bps by the crystal oscillator attached to the UART. Many boards, like those from Lava, offer bit rates greater than by using faster crystal oscillator. The down side is one must tell the driver to use a bit rate of 28800 to really get a bit rate of.

The first time a UART is touched by an app, the SIO2K drivers probe the UART to determine if it is using a standard crystal oscillator or not. If the frequency is not standard, then the SIO2K drivers automatically adjust so that a request of 115200bps yields an actual bit rate of 115200bps. In addition, the maximum bit rate is adjusted and reported to applications that request the maximum bit rate. Boards like the Blue Heat from CTI use a 12x crystal and its top bit rate is 1382.4kbps.

Minimum touch during boot. The SIO2K drivers do not touch the UART hardware during boot. This was very difficult to do, while maintaining a compatible OS/2 serial driver. The "no touch" practically eliminates the possibility of traps occurring during the boot process when they are difficult to deal with. This does mean that a lot of processing will occur the first time a port is opened.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SIS900.OS2

SIS 900/7016 PCI Fast Ethernet Adapter.

  DEVICE=SIS900.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes Yes Yes

SMC1208.OS2

SMC EZ PCI COMBO Ethernet NIC.

DEVICE=SMC1208.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes Yes Yes

SMC8000.OS2

SMC Ethernet Adapter Family (SMC 8003, SMC 8013, SMC 8216, SMC 8416) NDIS driver.

DEVICE=SMC8000.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SMC9432.OS2

Network driver for SMC9432/TX (EtherPower II) 10/100 PCI NIC.

DEVICE=SMC9432.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes


SMCND.OS2

Acctron SMC 1211TX base 10/100 PCI ethernet card.

DEVICE=SMCND.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SMCPWR.OS2

SMC EtherPower for OS/2. NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/dec.zip.

DEVICE=SMCPWR.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SND16.SYS

The Snd16.sys driver is used by the MAD16 soundcard.

DEVICE=C:\Os2\Boot\Snd16.sys <parameters>

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SND931.SYS

OPTiSound 82C931 Sound Card Driver.

DEVICE=SND931.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SNDSCAPE.SYS

Ensoniq Soundscape VIVO (SND-ENSVIVO) AD1848 Audio OS/2 Device Driver.

DEVICE=SNDSCAPE.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SOCKETS.SYS

Network driver.

DEVICE=\Mptn\Potocol\Sockets.sys <parameter>

Parameters:

  • /c:value

Number of the COM port to which debug information should be sent. Value may be any valid COM port number . Default = 2

  • /v

Display the banner at boot time.

  • /uis:0

Turn off unique ID for select(). If this parameter is not set it defaults to ON .

  • /mem:value

Number of 4kbyte clusters allocated at initialization time. Value can be in the range from 30 to 32766 . Default = 75

  • /gdt:value

The maximum number of 64kbyte blocks the stack can allocate. Default = 80


TIP: According to IBM, the undocumented parameter /UIS:0 is for use on the 3172 Offload System to improve performance. This parameter is only intended for use on the 3172 Offload System, and turns off the process id : thread id processing on select() calls in the stack.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SOCKETSK.SYS

32bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak 13 for Warp 4. Part of the TCP/IP Ver. 4.x firewall.

DEVICE=SOCKETSK.SYS <parameter>

Parameter:

  • /V

Verbose, shows version-number

  • /MEM:#

amount of 4KB Clusters. Standard = 75; valid Range = 30 - 32766

  • /GDT:#

max. amount of 64KB Blocks the Stack can arrange; Standard = 80

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SOLO.SYS

Driver for ESS SOLO 1 based soundcards or motherboards.

DEVICE=SOLO.SYS <parameter>

Parameter:

  • /O:ENABLEWAVETABLE

If your installation includes an ES689 or ES692 WaveTable adding thid parameter to the config.sys line will cause the driver to use the wavetable as the primary midi.

  • /R:n

(where n is in milliseconds and between 1 and 32) this parameter allows the user to over ride the default timer resolution (5ms). Increasing this value will cause te driver to get dispatched less often and so use less cpu time, however this can cause the tempo to drag. Decreasing this value below 5 will cause the driver to use more cpu time and can interfere with other timers.

The IBM Mixer IOCTLS fully implemented in the Solo driver and this driver can be controlled using IBM's Warp Mixer. Available as Warpmix.zip

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SPCIIRQ.SYS

Change IRQ for PCI cards.

DEVICE=SPCIIRQ.SYS <parameter>

Parameter:

  • 0..255
  • 0..31
  • 0..7
  • 1..4 fr #A..#B
  • 0..15

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SPKRDD.SYS

The Speaker audio device driver provide support for playing digital audio waveform files on the standard PC speaker by using the MMPM/2 audio system. The speaker driver provides support for PCM waveform files that are (8-bit/16-bit, stereo/mono, 11Khz-44khz).

DEVICE=SPKRDD.SYS

BETTER DON'T USE IT, if you need (or want) sound on a regular base better buy one of those cheap soundcards.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SPX.SYS

Provides support for the Novell Netware SPX protocol.

DEVICE=C:\Netware\Spx.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SRVIFS.SYS

Part of the ThinIFS by IBM.

DEVICE=SRVIFS.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SSCOMA1.SYS

OS/2 Serial port driver with auto-detection of Serial Solutions PCI serial cards available at: http://www.brainboxes.com/

PCI card support, 115200 baud rate, ISA interrupt sharing cards with a shared interrupt status register, PCMCIA single function serial communications card support, the device driver is a replacement for the COM.SYS standard serial port driver. Up to 8 COM ports can be opened.

DEVICE=SSCOMA1.SYS <parameter>

Parameter:

  • /TTEMPLATE.PCI

This template describes a range of PCI coms cards and gives additional information to the driver about a specific card's non-standard features.

  • /L

List the detected PCI cards

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SSMDD.SYS

SSMDD.SYS is the Ring 0 device driver of the Sync/Stream Manager. The Sync/Stream Manager is comprised of two modules: SSMDD.SYS and SSM.DLL.

DEVICE=C:\MMOS2\SSMDD.SYS <parameter>

Parameter:

  • /S:sss

Specifies the number of streams that can be created at the same time. Values range from 1 through 64. The default value for machines with more than 8MB of memory is 12. The default value for machines with 8MB of memory or less is 6.

  • /P:ppp

Specifies the number of processes that can create streams at the same time. Values range from 1 through 64. The default value for machines with more than 8MB of memory is 12. The default value for machines with 8MB of memory or less is 6.

  • /H:hhh

Specifies the maximum amount of heap space (KB) that will be used. Values range from 16 through 256; the default value is 64.

  • /Q:qqq

Specifies the size of the event queue (per process). Values range from 2 through 1024; the default value is 64.

  • /E:eee

Specifies the number of events that can be enabled (per stream). Values range from 1 through 1024. The default value for machines with more than 8MB of memory is 32. The default value for machines with 8MB of memory or less is 20.

NOTE: The DEVICE=SSMDD.SYS statement must appear as the first Ring 0 stream handler statement in CONFIG.SYS.

Sync/Stream Resource Limits

  • The maximum number of streams is 64.
  • The maximum number of streams in a sync group is 64.
  • The maximum number of processes controlling streams is 64.
  • The maximum size of Sync/Stream Manager event queue per process is 1024 entries.

Example:

DEVICE=C:\MMOS2\SSMDD.SYS /S:64 /P:64 /H:256 /Q:1024 /E:1024

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SUMMA.SYS

Driver for Summa MM1201 format graphics tablet.

DEVICE=SUMMA.SYS <paremeter>

Parameter:

  • SERIAL=COMn - n=the serial port where the tablet is attached
  • /a - Sets the tablet to ABSOLUTE mode.
  • /r - Sets the tablet to RELATIVE mode (mouse emulation mode).
  • /xl:n - Sets the lower X limit of the tablet aperture, n = number.
  • /yl:n - Lower Y limit aperture.
  • /xh:n - Upper X limit aperture.
  • /yh:n - Upper Y limit aperture.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SVDISK.SYS

This is the driver for the Super Virtual Disk tool, which emulates a floppy drive in memory. Super Virtual Disk (SVDisk) is a 32-bit OS/2 device driver that emulates either a removable Virtual Disk (VDisk) or a removable Virtual Floppy (VFloppy) drive. By using OS/2's virtual memory management facility, SVDisk allows the entire contents of the disk to be swapped out via the paging mechanism. If the SVDisk is frequently accessed, OS/2 will keep the most recently used memory pages in RAM, SVDisk will essentially behave like a RAM Disk.

DEVICE=C:\SVDisk\SVDisk.sys <parameter>

Parameter:

  • n

the possible values for VFloppy device are: 360, 720, 1200, 1440, and 2880. Use 1520, 1840 and 3680 for XDF VFloppy. Since SVDisk defaults to a 1.44MB VFloppy device, the 1440 parameter can be omitted.

  • ssss

the size of the VDisk device. The possible values for ssss are from 16 to 131056 (16KB to 128MB.) The VDisk device will always round up the size into 16Kb boundary.

  • eeee

(optional) the root directory entries for the device. Default 64

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SWD1.SYS

SWD1.SYS is an OS/2 device driver for the Superwatchdog SWD1. The purpose is to detect and restart a hanging system by hardware. [2] [3]

SWITCH.OS2

Virtual PC for OS/2 Virtual Switch Driver. Virtual Switch Networking is the most powerful way of connecting your guest systems to an Ethernet network. It assigns a unique MAC address to your virtual machine, allowing it to use arbitrary network protocols and even act as a server. For other machine in the network, the virtual machine appears as an additional network station and it is indistinguishable from a "real" PC.

Note that while Virtual Switch Networking gives you more power and flexibility, it also means additional administration. The virtual machine uses a MAC address of its own and therefore needs a unique IP address etc. For typical TCP/IP requirements, the Shared Networking (NAT) is recommended.

DEVICE=SWITCH.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes

SYSINFO.SYS

This driver is needed foby the System Information Tool.

DEVICE=\NETFIN\SYSINFO.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SYSIOS2.SYS

This device driver is required by the System Information Tools provided in the "BonusPak" that comes with OS/2 Warp. If you plan on using these tools, do not delete this driver.

DEVICE=SYSIOS2.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

TC15DVR.SYS

Driver of Backmaster tape backup system.

DEVICE=TC15DVR.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

TC902X.OS2

Tamarack tmi TC9021 Ethernet MAC Adapter.

DEVICE=TC902X.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

TCPBEUI.OS2

This is the TCPBEUI (NetBIOS over TCP/IP) protocol driver.

DEVICE=C:\Ibmcom\Protocol\TcpBEUI.os2 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* * Yes Yes

TESTCFG.SYS

Test configuration device driver. TESTCFG.SYS is used during the install process to test your systems configuration. It is also used by the Selective Install process and during device driver installations.

DEVICE=C:\Boot\Testcfg.sys 

NOTE: Because this driver is used by the Selective Install process, it should not be deleted.

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

THESEUS2.SYS

Driver for the outdated memory analysis tool THESEUS2 by IBM. See DEVICE THESEUS5.SYS for an update.

DEVICE=THESEUS2.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

THESEUS5.SYS

Driver for the new memory analysis tool THESEUS3 by IBM downloadable at: ftp://ftp.boulder.ibm.com/ps/products/os2/fixes/v4warp/theseus3/

DEVICE=THESEUS5.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

TOKEN.SYS

This line differs depending on the network board you have.

DEVICE=TOKEN.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

TR2KNDIS.OS2

Texas Instruments TokenLite Compatible Token-Ring Adapter driver.

DEVICE=TR2KNDIS.OS2

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

TSRKRN.SYS

Module for Teles ISDN-Cards.

DEVICE=TSRKRN.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

UART.SYS

Basic UART device driver for DEVICE SIO2K.SYS.

DEVICE=UART.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ULTRADD.SYS

Device driver for Gravis Ultra Soundcards (discontinued)

DEVICE=ULTRADD.SYS <parameter>

Now FREE available at http://www.xs4all.nl/~sandervl free REGISTRATION KEY: 191181338

Parameter:

  • /P:,
  • /I:,
  • /D:,
  • /C:

(default = 28) (Ignored on a GUS PnP)

  • /J

(enable joystick)

  • /L

(always enable line-in)

  • /V

(verbose messages at startup)

  • /X

Displays initial Code & Data offsets (for debugging crashes)

The next switches are only for the GUS PnP (Pro) and other InterWave based soundcards:

  • /G

(enable GUS PnP (and Interwave) detection)

  • /R

(force PnP reset if your system doesn't have a PnP BIOS and you are NOT running OS/2 Warp 4.0) NOTE: /R seems to be necessary for the Reveal WaveXtreme

  • /E:XXXXXXX

(3 letters + 4 digits) (PnP ISA Vendor ID for Interwave based soundcards not sold by Gravis example (uses the GUS PnP Vendor ID): /E:GRV0001 The Vendor ID can be found in the iw.ini file)

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ULTRAVDD.SYS

Virtual Device driver for Gravis Ultra Soundcard for DOS (discontinued).

DEVICE=ULTRAVDD.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

UNICODE.SYS

Warp Server for E-Business Unicode Driver, enables unicode and locale support. Necessary for JFS.IFS.

DEVICE=UNICODE.SYS <parameter>

Parameter:

  • -L

Specifies that base locale setting is permanent. If selected \LANGUAGE\LOCALE\DEFAULT.LOC overrides the config.sys settings.

  • -x

Disables codepage conversion, must not be used with JFS.IFS

  • -V

Verbose

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No Yes

UPSMON.SYS

A free UPS monitor found on Hobbes to monitor a serial port for UPS events from APC's 'Back UPS' line of devices. Requires a serial port and special Non-standard Null-modem cable, usually provided by APC. The author provides infomation to construct this cable, if user needs one. Comes with a daemon that is started from the startup folder.

DEVICE=UPSMON.SYS

Platform Support

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

USLGENIO.SYS

Driver for the TV HappyPlayer, this driver can be used with TV cards which have Bt848, Bt849, Bt878 or Bt879 chipsets. This driver will not work with other TV applications.

DEVICE=C:\Apps\HappyTV\Uslgenio.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

V110.SYS

Module for Teles ISDN cards

DEVICE=V110.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

V8514A.SYS

Virtual device driver for 8514/A graphic cards used by DOS and Windows.

DEVICE=C:\Os2\Boot\V8514a.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VAD64.SYS

Virtual Device driver used by ATI 3D Rage graphic adapter cards. Gives support for DOS and WIN-OS/2.

DEVICE=C:\OS2\Vad64.sys
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

VAPM.SYS

Virtual device driver for Advanced Power Management used by DOS and Windows.

DEVICE=C:\Os2\Boot\Vapm.sys 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

VASPI.SYS

Adaptec ASPI device drivers for SCSI support.

DEVICE=VASPI.SYS

After you have installed the driver(s) correctly and have restarted your system, you will find a new entry in the DOS settings of DOS program objects, ASPI_ENABLE. This parameter defines, if ASPI is available in the session started from this object. The default is OFF, i.e. the ASPI interface is NOT available. Please change this parameter for all those program objects which you use to start your (DOS and WIN-OS/2) ASPI applications to ON.

The default (OFF) can be changed globally to ON by adding the option /ON to the line DEVICE=C:\OS2\VASPI.SYS in your CONFIG.SYS. In this case all DOS and WIN-OS/2 sessions have ASPI available automatically, but you can still disable ASPI for each program object individually.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VASACOM1.SYS

This driver was found on XTEL software configurations (version 5.6 (MINI X-TEL) and 6.0). This driver is for PLC usage.

Examples:

DEVICE=X:\OS2\VASACOM1.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

VASPIDD.SYS

Adaptec ASPI device drivers for SCSI support.

DEVICE=VASPIDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VAUDDRV.SYS

DOS Soundcard-Driver.

  DEVICE=VAUDDRV.SYS

Parameter:

  • ES16881$ for Soundcards with ESS 1688 chip
  • ES18681$ for Soundcards with ESS 1868 chip
  • ES18691$ for Soundcrads with ESS 1869 chip

NOTE: the parameter is the link between the OS2 driver and the DOS driver. The DOS driver inherits it's settings associated with the parameter.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VBOXGUEST.SYS

This driver is for OS/2 guests running inside a VirtualBox virtual machine. Included on the VirtualBox Guest Additions virtual CD image. Last version: 1.6.51 - 2008

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

VBOXMOUSE.SYS

This driver is for OS/2-eComStation running as guest under a VirtualBox virtual machine. It is the mouse pointer driver. This driver allows you to use the mouse directly inside the OS/2-eComStation virtual machine and switch back to the host machine without using the control-right key to release it. This driver is included on the VirtualBox Guest Additions virtual CD image.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

VBSAUDIO.SYS

Virtual DOS Driver for the C-Media CMI 8330 soundcard.

DEVICE=VBSAUDIO.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCADCMDR.SYS

Ctrl-Alt-Del Commander DOS FS Game Boost Driver.

DEVICE=VCADCMDR.SYS

NOTE: It is reported that fixpak 13 for Warp 4 doesn't work correctly with this driver.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCAPI.SYS

Teles Virtual DOS ISDN Capi Driver.

DEVICE=VCAPI.SYS

Note: Delete this driver when running Warp Server for E-Business or Fixpack 13 for Warp 4 otherwise you'll get a Trap.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCAPI20.SYS

ELSA Virtual DOS ISDN CAPI 2.0 Driver

DEVICE=VCAPI20.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCAPIAVM.SYS

AVM Virtual DOS Driver for the ISDN controllers B1 and Fritz.

DEVICE=VCAPIAVM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCDROM.SYS

Virtual device driver for CDRom drives used by DOS and Windows.

DEVICE=C:\Os2\Boot\Vcdrom.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCFOS.SYS

Gives support for CFOS in DOS and Windows.

DEVICE=C:\Cfos\Vcfos.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCGA.SYS

Virtual device driver for colour graphic adapters (CGA) used by DOS and Windows.

DEVICE=C:\Os2\Mdos\Vcga.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCOM.SYS

Virtual device driver for the serial Ports COMx, used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VCOM.SYS

NOTE: If you are using COM3 and/or COM4, add the appropriate parameters to the COM.SYS line above only. It is not necessary to add any parameters to this line. VCOM.SYS inherits its parameters from the COM.SYS line.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCOMPAT.SYS

Compatibility VDD. It hooks itself into the middle of several APIs and it contains a magical VM patcher, that is able to patch out some buggy routines on-the-fly, which means the user won't notice that he got a broken program.

DEVICE=C:\OS2\BOOT\VCOMPAT.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VCSHDD.SYS

Is needed for the video parts of MMOS2.

DEVICE=C:\Mmos2\Vcshdd.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VDISK.SYS

As in DOS, this driver installs a RAM disk. In this example, the RAM disk is 512k with the sectors and directories parameters set at the default level (64-byte sectors and 64 directory entries). With DOS, a RAM disk could significantly improve system performance, but because OS/2 handles your memory far more efficiently than DOS and has its own sophisticated caching routines, using a RAM disk is not recommended.

CAUTION: Because a RAM disk takes available memory away from OS/2, you may negatively impact system performance on systems with less than 12MB of RAM. Unless you have lots of RAM or have a very specific need, don't install a RAM disk.

NOTE: If you do install VDISK.SYS and you also have EXTDSKDD.SYS installed, VDISK.SYS must be placed after EXTDSKDD.SYS in your config.sys file. Check your on-line Command Reference for information on EXTDSKDD.SYS.

TIP: Better use the RAM(64).IFS by Karl Olson, see IFS.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VDOSTCP.SYS

Virtual device driver for the TCP/IP protocol used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VDOSTCP.SYS

Parameter:

  • /C:x

x is the number of the serial port.

TIP: If you don't need TCP/IP support in DOS sessions REM this line.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VDOSTCP.VDD

DOS API Driver for the TCP/IP protocol.

DEVICE=C:\OS2\BOOT\VDOSTCP.VDD

TIP: If you don't need TCP/IP support in DOS sessions REM this line.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VDPMI.SYS

Supports the DPMI memory access and is required to support all Windows applications.

DEVICE=C:\OS2\MDOS\VDPMI.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VDPX.SYS

This driver is the protected mode to real mode driver for DPMI applications.

DEVICE=C:\OS2\MDOS\VDPX.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VDTA.SYS

DOS Virtual device driver for the Data Transport Agent (DTA)

DEVICE=VDTA.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VEGA.SYS

Virtual device driver for EGA graphic cards used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VEGA.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VEMM.SYS

Used to support Extended Memory use in DOS and Windows programs.

DEVICE=C:\OS2\MDOS\VEMM.SYS <parameter>

Parameters:

  • /S=n

Sets the limit of EMS memory in blocks of 1024k. Default is 2.

  • /L=n

Size of conventional memory that can be remapped. Default is none.

  • /F=nnnn

Memory frame address to be used to map EMS. Default is AUTO.

NOTE: Settings you specify in a DOS session will override these parameters.

NOTE: The VEMM.SYS device must be listed in your config.sys file before the VXMS.SYS device.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VFDISK.SYS

Virtual Floppy Disk driver, it emulates a floppy drive in the memory. VFDISK by IBM is a virtual floppy disk device driver that allows track reading, writing, and formatting like a normal floppy disk (2.88 Mb,1.44 Mb,1.2 Mb, 360K, or 1.84Mb). This can be useful for automation of diskette image builds and for creating virtual floppies for one-time installs of distributed diskette images. Can be found on OS/2 ServicePak CD-ROMs, V 3.0 is maintained by Daniela Engert

DEVICE=C:\Os2\Boot\Vfdisk.sys <parameter>

Parameter:

  • 1 - 3.5" 1.44 Mb Floppy (default)
  • 2 - 5.25" 1.2 Mb Floppy
  • 3 - 3.5" 720 Kb Floppy
  • 4 - 3.5" 2.88 Mb Floppy
  • 5 - 5.25" 360K Floppy
  • 6 - 3.5" 1.84 Mb Floppy

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VGENAUD.SYS

Generic WinOS/2 Audio Driver R0 VDD component.

DEVICE=VGENAUD.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VHAPI.OS2

Paul Kurr wrote the following. "This provides for Virtual HLLAPI support within VDM's (not sure about VMB's). This allows DOS programs that use the HLLAPI to access the HOST sessions running at the OS/2 level under comm mgr. So you can actually watch your comm mgr sessions in one window and your DOS program in another while they interact."

DEVICE=VHAPI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VIPX.SYS

This driver enables the Novell Netware IPX support for DOS based Netware utilities.

DEVICE=C:\NETWARE\VIPX.SYS 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VKBD.SYS

Virtual device driver for the keyboard used by DOS and Windows.

DEVICE=C:\OS2\BOOT\Vkbd.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VLAN.OS2

OS/2 Virtual LAN Kernal.

DEVICE=VLAN.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

VLFN.SYS

Driver for long filenames in DOS sessions.

DEVICE=VLFN.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VLFNMEM.SYS

Driver for long filenames in DOS sessions.

DEVICE=VLFNMEM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VLTMODEM.SYS

Lucent Technologies Virtual DOS Modem Driver, V. 5.55 Beta 3. Available for FREE at http://www.drmartinus.de/notebook2/notebook.htm

DEVICE=VLTMODEM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMAD16.SYS

Virtual device driver for the MAD16 soundcard used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VMAD16.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMANWIN.SYS

This driver is used by your Graphic card to support Windows.

DEVICE=C:\OS2\MDOS\VMANWIN.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMDRV.SYS

This driver is used by Microsoft Virtual PC. Called OS/2 Additions Driver.

DEVICE=C:\VM\VMDRV.SYS

Parameters:

  • /Q

Quiet Mode: Disable messages at boot.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

VMGAX64.SYS

Virtual device driver for Matrox graphic cards.

DEVICE=C:\MGA\OS2\VMGAX64.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMMOUSE.SYS

This is Mouse Driver included on Microsoft Virtual Machine Additions for OS/2. This one allows to automatic switch from Windows to OS/2 running on Microsoft Virtual PC and viceversa without pressing the host key.

DEVICE=C:\VM\VMMOUSE.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

VMODEM.SYS

Ray Gwinn's Virtaul Modem device driver.

DEVICE=VMODEM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMONO.SYS

Virtual device driver for monochrome graphic cards used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VMONO.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMOUSE.SYS

Virtual device driver for the mouse used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VMOUSE.SYS 

NOTE: If you don't have this line (or you REM'd it), you will not have mouse support in your DOS sessions.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMPU401.SYS

Virtual DOS MPU401 driver.

DEVICE=VMPU401.SYS

Parameter:

  • MPU4011$

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VMVDD.SYS

This driver comes with Microsoft Virtual Machine Additions for OS/2 for MS Virtual PC 2007.

DEVICE=x:\VM\VMVDD.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

VNETAPI.OS2

This driver is part of the File and Print client for OS/2.

Paul Kurr wrote: "This sets up the virtual network support API within the VDM's (not VMB's). This allows DOS programs running within a VDM to "see" that the network is loaded, and interact with it (get/set redirections and such). If VDOLANAPI support is required in a VMB the device driver VNETAPI.SYS needs to be loaded within the VMB (this is found in \IBMLAN\NETPROG)."

DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VNETAPI.SYS

Paul Kurr wrote: "This sets up the virtual network support API within the VDM's (not VMB's). This allows DOS programs running within a VDM to "see" that the network is loaded, and interact with it (get/set redirections and such). If VDOLANAPI support is required in a VMB the device driver VNETAPI.SYS needs to be loaded within the VMB (this is found in \IBMLAN\NETPROG)."

DEVICE=VNETAPI.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VNPX.SYS

This device driver works _with_ your systems math coprocessor. If you do not have a math coprocessor, this driver will not load. Some have suggested that if you add it to your config.sys you will see an enhancement in your systems performance. Not so. There is no reason for it to be added to your config.sys file. IF YOU HAVE A MATH COPROCESSOR, OS/2 WILL LOAD THIS DRIVER AUTOMATICALLY. If you add it to your config.sys file, a second copy of the driver will be loaded. In doing so, many have reported that no DOS programs would run. DO NOT ADD THIS STATEMENT TO YOUR CONFIG.SYS FILE.

DEVICE=VNPX.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VP9100.SYS

Virtual device driver for Weitek P9100 based graphic cards used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VP9100.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VP91VGA.SYS

Virtual device driver for Weitek P9100 based graphic cards used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VP91VGA.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VPC.SYS

Virtual Dos Driver of Process Commander.

DEVICE=VPC.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VPCAPP.SYS

InnoTek Virtual PC for OS/2 Application driver. Virtual PC for OS/2 allows you to run additional operating systems on top of your OS/2 system. It is based on Virtual PC by Connectix Corporation, delivering the most advanced virtualization technology available.

DEVICE=VPCAPP.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VPCMCIA.SYS

This driver gives support for PCMCIA cards in DOS and Windows sessions.

DEVICE=C:\OS2\BOOT\VPCMCIA.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VPICPARM.SYS

Some applications like PCAS (and some terminal emulators) have problems sharing IRQ9 in a VDM. Since the DOS Virtual Device drivers are not loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added starting with Warp 3 FixPak 38 and Warp 4 FixPak 8.

To prevent sharing of IRQ9 in a VDM, add the device in config.sys: Next, in the settings for the program that requires exclusive access to IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON. When you next boot your system, VDMs will not share IRQ

DEVICE=VPICPARM.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VPRPMI.SYS

Private video PMI virtual device driver. GRADD Display Drivers - generic DOS part. Some laptops, including those that use the Intel i845, the S3 Savage/IX or S3 SuperSavage chipsets, will require an additional driver for full LCD BIOS support. When booting with the LCD panel active, if the OS/2 System object does not display refresh rate selection, and/or displays video modes larger than your LCD panel, then you need this driver. This driver should not be required for the"Convenience Pak" releases of OS/2 Warp 4 and WSeB.

DEVICE=C:\OS2\MDOS\VPRPMI.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VSHELL.SYS

This dricver loads the Novell Netware network shell. It is automatically used for all DOS and Windows sessions that require it.

DEVICE=C:\NETWARE\VSHELL.SYS <parameter>

Parameters:

  • Value can be Global or Local .
  • Default = Global
  • :Li. Global

All DOS, Windows and OS/2 sessions set up for global login support share a single login to a Netware server. Drive mappings and port captures from one session apply to all the other sessions. This is useful in environments where the number of connections is carefully monitored. :Li. Local All DOS and Windows sessions set up for private login support have their own logins to a Netware server. Drive mappings and port captures from one session do not apply to the other sessions. This is useful in environments where users need logins from DOS and Windows sessions to be separate from logins from OS/2 sessions.

You can change this parameter also in the DOS/Windows settings of each Program object.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VSIO.SYS

Virtual device driver for the serial ports COMx used by DOS and Windows. This is a replacement for the Vcom.sys driver.

DEVICE=C:\Os2\Boot\VSIO.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VSIO2K.SYS

Excellent replacement driver for VCOM.SYS. If you utilize communications software on a regular basis at high speeds (e.g. 14,400), then the SIO2K drivers are the way to go. Be sure you have REM'd out VCOM.SYS when using. SIO2K.SYS and VSIO2K.SYS are Shareware, not Freeware. See also SIO2K.SYS.

DEVICE=VSIO2K.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VSND931.SYS

OPTiSound 82C931 Virtual Audio Card Driver.

DEVICE=VSND931.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VSVGA.SYS

Virtual device driver for SVGA graphic cards used by DOS and Windows.

DEVICE=x:\OS2\BOOT\VSVGA.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VVGA.SYS

Virtual device driver for VGA graphic cards used by DOS and Windows.

DEVICE=x:\OS2\BOOT\VVGA.SYS 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VVTCAPT.SYS

TVShow Video Capturing driver. Available at: http://os2.kiev.ua

DEVICE=VVTCAPT.SYS

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VW32S.SYS

Supplies support for the WIN32S Windows APIs. Only needed for Windows programs that use WIN32S APIs.

DEVICE=C:\OS2\MDOS\VW32S.SYS

NOTE: This driver has no parameters.

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VWCAT.SYS

This driver is used by the Watchcat task killer.

DEVICE=x:\Watchcat\Vwcat.sys 

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VWIN.SYS

This driver provides seamless Windows support in Win-OS2.

DEVICE=C:\OS2\MDOS\VWIN.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VX00.SYS

Old version of Ray Gwinn's communication driver, needed by some DOS-VDM programs.

TIP: by Mike Luther To load it together with the later version of VMODEM.SYS from SIO2K these entries must be done:

rem device=C:\sio2k\esp.sys logfile=C:\sio2k\sio2k.log NoPause
device=C:\sio2k\uart.sys logfile=C:\sio2k\sio2k.log
device=C:\sio2k\vsio2k.sys logfile=C:\sio2k\vsio2k.log _ vIrqList(2=3,1=4,3=12)
device=C:\sio2k\vx00.sys
device=C:\sio2k\vmodem.sys logfile=C:\sio2k\sio2k.log NoPause nPorts=1
device=C:\sio2k\sio2k.sys logfile=C:\sio2k\sio2k.log 
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VXGA.SYS

Virtual device driver for XGA graphiccards used by DOS and Windows.

DEVICE=C:\OS2\BOOT\VXGA.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VXMS.SYS

Supports Extended Memory in DOS and Windows applications. XMS allows DOS programs to access more than one MB of memory.

DEVICE=C:\OS2\MDOS\VXMS.SYS <parameter>

Parameters:

  • /UMB

Upper memory block support in DOS sessions.

  • /NOUMB

No upper memory block support.

  • /XXMLIMIT=m,n

Indicates the total system wide memory limit.

  • /HMAMIN=m

Sets the minimum request size for high memory, from 1k to 63k.

  • /NUMHANDLES=m

Sets the number of handles in each DOS session, from 1 to 128.

NOTE: The VXMS.SYS device must be listed in your config.sys file after the VEMM.SYS device.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VYMF724.SYS

Virtual DOS YAMAHA YMF724 sound card driver.

DEVICE=VYMF724.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WACOMOS2.SYS

Pen for OS/2 Device Driver for Wacom SD-501.

DEVICE=WACOMOS2.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WARPDRVR.SYS

Driver for TVShow.

DEVICE=WARPDRVR.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WATCHCRD.SYS

WATCHCRD.SYS is an OS/2 device driver for the CEWS WatchCard. The purpose is to detect and restart a hanging system by hardware. [4], [5]

WATCHCAT.SYS

This driver is used by the Watchcat task killer.

DEVICE=x:\WATCHCAT\WATCHCAT.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WCAST.SYS

This driver gives support for all PCI Hauppauge TV-cards. The USB versions are NOT supported.

DEVICE=x:\MMOS2\WCAST.SYS <parameter>

Parameter:

  • /M=xxxxx - memory address
  • /I=xx - Interrupt address
  • /P=xxx - IO Port address
  • /N=x - Device Number
  • /D=x - DMA Channel
  • /F=Filename - Initialisation file
  • /X or /X1 - Force install, access hardware if present
  • /X2 - Force install, access hardware even if not present
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WCPCI.SYS

WatchCard PCI Watchdog driver by Juergen Dittmer.

NOTE: This driver is not supported by the manufacturer and the author of this software is not related to this company.

DEVICE=WCPCI.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WIPEDD.SYS

BocaSoft WipeOut/2 screen saver program.

DEVICE=WIPEDD.SYS
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

XF86SUP.SYS

Driver needed by XFree86/OS2, You will be unable to run XFree86/OS2 without the XF86sup.sys driver.

DEVICE=x:\XFree86\lib\XF86Sup.sys 

TIP: See the excellent guide by Rob Fargher in Voice 2/99 for installing XFREE.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

XSMOUSE.SYS

This driver enables you to send absolute mouse events into the system. It provides an application programming interface that conforms to the standard DosRead and DosWrite functions and as such may be easily used from rexx procedures using the charin and charout functions. It has been especially designed to ease the development and integration of touch screen solutions into the system. Created by Wim Brul.

DEVICE=C:\OS2\BOOT\XSMOUSE.SYS

Example:

DEVICE=C:\OS2\BOOT\MOUSE.SYS STYPE=XSMOUSE$

Platform Support:

OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No Yes Yes

XMOUSE.SYS

Enhanced mouse driver by Martin Lafaix. It is intended to replace the mouse.sys driver as included in the scrollms.exe package.

DEVICE=XMOUSE.SYS

Adds support for the following mouse types:

  • Intellimouse Explorer (five buttons + wheel)
  • Logitech MouseMan (three buttons)
  • Logitech M-BJ58 Optical scroll mouse (three buttons + wheel)
  • Logitech M-RG45 Cordless wheel mouse (three buttons + wheel)
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

YMF724.SYS

PCI Yamaha YMF724 (DS-1) driver.

DEVICE=YMF724.SYS

TIP: Together with Daniela Engerts patchymf.zip the driver can support some more chips.

These are PCI vendor ID: 1073h (Yamaha)

  • YMF724D (DS-1) 0004h
  • YMF724F (DS-1) 000Dh
  • YMF740C (DS-1L) 000Ch
  • YMF744B (DS-1S) 0010h
  • YMF754 (DS-1E) 0012h

If you need a mixer for it, there is the Free 724mix a simple mixer with a VIO-interface for YMF724-based sound cards. It also supports YMF724 compatible chips such as YMF740, YMF744 and YMF754. Available at http://os2.ru/projects/724mix/index.phtml.en

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes