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.
BASEDEV installs a base device driver used by OS/2 when it is first started. The statement cannot contain either a drive or path because OS/2 cannot process such information at the stage at which these statements are loaded. These base device drivers include (not all delivered or available drivers are listed, but I've included most common and all additionally basedev's of the fixpaks):
The basedev's are loaded according to their extensions in the following order:
SYS
BID
VSD
TSD
ADD
I13
FLT
DMD
This means all basedevices with the extension SYS are loaded first and those with DMD last. This could also the reason for some trouble you might have.
For Warp 3 and 4 BASEDEV's must reside either in the root or in the \os2\boot directory. A rule IBM itself disregards e.g. with the IBM Thinkpad drivers. They are installed in \os2. If BASEDEVICE Drivers are not in these three directories (\;\os2;\os2\boot;) they will fail to work. In General it is recommended to copy all BASEDEVICE Drivers ONLY to your \os2\boot directory. If any installation routine copies them to another place please move them to \os2\boot.
<<=TIP=>> You can identify Driver failures by pressing ALT F2 during boot as long as the screen displays OS/2 in the upper left corner.
<<=TIP=>> Adding the /V (=Verbose) parameter to drivers could tell you some useful information. Example BASEDEV=IBM1S506.ADD /V
<<=TIP=>> OS/2 will install the BASEDEV in the order they appear in the CONFIG.SYS, you may need to rearrange the order in which drivers appear in the CONFIG.SYS.
<<=TIP=>> If you are using an Adaptec SCSI Card you can also use BASEDEV=AHA152X.ADD /V /F:x to force the target SCSI ID x. The host adapter will assume that the target ID x is connected to SCSI Bus.
<<=TIP=>> By Prof. C.W. Fischer Physics Department Director CPES Micro-Computer Lab. Users may be interested in a undocumented parameter on the Adaptec AHA154x.add file i.e /DBUFF. Anyone using this SCSI adapter will loose access to RAM above 16M. It's a Bus mastering problem on ISA (thanks to Steven Levine).
<<=NOTE=>> When you use Seagate Backup Exec for OS/2 Warp, Version 3.0 with both a hard drive and a SCSI or QIC backup device connected you have to add - to avoid DMA errors - the following to your driver line to prevent BUS errors: /V /A:0 /BON /A:0 /BOFF:8
supports SCSI on Adaptec 7870 Ultra Scsi controllers (e.g. AHA-2940) or earlier
Universal Parameters:
/ET -- Allow embedded targets. This parameter indicates that the ADD should assume that all targets have more than one logical unit (LUN) defined.
/!ET -- Do not allow embedded targets (DEFAULT). This parameter indicates that the ADD should assume that all targets have only one logical unit (LUN) defined.
/V -- Load driver verbosely. This parameter will display the driver name as well as the version number and Adaptec copyright if the driver loads successfully. Information on all targets found in the system will also be displayed.
/PCIHW -- Enables driver to access PCI configuration hardware registers. This switch is implemented because in some PCI systems, accessing PCI configuration space through PCI BIOS function calls causes problems. This switch is enabled by default. New with Version 3.02
/!PCIHW -- Disables the PCIHW switch. This parameter will cause the driver to access the PCI configuration space through PCI BIOS function calls. New with version 3.02
General Unit Parameters:
/I -- Ignore the specified adapter. This allows another driver to share the adapters that the ADD would normally use.
/DM -- Enable DASD manager support (DEFAULT). This parameter allows OS2DASD.DMD to control the specified target(s) if they are identified as DASD (hard disk) devices.
/!DM -- Disable DASD manager support. This parameter prevents OS2DASD.DMD from controlling the specified target(s).
/SM -- Enable SCSI manager support (DEFAULT). This parameter allows OS2SCSI.DMD to control the specified target(s) if they are identified as NON-DASD SCSI devices. All SCSI hard drives will be controlled by OS2DASD.DMD.
/!SM -- Disable SCSI manager support. This parameter prevents OS2SCSI.DMD from controlling the specified target(s).
/TAG:n -- n=1-16. Specifies the maximum number of tagged commands for all target devices on the host adapter (1-16). A value of 1 disables tagged queuing. The maximum number allowed is 16. (The default is 8.)
/UR -- Enables reporting of under runs (DEFAULT).
/!UR -- Disables reporting of under runs.
<<=TIP=>> If Warp doesn't recognise the AIC7870 Driver add the parameter /A:n n=Number of Controller and /TAG:n n=number of PCI-Slot to AIC7870.ADD. It seems that the version 2.2 of the Adaptec 2940 driver does not work correctly with RSJ, but version 2.11 works fine.
[Universal Parameter] - An option that applies to all adapters controlled by the driver.
[Adapter ID] - /A:n, where n is the number (zero relative) of the adapter installed in the system. The adapter ID is determined when the driver is loaded based on the order that adapters are found in the system. (Refer to the Configuration Examples in the "General Unit Parameters" section below for information on how to use this option.)
[Unit Parameter] - Modifies the behavior of the selected host adapter.
[SCSI Target ID] - The targets to which the Unit Parameter will be applied. This parameter may be a single ID (d) or list of IDs (d,d,d).
Universal Parameters:
/ET -- Allow embedded targets. This parameter indicates that the ADD should assume that all targets have more than one logical unit (LUN) defined.
/!ET -- Do not allow embedded targets (DEFAULT). This parameter indicates that the ADD should assume that all targets have only one logical unit (LUN) defined.
/V -- Load driver verbosely. This parameter will display the driver name as well as the version number and Adaptec copyright if the driver loads successfully. Information on all targets found in the system will also be displayed.
Unit Parameters:
General:
/I -- Ignore the specified adapter. This allows another driver to share the adapters that the ADD would normally use.
/DM -- Enable DASD manager support (DEFAULT). This parameter allows OS2DASD.DMD to control the specified target(s) if they are identified as DASD (hard disk) devices.
/!DM -- Disable DASD manager support. This parameter prevents OS2DASD.DMD from controlling the specified target(s).
/SM -- Enable SCSI manager support (DEFAULT). This parameter allows OS2SCSI.DMD to control the specified target(s) if they are identified as NON-DASD SCSI devices. All SCSI hard drives will be controlled by OS2DASD.DMD.
/!SM -- Disable SCSI manager support. This parameter prevents OS2SCSI.DMD from controlling the specified target(s).
/TAG -- Specifies the maximum number of tagged commands for all target devices on the host adapter (1-16). A value of 1 disables tagged queuing. The maximum number allowed is 16. (The default is 8.)
/UR -- Enables reporting of under runs (DEFAULT).
/!UR -- Disables reporting of under runs.
<<=NOTE=>>
Intel Errata #8511 lists known data integrity issues with the processor cache on the Saturn-1 chipset (82424TX). For this reason, Adaptec recommends that processor cache be disabled via the CMOS setup to avoid data corruption. For more information, see Intel Errata #8511. You may get this from Intel's FaxBack system at 800.628.2283 or 916.356.3105.
There are installation problems when installing on the maximum hard disk drive partition size supported by OS/2 v3.0. On OS/2 v3.0 it is a known problem. Refer to IBM for further info. IBM's APARs PJ15988 and PJ 6151 deal with this issue.
There are known installation problems installing OS/2 Warp v4.0 on a Micron (LSI chipset) 64 bit PCI system.
There are known installation problems installing OS/2 Warp with 8MB of RAM unless all the third-party basedev statements are removed from config.sys.
There are known installation problems installing OS/2 using two SCSI host adapters on a "Marl" motherboard. Whenever you have a LVD HDD on one Ultra160 host adapter and a HDD, CD-ROM, and removable Syjet on another UltraSCSI host adapter, Syjet conflicts with the CD-ROM and the system is unable to access the CD-ROM.
This version of the Ultra160 Family Manager Set driver supports the AIC-7892/99 Family of Host Adapters. Adapter numbers are first assigned to boards with their BIOS enabled. The numbers are assigned from lowest BIOS address to highest address. Any remaining boards are assigned numbers by scanning slots. Each slot is a combination of a bus number and a device number pair starting from lowest to highest numbers, and the adapters are assigned a number in the order they are found.
Example: Bus 0, device 0 assigned as adapter 0; Bus 1, device 1 assigned as adapter 1, etc.
There are no switches for controlling OS2ASPI.DMD directly. IBM did not define them in their specification and Adaptec cannot be sure that other host adapters will have the same switches. OS2SCSI.DMD will only allocate devices when a device driver requests it, but this will prevent OS2ASPI from accessing it. There is nothing in the ASPI specification regarding device allocation so OS2ASPI must rely on other managers to fairly share targets. This should only be a problem if you have two drivers that use different managers and you want them both to access the same target at the same time.
Do NOT disable DASD manager access to target 0 if you are booting from your SCSI host adapter. This will prevent the system from booting!
Fault Tolerance is supported in the driver. However, ABORT and SCSI BUS RESET will only work for targets that are properly behaved.
IBM does not support installing the operating system onto magneto optical devices. Additionally, OPTICAL.SYS (OS/2 3.0) or OPTICAL.DMD (OS/2 4.0) allows magneto optical devices to be supported as though they were large floppy devices.
LOCKDRV.FLT allows removable media such as MO's to be supported as though they were fixed hard drives. It is not possible to install OS/2 3.0 on drives with capacity greater than 8 GB, nor in a partition greater than 4 GB.
OS/2 will allocate the SCSI devices as the order in CONFIG.SYS if two drivers (such as the AIC7870.ADD and AICU160.ADD) are loaded. OS/2 will assign drive letters for SCSI devices first then IDE devices.
/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.
/P:xxx - SB cards base address.
/M:xxx - MKE compatible cards CDRom base address.
/T:x - Switch for standalone cards. if x=1 then it is a Sound card. (Default),if x=2 then it is a standalone card.
/D:x - Double Speed switch.
/N:x - Single Speed switch. if x=0 to x=3 implies the drive number, ix x=a implies that all drives are to be made double or single speed. /d:a is default.
/NS - No scan. Implies that only one drive present with ID=0 and will not scan for other drives. Scaning for all drives is default procedure.
Disk adapter drivers for the ERACOM (www.eracom.com.au) PCVault product used by a number of banks. The product gives transparent hard disk encryption amongst other things.
<<=IMPORTANT NOTE=>> The order of the base drivers must be:
basedev=cryp2x.sys
basedev=crypie2x.sys
basedev=edasdf.flt
And they should be at the end of the config.sys
Disk adapter drivers for the ERACOM (www.eracom.com.au) PCVault product used by a number of banks. The product gives transparent hard disk encryption amongst other things.
<<=IMPORTANT NOTE=>> The order of the base drivers must be:
basedev=cryp2x.sys
basedev=crypie2x.sys
basedev=edasdf.flt
And they should be at the end of the config.sys
/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)
If yes REM or delete them, otherwise you'll get a trap with PMMERGE and QUERYMCD at boot. Tested with Warp 4, FP15.
<<=NOTE=>> When you have the Flash Navigator Plug-In installed, disable the sound in 'about.plugins' Flash settings, otherwise your system will freeze and you have to reboot whenever you visit a site with Flash.
replacement for IBMATAPI.FLT by Daniela Engert (d.engert@odn.de). This filter driver supports all of the ATAPI disks that IBMATAPI does (LS-120, ZIP-100, JAZZ), and in addition the ZIP-250 (including full media swapping). Superceded by DANIATAPI.FLT.
This highly recommended filter driver supports all types of ATAPI devices by Daniela Engert (dani@ngrt.de) shortened to the 8.3 naming convention for use on floppy-bootdisks. See BASEDEV DANIATAPI.FLT for more information
This highly recommended filter driver supports all types of ATAPI devices by Daniela Engert (dani@ngrt.de). It is a superset of IBMIDECD.FLT, IBMATAPI.FLT and DaniADsk.FLT, and supports all devices that the mentioned drivers do. Additionally, all ATAPI devices can be accessed through the OS/2 ASPI software interface. Each EIDE channel shows up as a SCSI channel, and each ATAPI device as a SCSI device (master = SCSI ID 0, slave = SCSI ID 1).
<<=NOTE=>> Make sure that all other ATAPI related drivers are inactive or come after DaniATAPI.FLT in your CONFIG.SYS. If you intend to run the BootOS utility or to install this filter driver on a 8.3-only filesystem, rename the driver to DaniATAP.FLT.
- can deal with the ATAPI ZIP-250
- improved ZIP performance (up to factor 4 on ZIP-250)
- supports arbitrary swapping of 100MB and 250MB media
- reflects the current media capacity up to FDISK, DISKIO or the like
- OS/2 boot from ZIP is possible
- faster 32bit PIO in conjunction with DANIS506.ADD (rel. 1.1.1 or later)
- Busmaster DMA mode works and is tested with Intel, VIA, AMD, HPT, SiS and CMD chipsets until now. Busmaster DMA is available now for ALi as well (CD/DVD-ROM is safe, but some chip revisions fail on DMA write operations!). Due to hardware limitations there is no 32bit PIO and no busmaster DMA possible for ATAPI devices attached to a Promise Ultra controller.
- ATAPI devices appear to the rest of the system as regular SCSI-2 devices if used with DANIS506.ADD (rel. 1.1.5 or later). This may be disabled globally or individually.
- advanced "hot-swap" support if used with DANIS506.ADD (rel. 1.1.9 or later)
- support for PCCard (formerly: PCMCIA) ATAPI devices (like the Iomega PCMCIA ZIP-250 or the Iomega Click!40)
- the translation of old-style 6-byte SCSI commands into their more modern 10-byte counterparts is no longer hardcoded. The device is sensed now to check if it requires this translation.
- like DaniS506.ADD, this driver stores boot messages internally for later readout. To view them, issue "copy ATAPI$ con:", to dump them into a file, issue "copy ATAPI$ anyfile".
- automatic media unload on shutdown if desired
Parameter:
This driver supports all switches and options that IBM1ATAPI.FLT supports.
/SCSI The export of ATAPI devices as SCSI-2 device can be enabled and/or disabled globally, per adapter channel, or per individual unit by adding the options /SCSI or /!SCSI. If these options are in front of any /A: option, they apply globally. If they come after an /A:x option but before any /U: option, they apply to adapter channel x and override the global setting. If they come after any /U:y option, then they apply to the single unit y only and override both the global and the adapter setting. Default is a global visibility of all ATAPI devices as SCSI devices.
The export is globally disabled also and cannot be overridden if the driver is renamed to any name beginning with IBM (case insensitive). This avoids confusion of the OS/2 installer if you replace IBMIDECD.FLT on installation disk #1 by a renamed version of DaniATAPI.FLT.
/ZA To enable booting OS/2 from an ATAPI ZIP drive, I introduced the new /ZA switch ('map ZIP to A:'). It takes effect only if the BIOS has mapped the ZIP to drive letter A: in order to boot from it; in all other cases the /ZA option is a no-op.
If there are floppy disk drives in your system, then - as a side effect - /ZA remaps floppy drive A: to B:, and floppy drive B: (if present) is no longer accessable. Due to limitations in OS2DASD.DMD (?) floppy reads and writes are a little 'rocky' in this case.
A boot from ZIP automatically locks the boot medium in the drive, media swapping is no longer possible! This lock is imposed automatically by OS2DASD. If you insist to eject the locked medium by the 'eject' command, this command obviously is routed into nirvana and causes a kernel trap.
/EJ Some people (like me) don't like media left in removable media devices (especially ZIP drives) on system shutdown, but tend to forget to eject them before powering down the system. The new /EJ option fills the void. If /EJ appears in front of all /A:n options, it acts globally on all devices controlled by DANIATAPI.FLT; if /EJ comes after an /A:n but before accompanied /U:m options, it acts on all units of that adapter channel; if it comes after an /U:m option, /EJ acts only on that particular unit. In any case, all units marked by /EJ receive a command to eject inserted media on shutdown right after file systems are closed.
/TYPE Units marked as "hot-swappable" on DANIS506.ADD's command line (by /FORCE /ATAPI) need the new option /TYPE: to advice DaniATAPI.FLT to report appropriate device types to the device managers. The same applies to PCCard adapter channels (marked as /FORCE /PCMCIA on DANIS506.ADD's command line). This is done by additional characters designating the supported device types:
'c' or 'C': all CD-ROM like devices (CD-ROM, CD-R/W, DVD-ROM, DVD-RAM) 'z' or 'Z': all ZIP drives 'l' or 'L': the LS-120 drive
There may be more in the future. Some examples on how to use this option:
1) You have an IBM ThinkPad 600 and intend to plug a floppy drive, a CD-ROM, and a ZIP-100 into its UltraBay. The TPs have got the UltraBay connected to the secondary EIDE port. Then you need
2) You have notebook which can be equipped with either a LS-120 drive, a DVD-ROM, or a CD writer. Then you need
BASEDEV=DaniATAPI.FLT /A:x /U:y /TYPE:CL
To pick the correct values for /A and /U have a look at the boot messages.
INTEROPERABILITY TIPS
In general, DaniATAPI.FLT is intended to replace all other EIDE ATAPI filter drivers. If you need to run another filter driver, there are two choices:
1) list DaniATAPI.FLT before all other EIDE filter drivers in CONFIG.SYS and disable it on a particular adapter by /A:x /I.
2) list DaniATAPI.FLT after all other EIDE filter drivers in CONFIG.SYS and let it control the ATAPI units left over.
CDRecord:
There are no further options required if you like to run CDRecord/2, but not RSJ with your CD writer. The writer is visible to CDRecord as a regular SCSI CD writer by default. Just run "CDRecord -scanbus" to locate the CD writer on one of the SCSI buses and memorize its address (bus,unit,lun).
RSJ:
DaniATAPI.FLT is fully compatible to the RSJ cdwriter filesystem and its accompanied utilities. In fact, if you run DaniATAPI.FLT instead of RSJIDECD.FLT you can take advantage of the improved data transfer modes (32bit PIO and busmaster DMA) on all supported chipsets (RSJIDECD.FLT is derived from IBMIDECD.FLT and thus supports busmaster DMA on Intel chipsets only). If your CD writer model is listed cddrv.inf you don't even need *** LOCKCDR.FLT; DaniATAPI.FLT reorders its SCSI unit mapping if it finds a CD writer unit so that RSJ is happy.
So there are several choices available (listed in order of preference)
1) BASEDEV=DaniATAPI.FLT
This enables full use of the CD writer unit as regular CD ROM device, RSJ writer device, and CDRecord writer device. If your particular model isn't listed in RSJ's cddrv.inf, then you need to add a line reading like this example:
Important is this part ^^^^^^^^^^^^^^^^^^^^^^^, it *must* match the SCSI IDENTIFY string of your particular model.
Caution: some devices return different identification strings for the ATAPI IDENTIFY and the SCSI IDENTIFY commands! The former one is shown at boot or some ATA/ATAPI tools, the latter one can be seen with some SCSI bus interrogators (e.g. "CDRecord -scanbus");
in case of a pre-3.0 version of RSJ, change the line into
2) BASEDEV=DaniATAPI.FLT or or
BASEDEV=LOCKCDR.FLT
This disables using the CD writer unit as a regular CD ROM drive. You better prevent DaniATAPI.FLT from exporting the CD writer as SCSI device by applying one of the /!SCSI options, because it will be exported by LOCKCDR.FLT now (too). Both RSJ and CDRecord may use the writer. If your CD writer model isn't listed in cddrv.inf, LOCKCDR.FLT from RSJ 3.x will autodetect and autoconfigure it.
This is very similar to the section above, but DaniATAPI will install an additional backdoor to re-enable regular CD ROM operation via OS2CDROM.DMD (or replacements).
Now RSJIDECD.FLT will control *all* CD-ROM/R/RW/RAM and DVD-ROM/RAM devices, DaniATAPI.FLT all other ATAPI devices. None of the advanced data transfer modes are available on non-Intel chipsets which is particularly bad on fast CD writers where little impact on CPU load is desirable.
BackAgain:
DaniATAPI.FLT is supposed to work with ATAPI tape drives. Thus CDSEIDE.FLT should no longer be required. Unfortunately BA2K doesn't support the OnStream DI-30 tape drive that I have available so I cannot check if DaniATAPI.FLT will work flawlessly with other supported tape drives.
SANE:
SANE users may find that the SCSI bus number, for their scanner, will change when DaniATAPI.FLT is used. You may need to run FIND-SCANNER.EXE, and edit the scanner address in the *.CONF file, to correct the address. This should be a one time change, unless you switch back to the IBM supplied drivers.
Replacement Driver for OS2DASD.DMD by Daniela Engert supports also Partiontypes 0B, 0C and 0F to ease the coexistance with WinXY
For a discussion of these types see: Introduction, Partition types
<<=NOTE=>> DANIDASD.DMD does not work with OS2LVM.DMD, so use it in NON-LVM Systems only.
<<=NOTE=>> Together with DANIDASD.DMD the use of PARTFILT.FLT is no longer necessary to access FAT32 drives.
Parameter:
/BD: overcomes boot problems which result in "can't operate hard disk" messages. This is common if OS/2 is booted without proper help of OS/2 Bootmanager which is required to notify OS/2 of the *correct* boot drive letter. If there is no boot manager with this capability available (e.g. when booting from removable media), or the boot manager fails to figure out the correct boot drive letter, you can tell DaniDASD.DMD the correct one which will override the boot drive letter assignment from the first boot stage.
Example: in a mixed SCSI/EIDE environment with two SCSI adapters and two different EIDE controllers involved (my current setup at home), the ATAPI ZIP250 drive gets assigned drive letter M:. To boot from this unit I have this line in CONFIG.SYS of the ZIP boot floppy
BASEDEV=DaniDASD.DMD /BD:M
<<=TIP=>> You may also need a FAT32 aware FDISK.EXE. It was included in FP10 - FP14 for Warp4
<<=TIP=>> By Daniela Engert:
You want to get rid of the LVM layer in WSeB/ACP/MCP/eCS ?
I checked that on an old WSeB installation with only compatibility volumes, yesterday. I removed these two lines in CONFIG.SYS
BASEDEV=OS2DASD.DMD // the LVM-aware DASD manager
BASEDEV=OS2LVM.DMD // the LVM layer
and added this single line
BASEDEV=DaniDASD.DMD // the non-LVM-aware DASD manager
The system behaved DASD wise like an ordinary Warp4 system afterwards. A Warp4 OS2DASD.DMD will do as well.
Highly recommended replacement IBM1S506.ADD EIDE driver by Daniela Engert (d.engert@odn.de)
EIDE driver with support for Intel, VIA, ALi, SiS, CMD, Promise, Cyrix, HighPoint, AMD, SMSC, ServerWorks, and Opti chipsets, and generic busmaster support for all SFF-8038i compliant chips.
Enhancements are:
- (supports the Intel PIIX, just like IBM1S506 does) plus some PIIX4 variants unsupported by IBM1S506
- supports the Intel i8xx ICH/ICH0/ICH2 (Whitney/Camino/Carmel/Solano)
- supports the VIA 571 IDE controller
- supports the ALi 5229 IDE controller
- supports the SiS 5513 IDE controller
- supports the CMD 643/646/648/649 IDE controllers (this includes OEMs like AMI)
- supports the Promise Ultra33/66/100 IDE controllers
- supports the Cyrix 5530 IDE controller (Cyrix MediaGX)
- supports the HighPoint HPT366/368/370 IDE controller
- supports the AMD756 and AMD766 (experimental) IDE controllers
- supports the Artop ATP850UF and ATP860 (experimental) IDE controllers
- supports the SMSC SLC90E66 IDE controller (PIIX4 look-alike) (exp.)
- supports the ServerWorks ROSB4 IDE controller
- supports the Opti IDE controllers
- generic busmaster support for SFF-8038i compliant controllers
- supports PCCard (formerly: PCMCIA) ATA/ATAPI controllers
- supports the external DriveBay and other PCCard attached units
- no need for chipset initialization by the BIOS (Intel, VIA, ALi, SiS, CMD, Promise, and HighPoint)
- Ultra33-DMA on all of the above chipsets which can do Ultra-DMA
- Ultra ATA-66 on AMD, VIA, SiS, Promise, HighPoint, Intel, CMD, ALi, and SMSC
- Ultra ATA-100 on HighPoint, Promise, VIA, CMD, Intel (these all tested),
- AMD, ALi, and SiS (all of these experimental).
- faster PIO due to 32bit IO
- sets device inactivity timers (POWERSV.SYS is no longer needed)
- adjustable SMS length
- adjustable drive noise level
- improved support for removable media drives (in particular Castlewood ORB EIDE)
- can change removable media drives to fixed media drives and vice-versa
- supports devices which don't spin up automatically
- optional limit data transfer rates for more reliability
- adapts/auto-adapts chip timings to PCI clock
- supposed to work with drive capacities up to 128GB (ATA limit), tested with drives up to 75GB now
- improved compatibility with current BIOSes (IBM1S506.ADD fails on an increasing number of recent BIOS implementations)
- performance and feature tuning options
- up to 8 EIDE channels
- some fixes for bugs introduced with the last release
- some fixes for bugs and omissions in the IBM code ;-)
Parameter:
Universal:
/!V /VL /VLL (quiet) (not) Verbose mode (less/lesser verbose)
/!W /WL /WLL (quiet) same as /!V, but pauses screen
/!AA (beep) No Audible Alerts
/PCLK:x (33MHz) PCI Clock (DECIMAL)
/GBM (off) Generic Busmaster Mode
/FORCEGBM (off) Force Generic Busmaster mode
/!SHUTDOWN (not) Shutdown each attached device
/MGAFIX (off) Fix problem with Matrox drivers
/DEBUG:n (0) Set debug level (DECIMAL)
/!BIOS (call BIOS) Disable all BIOS Int13 calls
Adapter
/A:n (n/a) Adapter number (0, 1, .. 7)
/!R (enable) Disable adapter resets
/P:hhh (PCI, Snooper) Base port address (HEX)
/PORT:hhh same as /P
/IRQ:n (PCI, Snooper) IRQ level (DECIMAL)
/I (off) Ignore adapter
/!BM (ATA : enable)(not) Enable BusMaster DMA (ATAPI: disable)
/PF:xxxx (0) Register access timings
/80WIRE (autodetect) 80 wire cable present
/FORCEGBM (off) Force Generic Busmaster mode
/PCMCIA (off) channel is implemented by PCCard adapter
/TO:n (DECIMAL) (5s/dynamic) Interrupt timeout
Unit
/U:n (n/a) Unit number (0, 1)
/UNIT:n same as /U
/T:n (5s) Error retry time in seconds (DECIMAL)
/GEO:n,n,n,n (autodetect) Drive geometry override (DECIMAL)
/!SMS (autodetect) Disable block mode
/SMS:n (autodetect) Set SMS block length to n
/LBA (autodetect) LBA addressing support
/!DM (off) Prevents OS2DASD.DMD from managing the device
/FORCE (off) Force unit present
/!ATAPI (autodetect) Force (not) ATAPI device
/IT:x (BIOS) Inactivity timer (DECIMAL)
/MR:udp (maximum) Limit data rate of a device
/PF:xxxx (0) Register access timings
/!RMV (device default) (not) removable media drive
/NL:n (current device noise level, n = 0 (faint) ... 126 (noisysetting)
Obsolete
/!CYLA
/DC:n
/!DSG
/DT:x
/NEC
Undocumented
/RESMGR
Rule of thumb: if your system doesn't suffer from any (possibly unknown) flaws, not a single command line option is required. The driver adapts itself to the environment and runs at maximum performance.
In some situations, you may need some of the following options to achieve optimum performance:
- by default, ATAPI devices are initialized to PIO mode only. If you intend to run particular ATAPI devices using busmaster DMA, apply the proper /A:x /U:y /BM options.
For a detailed discussion of all parameters see the Danis506.doc delivered with the driver.
/S[=ID-List] Forces Safe transfermode. Optionally you can specify the target-id's, otherwise this parameter is valid for all targets.
Examples:
/S ;forces safe mode for all targets
/S=0,1,2,3 ;forces safe mode for target-id's 0,1,2 and 3
/S=0;1;2;3 ;same as above
/S=0123 ;same as above
/S:0123 ;same as above
/S=0,1;23 ;same as above
/U[=ID-List] Forces Uni-Directional transfermode. Optionally you can specify the target-id's, otherwise this parameter is valid for all targets.
/B[=ID-List] Forces Bi-Directional transfermode. Optionally you can specify the target-id's, otherwise this parameter is valid for all targets.
/US[=ID-List] Forces Uni-Directional Safe transfermode. Optionally you can specify the target-id's, otherwise this parameter is valid for all targets.
/BS[=ID-List] Forces Bi-Directional Safe transfermode. Optionally you can specify the target-id's, otherwise this parameter is valid for all targets.
/EPP8[=ID-List] Forces EPP-Byte mode. This parameter can help to solve problems related to some EPP port hardware. Optionally you can specify the target-id's, otherwise this parameter is valid for all targets.
/PORT=xxx xxx=378, 278 or 3BC, this parameter selects the I/O address the driver should use. Normaly you don't need this parameter, because the driver automatically detects the port, where the SCSI cable is connected. If the driver fails to do this or in case of conflict with other adapter cards this parameter will force the driver to check only the given port address.
/PORT=xxx If you are working with several SCSI hostadapters, type in the adapter number (for PCI hostadapters, starting with zero) or the I/O address (for ISA hostadapters) as the parameter's attribute. In this case, you will have to start the driver by specifying the adapter number or I/O address resp. for every connected hostadapter separately. This parameter is not required if you are working with only one SCSI hostadapter.
/PS=x This parameter controls the Power Save function by specifying the maximum inactivity period (from 1 to 60 minutes). If the set value is exceeded, any hard disks, removable disks and CD ROM drives will be switched off automatically. The relevant device will be started again when it is accessed later. Not setting this parameter means that the function is disabled.
/ID=x x = hostadapter's SCSI ID. The SCSI ID of the hostadapter will be set automatically if this parameter is not specified. Valid SCSI ID values are 0 to 7. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/LUN This parameter enables the device's support of several LUNs (Logical Units). However, most SCSI devices only have LUN 0 available to them so that you will need this parameter only for special cases. Host adapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/!SN=x,..,x This parameter defines the devices that are to run in asynchronous instead of in synchronous mode even if the device tries to switch into synchronous mode. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/SN=x,..,x This parameter specifies the devices to be operated in Synchronous Data Transfer mode if this mode is supported by these devices. If you do not set this parameter only devices that can switch into synchronous mode themselves will be operated in this mode, all other devices will remain in asynchronousmode.
/!SM=x,..,x Use this parameter to specify a list of SCSI IDs representing the devices that are not to be supported by OS/2's Device Manager. As a rule, all connected devices can be controlled by the SCSI Device Manager.
/!DM=x,..,x Use this parameter to specify a list of SCSI IDs representing the
devices that are not to be supported by OS/2's DASD Manager (Device Manager for disk drives). As a rule, all connected devices can be controlled by DASD Manager.
/Q Suppresses all onscreen messages (including error messages) during driver installation.
<<=NOTE=>> For using scanners please insert the following parameters in the adapter-settings /!SN=(Scanner ID) /!DISC=(Scanners ID) Example: the scanner's ID is 6: /!SN=6 /!DISC=6.
/PORT=xxx If you are working with several SCSI hostadapters, type in the adapter number (for PCI hostadapters, starting with zero) or the I/O address (for ISA hostadapters) as the parameter's attribute. In this case, you will have to start the driver by specifying the adapter number or I/O address resp. for every connected hostadapter separately. This parameter is not required if you are working with only one SCSI hostadapter.
/PS=x This parameter controls the Power Save function by specifying the maximum inactivity period (from 1 to 60 minutes). If the set value is exceeded, any hard disks, removable disks and CD ROM drives will be switched off automatically. The relevant device will be started again when it is accessed later. Not setting this parameter means that the function is disabled.
/ID=x x = hostadapter's SCSI ID. The SCSI ID of the hostadapter will be set automatically if this parameter is not specified. Valid SCSI ID values are 0 to 7. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/LUN This parameter enables the device's support of several LUNs (Logical Units). However, most SCSI devices only have LUN 0 available to them so that you will need this parameter only for special cases. Host adapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/!SN=x,..,x This parameter defines the devices that are to run in asynchronous instead of in synchronous mode even if the device tries to switch into synchronous mode. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/SN=x,..,x This parameter specifies the devices to be operated in Synchronous Data Transfer mode if this mode is supported by these devices. If you do not set this parameter only devices that can switch into synchronous mode themselves will be operated in this mode, all other devices will remain in asynchronousmode.
/!SM=x,..,x Use this parameter to specify a list of SCSI IDs representing the devices that are not to be supported by OS/2's Device Manager. As a rule, all connected devices can be controlled by the SCSI Device Manager.
/!DM=x,..,x Use this parameter to specify a list of SCSI IDs representing the
devices that are not to be supported by OS/2's DASD Manager (Device Manager for disk drives). As a rule, all connected devices can be controlled by DASD Manager.
/Q Suppresses all on screen messages (including error messages) during driver installation.
/PORT=xxx If you are working with several SCSI hostadapters, type in the adapter number (for PCI hostadapters, starting with zero) or the I/O address (for ISA hostadapters) as the parameter's attribute. In this case, you will have to start the driver by specifying the adapter number or I/O address resp. for every connected hostadapter separately. This parameter is not required if you are working with only one SCSI hostadapter.
/PS=x This parameter controls the Power Save function by specifying the maximum inactivity period (from 1 to 60 minutes). If the set value is exceeded, any hard disks, removable disks and CD ROM drives will be switched off automatically. The relevant device will be started again when it is accessed later. Not setting this parameter means that the function is disabled.
/ID=x x = hostadapter's SCSI ID. The SCSI ID of the hostadapter will be set automatically if this parameter is not specified. Valid SCSI ID values are 0 to 7. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/LUN This parameter enables the device's support of several LUNs (Logical Units). However, most SCSI devices only have LUN 0 available to them so that you will need this parameter only for special cases. Host adapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/!SN=x,..,x This parameter defines the devices that are to run in asynchronous instead of in synchronous mode even if the device tries to switch into synchronous mode. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/SN=x,..,x This parameter specifies the devices to be operated in Synchronous Data Transfer mode if this mode is supported by these devices. If you do not set this parameter only devices that can switch into synchronous mode themselves will be operated in this mode, all other devices will remain in asynchronousmode.
/!SM=x,..,x Use this parameter to specify a list of SCSI IDs representing the devices that are not to be supported by OS/2's Device Manager. As a rule, all connected devices can be controlled by the SCSI Device Manager.
/!DM=x,..,x Use this parameter to specify a list of SCSI IDs representing the
devices that are not to be supported by OS/2's DASD Manager (Device Manager for disk drives). As a rule, all connected devices can be controlled by DASD Manager.
/Q Suppresses all on screen messages (including error messages) during driver installation.
/PORT=xxx If you are working with several SCSI hostadapters, type in the adapter number (for PCI hostadapters, starting with zero) or the I/O address (for ISA hostadapters) as the parameter's attribute. In this case, you will have to start the driver by specifying the adapter number or I/O address resp. for every connected hostadapter separately. This parameter is not required if you are working with only one SCSI hostadapter.
/PS=x This parameter controls the Power Save function by specifying the maximum inactivity period (from 1 to 60 minutes). If the set value is exceeded, any hard disks, removable disks and CD ROM drives will be switched off automatically. The relevant device will be started again when it is accessed later. Not setting this parameter means that the function is disabled.
/ID=x x = hostadapter's SCSI ID. The SCSI ID of the hostadapter will be set automatically if this parameter is not specified. Valid SCSI ID values are 0 to 7. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/LUN This parameter enables the device's support of several LUNs (Logical Units). However, most SCSI devices only have LUN 0 available to them so that you will need this parameter only for special cases. Host adapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/!SN=x,..,x This parameter defines the devices that are to run in asynchronous instead of in synchronous mode even if the device tries to switch into synchronous mode. Hostadapters supplied with a SCSI setup ignore this parameter and use the setup settings instead.
/SN=x,..,x This parameter specifies the devices to be operated in Synchronous Data Transfer mode if this mode is supported by these devices. If you do not set this parameter only devices that can switch into synchronous mode themselves will be operated in this mode, all other devices will remain in asynchronousmode.
/!SM=x,..,x Use this parameter to specify a list of SCSI IDs representing the devices that are not to be supported by OS/2's Device Manager. As a rule, all connected devices can be controlled by the SCSI Device Manager.
/!DM=x,..,x Use this parameter to specify a list of SCSI IDs representing the
devices that are not to be supported by OS/2's DASD Manager (Device Manager for disk drives). As a rule, all connected devices can be controlled by DASD Manager.
/Q Suppresses all on screen messages (including error messages) during driver installation.
Encryption adapter driver for the ERACOM (www.eracom.com.au) PCVault product used by a number of banks. The product gives transparent hard disk encryption amongst other things.
<<=IMPORTANT NOTE=>> The order of the base drivers must be:
basedev=cryp2x.sys
basedev=crypie2x.sys
basedev=edasdf.flt
And they should be at the end of the config.sys
a filter device driver for OS/2 that makes it possible to load an IFS for linux partitions. (Without this filter you must patch the partition table. On many systems doing so may cause LILO to fail.).
Ext2flt.flt is part of the EXT2-OS2.ZIP package. Together with you can also hide the falsely recognised NTFS.
In addition this driver is capable to control in what order drive letters are assigned to partitions on fixed disks. It will also allow you to access hidden primary partitions under OS/2.
Parameter:
/Q Quiet install. Prevents the filter from displaying messages.
/V Verbose install. Displays some diagnostic messages.
/W Allows the virtual partitions to be written to.
/A Virtualize all partitions found. The only good reason to use this is along with the /M option when you want to control the mounting order of all the partitions. You must use the /W option if you use the /A option; otherwise OS/2 may crash when it tries to write to the partition.
<<=NOTE=>> Using the /A option may change your drive letters causing the your system to be unbootable. Use the /M option together with /A. (This may change in the future.
/M Mounts the partitions in the order specified in the mount list, which should be a list of numbers separated by commas. The partitions are numbered 0 on a first come basis. (Not the OS/2 uses.)
/V - Verbose switch. This switch enables driver verbosity at initialization time.
/QU - Warning-error suppression switch. When invoked, the driver will not complain about references to non-existent targets/LUNs specified on the BusLogic ADD driver command line.
/O - Early Opti chipset work-around switch. This switch provides a work-around for an early version of the Opti PCI chipset which can generate spurious interrupts. Do not use this option unless your system hangs at boot-time and you are using an Opti chipset.
/SH - Allow sharing of IRQ across different host adapter families. This option is not necessary when sharing an IRQ within the FlashPoint product family. A side-effect of using this switch is less responsive mouse and keyboard event recognition during heavy I/O.
/A:x - Adapter identification switch. x is between 0 and 5 and identifies the adapter being referenced. This switch is followed by one or more of the switches below.
/DM:xx - DASD Manager Support switch. As defined by IBM, this switch enables/disables support for this unit by the IBM-supplied DASD Manager (OS2DASD.DMD).
/SM:xx SCSI Manager Support switch. As defined by IBM, this switch enables/disables support for this unit by the IBM-supplied SCSI Manager (OS2SCSI.DMD).
/TQ - Enable tagged queuing support on ALL targets on the specified host adapter (specified by the receding /A: switch) that supports tagged queuing.
<<=NOTE=>> Tagged queuing is an advanced SCSI-II feature that allows overlapped commands to a SCSI device, resulting in enhanced performance. While BusLogic provides support for this important SCSI-II feature, not all SCSI devices support tagged queuing. The SCSI device must support tagged queuing to take advantage of this feature.
BusLogic's OS/2 SCSI Adapter Driver defaults to tagged queuing DISABLED on all devices. For devices that support tagged queuing, the following command line switches are provided to manage tagged queuing support on a finer device-specific level.
/TQ:x,y,z,... - Enable tagged queuing support on a specified list of SCSI targets. x,y,and z is a list of embedded SCSI targets separated by commas. The Logical Unit Number (LUN) is presumed to be 0.
/TQ:(a,b), (c,d), ... - Enable tagged queuing support on a specified list of pairs of SCSI targets/LUNs in parenthesies. Each parenthesized pair is separated by commas.
/LUNS:xx - This switch specifies the maximum number of Logical Units (LUNs) the host adapter will support (try to detect). If the switch is not specified, the default is 8. Valid range is from 1 to 32. If the host adapter only has embedded SCSI targets attached (that is, all attached devices are at LUN 0), it is recommended to set this option value to 1 to turn off LUN support for LUNs other than 0.
/TO:xx - Command Timeout switch. This per-host adapter switch specifies a timeout on each I/O request in seconds. It takes a decimal digit input between 1 and 99. The driver default is 15 seconds in this absence of this switch. Setting the timeout value to 0 turns off the timeout mechanism.
<<=NOTE=>> This switch has no effect on tape requests.
/MR:xx - Maximum Request switch. This per-host adapter switch specifies the maximum number of requests that can be pending on the host adapter. Valid range is 1 - 64. Default is 16.
/MA:xx - Maximum Active switch. This per-host adapter switch specifies the maximum number of active requests that can be outstanding on each device on the host adapter. Valid range is 1 - . Default is 8. This value can be adjusted to increase performance.
supports diskette drives on non-Micro Channel PC's.
<<=TIP=>> If you wish to prevent users from using the floppy drives under OS/2 (to keep them from loading non-authorised programs or in a workstation situation), REM the BASEDEV=IBMxFLPY.ADD line (where x is 1 for ISA and EISA machines, or 2 for Microchannel).
<<=NOTE=>> In Warp, the install program may have placed both IBM1FLPY.ADD and IBM2FLPY.ADD BASEDEV drivers in your config.sys. Remove IBM2FLPY.ADD if you don't have a Micro Channel PC.
The correct setting for e.g. a IBM Thinkpad 560 with external floppy disk is (see the Warp Reference book for a detailed description):
BASEDEV=IBM1FLPY.ADD /A:0 /FORCE:2 /U:0 /F:1.44MB /U:1 /F:1.44MB
Using the /DAPM Parameter (which disables the Power Managment) may also help on some Notebooks (e.g. Thinkpad 600) who can't find the Floppy.
supports (E)IDE disk drives, non-Micro Channel PC's.
a list of all parameters is enclosed in your OS/2 online help
New Parameters (not listed in online help):
/W (Wait) pauses the config.sys after displaying the verbose
/!SHUTDOWN disables the new shutdown behaviour.
/FORCE Forces the emulation of an IDE CDROM drive, even though one is not present.
If you are using the /BM or !BM parameters to enable or disable busmaster; you MUST specify the adapter with /A:x. You can also specify the unit on that adapter with /U:z. For example:
BASEDEV=IBM1S506.ADD /A:0 /U:0 /!BM or /A:0 /!BM to disable BUS Master DMA
BASEDEV=IBM1S506.ADD /A:0 /U:0 /BM or /A:0 /BM to enable
<<=TIP=>> If you have an IBM Thinkpad 760E/ED/ELD/EL that exhibits sluggish harddisk behaviour (pausing intermittently with hard drive light on) after FixPaks have been applied, add the /!BM parameter to the BASEDEV=IBM1S506.ADD statement (if present) in your CONFIG.SYS. This will disable the Bus Mastering function whose default has been changed from OFF to ON.
Example: BASEDEV=IBM1S506.ADD /A:0 /!BM /U:1 /ATAPI /FORCE
<<=TIP=>> A 'New Feature' that went into IBM1S506.ADD to flush buffers more reliably during shutdown using C-A-D seems to cause some disks to SPIN DOWN and stay there. Add " /!SHUTDOWN". This is known to fix the problem.
<<=NOTE=>> /SMS! works only if the hardware doesn't report SMS capability, otherwise SMS enabled will be used regardless if the parameter is set or not.
<<=TIP=>> If you want to use SCSI Hardisks together with (E)IDE-Disks and to boot from SCSI first, make sure that the SCSI-Drivers are in front of the IDE-Drivers (normally IBM1S506.ADD).
<<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but after PCMCIA.SYS
Parameter:
/C0=z : These parameters define the IRQ level to be used by the
/C1=z : Socket Services driver. The new Card Services and Socket Services drivers for OS/2 do not use a hardware interrupt to notify the PCMCIA status change, so you do not need these parameters.
/IG0=y : This parameter defines a slot number, which Socket Services ignores. If you use the "Point enabler" supplied with a PC Card, you should take into consideration the coexistence with Socket Services.
For Example, "/IG0=1" defines that slot 1 is reserved for a "Point enabler" and Socket Services will ignore the slot.
/RI0=x : This parameter defines a slot number, where Socket Services disables the RI_OUT signal. If you are using a modem card with a ThinkPad computer, and you can't enable the "suspend" or "hibernation" function while the modem card is inserted, please try this parameter.
For Example, "/RI0=1" specifies slot 1.
/D : This parameter enables "Warm docking" from the view point of PCMCIA hardware. By adding this parameter, two additional PCMCIA slots are reserved for the docking station.
/APOFF : This parameter turns off the Auto-Power Mode. If the Auto-Power Mode is ON, a PC Card will be automatically turned ON by the hardware when it is inserted. The default for Auto-Power Mode is ON.
/IO0=s : This parameter defines the slot number, for which Socket Services will change the way the -IOCS16 signal is generated. By default, the -IOCS16 signal is generated based on the -IOIS16 signal from the PC Card. If this parameter is specified, the -IOCS16 signal is generated based on the I/O data size which is specified by the Client program. This option is needed for some cards which do not generate the -IOIS16 signal. You need to verify this information with PCMCIA card vendors.
For Example, "/IO0=1" specifies that the -IOCS16 signal for slot 1 is to be generated based on the I/O data size specified by the Client program.
Point Enabler Adapter card drivers are device drivers that support specific Adapter cards without requiring the use of the Card and Socket services provided in the PC Card Director package.
Problems using these Point Enabler device driver will occur when used in conjunction with the Card and Socket Services. The problem that must likely will occur is that the Point Enabler Adapter card will not function. The PC Card Director will indicate that the Card Type is incorrect and the Status of the Card will be 'IN' instead of 'READY'.
In order to use a Adapter card with Point Enabler Device driver a configuration parameter must be added to the IBM2SS14.SYS device driver entry in CONFIG.SYS. The parameter is as follows:
/IG0=y : Where 'y' defines the slot number that contains the Adapter card using the Point Enabler Device Driver.
After the system has been rebooted the slot specified in the configuration parameter will be ignored by Card and Socket Services allowing that slot to be used by Point Enabler device drivers. It also means the following:
- the PC Card Director program will not detect the insertion or removal of adapter cards in that slot
- Adapter cards with device drivers that utilitize Card and Socket Services can no longer use that slot
The following is a list of Adapter Cards that use Point Enabled Device Drivers:
IBM 10/100 EtherJet Cardbus Adapter
IBM 10/100 EtherJet Cardbus Adapter with 56K modem
Intel PRO/100 Cardbus II
Xircom CreditCard Ethernet Adapter II
Xircom CreditCard Ethernet Adapter 10/100
New with Fixpaks since Fixpak 6/35 supports ATAPI Removable Media like ZIP100 and ZIP250, LS120 attached to an IDE Port.
<<=TIP=>> If you have removable media drives (MO, IOMEGA, SYQUEST and others) look at http://rheooptik.fmf.uni-freiburg.de/www/faq/ remmedia.php for a detailed removable media FAQ.
Supports generic disk adapters supported by the BIOS.
Using this driver is very slow, but it works with every harddisk supported by your BIOS, even scsi.
The hardware specific part of the keyboard driver.
The software specific part is KBDBASE.SYS
<> Some Tools e.g. the Ctrl-Alt-Del Commander form Perez Computing or the Process-Commander from Stardock are replacing KBDBASE.SYS by there own version. Whenever you deinstall these tools manually be shure to revert to the original KBDBASE.SYS. It is also reported that Process-Commander fails with Warp 4.5 versions (WSeB and Warp4 Fixpak 13 or higher)
Parameter:
/NONE starts OS/2 even when no keyboard is attached. Useful for unsupervised operation.
<<=TIP=>> For the mostly sold so called 'Win95-Keyboards' (how ironic, as with windows9x you can only loose) there are two replacement drivers: One by Robert Muchsel (muchsel@acm.org), Release is Ver 2.00 available under winkey02.zip, and a newer one available at: http://os2.avi.kiev.ua/ Release is ver.021
<<=TIP=>> By Kovacs Istvan: If you try BASEDEV=IMBKBD.SYS /NUMON numlock could turned on like with the utility 'jshifter'. Works only with some releases of the IBMKBD.SYS delivered with Warp. According to the mails I've got it seems that the parameter doesn't work on nearly most keyboards, (but one some) so you have still to use 'jshifter' available at: http://www.gbar.dtu.dk/~c948129, or 'numlock' by Peter Engels available at http://www.uni-bonn.de/~uzs0ad.
<<=TIP=>> If you prefer a so called Dvorak keyboard layout (a keyboard which tends to arrange the characters more ergonomic than the qwerty type - which was a need when constructing mechanical typewriters at the end of the 19.th century - since Fixpak 8 for Warp 4 (maybe earlier, but this was the first time I was aware of its existance) go to your keyboard settings in the System Setup folder and simply select Dvorak (for left and righthanded !, but only in English). Now you only need a keyboard with a Dvorak layout (or one of these old but beautiful IBM keyboards with a 'klick' and 'solid as a rock', here you can pull the caps and place em where you want). This is another new goodie in OS/2 IBM never speaks of.
/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)
<<=TIP=>> There is no longer any reason to use these drivers unless you need to use the protect utility to password protect your disks. Better use the new O2DASD.DMD
Advantages:
Works with any OS/2 supported SCSI card.
Allows you to use multiple SCSI devices on your SCSI card.
Compatible with the format that the disks come with from the factory (in non-fixed mode).
Disadvantages:
Slow, unless you use fixed mode.
Fixed mode must be partitioned and, as such, all cartridges must be partitioned and will no longer work with DOS, Windows, or OS/2 not running with fixed mode drivers.
In fixed mode, disks have to be unmounted and remounted using a utility before they can be ejected and after they have been reinserted.
Needs HPFSRem to gain HPFS removability support.
An utility to enable the read/write combining code in the K6 processor.
One needs to get the documentation for the k6 chip and discover the correct formula for the value to use for the video register. The authors suggested value doesn't work in most cases.
<<=TIP=>> See also BASEDEV WACKER.SYS which is recommended by users.
Some CD recorders claim to be CDROM drives. As OS2CDROM.DMD allocates all CDROM drives at bootup, those recorders cannot be accessed by additional software, including the RSJ CD Writer File System. To correct this behaviour, the filter device driver LOCKCDR.FLT is added to the file CONFIG.SYS; all already known CD recorders will be converted to WORM devices automatically.
parameters
-a: Filters all commands. Solves problems with the SCSI Bus reset after a session.
-i:"Recorder Name" can be used to specify the device name of the unknown CD recorder.
Example:
BASEDEV=LOCKCDR.FLT -i:"IMS CDD2000"
In this example, the Philips recorder CDR2000 is added to the built-in list of CD recorders. During bootup, the OS/2-internal device tables are modified such that the CD recorder is treated as a WORM device instead of a CDROM.
The name of all connected CDROM devices as well as whether they have been converted to WORM devices is printed to the screen while the system is booting.
<<=Note=>> It is not necessary to specify the complete device name. In the example above, specifying -i:"IMS" would do the same job. However, the more complete the device names are specified, the less likely it is that a CDROM drive is converted to a WORM device accidentally.
ASPI Device Manager for drivers according the ASPI specification by Adaptec. Replaces the ASPI4OS2.SYS by Adaptec.
Parameters:
/SHARE
/ALL
<<=TIP=>> If you are using RSJ CD Writer 2.59 or above you may add the parameter /ALL to BASEDEV=OS2ASPI.DMD. Also needed by SANE and CDRECORD.
After booting your machine, the recorder will be useable as a standard CDROM drive, and you will nevertheless be able to attach the CD to our filesystem. But please ensure that you're not using the CDROM drive letter at the same time when the CDR is attached to RSJ's filesystem, otherwise this will result in errors. If you are using RSJ CD Writer 2.7 you can add unsupported drives
Device Manager, is a general purpose driver for disk drives, and is always needed.
Together with the 'new' OSDASD.DMD since fixpak 6/35 parameters are:
/rf (removable to fixed) Together with this parameter it is possible to handle formerly only as 'superfloppy' available removable disks as partitionized disks.
/of (optical to fixed) Like /rf but for MO (MagnetoOptical) Drives.
/LF Forces all removable devices to be treated as Large Floppy rather than partitioned media.
/MP Used to support allocating a predetermined number of drive letters for a partitioned removable media device. Note that this option only applies to partitioned removable devices, and is ignored for any other device type.
<<=IMPORTANT NOTE=>> Some parameters are case sensitive. IN UPPERCASE THEY DON'T WORK !
Logical Volume Device Manager in Warp Server for E-Business
OS2LVM.DMD [...] sits between the IFSM and OS2DASD providing the logical view of the DASD to the OS/2 file system. OS2LVM also provides Bad Block Relocation (BBR) for JFS.
<<=NOTE=>> The statement BASEDEV=OS2LVM.DMD must immediately follow the BASEDEV=OS2DASD.DMD statement in config.sys.
replacement for print01.sys, enables bi-directional printing fast prints without heavy system load (but you really need a appropriate printer cable). Available at: ftp://ftp.boulder.ibm.com/ps/products/os2/os2ddpak/bidi.exe
This solution will work in polling mode by default.
<<=NOTE=>> By William L. Hartzell: With PAR1284.SYS the PRINTMONBUFSIZE setting will not be used.
Parameter:
/LPTx (where x is 1,2,3) enables interrupt mode. The switch is required to be in capital letters. Thus, LPT1 can be interrupt driven and LPT2 can be polled.
i.e. BASEDEV=PAR1284.SYS /LPT1 will make only LPT1 use interrupts.
<<=NOTE=>> To work print01.sys or print02.sys must be disabled by putting a REM in front or deleted from the config.sys. If unknown system hangs are experienced during printing, remove DEVICE=APM.SYS and DEVICE=VAPM.SYS from Config.sys.
<<=NOTE=>> Using PAR1284.SYS togehter with some Crystal Cards relying on CWCUTIL.EXE refuse the system to work
<<=NOTE=>> The use of PAR1284.SYS and the scrollmouse dribvers from IBM is exclusive. You can only use on of them.
PARTFILT.flt is a filter device driver for OS/2 that makes it possible to load an IFS for linux partitions. (Without this filter you must patch the partition table. On many systems doing so may cause LILO to fail.)
The filter now is NOT specific for Linux. In addition this driver is capable to control in what order drive letters are assigned to partitions on fixed disks. It will also allow you to access hidden primary partitions under OS/2.
Parameter:
/Q Load quietly
/W Enables Writing to the faked partitions. Without this option the faked partitions are read-only.
/A This option does two things:
- Disables OS/2 to access all partitions, but:
- Virtualizes (or fakes) all known partitions. Known partitions are the normal FAT partitions, IFS (=mainly HPFS) partitions and the partitions specified with the /P option. All primary partitions of known types are also virtualized, and will be accessible from OS/2. This option must be used in conjunction with the /M option.
When this option is specified, the /W option is automatically set, because otherwise OS/2 will not boot.
/M - Specifies the order in which partitions must be mounted.
<<=WARNING=>> Incorrect usage of the /A and /M options could make your system unbootable.
=> USING THE /A and /M OPTIONS is not advised! <=
if you need more information on these options please see:
http://ourworld.compuserve.com/homepages/hkelder
/P This option is used to tell PARTFILT which partition type are to be faked. You should NOT use partition types already supported by OS/2 since this would result in a single partition being mounted two times. The list should consist of partition type numbers (in hexadecimal), separated by comma's.
To make PARTFILT.FLT fake a FAT32 partition the /P option should be /P 0B.
To make PARTFILT.FLT fake a FAT32X partition the /P option should be /P 0C.
To make PARTFILT.FLT fake a LINUX partition the /P option should be /P 83.
Or you can use a combination of the types e.g. /P 0B,0C
<<=NOTE=>> The best location in the config.sys seems to differ depending on your configuration. Some state FAT32.IFS will only work is PARTFILT is the first basedev, other claim it only works if PARTFILT is the last one. A specific problem was reported when using a SCSI powersave basedev that only seemed to work if PARTFILT was the last basedev.
<<=ATTENTION=>> Must be in front of all other PCMCIA Drivers
Parameter:
/R:200 : Specify that card services will conform to the PCMCIA 2.0 standard. This is the default value.
/R:500 : Specify that card services will conform to the PCMCIA 5.0 standard instead of the PCMCIA 2.0 standard which is the default value.
/P : In previous releases, this parameter disabled the hardware interrupt which was used by OS/2 Socket Services drivers to notify clients of a change in status.
Neither the new Card Services nor Socket Services drivers for OS/2 use a hardware interrupt to signal PCMCIA status changes. So this parameter is no longer needed.
The probably easiest procedure installing pcmcia has been described on OS/2 Online (http://www.os2-online.de):
Unpack the file PCMCIADD found on disk 17 of the OS/2 Warp install CD (directory OS2IMAGE), best into the OS2 directory on your harddisk. Then replace the line BASEDEV=IBM2TOS1.SYS with the following lines in your CONFIG.SYS:
BASEDEV=IBM2AMB1.SYS
BASEDEV=IBM2AST1.SYS
BASEDEV=IBM2CAD1.SYS
BASEDEV=IBM2CMQ1.SYS
BASEDEV=IBM2MAT1.SYS
BASEDEV=IBM2NCR1.SYS
BASEDEV=IBM2NEC1.SYS
BASEDEV=IBM2SS01.SYS
BASEDEV=IBM2SS02.SYS
BASEDEV=IBM2TOS1.SYS
BASEDEV=IBM2ZEN1.SYS
BASEDEV=IBM2ZOS1.SYS
BASEDEV=SS2PCIC1.SYS
BASEDEV=SS2TCIC1.SYS
When OS/2 boots press Alt-F2 when the rectangle appears in the top left corner of the screen, and OS/2 will tell you which driver was loaded. It is possible that your machine works with more than one, you'll then have to find out yourself which one works best!
If you have specific drivers for your notebook computer
Do not install the PCMCIA support when installing OS/2 on your machine. Instead, once you are done with the installation of OS/2, chose Device Installation from the System/System Configuration folder and install the PCMCIA driver from diskette or use the installation program provided with your driver. Check the information provided with your driver before installing OS/2 Warp or the PCMCIA support.
If your driver comes only in the form of the driver files, you need to do a manual installation, i.e. you need to edit the CONFIG.SYS file yourself. In that case install any PCMCIA support (as explained above). Then copy the driver files into the directory x:\os2\boot. After that, open the CONFIG.SYS in the editor and change the line BASEDEV= PCMCIA_driver (replace "PCMCIA_driver" with the driver name you installed) into BASEDEV=newdriver where "newdriver" is the name of the driver file you got). Take care that the PCMCIA drivers precede any COM drivers.
In some machines, an additional line has to be included in the CONFIG.SYS file: BASEDEV=RESERVE.SYS /mem:nnnn mmmm (nnnn has to be replaced with the address where PCMCIA usually would start and mmmm has to be replaced with a value of 1000 or more (increased in steps of 1000)). First run rmview /mem to find out at which address PCMCIA is located. This would be the hex number that comes in place of nnnn. Then try out whether it works with 1000 (in place of mmmm). RESERVE.SYS actually prohibits the PCMCIA driver to use this area and thus avoids a conflict which otherwise arises. If 1000 doesn't work try 2000 etc.
Xircom's own drivers don't work: For some PCMCIA cards (particularly XIRCOM with their own drivers) the IBM PCMCIA socket for the particular socket in which the card is inserted has to be disabled by installing socket services with the parameter /S0=1 which will disable socket services for the second PCMCIA slot (if there are two slots; if there is just one slot it won't do any good). An alternative is the switch /ig0=1 (1 is the port number). By using a proper script, it may even be possible to go without any of these switches.
PCMCIA doesn't work: In some notebook computers the BIOS has to be modified so that the PCMCIA becomes compatible with the available OS/2 driver. The mode in which the PCMCIA functions may need to be set from Busmaster to 16-bit or PCIC compatible. Check the info for individual notebooks on this page and consult your notebook's manual!
IBM Token Ring PCMCIA adapter doesn't work: Try setting in MPTS the IRQ to 5 and the adapter type from primary to alternate (address X=20).
Parallel Port-attached ZIP 100, ZIP+, and ZIP 250 driver
This driver supports daisy chaining, up to a total of five drives. The connections must be CPU -> ZIP Plus/250 -> ZIP Plus/250-> ZIP (original), which MUST be last. Note that ZIP Plus terminator MUST BE OFF unless it is the LAST drive in the chain. If a ZIP (original) is the last drive, then the ZIP Plus termintor MUST BE OFF.
<<=NOTE=>> At the moment formatting zip-disks with HPFS gives you a trap.
PARAMETERS
/V Verbose Output
/PORT:# # = Parallel port address (ie 378, 278, 3bc)
MULTIPLE PARALLEL PORT DRIVES
Each driver instance supports ONLY one parallel port. To install TWO instances, you MUST specify the /PORT: parameter on at least one driver statement to get to the LPT2 port; for example:
OS/2 versions that use LVM for managing hard file space exhibit several pecularities working with ZIP drives.
1. Even though media is inserted at boot time, a drive letter may not be assigned. To force the assignment of a driver letter, double click on the "Refresh Removable Media" object. If that fails, eject the media, re-insert, and double click on the "Refresh Removable Media" object.
2. LVM may report the ZIP drive as corrupted. You can still create a volume.
3. Do NOT do an LVM "Commit Changes" with ZIP media that already contains data inserted. The data may be lost.
supports attached printers on non-Micro Channel PC's.
<<=WARP TIP=>> With Warp, the default transmission protocol used by PRINTO1.SYS and PRINTO2.SYS is the polling transmission method. The protocol used by previous versions of OS/2 was the interrupt transmission method. In Warp, you can change back to the interrupt method by adding the /IRQ parameter.
<<=TIP=>> From Paul Kurr: "Since I'm running on a LAN at work here, I have no need for direct printer support of any kind since this is taken care of by my NOS (LAN Server). So I have REM'd BASEVEV=PRINT01.SYS to save some RAM."
This driver reserves hardwareressources for drivers, especially for those who are not recognised by the ressourcemanager.
See OS/2 Reference Book for a detailed discussion of the parameters
<<=Tip=>> By Sam Detweiler: "for adapters that are not PnP and do not have a legacy detector, one can use the DOCUMENTED approach of adding a BASEDEV=RESERVE.SYS /p:2e8,8 to the config.sys and re-running hardware detection at the next boot. It causes the reserve.snp to preallocate the defined resources so that PnP adapters can't use them.
<<=TIP=>> By Paul F.Grobler: The tablet / enhanced mouse driver by M. Finney was broken by the GA code of Merlin but I found a workaround. The symptoms I got was an error free driver load (including vmouse.sys), a mouse cursor on the first graphic mode screen but the mouse pointer was static i.e. it would not move. All that was required was to put a "BASEDEV=RESERVE.SYS /IO:3f8,8 /IRQ:4" as the first line of my config. sys. You will note that the values correspond to normal com1 as this is were my tablet is connected. By modifying the values to /IO:2f8,8 and /IRQ:3 this should work for com2.
Modified IBMIDECD.FLT for the RSJ CD-Toasting software since V 2.70 that works correct with writing commands and command timeouts. Will be removed as soon as a corrected IBMIDECD.FLT is available.
<<=TIP=>> Not needed when you have a SCSI-only system. If you get a trap 000d during boot REM this line and use BASEDEV=IBMIDECD.FLT instead.
Driver for proprietary (IDE) Soundblaster interface CDRom drives. Supports only 1 CD drive.
Parameter:
/P:nnn - Specifies the base I/O port address of the interface card. The value must be the same number as the port address selected by the jumper on the host interface card.
/T:nn - Sets the adapter type connected to the CD-ROM drive. Supported value is: 2 = Creative Labs CD-ROM interface card (not Sound Blaster)
/NS - Disable drive select scan. Driver will not scan for more than one CD-ROM drive.
Socket Services for Intel i82365 and compatibles by Michael Havens (mwhav@mindspiring.com). Tested with the Texas Instruments PCI 1221 controller in Twinhead notebook. It may work with other TI 122*, 12**, and other compatible controllers.
/AP:[m,]on Automatically assign a IRQ number to PCI or CardBus PC Card adapter 'm', if BIOS didn't assign a PCI IRQ (Interrupt Line register doesn't contain valid IRQ number). If no adapter number is specified, this switch will be applied for all adapters. The switch will be ignored for ISA PC Card adapters.
/B:n For ISA adapters only: use I/O base address 'n' (0x100 <= n <= 0x3FF) for detection of ISA adapters (default: autodetect). This switch will be ignored for PCI/CardBus adapters.
/BE:auto Perform bus enumeration for CardBus adapters only if CardBus bus number not already assigned by BIOS.
/BE:off Disable bus enumeration for CardBus adapters. By default, Socket Services performs bus enumeration for CardBus adapters since most versions of BIOS don't perform this correctly. If you are sure that you have BIOS which performs the bus enumeration correctly, use /BE:off switch.
/DP:m Assign different PCI IRQs to sockets of PCI or CardBus PC Card adapter 'm'. Will be used only, if '/AP:[m,]on' switch is selected.
/E Enable screen output (default: silent).
/EC:[m,]auto Do not change setting of 'power switch clock' register for adapter 'm' but use setting assigned by BIOS. If no adapter number is specified, this option is chosen for all adapters. (Default: use power switch clock generated by PCI clock)
<<=Note=>> This switch is ignored for all PC Card adapters except TI
PCI121x/122x and TI PCI1250/1450
/EC:[m,]on Use external power switch clock for adapter 'm'. If no adapter number is specified, this option is chosen for all adapters. (Default: use power switch clock generated by PCI clock)
<<=Note=>> This switch is ignored for all PC Card adapters except TI PCI121x/122x and TI PCI1250/1450
/FB:n Specify number of first PCI bus available for CardBus adapters (Default: 1). This option is ignored in /BE:off mode.
/FP:off Disable full search for PCI PC-Card adapters. This option should be selected, if non-existent PCI PC-Card adapters are detected.
/FS:n Socket IRQ filter. Socket Services will not assign IRQ for sockets if corresponding bit is set in the mask. For example, if n is 0x20 than SS will not configure socket on IRQ5.
/H Print help text.
/IA:on Always assign I/O base address for PCI adapters. By default Socket Services assigns I/O base address for PCI adapters only, if base retrieved from PCI configuration space is 0.
/IF:on Detect ISA/EISA adapters before PCI/CardBus adapters (default: detect PCI/CardBus adapters before ISA/EISA).
/II:[m,]off Disable writing of interrupt mode into registers of PC Card adapter 'm'. If no adapter number is specified, this switch will be applied for all adapters. This switch will be ignored for all adapters which don't support interrupt mode (see /IM description).
/IM:m,t Set interrupt mode used for adapter 'm' (default: Par). This setting is ignored for Non-CardBus adapters. Possible values for type 't' are (default is Par):
Par
TI1130/1x31: Use parallel ISA-type interrupts; TI12xx: Use parallel ISA and PCI interrupts; CL-6832, OZ6832: Use External-Hardware Interrupt mode;
Ricoh RB5C478: Use parallel interrupt mode.
Ser
TI1130/1x31: Use serialized interrupt type scheme;
TI12xx: Use serialized ISA and PCI interrupts;
CL-6832, OZ6832: Use PC/PCI Serial Interrupt protocol;
Ricoh RB5C478: Use serialized interrupt mode.
PPci
TI 12xx
Cl-6832 Use parallel PCI
OZ6832
ISPP
TI 12xx only: Use serialized ISA and parallel PCI interrupts. Will be ignored for all other adapters
PWay
CL-6832, OZ6832: Use PCI/Way Interrupt Signaling mode. Will be ignored for all other adapters.
/IN:on Ignore PCI device function number when setting PCI interrupt through BIOS call. (Pass 0 as function number instead.) (default: off)
/IO:m,n For PCI/CardBus adapters only: use I/O base address 'n' for PCI/CardBus adapter 'm' (default: find base of free I/O range). Caution: adapter will be ignored if specified base can't be used. This switch will be ignored for ISA adapters.
/IR:[m,]off Disable routing of ISA IRQs on adapter 'm'. If no adapter number is specified, this switch will be applied for all adapters. This switch should be used for PCI/CardBus controllers, if the ISA IRQ-routing paddleboard is not connected.
/IW:m,n Limit number of I/O windows per socket on adapter m to n.
/MH:n Adapter IRQ filter. Socket Services will not use IRQ for adapters if corresponding bit is set in the mask. For example, if n is 0x8000 than SS will not use IRQ 15
/MS:m,n Support maximal number of sockets 'n' for adapter 'm' (default: autodetect). If n=0 is specified, adapter will be ignored.
/MW:m,n Limit number of memory windows per socket on adapter m to n.
/MX:[m,]off Do not initialize the multiplex IRQ routing register on adapter 'm'. If no adapter number is specified, this switch will be applied for all adapters. (Default: Initialize register). This switch is only used on TI PCI122x/1250/1450 adapters and is ignored for all other adapters.
/OZ:97:off OZ6832 PC Card adapter only: reset PC97 IRQ support bit.
/OZ:97:on OZ6832 PC Card adapter only: set PC97 IRQ support bit.
/OZ:IL:off OZ6832 PC Card adapter only: reset ISA Legacy bit.
/OZ:IL:on OZ6832 PC Card adapter only: set ISA Legacy bit.
/PD:off Disable automatic power-down for broken cards, which is done by default for PCI adapters. This automatic power-down avoids system lock, which occurs on PCI adapters if broken cards couldn't be powered-up successfully (i.e. power doesn't become active or card doesn't become ready)
/PI:m,[n,]I Assign IRQ number 'i' as PCI IRQ for adapter 'm', socket 'n'. If no socket number 'n' is specified, the IRQ number is the same for all sockets of the adapter. This IRQ number will be written to the PCI configuration space (Interrupt Line register) of the specified adapter. For CardBus adapters: the IRQ number will be written to the PCI configuration spaces of all sockets. The IRQ number will be ignored for ISA PC-Card adapters. Main purpose of this switch is for CardBus adapters, since many old BIOSes don't assign IRQ number in Interrupt Line registers. The IRQ number must be level sensitive (routed to PCI IRQ), otherwise CardBus cards and Status Change Interrupt will not work.
/RA:[m,]off Disable assignment of free base addresses for CardBus register memory windows on adapter 'm'. Use base addresses assigned by BIOS instead (except this base is 0). If no adapter number is specified, this option will be chosen for all adapters.
/SA:m,n Swap adapter m with adapter n. Multiple use of /SA switch is possible.
/SC:m,n Use Status Change Interrupt 'n' for adapter 'm' (default: Card Services select Status Change Interrupt).
/SI:off Do not set PCI interrupt on hardware, only write Interrupt Line register. (default: on)
/VS:33 Power 16-bit cards always to Vcc=3.3V, regardless voltage sense reported from the card. All pure 5V 16-bit cards will not work when using this switch.
/VS:50 Power 16-bit cards always to Vcc=5V, regardless voltage sense reported from the card. CAUTION: Using this switch can damage pure 3.3V 16-bit cards. Never insert such cards when using this switch.
/VS:auto Don't use voltage sense reported from 16-bit card directly, but execute algorithm to check if voltage reported from the card is correct. Power card to Vcc=5V, if this checking shows that card reports voltage incorrectly. Switch /VS:auto is necessary to support 16-bit 5V ATA cards which report voltage sense incorrectly. But be aware that pure 16-bit 3.3V cards may be damaged, if they don't comply with PC Card Standard. Switch /VS:auto is ignored, if CardBus card is inserted, i.e. for CardBus cards always voltage sense reported from the card is used.
/VS:off Same as /VS:auto. Provided for backward compatibility.
/W:n Use number of Wait States 'n' for 16-bit I/O access. This value could be 0 or 1 (default 1).
/XP:[m,]I Exclude IRQ 'i' from automatic PCI IRQ assignment. Will be used only, if '/AP:[m,]on' switch is selected. Multiple use of /XP switch is possible.
Known Problems:
1 In OS/2 Warp 3 the ATA card cannot be configured if it was inserted after boot of system. It was found that PCM2ATA.ADD drivers de-registers the timer procedure by end of the initialization stage. As result the MountCard procedure is never called for the card inserted into the system after the BOOT time. OS/2 Warp 4 contains new version of PCM2ATA.ADD driver that supports hot insertion of ATA cards.
2 PC card can be configured but does not work if notebook contains Sound card and it is configured on IRQ5. The Sound card IRQ 5 is not enabled when PC starts. The OS/2 is getting knowledge about the usage of IRQ 5 only when sound card driver is starting. The IBM Card Services is a ®base¯ driver and starting before the soundcard driver. Therefore Card Services considering IRQ 5 free may assign it to the PC Card. Problem can be by-passed by re-configuring of Sound card via BIOS setup program with higher IRQ number.
3 Most of Xircom Network card drivers contain point enabler. Such enabler do not register Card Services client and do not report card configuration to Card Services. For this reason Card Services considering that card was not configured will turn card power off and card will be no longer operational. This is the problem of Xircom NDIS driver non-compliant with PC Card Standard.
4 SunDisk SPDL5 1.3 will not be configured. This card holds card configuration in vendor-specific tuple rather then in CISTPL_CFTABLE_ENTRY. IBM ATA driver do not check for this condition.
<<=NOTE=>> The SYM416 card is a plug-n-play card which can interfere with sound cards (both legacy and plug-n-play) installed or possibly other plug-n-play devices. The following driver parameter can OVERRIDE the automatic card setting:
<<=NOTE=>> If the drive does not support synchronous or tagged command queing. Use /!SN or /!Q on the driver. e.g. BASEDEV=SYMC8XX.ADD /V /!SN /!Q
Parameter:
/VERBOSE or /V This option appears on the command line by default. It enables display of a banner, version number, and SCSI bus information during startup of the system.
/!DM Option This option disables use of the IBM-supplied DASD manager (OS2DASD.DMD) for the devices listed. The DASD manager supports direct access devices such as hard drives.
Usage: /!DM[,]*
For example, to disable OS2DASD.DMD for devices on host adapter 0 at target
IDs 3 and 5, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look
like this:
BASEDEV=SYM8XX.ADD /!DM<0:3>,<0:5>
/!SM This option disables use of the IBM-supplied SCSI manager (OS2SCSI.DMD) for the devices listed. The SCSI manager supports SCSI tape drives.
Usage: /!SM[,]*
For example, to disable OS2SCSI.DMD for devices on host adapter 0 at target IDs
3 and 5, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like
this:
BASEDEV=SYM8XX.ADD /!SM<0:3>,<0:5>
/EXCLUDE or /X This option disables a host adapter so that it is not seen by the SDMS OS/2 device drivers. This allows a host adapter to be ignored without physically removing the board from the system. This may be necessary if the adapter in question is causing a resource conflict.
Note: If you exclude the adapter to which the boot device is attached, then
you will not be able to boot.
Usage: /EXCLUDE[,]*
Where:
chip is a unique identifier that indicates the LSI Logic board type. The
Verbose option displays a table with this value appearing in the "CHIP"
column.
bus represents the PCI bus number into which the adapter is plugged. The
Verbose option displays a table with this value appearing in the "BUS"
column.
dev/func is the number derived by combining the PCI device and function
numbers and serves as a unique board identifier in conjunction with
the PCI bus. The Verbose option displays a table with this hexadecimal
value appearing in the "DEV/FUNC" column. It may contain an A, B, C, D,
E, or F as part of its value.
For example, to exclude a host adapter with chip type F, PCI bus number 0
and dev/func number A0, the line in the CONFIG.SYS file that loads SYM8XX.ADD
should look like this:
BASEDEV=SYM8XX.ADD /EXCLUDE
or
BASEDEV=SYM8XX.ADD /X
/SYNCH_RATE or /SR This option sets the maximum synchronous transfer rate (in Mbyte transfers per second) to negotiate with a particular device. The allowable values for this setting are 0, 5, 10, 20, and 40 Mbyte transfers per second, if the adapter is capable of the specified speed. All host adapters in the LSI Logic family
support at least 10 Mbyte transfers per second; some support 20 or 40 Mbyte
transfers per second. To turn off synchronous transfers for a particular device,
specify 0 (zero). The value set by this option only defines the maximum transfer
rate negotiated. The actual rate also depends on the device's capability. The
default value is the fastest transfer rate that is supported by a particular
host adapter.
Note: The maximum synchronous transfer rates effectively double when the
adapter and device permit wide transfers (See the /WIDTH option).
For example, a synchronous transfer rate setting of 40 Mbyte transfers
per second will actually produce a transfer rate of 80 Mbyte transfers
per second if the adapter and device both allow and are set to perform
wide transfers.
Usage: /SYNCH_RATE=n[,n]*
Where: n = 0, 5, 10, 20, or 40.
Two examples illustrate how to use this option:
1. To turn off synchronous transfers to ID 3 on host adapter 0, the
line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /SYNCH_RATE=0<0:3>
2. To set synchronous transfers to 10 Mbyte transfers per second on all devices
on host adapter 1, the line in the CONFIG.SYS file that loads SYM8XX.ADD
should look like this:
BASEDEV=SYM8XX.ADD /SR=10<1>
/SYNCH_OFFSET or /SO This option sets the maximum synchronous offset to negotiate with a particular device. The allowable values for this setting are 0 to the maximum synchronous offset supported by the specified adapter. The LSI Logic controller chips support offsets up to 31. Refer to your host adapter user's guide for
information on the maximum offset supported by your host adapter. If 0 (zero)
is specified for the synchronous offset value, synchronous transfers are turned
off for any specified device. The value set by this option only defines the
maximum offset that is negotiated. The resulting rate also depends on the
device's capability. The default value is the maximum offset that is supported
by a particular host adapter.
Usage: /SYNCH_OFFSET=n[,n]*
Where: n = 0 up to maximum synchronous offset for the adapter.
For example, to change the synchronous offset to 6 for ID 3 on host adapter 0,
the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /SYNCH_OFFSET=6<0:3>
or
BASEDEV=SYM8XX.ADD /SO=6<0:3>
/TIMEOUT or /T The SDMS device drivers use a timeout mechanism to detect certain errors. When the driver issues a command to a SCSI device, a timer is started. If the timer expires before the command completes, the driver assumes that something is wrong with the device, and takes steps to recover. The default value
for this is 10 seconds. If you set the value to be less than the system has
allocated for a particular device, your value will be ignored. To turn off the
timeout mechanism for a particular device, set the value to 0 (zero).
Usage: /TIMEOUT=n[,n]*
Where: n = timeout value in seconds for device (0-65535).
For example, if you have a particularly slow device at ID 3 on host adapter 0
and you wish to extend the timeout on this device to 60 seconds, then the line
in the CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /TIMEOUT=60<0:3>
or
BASEDEV=SYM8XX.ADD /T=60<0:3>
/DISCONNECT or /DC SCSI devices have the ability to disconnect from the bus during an I/O transfer. This option allows (or does not allow) a device to disconnect during an I/O transfer. If a particular adapter has parity checking disabled, then you
must use this option to disable disconnects for all devices on that adapter
that do not generate parity. Refer to the /PARITY option for more information.
Usage: /DISCONNECT=n[,n]*
Where: n = ON is the default value for all devices, which allows disconnects.
OFF does not allow disconnects.
For example, to disable disconnects on the device at ID 2 on host adapter 0,
then the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like
this:
BASEDEV=SYM8XX.ADD /DISCONNECT=OFF<0:2>
or
BASEDEV=SYM8XX.ADD /DC=OFF<0:2>
/PARITY or /P The LSI Logic chips are capable of enabling or disabling the SCSI bus data integrity checking feature known as parity. Some non-compliant SCSI devices sold as SCSI devices do not generate parity. You can use this option to disable parity checking. The LSI Logic chips always generate parity (for outputs), but may optionally check the parity (for inputs).
Note: When disabling parity checking, you must disable disconnects for
any device that does not generate parity, as the LSI Logic chips
cannot disable parity checking for that device during the reselection
phase. If a device does not generate parity and it disconnects, the
I/O never completes as the reselection never completes. Refer to using
the /DISCONNECT option for more information about disabling disconnects
for a device.
Usage: /PARITY=n[,n]*
Where: n = ON is the default value for all devices, which enables parity
checking. OFF disables parity checking.
For example, to turn off parity checking on host adapter 0, the line in the
CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /PARITY=OFF<0>
or
BASEDEV=SYM8XX.ADD /P=OFF<0>
/QTAG or /QT Queue tagging allows more than one outstanding command per SCSI device. Some non-compliant SCSI devices sold as SCSI devices do not allow queue tags, in which case queue tagging needs to be disabled. The value given in the command line will be the depth of the queue for queue tags for the device(s) indicated. To disable queue tag support, a value of 0 or 1 should be given.
Usage: /QTAG=n[,n]*
Where: n = the number of queue tags allowed for a device (0-256).
Two examples illustrate how to use this option:
1. To turn off queue tagging for ID 3 on host adapter 0, the line in the
CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /QTAG=0<0:3>
2. To set the queue depth to 5 for all devices on host adapter 2, the line in
the CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /QT=5<2>
/WIDTH or /W Devices attached to a SCSI bus are narrow or wide devices. Narrow devices transfer data one byte (or 8 bits) at a time. Wide devices transfer two bytes
(or 16 bits) at a time. The value given in the command line option will
determine the size of data transfers.
Usage: /WIDTH=n[,n]*
Where: n = 8 or 16.
Two examples illustrate how to use this option:
1. To have the device at ID 3 on host adapter 0 treated as a narrow device,
the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /WIDTH=8<0:3>
2. To have all devices on host adapter 2 treated as 8-bit devices, the line in
the CONFIG.SYS file that loads SYM8XX.ADD should look like this:
<<=NOTE=>> Both the SYM8XX.ADD and SYM_HI.ADD drivers support the SYM53C895A chip. If both drivers have been installed, whichever driver appears first in the CONFIG.SYS file will control the SYM53C895A chip.
/C0=z : These parameters define the IRQ level to be used by the
/C1=z Socket Services driver. The new Card Services and Socket Services drivers for OS/2 do not use a hardware interrupt to notify the PCMCIA status change, so you do not need these parameters.
/IG0=y : This parameter defines a slot number, which Socket Services ignores. If you use the "Point enabler" supplied with a PC Card, you should take into consideration the coexistence with Socket Services.
/RI0=x : This parameter defines a slot number, where Socket Services disables the RI_OUT signal. For Example, "/RI0=1" specifies slot 1.
/D : This parameter enables "Warm docking" from the view point of PCMCIA hardware. By adding this parameter, two additional PCMCIA slots are reserved for the docking station.
/APOFF : This parameter turns off the Auto-Power Mode. If the Auto-Power Mode is ON, a PC Card will be automatically turned ON by the hardware when it is inserted. The default for Auto-Power Mode is ON.
/IO0=s : This parameter defines the slot number, for which Socket Services will change the way the -IOCS16 signal is generated. By default, the -IOCS16 signal is generated based on the -IOIS16 signal from the PC Card. If this parameter is specified, the -IOCS16 signal is generated based on the I/O data size which is specified by the Client program. This option is needed for some cards which do not generate the -IOIS16 signal. You need to verify this information with PCMCIA card vendors.
/C0=z : These parameters define the IRQ level to be used by the
/C1=z Socket Services driver. The new Card Services and Socket Services drivers for OS/2 do not use a hardware interrupt to notify the PCMCIA status change, so you do not need these parameters.
/IG0=y : This parameter defines a slot number, which Socket Services ignores. If you use the "Point enabler" supplied with a PC Card, you should take into consideration the coexistence with Socket Services.
/RI0=x : This parameter defines a slot number, where Socket Services disables the RI_OUT signal. For Example, "/RI0=1" specifies slot 1.
/D : This parameter enables "Warm docking" from the view point of PCMCIA hardware. By adding this parameter, two additional PCMCIA slots are reserved for the docking station.
/APOFF : This parameter turns off the Auto-Power Mode. If the Auto-Power Mode is ON, a PC Card will be automatically turned ON by the hardware when it is inserted. The default for Auto-Power Mode is ON.
/IO0=s : This parameter defines the slot number, for which Socket Services will change the way the -IOCS16 signal is generated. By default, the -IOCS16 signal is generated based on the -IOIS16 signal from the PC Card. If this parameter is specified, the -IOCS16 signal is generated based on the I/O data size which is specified by the Client program. This option is needed for some cards which do not generate the -IOIS16 signal. You need to verify this information with PCMCIA card vendors.
<<=ATTENTION=>> Only UHCI (Intel and Via) USB host controllers are supported. OHCI (Opti, SIS, ALI, CMD and Compaq) are not supported, so the USB drivers don't work with these chipsets.
<<=TIP=>>if you use the version from the Device Driver Pak2 available at:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/DDPak/xr_d002
the drivers supports Intel and VIA chipsets.
<<=NOTE=>> On IBM 365 System you have to add the parameter /FS
<<=TIP=>> A lot of Athlon motherboards are using the Via Southbridge VT82C686A chipset which provides 4 USB ports. Do you know if the Via drivers work with this Via chipset?". Robert Lalla, the author of the patched USB driver that works with VIA chipsets replied with this tip on how to get IBM's latest USB driver to work with VIA chipsets by applying a patch:
The VIA version of UHCI host driver that I uploaded to Hobbes last October is working for mice, keyboards, hubs and modem peripherals, maybe audio. For printers and removable disks updated USB base drivers are recommended. They are supplied from IBM together with the USB printer drivers. But again this USBUHCD.SYS is only enabled for Intel. The following patch script will add VIA support to USBUHCD.SYS dated Jan 2000:
-----save as VIA.PAT------------------
FILE USBUHCD.SYS
VER 2F2B C747040300
CHA 2F2E 01
-----------------------------------------------
- copy VIA.PAT to \OS2\BOOT
- set current directory \OS2\BOOT
- create a backup copy of USBUHCD.SYS
- run: PATCH VIA.PAT /A
A special aspect of the 686a Southbridge is that it does not contain one USB controller having 4 ports but instead 2 controllers (2 ports each). So unless one of both controllers is disabled explicitly, USBUHCD.SYS should be loaded twice(!) in CONFIG.SYS.
/DEBUG Displays even more messages. Not generally usefull.
/!SHARE Don't share disks with OS/2.
<<=NOTE=>>Load DSKLEEP.FLT before VRAID.FLT so DSKSLEEP.FLT can see the original disks. Load PARTFILT.FLT (from EXT2FS or FAT32.IFS) behind VRAID.FLT. PARTFILT.FLT duplicates any disk with an FAT32 or EXT2FS partition which will duplicate any VRAID partition residing on the same disks.
driver for the K6-2 (model 8+, CXT core) and K6-III CPUs.
This is Cornel Huth of 40th Floor Software free utility to enable the combined read and write functions of the K6 processors. It comes with a snoop utility that reports the value to be used for the register that enables the video write combining code. It is found for FREE only on his website http://www.40th.com as setup4k6.zip.
