[[ header START ]]

Welcome to OS2.GURU site! (eComStation.RU)

Select your language: Russian English Deutch Spanish Italian Portuguese Czech Polish French

Frequently asked questions and answers:
telegram

Форум обсуждение

telegram

Send message

telegram

[ +7-981-8529467 (Санкт-Петербург)

telegram

t.me/os2_guru

eComStation.RU


ru · en · de · es · it · pt · cz · pl · fr
OS/2 is a greatly different operating system for PC (ArcaOS, eComStation, IBM OS/2 Warp)
Applications, news, reviews, support of users, hardware, questions and answers.
 
[What is OS/2?  News  Install  Update  
 
 
Usage  Future  Community  Projects  

How to buy
russian OS/2 apps?

The concept of
OS/2 development

(Map of the site)

 
 
[[ head-3-search ]]

Database of OS/2 compatible hardware

[[ head-3-search END ]]

 
Update

 
Applications

 
Advantages:

 
For developer:

 
(Пайпы программ)

 
Companies:

 
History:

 
(Бонусы)

 
Advice:

 
(Барьеры и решения)

 
Technologies:

 
(Применение в науке, лаборатории, ..)

 

 
Solutions

 
New eComStation:

 
Future:

 
(Ссылки на другие сайты)

 
(Картинка дня)

 
OS/2 artefacts:

 
Gadgets:

ConfigTool 1.0.0 database - DEVICES

[ConfigTool page] [Table of contents] [Index]
DEVICE
DEVICE $ICPMOS2.SYS
DEVICE ACCND.OS2
DEVICE ACECAD.SYS
DEVICE AD1816DD.SYS
DEVICE AFINET.SYS
DEVICE AFINETK.SYS
DEVICE AFNB.SYS
DEVICE AFOS2.SYS
DEVICE AMOUSE.SYS
DEVICE APM.SYS
DEVICE ARTPAD.SYS
DEVICE ASP4CORE.SYS
DEVICE ASP4JOY.SYS
DEVICE ASP4OS2.SYS
DEVICE ASPIPFA.SYS
DEVICE ASPIROUT.SYS
DEVICE ASPITAPE.SYS
DEVICE ATI0.SYS
DEVICE ATIM64.SYS
DEVICE AVMB1.SYS
DEVICE BIPMAC.OS2
DEVICE BIPPDD.OS2
DEVICE BTSSCSI.SYS
DEVICE BUSAUDIO.SYS
DEVICE CAPI.DLL
DEVICE CAPI20.DLL
DEVICE CBENDIS.OS2
DEVICE CBEODI.OS2
DEVICE CCAX.SYS
DEVICE CCAXE.SYS
DEVICE CD1400.SYS
DEVICE CDBASPI.SYS
DEVICE CDMF.SYS
DEVICE CDMGRDRV.SYS
DEVICE CDROMMGR.DMD
DEVICE CE3NDIS.OS2
DEVICE CFMASPI.SYS
DEVICE CFOS.SYS
DEVICE CFOS20.SYS
DEVICE CLEANUP.SYS
DEVICE COM.SYS
DEVICE COM02.SYS
DEVICE CPASPI.SYS
DEVICE CPPOPA3.SYS
DEVICE CPPPAN40.SYS
DEVICE CPQNF3.SYS
DEVICE CPUMONP.SYS
DEVICE CTCDROM.DMD
DEVICE CWAUDIO.SYS
DEVICE CWGUTIL.SYS
DEVICE CWMPU401.SYS
DEVICE DC21X4.OS2
DEVICE DCF2CDE.SYS
DEVICE DCF2MGR.SYS
DEVICE DCF2PDD.SYS
DEVICE DCF77.SYS
DEVICE DDE4XTRA.SYS
DEVICE DE528.OS2
DEVICE DES.SYS
DEVICE DISKFIT.SYS
DEVICE DLKFET.OS2
DEVICE DLKPCI.OS2
DEVICE DOS.SYS
DEVICE DRVOCDB.SYS
DEVICE DRVOPPQT.SYS
DEVICE DRVOQ117.SYS
DEVICE DSS1C20X.SYS
DEVICE DSS1TE.SYS
DEVICE E100B.OS2
DEVICE EC2T.OS2
DEVICE ECRDRV.SYS
DEVICE EL59X.OS2
DEVICE EL90X.OS2
DEVICE ELNK3.OS2
DEVICE ELPC3.OS2
DEVICE ELPC3X.OS2
DEVICE ELSA.SYS
DEVICE EP325.OS2
DEVICE EP427.OS2
DEVICE EQNKRCSH.EXE
DEVICE EQNKVKBD.SYS
DEVICE EQNRCSH.EXE
DEVICE EQNVKBD.SYS
DEVICE ES1371.SYS
DEVICE ES1688DD.SYS
DEVICE ES1868DD.SYS
DEVICE ES1869DD.SYS
DEVICE ES198X.SYS
DEVICE ESP.SYS
DEVICE ET32ND.OS2
DEVICE ET32ND.SYS
DEVICE EXMOUSE2.SYS
DEVICE EXP16.OS2
DEVICE EXTDSKDD.SYS
DEVICE FASTNIC.OS2
DEVICE FETND.OS2
DEVICE FLSH2MTD.SYS
DEVICE FMD.SYS
DEVICE FMRADIO.SYS
DEVICE FTDVR.SYS
DEVICE FWIP.SYS
DEVICE FXWRAP.SYS
DEVICE GAMEDD.SYS
DEVICE GAMEPRT2.SYS
DEVICE GENSCSI.SYS
DEVICE GRADD.SYS
DEVICE HDLC.SYS
DEVICE HRTIMER.SYS
DEVICE IAS_DD.OS2
DEVICE IBMTOK.OS2
DEVICE ICHSND.SYS
DEVICE IDEHDD.SYS
DEVICE IFNDIS.SYS
DEVICE IFNDISNL.SYS
DEVICE INET.SYS
DEVICE IP22DRV.SYS
DEVICE IPSEC.SYS
DEVICE IPX.SYS
DEVICE IRCOMM.SYS
DEVICE IRDA_DD.OS2
DEVICE IRDA_PHY.OS2
DEVICE IRDD.SYS
DEVICE IRDNDIS.OS2
DEVICE IRMAC.OS2
DEVICE ISDNAPI.SYS
DEVICE ISDNC20X.SYS
DEVICE ISO8208.SYS
DEVICE IWZPAN40.SYS
DEVICE JJSCDROM.DMD
DEVICE KDBNET.SYS
DEVICE KILLER.SYS
DEVICE KMGAX64.SYS
DEVICE KOPYKAT.SYS
DEVICE KSCOM.SYS
DEVICE KTC40.OS2
DEVICE L100.OS2
DEVICE LANDD.OS2
DEVICE LANDD.SYS
DEVICE LANDLLDD.OS2
DEVICE LANDLLDD.SYS
DEVICE LANMSGDD.OS2
DEVICE LANPDD.OS2
DEVICE LANPDD.SYS
DEVICE LNE100.OS2
DEVICE LNEPCI.OS2
DEVICE LOG.SYS
DEVICE LPT49.SYS
DEVICE LPTDD.SYS
DEVICE LRCOM.SYS
DEVICE LRPAR.SYS
DEVICE LSL.SYS
DEVICE LTMDMOS2.SYS
DEVICE MACMYWI.OS2
DEVICE MAESTR2E.SYS
DEVICE MD5.SYS
DEVICE MEDIAOS2.SYS
DEVICE MEIO0437.SYS
DEVICE MIDI.SYS
DEVICE MODISK.DMD
DEVICE MODISK.SYS
DEVICE MOUSE.SYS
DEVICE MOUSE2.SYS
DEVICE MPU401.SYS
DEVICE MVPRODD.SYS
DEVICE MWAVEDD.SYS
DEVICE NE2000.OS2
DEVICE NETBEUI.OS2
DEVICE NETBIOS.OS2
DEVICE NETBIOS.SYS
DEVICE NETFLX3.OS2
DEVICE NMPIPE.SYS
DEVICE NOVAQOS2.SYS
DEVICE NOVASPI.SYS
DEVICE NPSERVER.SYS
DEVICE NTR2000.SYS
DEVICE NULLNDIS.OS2
DEVICE NWREQ.SYS
DEVICE ODI2NDI.OS2
DEVICE OPL3.SYS
DEVICE OPL3SA.SYS
DEVICE OPL4D.SYS
DEVICE OPTICAL.DMD
DEVICE OS2.SYS
DEVICE OS20MEMU.SYS
DEVICE OS2CDROM.DMD
DEVICE OS2OGL.SYS
DEVICE P6K7MTRR.SYS
DEVICE P9100.SYS
DEVICE PANEL.SYS
DEVICE PARADISE.SYS
DEVICE PAUSE.SYS
DEVICE PC.SYS
DEVICE PC100.OS2
DEVICE PCCOM2.SYS
DEVICE PCCOM4.SYS
DEVICE PCCOM8.SYS
DEVICE PCIND.OS2
DEVICE PCIOS2.SYS
DEVICE PCKBD.SYS
DEVICE PCLOGIC.SYS
DEVICE PCM2FLSH.SYS
DEVICE PCM2SRAM.SYS
DEVICE PCMNICCS.OS2
DEVICE PCMSSDIF.SYS
DEVICE PCNTND.OS2
DEVICE PDITOU01.SYS
DEVICE PDITOU02.SYS
DEVICE PMAC.OS2
DEVICE PMDD.SYS
DEVICE PNPND.OS2
DEVICE POINTDD.SYS
DEVICE PPPEMYWI.OS2
DEVICE PRANDIS.OS2
DEVICE PROTMAN.OS2
DEVICE PTDVR.SYS
DEVICE QAP2DRVR.SYS
DEVICE QCAMM.SYS
DEVICE QCOM.SYS
DEVICE QUICKCAM.SYS
DEVICE R0STUB.SYS
DEVICE RDRHELP.200
DEVICE REFPART.SYS
DEVICE RMAUDIO.SYS
DEVICE RODENT.SYS
DEVICE ROUTE.SYS
DEVICE RSJSCSI.SYS
DEVICE RSMVDWO.SYS
DEVICE RTFND.OS2
DEVICE RTSND.OS2
DEVICE RTSOS2.SYS
DEVICE RZT2BOOT.SYS
DEVICE S0TE.SYS
DEVICE SB16D2.SYS
DEVICE SBAWED2.SYS
DEVICE SBLIVE16.SYS
DEVICE SBLIVE32.SYS
DEVICE SBMIX.SYS
DEVICE SCANHP1.SYS
DEVICE SCANOS2.SYS
DEVICE SCAX.SYS
DEVICE SCAXE.SYS
DEVICE SDDHELP.SYS
DEVICE SDI_ASPI.SYS
DEVICE SDI_CISA.SYS
DEVICE SDI_IDE.SYS
DEVICE SDI_LPT.SYS
DEVICE SDI_SCSI.SYS
DEVICE SESDD32.SYS
DEVICE SIO.SYS
DEVICE SIO2K.SYS
DEVICE SIS900.OS2
DEVICE SMC9432.OS2
DEVICE SMCND.OS2
DEVICE SMCPWR.OS2
DEVICE SND16.SYS
DEVICE SNDSCAPE.SYS
DEVICE SOCKETS.SYS
DEVICE SOCKETSK.SYS
DEVICE SOLO.SYS
DEVICE SPKRDD.SYS
DEVICE SPX.SYS
DEVICE SRVIFS.SYS
DEVICE SSCOMA1.SYS
DEVICE SSMDD.SYS
DEVICE SVDISK.SYS
DEVICE SYSINFO.SYS
DEVICE SYSIOS2.SYS
DEVICE TC15DVR.SYS
DEVICE TCPBEUI.OS2
DEVICE TESTCFG.SYS
DEVICE THESEUS2.SYS
DEVICE THESEUS5.SYS
DEVICE TOKEN.SYS
DEVICE TOUCH.SYS
DEVICE TR2KNDIS.OS2
DEVICE TSRKRN.SYS
DEVICE UART.SYS
DEVICE ULTRADD.SYS
DEVICE UNICODE.SYS
DEVICE UPSMON.SYS
DEVICE USBAUDIO.SYS
DEVICE USBCOM.SYS
DEVICE USBKBD.SYS
DEVICE USBMOUSE.SYS
DEVICE USBPRT.SYS
DEVICE USBRESMG.SYS
DEVICE USLGENIO.SYS
DEVICE VCSHDD.SYS
DEVICE VDISK.SYS
DEVICE VFDISK.SYS
DEVICE VIAUDD.SYS
DEVICE W940ND.OS2
DEVICE WATCHCAT.SYS
DEVICE WCAST.SYS
DEVICE WIN32K.SYS
DEVICE XF86SUP.SYS
DEVICE YMF724.SYS

DEVICE
[Table of contents] [Index] [DEVICES]

As Device Drivers can reside everywhere a fully qualified path is necessary for correct operation.

DEVICE $ICPMOS2.SYS
[Table of contents] [Index] [DEVICES]

Power Management Driver for PCMCIA

<<=ATTENTION=>> Must be after all other listed drivers in the config.sys.

DEVICE ACCND.OS2
[Table of contents] [Index] [DEVICES]

ACCTON EN1207D Series Ethernet PCI Adapter NDIS driver

http://www.accton.com/accton/products/adapters/en1207d_wol/base.phpl

Network card in IBM's netvista 6269N2G

DEVICE ACECAD.SYS
[Table of contents] [Index] [DEVICES]

Driver for the ACECATIII digitizing board.

for working DEVICE=E:\OS2\BOOT\MOUSE.SYS STYPE=ACECAD$ must be added

DEVICE AD1816DD.SYS
[Table of contents] [Index] [DEVICES]

Analog Devices AD1816 Soundport Driver

Parameter:

/N:$strng$ - Device driver name assigned by MINSTALL
/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
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

DEVICE AFINET.SYS
[Table of contents] [Index] [DEVICES]

Part of the TCP/IP Protocol Drivers

DEVICE AFINETK.SYS
[Table of contents] [Index] [DEVICES]

32bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fixpak13 for Warp 4

Part of the TCP/IP Ver. 4.x firewall

Parameter:

/V Verbose, shows version-number

DEVICE AFNB.SYS
[Table of contents] [Index] [DEVICES]

Basic-NetBIOS-Socket-Support Driver

DEVICE AFOS2.SYS
[Table of contents] [Index] [DEVICES]

Part of the TCP/IP Protocol Drivers

Parameter:

/V Verbose, shows version-number

DEVICE AMOUSE.SYS
[Table of contents] [Index] [DEVICES]

Mouse Driver for Wheel Mices

like e.g. the:
Logitech Pilot Mouse+
Logitech Mouse Man+
Logitech Optical Wheel Mouse
Microsoft Intellimouse
IBM Scrollpoint Mouse

<<=NOTE=>> With Amouse installed XFree86 refuses to work

Available for FREE at http://home.t-online.de/home/klaus.breining/

DEVICE APM.SYS
[Table of contents] [Index] [DEVICES]

Device driver for ADVANCED POWER MANAGEMENT system. See also RUN APMDAEMN.EXE

Parameter:

/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).

▒╛. Б═╙╕╔:

RUN APMDAEMN.EXE

DEVICE ARTPAD.SYS
[Table of contents] [Index] [DEVICES]

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

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

DEVICE ASP4CORE.SYS
[Table of contents] [Index] [DEVICES]

Vortex AU8820 Core OS/2 driver

DEVICE ASP4JOY.SYS
[Table of contents] [Index] [DEVICES]

Vortex AU8820 OS/2 Joystick driver

DEVICE ASP4OS2.SYS
[Table of contents] [Index] [DEVICES]

Vortex AU8820 OS/2 MMPM/2 driver

DEVICE ASPIPFA.SYS
[Table of contents] [Index] [DEVICES]

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 ASPIROUT.SYS
[Table of contents] [Index] [DEVICES]

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

DEVICE ASPITAPE.SYS
[Table of contents] [Index] [DEVICES]

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 ATI0.SYS
[Table of contents] [Index] [DEVICES]

Driver for ATI 3D Rage

DEVICE ATIM64.SYS
[Table of contents] [Index] [DEVICES]

Driver for ATI 3D Rage

DEVICE AVMB1.SYS
[Table of contents] [Index] [DEVICES]

Driver for the AVM Active ISDN-Controller B1

Parameter:

/$- If old programs needs the old naming convention (like an outdated CFOS).

<<=NOTE=>> The passive AVM-Cards (like the Fritzcard) aren't supported by AVM with OS/2 Drivers.

DEVICE BIPMAC.OS2
[Table of contents] [Index] [DEVICES]

Driver for the IBM Active 2000 ISDN card

DEVICE BIPPDD.OS2
[Table of contents] [Index] [DEVICES]

Driver for the IBM Active 2000 ISDN card

DEVICE BTSSCSI.SYS
[Table of contents] [Index] [DEVICES]

driver for Back Again/2 SCSI tape support

DEVICE BUSAUDIO.SYS
[Table of contents] [Index] [DEVICES]

C-Media CMI 8330 Soundcard driver (AD 8329 Chip)

Parameters:

/D:n DMA channel, n=0,1 or 3

/I:n Interrupt, n=5,7,9,10,11 or 12

DEVICE CAPI.DLL
[Table of contents] [Index] [DEVICES]

CAPI-DLL v.1.1 16-bit for ISDN Cards

DEVICE CAPI20.DLL
[Table of contents] [Index] [DEVICES]

CAPI-DLL v.2.0 32-bit for ISDN Cards

DEVICE CBENDIS.OS2
[Table of contents] [Index] [DEVICES]

Xircom CardBus Ethernet 10/100 Adapter

DEVICE CBEODI.OS2
[Table of contents] [Index] [DEVICES]

Xircom CardBus Ethernet 10/100 Adapter OS/2 Netware ODI driver

DEVICE CCAX.SYS
[Table of contents] [Index] [DEVICES]

Device driver for HST Janus Saphire ISDN Cards and CAPI v.1.1/2.0 for 1TR6(German) protocol

DEVICE CCAXE.SYS
[Table of contents] [Index] [DEVICES]

Device driver for HST Janus Saphire ISDN Cards and CAPI v.1.1/2.0 for DSS-1 (ETSI) protocol

DEVICE CD1400.SYS
[Table of contents] [Index] [DEVICES]

RISC COM CD1400 Device driver by DECISION-COMPUTER INTERNATIONAL Co.,LTD

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 ).

DEVICE CDBASPI.SYS
[Table of contents] [Index] [DEVICES]

CD-TEK driver to access easily the PIONEER DRM-1804X autochange CD-ROM device

DEVICE CDMF.SYS
[Table of contents] [Index] [DEVICES]

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
DES. Many to don't consider it as strong an algorithm as Blowfish or Ideal, widely available competitors to this protocol.

DEVICE CDMGRDRV.SYS
[Table of contents] [Index] [DEVICES]

Driver of the FREE CD-Rom Manager for Plextor SCSI CD-ROM drives. Developed by Markus and Christian Mueller. Available at http://ourworld.compuserve.com/homepages/mjm5

DEVICE CDROMMGR.DMD
[Table of contents] [Index] [DEVICES]

CD-ROM device manager which prevents subsequent requests to different slots of a CD changer

<<=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.

DEVICE CE3NDIS.OS2
[Table of contents] [Index] [DEVICES]

Xircom Ethernet Adapter 10/100

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.

DEVICE CFMASPI.SYS
[Table of contents] [Index] [DEVICES]

Driver for the TWAIN Scanner Module by CFM (Computer for Mankind)

DEVICE CFOS.SYS
[Table of contents] [Index] [DEVICES]

'cFos' device driver receives the usual modem commands, the so-called AT commands from the communication programs and turns them into the corresponding ISDN CAPI commands. ISDN CAPI responses are turned into modem responses of the same meaning, so that the communication programs 'understand' them.

As you can enter any equipment names (e.g.: ISDN1) or several COM ports (a maximum of two in the shareware version, up to 30 in 'cFos Professional'). Be careful not to enter COM ports that actually exist as hardware and are in use (e.g. a COM port for your mouse).

<<=NOTE=>> The CFOS.SYS driver should be loaded after drivers for serial interfaces (COM.SYS oder SIO.SYS) and after the CAPI driver.

DEVICE CFOS20.SYS
[Table of contents] [Index] [DEVICES]

CAPI 2.0 CFOS device driver, for more details see DEVICE CFOS.SYS

DEVICE CLEANUP.SYS
[Table of contents] [Index] [DEVICES]

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.src

DEVICE COM.SYS
[Table of contents] [Index] [DEVICES]

Lets you use the communications ports COM1 and COM2. If you want to use COM3 or COM4 or change the IRQ of any COM port, see <<=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.

<<=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)

DEVICE COM02.SYS
[Table of contents] [Index] [DEVICES]

For IBM PS/2 model 90 & 95 only.

Lets you use the communications ports COM1 and COM2. See DEVICE COM.SYS

DEVICE CPASPI.SYS
[Table of contents] [Index] [DEVICES]

Driver for scanner access by Impos/2

DEVICE CPPOPA3.SYS
[Table of contents] [Index] [DEVICES]

Driver for IBM Visual Age C++ (Version 3)

DEVICE CPPPAN40.SYS
[Table of contents] [Index] [DEVICES]

Device driver for Visual Age for C++ 4.0 performance analysis

DEVICE CPQNF3.SYS
[Table of contents] [Index] [DEVICES]

OS/2 ODI Driver for Compaq NETFLEX-3/NETELLIGENT Controllers

DEVICE CPUMONP.SYS
[Table of contents] [Index] [DEVICES]

PU Monitor Plus, from Bon Ami Software

<<=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.

DEVICE CTCDROM.DMD
[Table of contents] [Index] [DEVICES]

Driver for Unite CD-Maker

DEVICE CWAUDIO.SYS
[Table of contents] [Index] [DEVICES]

Sound Drivers for the Crystal CS4231, 4232 (A, B), 4235, 4236 (B, D, E), 4237B, 4238B, 4239

<<=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 V.1.0 from http://freebyte.ml.org/~boga/OS2Programs.srcl

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)

DEVICE CWGUTIL.SYS
[Table of contents] [Index] [DEVICES]

Crystal DSP manager utility device driver

DEVICE CWMPU401.SYS
[Table of contents] [Index] [DEVICES]

Crystal MPU401 driver for a complete discription see MPU401.SYS

DEVICE DC21X4.OS2
[Table of contents] [Index] [DEVICES]

Digital Semicon. DC21X4-based Ethernet Adapter Network driver

DEVICE DCF2CDE.SYS
[Table of contents] [Index] [DEVICES]

Driver for DCF/2 a harddisk compression tool, also part of Linkright

DEVICE DCF2MGR.SYS
[Table of contents] [Index] [DEVICES]

Driver for DCF/2 a harddisk compression tool

DEVICE DCF2PDD.SYS
[Table of contents] [Index] [DEVICES]

Driver for DCF/2 a harddisk compression tool

DEVICE DCF77.SYS
[Table of contents] [Index] [DEVICES]

Driver for DCF77-Radiocontrol Watch

available for FREE at http://www.prog-link.com

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.

DEVICE DDE4XTRA.SYS
[Table of contents] [Index] [DEVICES]

Device driver for IBM 'C Set++' version 2.0 and 2.1.


<<=NOTE=>> Not tested if it works under Warp 4.0.

DEVICE DE528.OS2
[Table of contents] [Index] [DEVICES]

D-Link 528CT Ethernet Adapter Network driver

<<=NOTE=>> It is impossible with this driver to execute graphical apps using Exceed

DEVICE DES.SYS
[Table of contents] [Index] [DEVICES]

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 DISKFIT.SYS
[Table of contents] [Index] [DEVICES]

Driver for the fault tolerance system

See OS/2 manual for more information

DEVICE DLKFET.OS2
[Table of contents] [Index] [DEVICES]

D-Link DFE-530TX PCI Fast Ethernet Adapter

DEVICE DLKPCI.OS2
[Table of contents] [Index] [DEVICES]

D-Link PCI Fast Ethernet Adapter

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/dec.zip.

DEVICE DOS.SYS
[Table of contents] [Index] [DEVICES]

A device driver used to communicate between DOS and OS/2 applications running on the same system.

DEVICE DRVOCDB.SYS
[Table of contents] [Index] [DEVICES]

Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0

DEVICE DRVOPPQT.SYS
[Table of contents] [Index] [DEVICES]

Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0

DEVICE DRVOQ117.SYS
[Table of contents] [Index] [DEVICES]

Driver from Seagate Backup Exec for OS/2 Warp, Version 3.0

DEVICE DSS1C20X.SYS
[Table of contents] [Index] [DEVICES]

CAPI version 2.0 driver for ELSA ISDN board

D channel protocol : DSS1 (EURO-ISDN)
B channel protocols: HDLC transparent, bit transparent, X.75, T.70NL, V.120 ISO 8208 (X.25), T.90 modem function (V.34), Fax group 3 function (V.34 only for PCFpro, QuickStep 3000 and QuickStep 3000-PCI). FAX only for PCF, PCFpro, QuickStep 3000 and QuickStep 3000-PCI.

DEVICE DSS1TE.SYS
[Table of contents] [Index] [DEVICES]

Euro ISDN Module for Teles ISDN Cards

<<=TIP=>> If you not already have one better get one from ELSA. Newer Teles Cards are reported to produce many problems (if not fail in general) and there is definetly no further OS/2 development. Also newer Driver Versions (> 2.97) are reported to make trouble.

DEVICE E100B.OS2
[Table of contents] [Index] [DEVICES]

Intel EtherExpress PRO Adapter

DEVICE EC2T.OS2
[Table of contents] [Index] [DEVICES]

Linksys Combo PCMCIA EthernetCard (EC2T)

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.

DEVICE ECRDRV.SYS
[Table of contents] [Index] [DEVICES]

Driver for PolyPM a Remote Service Management Solution http://www.iss2you.com

DEVICE EL59X.OS2
[Table of contents] [Index] [DEVICES]

3Com Fast EtherLink & EtherLink III Bus Master Family Network driver

DEVICE EL90X.OS2
[Table of contents] [Index] [DEVICES]

3Com Fast EtherLink/EtherLink XL Family Network driver (e.g. 900 A/B)

DEVICE ELNK3.OS2
[Table of contents] [Index] [DEVICES]

3Com Etherlink III Adapter

DEVICE ELPC3.OS2
[Table of contents] [Index] [DEVICES]

3Com 3C589 EtherLink III PC Card OS/2 driver

<<=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.

DEVICE ELPC3X.OS2
[Table of contents] [Index] [DEVICES]

3Com EtherLink III LAN+Modem PC Card f│r OS2 V1.5 - Card Services driver

DEVICE ELSA.SYS
[Table of contents] [Index] [DEVICES]

Card specific part of GRADD display driver and settings for ELSA WINNER 2000/Office

DEVICE EP325.OS2
[Table of contents] [Index] [DEVICES]

OS/2 NDIS SURECOM EP-325 PCI Ethernet Adapter (based on Realtek RTL8029)

DEVICE EP427.OS2
[Table of contents] [Index] [DEVICES]

SureCom EtherPerfect-427 PCMCIA Ethernet Card

DEVICE EQNKRCSH.EXE
[Table of contents] [Index] [DEVICES]

Driver by Netfinity* Version 5.20.3

DEVICE EQNKVKBD.SYS
[Table of contents] [Index] [DEVICES]

Driver by Netfinity* Version 5.20.3

DEVICE EQNRCSH.EXE
[Table of contents] [Index] [DEVICES]

Part of DCAF (Distributed Console Access Facility)

<<=ATTENTION=>> If you don't have the IBM Internal Y2K fix it won't work after 31.12.1999

DEVICE EQNVKBD.SYS
[Table of contents] [Index] [DEVICES]

Part of DCAF (Distributed Console Access Facility)

<<=ATTENTION=>> See also DEVICE EQNRCSH.EXE

▒╛. Б═╙╕╔:

DEVICE EQNRCSH.EXE

DEVICE ES1371.SYS
[Table of contents] [Index] [DEVICES]

PCI Ensoniq ES1371 Audio Device Driver
No WinOS and Midi support.

<<=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

DEVICE ES1688DD.SYS
[Table of contents] [Index] [DEVICES]

Sounddriver for the ESS1688

A FREE mixer for this Soundchip is ESSMIX13.ZIP by Oleg Deribas (older@iname.com).

DEVICE ES1868DD.SYS
[Table of contents] [Index] [DEVICES]

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 ES1869DD.SYS
[Table of contents] [Index] [DEVICES]

Driver for the ESS 1869 soundchip

DEVICE ES198X.SYS
[Table of contents] [Index] [DEVICES]

ESS Allegro-1/Maestro-3 PCI Audio Device Driver

DEVICE ESP.SYS
[Table of contents] [Index] [DEVICES]

Ray Gwinn's Hayes ESP device driver

DEVICE ET32ND.OS2
[Table of contents] [Index] [DEVICES]

KTI Networks Inc. base 10 t/tx PCI combo ethernet card

DEVICE ET32ND.SYS
[Table of contents] [Index] [DEVICES]

Driver for KTI Networks System ethernet card.

DEVICE EXMOUSE2.SYS
[Table of contents] [Index] [DEVICES]

Kensington mouse driver for OS/2.

<<=NOTE=>> Doesn't work together with the Scitech Display driver

DEVICE EXP16.OS2
[Table of contents] [Index] [DEVICES]

Intel EtherExpress 16 Family Adapter Network driver

DEVICE EXTDSKDD.SYS
[Table of contents] [Index] [DEVICES]

EXTDSKDD.SYS supports external disk drives. See your online Command Reference for complete details.

DEVICE FASTNIC.OS2
[Table of contents] [Index] [DEVICES]

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 FETND.OS2
[Table of contents] [Index] [DEVICES]

PCI Fast Ethernet 10M/100M Adapter

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/via.zip.

DEVICE FLSH2MTD.SYS
[Table of contents] [Index] [DEVICES]

PCMCIA Storage Driver for OS/2 (FLASH MTD)

DEVICE FMD.SYS
[Table of contents] [Index] [DEVICES]

Driver required by Faxworks lite 2.* in Warp 3 or the Pro Versions of Faxworks/PMFax

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)

DEVICE FMRADIO.SYS
[Table of contents] [Index] [DEVICES]

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.

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.

DEVICE FTDVR.SYS
[Table of contents] [Index] [DEVICES]

Driver of Backmaster tape backup system.

DEVICE FWIP.SYS
[Table of contents] [Index] [DEVICES]

IBM TCP/IP Firewall IP Packet driver.

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.srcl 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)

DEVICE FXWRAP.SYS
[Table of contents] [Index] [DEVICES]

NDIS wrapper for the InJoy Firewall for OS/2

from: http://www.fx.dk/firewall

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

DEVICE GAMEDD.SYS
[Table of contents] [Index] [DEVICES]

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

available at http://www.tietomyrsky.fi/%7Ejaaskela/

DEVICE GAMEPRT2.SYS
[Table of contents] [Index] [DEVICES]

Joystick interface driver.

By Jose DaSilva silva@dowco.com

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.

DEVICE GENSCSI.SYS
[Table of contents] [Index] [DEVICES]

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 GRADD.SYS
[Table of contents] [Index] [DEVICES]

GRADD Display Drivers - generic part

DEVICE HDLC.SYS
[Table of contents] [Index] [DEVICES]

HDLC Module for Teles ISDN Cards

DEVICE HRTIMER.SYS
[Table of contents] [Index] [DEVICES]

HRTIMER.SYS is a high resolution timer implemented as a device driver. Shows more accurate reading of e.g. the CPU-Meter in Memsize.


<<=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).

DEVICE IAS_DD.OS2
[Table of contents] [Index] [DEVICES]

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 IBMTOK.OS2
[Table of contents] [Index] [DEVICES]

IBM compatible Token-Ring-Networkadapter

DEVICE ICHSND.SYS
[Table of contents] [Index] [DEVICES]

Analog Devices SoundMax Integrated Digital Audio AD1881 OS/2 driver for Intel 82801AA/AB chipset

DEVICE IDEHDD.SYS
[Table of contents] [Index] [DEVICES]

MULTIPORT Parallel Port hard disk drive device driver

http://www.multiport.de/Home_Deutsch/home_deutsch.phpl

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.

DEVICE IFNDIS.SYS
[Table of contents] [Index] [DEVICES]

Part of the TCP/IP Protocol Drivers used in older versions. Actual MPTN deletes this entry.

DEVICE IFNDISNL.SYS
[Table of contents] [Index] [DEVICES]

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.

<<=TIP=>> To get PPP (Pont to Point Protocol) download ftp://ftp.ibm.net/pub/PPP/PPP.ZIP

DEVICE INET.SYS
[Table of contents] [Index] [DEVICES]

TCP/IP Drivers for SLIP (Serial Line Internet Protocol) OS/2 TCP/IP Version 2 from the Warp 3 Internet Access Kit.

<<=TIP=>> For PPP see also DEVICE IFNDISNL.SYS

DEVICE IP22DRV.SYS
[Table of contents] [Index] [DEVICES]

Driver from Dualstor backup

DEVICE IPSEC.SYS
[Table of contents] [Index] [DEVICES]

Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall
Device driver used by the IBM TCP/IP Firewall to impliment the IPSEC protocol.

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 IPX.SYS
[Table of contents] [Index] [DEVICES]

Provides Novell IPX protocol support and is required for access to a NetWare server.

DEVICE IRCOMM.SYS
[Table of contents] [Index] [DEVICES]

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 IRDA_DD.OS2
[Table of contents] [Index] [DEVICES]

OS/2 IrDA Protocol Stack 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 IRDA_PHY.OS2
[Table of contents] [Index] [DEVICES]

OS/2 IrDA Protocol Stack 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 IRDD.SYS
[Table of contents] [Index] [DEVICES]

Installs the Infrared Device Driver at COM2

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.

DEVICE IRDNDIS.OS2
[Table of contents] [Index] [DEVICES]

IBM Infrared NDIS MAC Driver

DEVICE IRMAC.OS2
[Table of contents] [Index] [DEVICES]

IBM Wireless LAN PCMCIA Adapter driver

DEVICE ISDNAPI.SYS
[Table of contents] [Index] [DEVICES]

Module for Teles ISDN Cards

DEVICE ISDNC20X.SYS
[Table of contents] [Index] [DEVICES]

CAPI version 2.0 driver for ELSA ISDN board

D channel protocol : 1TR6 (national ISDN)
B channel protocols: HDLC transparent, bit transparent, X.75, T.70NL, V.120 ISO 8208 (X.25), T.90 modem function (V.34), Fax group 3 function (V.34 only for PCFpro, QuickStep 3000 and QuickStep 3000-PCI). FAX only for PCF, PCFpro, QuickStep 3000 and QuickStep 3000-PCI

DEVICE ISO8208.SYS
[Table of contents] [Index] [DEVICES]

ISO 8208 Module for Teles ISDN-Cards

DEVICE IWZPAN40.SYS
[Table of contents] [Index] [DEVICES]

Performance analyzer device driver from the IBMCOBOL v 2.2.2

DEVICE JJSCDROM.DMD
[Table of contents] [Index] [DEVICES]

modified CD-ROM device manager with CD-DA digital readout / multisessioning enhancement developed by Takayuki Suwa (jjsuwa@sys3175.com)

Parameters:

/U:n - "Specifying CD-ROM unit" option. It will be used with some unit-based options such as /F (see below). 0 indicates first unit, and no /U option means all ones.

/FC+ : forcing to turn on "CD-DA readable" flag

/FCS : forcing Sony CDU-561 compatible CD-DA readout method (SCSI unit only)

/FCT : forcing Toshiba XM-3401 compatible CD-DA readout method (SCSI unit only)

/FC : same as /FC+ /FCS

/FM+ : forcing to turn on "multisessioning-aware" flag

/FMT : forcing Toshiba XM-3401 compatible multisessioning method (SCSI unit only)

/FMS : forcing Sony CDU-561 compatible multisessioning method (SCSI unit only)

/FMC : forcing Chinon CDS-535 compatible multisessioning method (SCSI unit only)

/FMN : forcing NEC 84-1 compatible multisessioning method (SCSI unit only)

/FMH : forcing HP C4324 compatible multisessioning method (SCSI unit only)

/FM : same as /FM+ /FMS

/F : same as /FC+ /FCS /FM+ /FMS

/W - "WORM-devices as CD-ROM" option. For some WORM-style SCSI CD-R drives.

/I - "Ignore unit" option (/I). This is unit-based option like /F and should be with /U. Without /U option will cause no CD-ROM drive present.

/V - "Verbose" option (/V). It will display some information such as:

IBM OS/2 JJSCDROM.DMD (960528) (JJ20000506)
ui : di-ai-un-l : vendor product rev [flag]
00 : 02-00-03-0 : TEAC CD-ROM CD-532S 3.0A [+S+S]
01 : 02-00-05-0 : TOSHIBA CD-ROM XM-3501TA 2694 [+T+T]
^^ ^^ ^^ ^^ ^ ^^^^^^^^ ^^^^^^^^^^^^^^^^ ^^^^ ^^^^
| | | | | | | | ||||
a b c d e f g h ijkl
a : # of CD-ROM unit index, for /U option
b : # of adapter device driver index installed
c : # of adapter index controlled by each adapter device driver
d : (physical) unit number connected to each adapter
and detected as CD-ROM (or WORM)
e : logical unit number in each physical unit
f, g, h : device inquiry strings
i : + if "CD-DA readable" flag is turned on
j : CD-DA readout method forced [S/T/blank]
k : + if "multisessioning-aware" flag is turned on
l : multisessioning method forced [T/S/C/N/H/blank]


Examples:

Uses a Sony CDU-561 compatible CD-ROM unit, but cannot be recognized CD-DA readout/multisessioning feature by standard OS2CDROM.DMD

DEVICE=d:\OS2\BOOT\JJSCDROM.DMD /F

- Uses 3 CD-ROM units, one (unit #0) IDE ATAPI drive, one (unit #1) Toshiba SCSI OEM-version (non-Toshiba SCSI Inquiry) drive and (unit #2) Sony CDU-561 compatible SCSI

DEVICE=d:\OS2\BOOT\JJSCDROM.DMD /U:1 /FC+ /FCT /FM+ /FMT /U:2 /F

- Uses WORM-style SCSI CD-R as CD-ROM, such as Yamaha CDR102

DEVICE=d:\OS2\BOOT\JJSCDROM.DMD /W

- Ignores 2nd CD-ROM unit for other CD-ROM driver/file system such as RSJ CD-Writer CDWFS or Pegasus-OFS

DEVICE=d:\OS2\BOOT\JJSCDROM.DMD /U:2 /I

DEVICE KDBNET.SYS
[Table of contents] [Index] [DEVICES]

Kernel Failure Networkprotocol, enables remote Kernel-Failure repair over TCP/IP

DEVICE KILLER.SYS
[Table of contents] [Index] [DEVICES]

WatchCat 2.1 Process Manipulation Center Driver

DEVICE KMGAX64.SYS
[Table of contents] [Index] [DEVICES]

Driver for the Matrox Video Cards

DEVICE KOPYKAT.SYS
[Table of contents] [Index] [DEVICES]

driver for KopyKat Remote Control Software by Hilgraeve INC.

DEVICE KSCOM.SYS
[Table of contents] [Index] [DEVICES]

Kamell ISDN Comport Device Driver (At-Commands with Fax Class 2.0)

Parameter:

/P:COMx Port (Default COM3)

/C:x Controller (Default Controller)

/S:x Serialnumber

/A:x Activation key

/K:DIVA Cardtype (only for Eicon DIehl DIVA Cards Version 5.0.3 or higher)

DEVICE KTC40.OS2
[Table of contents] [Index] [DEVICES]

Kingston EtheRx PCI-Ethernet-Networkadapter driver

DEVICE L100.OS2
[Table of contents] [Index] [DEVICES]

PNIC 100 Base FX Fast Ethernet adapter


NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.

DEVICE LANDD.OS2
[Table of contents] [Index] [DEVICES]

IBM IEEE 802.2 NDIS protocol driver

Information passed by Sergey I. Yevtushenko (evsi@naverex.kiev.ua) http://www.naverex.kiev.ua/~evsi/

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 TokenRing if I remember correctly) frames in a NIC-independent way. Format of the frame described in IEEE 802.2 standard. Applications using this protocol driver are e.g.: Lexmarks' MarkVision uses it for Lexlink protocol support and Remote IPL.

DEVICE LANDD.SYS
[Table of contents] [Index] [DEVICES]

Lan Manager's user device driver.

Provides services for MAC frame protocols.

<<=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.)

DEVICE LANDLLDD.OS2
[Table of contents] [Index] [DEVICES]

Lan Manager interface to LAND.OS2--the 802.2 protocol

DEVICE LANDLLDD.SYS
[Table of contents] [Index] [DEVICES]

Lan Manager's common dll device driver.

DEVICE LANMSGDD.OS2
[Table of contents] [Index] [DEVICES]

=drive:\IBMCOM\LANMSGDD.OS2 /I:drive:\IBMCOM /S

The only thing I know about this is, that it writes a log named LANTRAG.LOG into drive:\IBMCOM

DEVICE LANPDD.OS2
[Table of contents] [Index] [DEVICES]

LAN Driver needed for Netbios and IEEE 802.2 protocols, enables the use of LANVDD.OS2

DEVICE LANPDD.SYS
[Table of contents] [Index] [DEVICES]

Lan Manager's kernel device driver.

DEVICE LNE100.OS2
[Table of contents] [Index] [DEVICES]

Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4)

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/liteon.zip.

DEVICE LNEPCI.OS2
[Table of contents] [Index] [DEVICES]

Linksys LNEPCI/LNE100TX Ethernet Adapter

DEVICE LOG.SYS
[Table of contents] [Index] [DEVICES]

This optional device driver installs OS/2s error log file. If you want a log of errors that occur on your system, then add this and the next line to your config.sys file. If you are interested in such things, you may wish to play with it, but be forewarned, the error log information is cryptic and incomplete. See note below. To learn what these codes mean, you need to have IBM's Systems Network Architecture Formats (GA27-3136-12) or, for a reasonable overview, get OS/2 2.1 Unleashed, 1993, SMAs Publishing.

Parameter

/E:nn sets the size of the error log protocol. The range is from 4kb to 64kb with 8kb as the default.

/OFF stopps logging

/A:nn sets the size of the error log buffer. The range is from 4kb to 64kb.

You will get a short and quick message during boot up indicating that Logging has been installed and what the buffer size is.

<<=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.

DEVICE LPT49.SYS
[Table of contents] [Index] [DEVICES]

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 LPTDD.SYS
[Table of contents] [Index] [DEVICES]

Driver for the LPTools, a parallel to parallel port solution like laplink.

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

DEVICE LRCOM.SYS
[Table of contents] [Index] [DEVICES]

Linkright serial port driver

LinkRight is a serial and parallel port file transfer utility for OS/2.

DEVICE LRPAR.SYS
[Table of contents] [Index] [DEVICES]

Linkright parallel port driver

LinkRight is a serial and parallel port file transfer utility for OS/2.

Parameters:

/Q:7 uses IRQ7 or /Q:5 uses IRQ5. These are the only IRQs supported. Interupt driven mode can only be used if PRINT01.SYS or PRINT02.SYS also uses the same interupt. If no /Q option is selected, polled is assumed.

/P is for polled. This is a useless option, since it is the default.

/A:3BC or /A:378 or /A:278 select the address of the LPT port for LinkRight to use. If this parameter is used, only one address can
be specified. Then, when you select Connect from the LinkRight menu, no matter which LPT port you select, either LPT1, LPT2 or
LPT3, LinkRight will use the address specified. If this parameter is not included, LinkRight reads the BIOS info at bootup time to
get the LPT addresses.

/M is to specify MicroChannel machines. For some MicroChannel systems when booted from bootable floppies, LinkRight would not see that it was MicroChannel and would assume an ISA bus. This caused the driver to fail. So if you boot your MicroChannel system from floppies
and the LinkRight driver displays a message at bootup time saying an ISA bus was found, use this parameter to fix the problem.

The preferred and suggested mode of use is no parameters on the LRPAR.SYS line in CONFIG.SYS. You can add parameters if there are
any problems.

DEVICE LSL.SYS
[Table of contents] [Index] [DEVICES]

Loads Link support Layer driver. It is the lowest layer in the Novell Open Data Link Interface model and is required at all times for the requester to be active.

DEVICE LTMDMOS2.SYS
[Table of contents] [Index] [DEVICES]

Lucent Technologies Modem Driver



An older V. 5.55 Beta 3 is available for FREE at http://www.drmartinus.de/notebook2/notebook.src

DEVICE MACMYWI.OS2
[Table of contents] [Index] [DEVICES]

ISDNPM Support Driver

DEVICE MAESTR2E.SYS
[Table of contents] [Index] [DEVICES]

AudioDrive Maestro-2E OS/2 Driver modified by Daniela Engert

DEVICE MD5.SYS
[Table of contents] [Index] [DEVICES]

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 MEDIAOS2.SYS
[Table of contents] [Index] [DEVICES]

MediaDrive OS/2 Device Driver. The MediaDrive is an internal PCCARD-Drive for Workstations. Useful e.g. for Digital-Cameras

available at http://www.altec-computersysteme.com

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.

DEVICE MEIO0437.SYS
[Table of contents] [Index] [DEVICES]

Driver for the MWAVE Modem for IBM Thinkpads

DEVICE MIDI.SYS
[Table of contents] [Index] [DEVICES]

Real Time Midi Driver new with Warp 4

<<=TIP=>> For working with Midi there is the MIDI Station Sequencer: http://www.dinosoft.it/~midistation/index.srcl

DEVICE MODISK.DMD
[Table of contents] [Index] [DEVICES]

MO device driver from Fujitsu

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.

DEVICE MODISK.SYS
[Table of contents] [Index] [DEVICES]

Magneto Optical Device Driver

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


DEVICE MOUSE.SYS
[Table of contents] [Index] [DEVICES]

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

<<=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. 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.srcl. 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

▒╛. Б═╙╕╔:

DEVICE AMOUSE.SYS

DEVICE MOUSE2.SYS
[Table of contents] [Index] [DEVICES]

Driver for the Trackpoint of IBM Thinkpads

DEVICE MPU401.SYS
[Table of contents] [Index] [DEVICES]

Audio device driver for the MPU401.

There are different drivers from IBM, Cirrus and one from Theta Band which is also capable of recording.

Parameter:

/Pn:hhh Basis I/O (Port) Adress

/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).

DEVICE MVPRODD.SYS
[Table of contents] [Index] [DEVICES]

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.

<<=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.

DEVICE MWAVEDD.SYS
[Table of contents] [Index] [DEVICES]

Driver for MWAVE Modem on IBM Thinkpads

DEVICE NE2000.OS2
[Table of contents] [Index] [DEVICES]

Eagle Technology NE2000plus Ethernet Adapter

DEVICE NETBEUI.OS2
[Table of contents] [Index] [DEVICES]

IBM OS/2 Netbios protocol driver

DEVICE NETBIOS.OS2
[Table of contents] [Index] [DEVICES]

Netbios API driver

<<=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.

DEVICE NETBIOS.SYS
[Table of contents] [Index] [DEVICES]

Loads support for the NETBIOS protocol.

<<=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)

DEVICE NETFLX3.OS2
[Table of contents] [Index] [DEVICES]

OS/2 NDIS 2 Driver for Compaq NetFlex-3/Netelligent Controllers

DEVICE NMPIPE.SYS
[Table of contents] [Index] [DEVICES]

Loads the support for client-only Named Pipes support.

DEVICE NOVAQOS2.SYS
[Table of contents] [Index] [DEVICES]

Driver for backup-software from NOVABACK

DEVICE NOVASPI.SYS
[Table of contents] [Index] [DEVICES]

Driver for backup-software from NOVABACK

DEVICE NPSERVER.SYS
[Table of contents] [Index] [DEVICES]

Loads support for your workstation to function as a Named Pipes server.

DEVICE NTR2000.SYS
[Table of contents] [Index] [DEVICES]

ODI Driver for Token Ring Networkcards

DEVICE NULLNDIS.OS2
[Table of contents] [Index] [DEVICES]

IBM NULL MAC-driver

Installed if you have NO Network Adapter.

DEVICE NWREQ.SYS
[Table of contents] [Index] [DEVICES]

This is the CORE REQUESTER MODULE. This line must follow any lines that support IPX, SPX, or Named Pipes.

DEVICE ODI2NDI.OS2
[Table of contents] [Index] [DEVICES]

IBM support for the Netware Requester

DEVICE OPL3.SYS
[Table of contents] [Index] [DEVICES]

FM Synthesis OPL3 Midi driver

Parameter:

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

DEVICE OPL3SA.SYS
[Table of contents] [Index] [DEVICES]

FM Synthesis OPL3 Yamaha SAx Soundchip

DEVICE OPL4D.SYS
[Table of contents] [Index] [DEVICES]

Yahama Fm Sythesis OPL4 MIDI Driver

Parameter:

/P:xxx - Midiport Address, 300, 310, 330 or 388 (default)

/N:OPL41$

DEVICE OPTICAL.DMD
[Table of contents] [Index] [DEVICES]

New with Warp4 Device Manager for Optical devices like MO

<<=TIP=>> If you have removable media drives (MO, IOMEGA, SYQUEST and others) look at http://rheooptik.fmf.uni-freiburg.de/www/faq/remmedia.src for a detailed removable media FAQ.

DEVICE OS2.SYS
[Table of contents] [Index] [DEVICES]

These drivers only work for Iomega SCSI adapters and the Parallel Port version of the Zip 100 drive.

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)


Advantages:

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.phpl

▒╛. Б═╙╕╔:

BASEDEV PPAOS2.ADD

DEVICE OS20MEMU.SYS
[Table of contents] [Index] [DEVICES]

OS20MEMU is a Memory Analyser for OS/2 (IBM EWS)

DEVICE OS2CDROM.DMD
[Table of contents] [Index] [DEVICES]

OS/2 driver used on many, but not all CD-ROM's.

Parameter:

/Q supresses error messages.

/V Verbose, shows the found drives and Manufacturer string

<<=TIP=>> See also JJSCDROM.SYS for enabling digital transfer on some drives.

▒╛. Б═╙╕╔:

DEVICE JJSCDROM.DMD

DEVICE OS2OGL.SYS
[Table of contents] [Index] [DEVICES]

Pentium Pro optimised Open GL Driver

<<=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.

DEVICE P6K7MTRR.SYS
[Table of contents] [Index] [DEVICES]

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 P9100.SYS
[Table of contents] [Index] [DEVICES]

Driver for Videocards using the Weitek P9100 chip

DEVICE PANEL.SYS
[Table of contents] [Index] [DEVICES]

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.srcl

DEVICE PARADISE.SYS
[Table of contents] [Index] [DEVICES]

Driver for the Paradise mixer for all Crystal CS423x souncards using a mode-3 driver

DEVICE PAUSE.SYS
[Table of contents] [Index] [DEVICES]

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

DEVICE PC.SYS
[Table of contents] [Index] [DEVICES]

Driver from Process Commander by Stardock

DEVICE PC100.OS2
[Table of contents] [Index] [DEVICES]

Linksys EtherFast 10/100 PC Card

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/pcmcia.zip.

DEVICE PCCOM2.SYS
[Table of contents] [Index] [DEVICES]

PCCOM 2 PORT Card Device driver

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 )

DEVICE PCCOM4.SYS
[Table of contents] [Index] [DEVICES]

PCCOM 4 PORT Card Device driver

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 )

DEVICE PCCOM8.SYS
[Table of contents] [Index] [DEVICES]

PCCOM 8 PORT Card Device driver

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 PCIND.OS2
[Table of contents] [Index] [DEVICES]

NDIS driver for RealTek RTL-8029 based NE2000-combatible cards

DEVICE PCIOS2.SYS
[Table of contents] [Index] [DEVICES]

ODI driver for RealTek RTL-8029 based NE2000-combatible cards

DEVICE PCKBD.SYS
[Table of contents] [Index] [DEVICES]

Process Commander Keyboard driver

The PCKBD line lets full-screen Process Commander be invoked, even
when the customized KBDBASE.SYS is not being used.

Parameter:

KEYB:CA-A

DEVICE PCLOGIC.SYS
[Table of contents] [Index] [DEVICES]

Provides mouse support for Genius, Logitech, PC Mouse Systems

<<=ATTENTION=>> Must reside between POINTDD.SYS and MOUSE.SYS

DEVICE PCM2FLSH.SYS
[Table of contents] [Index] [DEVICES]

PCMCIA Storage Driver for OS/2 (FLASH)

DEVICE PCM2SRAM.SYS
[Table of contents] [Index] [DEVICES]

PCMCIA Storage Driver for OS/2 (SRAM)

DEVICE PCMNICCS.OS2
[Table of contents] [Index] [DEVICES]

IBM Ethernet Adapter (PCMCIA) driver

DEVICE PCMSSDIF.SYS
[Table of contents] [Index] [DEVICES]

PCMCIA Storage Driver for OS/2 (Interface)

DEVICE PCNTND.OS2
[Table of contents] [Index] [DEVICES]

AMD PCNet Ethernet Family Adapter driver

DEVICE PDITOU01.SYS
[Table of contents] [Index] [DEVICES]

See DEVICE TOUCH.SYS

DEVICE PDITOU02.SYS
[Table of contents] [Index] [DEVICES]

See DEVICE TOUCH.SYS

DEVICE PMAC.OS2
[Table of contents] [Index] [DEVICES]

SSW-Parallelportdriver for Adapter without NIC

If there is an printer also connected to the parallel port there must be the BASEDEV=PRINT01(or 2).SYS /IRQ set. To switch between PMAC and Printer got to the drive:/IBMCOM directory and execute PMAC.EXE -R. To reestablish connection with PMAC type PMAC.EXE -C.

JERRY ROWE's WARP REMOTE INSTALL PAGE

This page is a preliminary FAQ about installing OS/2 Warp 4 over a laplink cable from a Server to a Client.

First, you must set the Server up to use the parallel port (SSW Parallel MAC driver) network driver. You do this from MPTS [just type MPTS at the command line]. Select the driver, and add Netbios as a protocol.

Then Edit the SSW Parallel MAC driver in MPTS and Note its address. It should be 40000000000A.

Then open up the OS/2 Warp Remote Install object. Create the remote install disks. Be sure to use the same SSW Parallel MAC driver.

Then edit the protocol.ini file on the 2nd disk. Inside it, insure that the MAC address is something other than 40000000000A. Using 40000000000B will work fine.

Save the file.

Now, shutdown and reboot the machine.

Then examine \ibmcom\lantran.log and look for the reference to the Adapter # for the parallel port adapter. If you have another adapter in the Server, the number may be 1, otherwise it will be 0.

Find Server Adapter #
Note that the Adapter #=1 in the file below. If your parallel port is setup for adapter #=0, then lantran.log will be different.
==file lantran.log=========================================
PARALLEL PORT MAC V 1.0 by Savant Software Inc. Copyright (C) 1994, 1995
SAVANT SOFTWARE: PORT ADDRESS(ES): LPT1
SAVANT SOFTWARE: PORT ADDRESS CONFIGURED: LPT1(378)
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
IBM LANDD is accessing IBM 802.3 LAN Interface.
Adapter 1 was initialized and opened successfully.
Adapter 1 is using node address 40000000000A. The Token-Ring
format is 02000000
IBM LANDD was successfully bound to MAC: pmac_nif->VECTOR.
==end file lantran.log=========================================

Install service.exe and other files.

If they were not installed during the Warp install, follow these instructions.

Given that my CDRom drive is I:, and My Warp 4 drive is H:, issue this command:

[H:\]I:\CID\SRVIFS\thinsrv /s:. /t:h:\cid\SRVIFS
/r:h:\ibminst\tables\service.ini /tu:h:\

THINSRV completed successfully.

This creates a line in startup.cmd and creates startup.cmd if necessary.
START H:\CID\SRVIFS\SERVICE.EXE /INI=SERVICE

Thinsrv also adds:

h:\cid\SRVIFS;

to the PATH and DPATH statements in CONFIG.SYS.

Because these changes will not take effect until a reboot, the command in STARTUP.CMD will not work until then.

However, you can:

cd \cid\srvifs service /ini=service

to start it right away from the command line.

You will probably want to remove the commands from Startup.cmd at this time to prevent the Server facility from running all the time.

You may also want to create another cmd file with the service command in it if you would like to run it interactively.

Edit h:\cid\service.ini

Note Alias's and Path near bottom. Should be correct for the CD Note Adapter #. Should match # from Lantran.log.
=============================================================
;SRVIFS INI file for OS/2 Warp Remote Install Server - 7CPESGDV
Name = 7CPESGDV
GroupName = NO
Adapter = 1
MaxClients = 5
MaxFiles = 9999
ClientWorkers = 8
Path = I:\
Alias = ReadOnly,Single,CDROM,I:\
Alias = ReadWrite,Single,STATUS,H:\IBMINST\RSP\REMOTE
==============================================================

With these changes made, shut down the computer and reboot. After it comes up, the GUI front end for the Remote install should work.

===Config.sys on disk 1 ===================
CALL=A:\SRVATTCH.EXE z: \\7CPESGDV\CDROM
DEVICE=A:\SRVIFS.SYS
IFS=A:\SRVIFSC.IFS * /T
CALL=A:\SRVATTCH.EXE w: \\7CPESGDV\STATUS
RUN=Z:\CID\LOCINSTU\SRVREXX.EXE
libpath=.;\os2\install;\os2\dll;z:\cid\locinstu;
set os2_shell=cdboot.exe
set oemprogram=\ibminst\npconfig.exe
set exitwhendone=1
set ADAPTER_NIF=PMAC.NIF
set SRVNAME1=7CPESGDV
set SAVECONNECT=1
================================================

Now, change to H: [warp 4 drive] and start server.
cd \cid
SERVICE.EXE /INI=SERVICE

Now, boot the client off the disk set.

Should work. If it does not, check the hardware configuration of the parallel ports and insure they are set to bi-directional if that option is offered.

I successfully installed Warp 4 on a Thinkpad using this method.

After the install, you should also be able to network between the two computers over the laplink cable using OS/2 Peer.

DEVICE PMDD.SYS
[Table of contents] [Index] [DEVICES]

Driver to provide pointer draw support along with POINTDD.SYS.

<<=WARNING=>> OS/2 will not start without this line in your config.sys file.

DEVICE PNPND.OS2
[Table of contents] [Index] [DEVICES]

Device driver for the RTL8019 Ethernet card.

DEVICE POINTDD.SYS
[Table of contents] [Index] [DEVICES]

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.

<<=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.

DEVICE PPPEMYWI.OS2
[Table of contents] [Index] [DEVICES]

PPP over Ethernet Protocol driver included in ISDNPM 3.0

DEVICE PRANDIS.OS2
[Table of contents] [Index] [DEVICES]

NDIS-Mac for the Parallel Port

available for FREE at http://www.w-4.de/~tbaumann/ (there is also the PEER FAQ)

supports:

PPLINK-Fullduplexcable (needs PS/2 bidirectional port)
LAPLINK/INTERLNK-Cable
JFACOMM-Halfduplexcable

For using it edit the following files:

1. PROTOCOL.INI (in directory IBMCOM)

[NETBEUI_nif]

ADAPTRATE = 0
TI = 60000
T1 = 10000
T2 = 2000
MAXIN = 5
MAXOUT = 5

2. IBMLAN.INI (in directory IBMLAN)


[requester]

sesstimeout = 300

[peer]

; The next lines help you to locate bits in the srvheuristics entry.
; 1 V Bit 15 changed to 2 to increase timeout
; 0123456789012345678
srvheuristics = 1111014111131102133

DEVICE PROTMAN.OS2
[Table of contents] [Index] [DEVICES]

=drive:\IBMCOM\PROTMAN.OS2 /I:drive:\IBMCOM

IBM OS/2 LAN Protocol Manager

DEVICE PTDVR.SYS
[Table of contents] [Index] [DEVICES]

Driver of Backmaster tape backup system.

DEVICE QAP2DRVR.SYS
[Table of contents] [Index] [DEVICES]

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.

Information by Wm D Loughman (wdlkhl@attglobal.net)

DEVICE QCAMM.SYS
[Table of contents] [Index] [DEVICES]

driver for the Connectix Quickcam connected to parallel port

QCammdd01.zip is FREE for personal use

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

DEVICE QCOM.SYS
[Table of contents] [Index] [DEVICES]

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 QUICKCAM.SYS
[Table of contents] [Index] [DEVICES]

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.src

DEVICE R0STUB.SYS
[Table of contents] [Index] [DEVICES]

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.

Information by Roderick Klein (rwklein@mensys.nl) developer of generic WIN/OS2 audio driver. http://home.wanadoo.nl/~rwklein/index.src

DEVICE RDRHELP.200
[Table of contents] [Index] [DEVICES]

used by the Netbios protocol

provide support for LAN Server.

DEVICE REFPART.SYS
[Table of contents] [Index] [DEVICES]

Driver for accessing the Refernce Partition on IBM PS/2 Microchannel Machines

Information by: Ralph-Marcus Boenicke

DEVICE RMAUDIO.SYS
[Table of contents] [Index] [DEVICES]

Reel Magic sound card driver

DEVICE RODENT.SYS
[Table of contents] [Index] [DEVICES]

Device driver for the shareware mouse driver Rodent.

DEVICE ROUTE.SYS
[Table of contents] [Index] [DEVICES]

Driver used by the Netware client

DEVICE RSJSCSI.SYS
[Table of contents] [Index] [DEVICES]

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).

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).

DEVICE RSMVDWO.SYS
[Table of contents] [Index] [DEVICES]

Driver for PolyPM a Remote Service Management Solution http://www.iss2you.com

DEVICE RTFND.OS2
[Table of contents] [Index] [DEVICES]

RTL8129 Fast Ethernet Adapter

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/realtek.zip.

DEVICE RTSND.OS2
[Table of contents] [Index] [DEVICES]

NDIS MAC for RTL8139 Fast Ethernet Adapter

DEVICE RTSOS2.SYS
[Table of contents] [Index] [DEVICES]

ODI MAC for RTL8139 Fast Ethernet Adapter

DEVICE RZT2BOOT.SYS
[Table of contents] [Index] [DEVICES]

Driver used by the IBM AO-Manager

DEVICE S0TE.SYS
[Table of contents] [Index] [DEVICES]

Module for Teles ISDN-Cards

DEVICE SB16D2.SYS
[Table of contents] [Index] [DEVICES]

Driver for Sound Blaster 16 sound card.

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 (unfortunately no more free), available at http://www.datacomm.ch/~cbratschi/

DEVICE SBAWED2.SYS
[Table of contents] [Index] [DEVICES]

Driver for Sound Blaster AWE32 sound card.

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 OS2V.O.I.C.E 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

DEVICE SBLIVE16.SYS
[Table of contents] [Index] [DEVICES]

Soundblaster Live 16Bit MMPM/2 Sounddriver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)

Parameters:

/V verbose (prints copyrights during driver init)
/C enable CD audio input
/M enable microphone audio input
/L enable linein audio input

<<=ATTENTION=>> Read the supplied readme.txt to avoid troubles if you have installed the scitech display drivers (SDDHELP.SYS).

DEVICE SBLIVE32.SYS
[Table of contents] [Index] [DEVICES]

Soundblaster Live 32Bit core audio driver ported from the Linux sources by Sander van Leuween (sandervl@xs4all.nl)

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.srcl where you can also find a couple of other useful OS/2 programs.

DEVICE SBMIX.SYS
[Table of contents] [Index] [DEVICES]

Soundblaster-mixer driver

DEVICE SCANHP1.SYS
[Table of contents] [Index] [DEVICES]

SCSISCAN OS/2 Copyright (c) 1992,1993 Danmar Systems Inc. Scanner Driver for use with the propietary SCSI controller included with the HPIIp series.

DEVICE SCANOS2.SYS
[Table of contents] [Index] [DEVICES]

SCSISCAN OS/2 Version 1.20, Copyright (c) 1992,1993 Danmar Systems Inc. ASPI Compatible Scanner Driver.

DEVICE SCAX.SYS
[Table of contents] [Index] [DEVICES]

Device driver for HST Janus ISDN ISA-Cards and CAPI v.1.1/2.0 for 1TR6 (German) protocol

DEVICE SCAXE.SYS
[Table of contents] [Index] [DEVICES]

Device driver for HST Janus ISDN ISA-Cards and CAPI v.1.1/2.0 for DSS-1 (ETSI) protocol

DEVICE SDDHELP.SYS
[Table of contents] [Index] [DEVICES]

Driver for the Scitech Display Doctor, also for some games (e.g. SNES9XOS2)
there is also a IBM Special Edition for FREE.

Supported chips (7.04 Beta 36):

3DLabs Permedia, Permedia 2, Permedia 2V, Permedia 3
3dfx Voodoo Banshee, Voodoo3, Voodoo4, Voodoo5
ARK 1000PV, 2000PV, 2000MT, 2000MI (Quadro64), 2000MI+ (Quadro64)
ATI Mach64 GX, Mach64 CX, Mach64 CT, Mach64 VT, 3D Rage, Mach64 VTB
ATI 3D Rage II, 3D Rage II+, Mach64 VT4, 3D Rage IIC, 3D Rage Pro
ATI 3D Rage LT Pro, Rage Mobility, Rage XL, Rage 128, Rage 128 Pro
ATI Rage Mobility 128
Alliance ProMotion 6422, ProMotion AT24, ProMotion AT3D
Chips & Technologies 65548, 65550, 65554, 65555, 69000
Cirrus Logic CL-GD5434, CL-GD5440, CL-GD5436, CL-GD5446
Cirrus Logic CL-GD7555 LCD, Laguna 5462, Laguna 5464, Laguna 5465
Cyrix MediaGX
InteGraphics CyberPro 2000, CyberPro 2010
Intel i740, i740 PCI, i810, i810/DC100, i810e, i815
Macronix 86250, 86251
Matrox MGA Millennium, MGA Millennium II, MGA Mystique
Matrox MGA Mystique 220, MGA-G100, MGA-G200, MGA-G400, MGA-G450
NVIDIA RIVA-128, RIVA-128ZX, RIVA-TNT, RIVA-TNT2, RIVA-TNT2 M64
NVIDIA RIVA-TNT2 Vanta, RIVA-TNT2 Ultra, GeForce 256, GeForce DDR
NVIDIA Quadro, GeForce2 GTS
NeoMagic MagicGraph 128, MagicGraph 128XD, MagicGraph 256AV
NeoMagic MagicMedia 256AV+, MagicMedia 256ZX, MagicMedia 256XL+
Number Nine Imagine 128, Imagine 128 II, Imagine 128 II VRAM
Number Nine Imagine 128 II DRAM, Ticket 2 Ride WRAM
Number Nine Ticket 2 Ride SGRAM, Ticket 2 Ride IV
OAK Spitfire 64107, Spitfire 64111, Eon 64017, Eon 64217, Warp 5
Philips 9710
Rendition Verite V1000, Verite V2200
S3 Trio32, Trio64, Trio64V+, Trio64UV+, Trio64V2/DX, Vision 864
S3 Vision 964, Vision 868, Vision 968, Virge, Virge/DX/GX, Virge/VX
S3 Virge/GX2, Virge/MX, Trio3D, Trio3D/2X, Savage3D, Savage4
S3 Savage/MX/IX, Savage2000
SiS 6202, 6205, 6215, 5597/5598, 6326, 5595/530, 5595/620, 300, 305
Sigma Designs RealMagic 64 GX
Trident TGUI9440, TGUI9440-R2, TGUI9680, ProVidia 9682
Trident Cyber9385 LCD, ProVidia 9685, 3DImage 975, Cyber9397 LCD
Trident 3DImage 985, Blade 3D, Blade 3D (Via)
Tseng Labs ET4000/W32p, ET6000, ET6100
Weitek P9000, P9100
VESA VBE 1.2, VBE 2.0, VBE 3.0

List of all supported laptop chips:

ATI 3D Rage LT Pro, Rage Mobility, Rage Mobility 128
Chips & Technologies 65550, 65554, 65555, 69000
Cirrus Logic CL-GD7555 LCD
NeoMagic MagicGraph 128, MagicGraph 128XD, MagicGraph 256AV
NeoMagic MagicMedia 256AV+, MagicMedia 256ZX, MagicMedia 256XL+
S3 Virge/MX, Savage/MX/IX
Trident Cyber9385 LCD, Cyber9397 LCD
VESA VBE 1.2, VBE 2.0, VBE 3.0

DEVICE SDI_ASPI.SYS
[Table of contents] [Index] [DEVICES]

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_CISA.SYS
[Table of contents] [Index] [DEVICES]

PC-BaX ISA Device Driver

This driver provides PC-BaX with support for a special CRISTIE 8-bit SCSI controller.

DEVICE SDI_IDE.SYS
[Table of contents] [Index] [DEVICES]

PC-BaX IDE Device Driver

This driver provides PC-BaX with support for IDE connected devices like Travan backup stations.

DEVICE SDI_LPT.SYS
[Table of contents] [Index] [DEVICES]

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_SCSI.SYS
[Table of contents] [Index] [DEVICES]

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 SESDD32.SYS
[Table of contents] [Index] [DEVICES]

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 SIO.SYS
[Table of contents] [Index] [DEVICES]

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.

SIO.SYS must reside in the config.sys after MOUSE.SYS ! Be sure you have REM'd out COM.SYS when using. SIO.SYS and VSIO.SYS are Shareware, not Freeware. See also VSIO.SYS. and DEVICE COM.SYS

DEVICE SIO2K.SYS
[Table of contents] [Index] [DEVICES]

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.

<<=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 115200 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 115200.

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.

DEVICE SIS900.OS2
[Table of contents] [Index] [DEVICES]

SIS 900/7016 PCI Fast Ethernet Adapter

DEVICE SMC9432.OS2
[Table of contents] [Index] [DEVICES]

Network driver for SMC9432/TX (EtherPower II) 10/100 PCI NIC

DEVICE SMCND.OS2
[Table of contents] [Index] [DEVICES]

Acctron SMC 1211TX base 10/100 PCI ethernet card

DEVICE SMCPWR.OS2
[Table of contents] [Index] [DEVICES]

SMC EtherPower for OS/2

NIC driver packages available at http://pws.prserv.net/mckinnis/nicpak/dec.zip.

DEVICE SND16.SYS
[Table of contents] [Index] [DEVICES]

Driver for the MAD16 Soundcards

DEVICE SNDSCAPE.SYS
[Table of contents] [Index] [DEVICES]

Ensoniq Soundscape VIVO (SND-ENSVIVO) AD1848 Audio OS/2 Device Driver

DEVICE SOCKETS.SYS
[Table of contents] [Index] [DEVICES]

Part of the TCP/IP Protocol Drivers

Parameters:

/C:# Failuresearch, COMPORT-Number; Standard = 2

/V Verbose

/UIS:0 disable ID for select(); Standard = ON

/MEM:# amount of 4KB Clusters. Standard = 75; valid Range = 30 - 32766

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

<<=TIP=>> According to IBM there is the undocumented parameter /UIS:0 for use on 3172 Offload System to improve the performance. This parameter is only intended for use on a 3172 Offload System and turns off the process id : thread id processing on select () calls in the stack

DEVICE SOCKETSK.SYS
[Table of contents] [Index] [DEVICES]

32bit TCP/IP Protocol Drivers using the KEE API introduced with WSeB and Fxpak 13 for Warp 4

Part of the TCP/IP Ver. 4.1/4.2/4.21 firewall

Parameter:

/V Verbose, shows version-number

DEVICE SOLO.SYS
[Table of contents] [Index] [DEVICES]

Driver for ESS SOLO 1 based soundcards or motherboards

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

DEVICE SPKRDD.SYS
[Table of contents] [Index] [DEVICES]

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).

BETTER DON'T USE IT, if you need (or want) sound on a regular base better buy one of those cheap soundcards.

DEVICE SPX.SYS
[Table of contents] [Index] [DEVICES]

Provides Novell SPX protocol support. It is my understanding that this command is required for some Novell printing utilities, but is optional in most cases.

DEVICE SRVIFS.SYS
[Table of contents] [Index] [DEVICES]

Part of the ThinIFS by IBM

DEVICE SSCOMA1.SYS
[Table of contents] [Index] [DEVICES]

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.

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

DEVICE SSMDD.SYS
[Table of contents] [Index] [DEVICES]

Driver for the IBM Sync/Stream Manager

Parameter:

/H:nn - The default is 32. For best results, set nn = 32 x (the number of movie clips being played). For example, if you plan on regularly viewing 2 clips
at a time, set nn to 64 (32 x 2).

DEVICE SVDISK.SYS
[Table of contents] [Index] [DEVICES]

Driver for the Super Virtual Disk by Albert J. Shan

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.

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

DEVICE SYSINFO.SYS
[Table of contents] [Index] [DEVICES]

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
[Table of contents] [Index] [DEVICES]

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 TC15DVR.SYS
[Table of contents] [Index] [DEVICES]

Driver of Backmaster tape backup system.

DEVICE TCPBEUI.OS2
[Table of contents] [Index] [DEVICES]

IBM OS/2 NETBIOS over TCP/IP Protocol driver

DEVICE TESTCFG.SYS
[Table of contents] [Index] [DEVICES]

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.

<<=NOTE=>> Because this driver is used by the Selective Install process, it should not be deleted.

DEVICE THESEUS2.SYS
[Table of contents] [Index] [DEVICES]

Driver for the outdated memory analysis tool THESEUS2 by IBM. See DEVICE THESEUS5.SYS for an update.

DEVICE THESEUS5.SYS
[Table of contents] [Index] [DEVICES]

Driver for the new memory analysis tool THESEUS3 by IBM downloadable at: ftp://ftp.boulder.ibm.com/ps/products/os2/fixes/v4warp/theseus3/

DEVICE TOKEN.SYS
[Table of contents] [Index] [DEVICES]

This line differs depending on the network board you have.

DEVICE TOUCH.SYS
[Table of contents] [Index] [DEVICES]

Implements support for touch devices. For a touch device to be effectively used, the POINTDD.SYS device driver and appropriate mouse device-driver support must be loaded. In addition, these statements must be included in the CONFIG.SYS file in the following order:

A device-dependent statement that gives the name of the file containing the information for the touch device you use.

A device-independent statement that identifies the touch device to TOUCH.SYS

If during installation, OS/2 detects a touch device installed on your system, the Install program automatically loads the required device-driver support necessary to enable the touch device. The touch device shares the auxiliary device (mouse) port on the system with the mouse by allowing the mouse to connect to the touch device, which is then connected to the system.

The Install program automatically adds the following statements to the CONFIG.SYS file:

DEVICE=drive:\OS2\PDITOU0x.SYS CODE=drive:\OS2TOUCO21.BIN INIT=drive:TOUCH.INI
DEVICE=drive:\OS2\TOUCH.SYS TYPE=PDITOU$
RUN=drive:\OS2\CALIBRATE.EXE-C drive:\OS2CALIBRAT.DAT
DEVICE=drive:\OS2\MOUSE.SYS TYPE=PDIMOU$

"x" is 1 or 2 depending on the bus architecture of your system. TOUCO21D.BIN is the touch-device microcode binary file and TOUCH.INI is a text file containing default parameter settings.

The RUN=CALIBRAT.EXE statement is to activate the Calibration program. This program performs the dual actions of downloading calibration-constant data to the touch device each time the system is started, and enabling recalibration of the touch device at initial setup, and when the device is moved to a new location.

To recalibrate the touch device, enter the following at an OS/2 command prompt:

x: (where "x" is your OS/2 boot drive.)
CD \OS2
CALIBRAT -U

DEVICE TR2KNDIS.OS2
[Table of contents] [Index] [DEVICES]

Texas Instruments TokenLite Compatible Token-Ring Adapter driver

DEVICE TSRKRN.SYS
[Table of contents] [Index] [DEVICES]

Module for Teles ISDN-Cards

DEVICE UART.SYS
[Table of contents] [Index] [DEVICES]

Basic UART device driver for DEVICE SIO2K.SYS

DEVICE ULTRADD.SYS
[Table of contents] [Index] [DEVICES]

Device driver for Gravis Ultra Soundcards (discontinued)

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)

DEVICE UNICODE.SYS
[Table of contents] [Index] [DEVICES]

Warp Server for E-Business Unicode Driver, enables unicode and locale support. Necessary for JFS.IFS.

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

DEVICE UPSMON.SYS
[Table of contents] [Index] [DEVICES]

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 USBAUDIO.SYS
[Table of contents] [Index] [DEVICES]

USB audio class drivers

DEVICE USBCOM.SYS
[Table of contents] [Index] [DEVICES]

USB modem driver.

<<=TIP=>> By William L. Hartzell: Know that you can assign an alias to the USB port by using /N:COMx at the end of the USBCOM driver line. Thus it becomes useable with software that does not know about USB ports. You will need one driver
line per modem.

DEVICE USBKBD.SYS
[Table of contents] [Index] [DEVICES]

USB Keyboard driver.

DEVICE USBMOUSE.SYS
[Table of contents] [Index] [DEVICES]

USB Mouse driver.

DEVICE USBPRT.SYS
[Table of contents] [Index] [DEVICES]

U(universal)S(erial)B(us) Printer Driver

USB print support for OS/2 is designed to serve all the USB printer
class devices which meet USB printer specifications.

DEVICE USBRESMG.SYS
[Table of contents] [Index] [DEVICES]

OS/2 USB Resource Manager

The purpose of this driver is to show all connected USB devices with exception of USB-hubs connected to the system.
It allows to view the USB Device Report and can thereby help a developer to see how a device registers at the system and
try to find reasons why a certain device which should run with installed drivers doesn't or in the development of new drivers.

The author can be contacted at usbguy@netlabs.org
If you use this package to check why an USB device doesn't work even you have the right USB drivers installed, include the following information:
- Config.sys
- Device report
- Timestamp of the USB drivers (creation date size)

DEVICE USLGENIO.SYS
[Table of contents] [Index] [DEVICES]

Driver for the TV-Happy Player supports - TV-tuner card based on Brooktree BT848A card (or newer), and for the 724mix a Mixer for Yamaha 724 compatible Soundcards

Available at http://www.os2.ru/projects

Models already supported:

AIMSlab Video Highway Xtreme
FlyVideo 98
AVER TVPhone98
AVER TVPhone (untested)
AVER TVCapture (untested)
Fly Video II (untested)

DEVICE VCSHDD.SYS
[Table of contents] [Index] [DEVICES]

Driver for the Video Recording Parts of MMOS2

DEVICE VDISK.SYS
[Table of contents] [Index] [DEVICES]

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.

DEVICE VFDISK.SYS
[Table of contents] [Index] [DEVICES]

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's

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

DEVICE VIAUDD.SYS
[Table of contents] [Index] [DEVICES]

VIA audio sound system driver for the VIA VT82C686A Southbridge with built in AC97 Controller

http://www.via.com.tw/drivers/index.src


<<=NOTE=>> Don't invest too much time. At the moment nobody seems to get this driver working

DEVICE W940ND.OS2
[Table of contents] [Index] [DEVICES]

PCI Network Device driver for Winbond W89C940 based PCI Ethernet Adapters.

DEVICE WATCHCAT.SYS
[Table of contents] [Index] [DEVICES]

WatchCat 2.1 device driver

DEVICE WCAST.SYS
[Table of contents] [Index] [DEVICES]

=drive:\MMOS2\WCAST.SYS /T=WCAST /F='C:\MMOS2\WCAST 1.INI' /N=1

Abbotsbury Software Ltd. driver for the Hauppauge WinTV line of cards.
Can be found on http://www.os2tv.com

DEVICE WIN32K.SYS
[Table of contents] [Index] [DEVICES]

win32k - Odin32 Ring 0 PE loader/converter for OS/2.


Odin is a free Open Source project with the goal to eventually provide a fully working Win32 (Win 95/98/NT/2000) runtime environment, making it possible to run your favorite Windows programs under OS/2, as if they were native OS/2 programs. The second goal of Odin is to provide the full Win32 application programming interface (API) so that it is possible to build OS/2 programs using Windows source code.

available at: http://www.netlabs.org

The win32k.sys driver makes PE (Win32) executables equal to native OS/2 executables by implementing a Ring 0 on-the-fly converter. The converter is Pe2Lx.exe. So, everything that works with Pe2Lx will probably work with win32k.sys. And vice versa, when Pe2lx can't handle it, win32k.sys won't either.

You may wonder how you may run a Win32 program using a device driver. You
don't have to worry about that, simply treat the Win32 program just as an another OS/2 program. OS/2 can't tell the difference! No conversion of dlls or running programs thru Pe.EXE.

Parameter:

-Quited Quiet driver initiation. Default: disabled (ie. -V)

-Verbose Verbose driver initiation. Default: enabled

-S: Full path to the current OS/2 kernel symbol file. When this is specified the given Default: symbol "database" and default locations are searched.


Loader parameters:

-SCript: Enable / disable UNIX script support. Default: Enabled.

-REXX: Enable / disable pure REXX script support. Default: Enabled.

-Java: Enable / disable JAVA loading.

-PE: Enabled / disable and set mode of the PE loading.

MIXED: Mix of Pe2Lx and Pe.exe. It uses Pe2Lx when possible and backs out to pe.exe if the executables aren't supported by the converter.

PE2LX: Pe2Lx loader only.

PE: Pe.exe only. The program is started using Pe.exe, and the process name will be pe.exe.

NOT: Disable PE loading.


Logging parameters:

-L<:E|:D> Enables/Disables logging. Default: disabled.

-Com:<1|2|3|4> or -C<1|2|3|4> Which com-port to log to. Default: -C2

-Warning:<1|2|3|4> or -W<1|2|3|4> Warning/info level for PE loader. (This is warnings and info which is published thru the com-port as logging information.) Default: -W0


Heap parameters:

-HEAPMax: Maximum swappable heap size in bytes. Default: 512KB

-Heapinit: Initial heapsize in bytes. Default: 16MB

-RESHEAPMax: Maximum resident heap size in bytes. Default: 256KB

-Resheapinit: Initial resident in bytes. Default: 16MB


OS/2 Loader parameter:

-Dllfixes<:E|:D> Enables or Disables the long DLL name and non .DLL extention fixes. OS/2 DLLs have been limited to 8 chars names since version 2.. This is a very bad limitation. Also OS/2 forces all DLL loaded to loadtime to have the extention '.DLL'. Both these retritions are removed if this option is enabled. For DLL with non .DLL extention the internal name must have to the extention included. (If you the experiences problems with IMPLIB.EXE, enclose the internal name in double-quotes.) You should not make a DLL with a name starting with DOSCALLS, DOSCALLS1, IBMVGA32, IBMDEV32 or IBMXGA32. Current state for this feature is EXPERIMENTAL. Default: Enabled


Obsolete:

-K: Ignored. Win32k scans the kernel image in memory!

DEVICE XF86SUP.SYS
[Table of contents] [Index] [DEVICES]

Driver for XFree86

<<=TIP=>> See the excellent guide by Rob Fargher in Voice 2/99 for installing XFREE

DEVICE YMF724.SYS
[Table of contents] [Index] [DEVICES]

PCI Yamaha YMF724 (DS-1) driver

<<=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


 
For dummies

Database of OS/2 compatible hardware

 
Reviews


     
  Why eComStation?
Features
Advantages
Usage
Clips and screenshots
   eComStation for
for businessmen
for students and engineers
for reselles of computers
community of users
   Developer
Distribute the program
Description of API, libraries
Start new project
Competition
   Applications
On-line catalogue
Select from eCo Market
   Support service
Contact the web-master
Buy eComStation
Frequently asked questions
for Beginners
 
 
© 2001 - 2021 eCo Software, All rights reserved
Сибирский Медведь технологическая компания
eComStation Serenity Systems International • OS/2 Warp IBM Corporation • ArcaOS Arca Noae