[Previous] [Contents] [Next]

Fsys.ide

Driver for IDE fixed-disk interface (QNX)

Syntax:

Fsys.ide [options]...

Options:

-a controller
Assume the controller is at this address (default is 1f0 hex).
-B
Ignore BIOS settings for the drive.
-c drivespec
Assume these parameters for the drive. You specify these in the following format:

You must include heads, cylinders, and sectors. If you omit disknum, unit 0 is assumed. (Default: autodetect)

-f fsys_name
Registered name of filesystem process to attach to (default: qnx/fsys32)
-i irq
Assume the controller is using this interrupt (default is 14).
-L
Do not use LBA.
-m maxsize
Allow no more than this many blocks to be transferred from the disk to memory in one operation (default is 127).
-M multi_limit
Maximum number of blocks per interrupt. (Default: maximum supported by the drive.)
-n device_name
Assign this name to the block special device associated with the hard disk. The default is hd, which yields a device name of /dev/hdn, where n is a unit number assigned by Fsys.
-N version_name
Assign this unique version name to this invocation of the driver. The name can be from 1 to 11 characters in length. (Default: IDE)
-p
Program drive to use whatever IO mode it is capable of, regardless of how it has been configured.
-R nretries
Number of times to retry bad blocks (default: 1)
-v
Verbose. Report information about drives.
-V
Do not scan for CMD-640 VL interface.

Description:

Fsys.ide is the driver for the Integrated Drive Electronics (IDE) disk drive interface. The IDE technology integrates the traditionally host-based controller electronics within the drive itself.

If Then use
you have an ATAPI device (e.g. CD-ROM) Fsys.eide
you have a removable hard drive Fsys.eide
you have only a hard drive but no shortage of memory Fsys.eide
you are low on memory, and have only a hard drive with LBA enabled Fsys.ata
you are low on memory, and have only a hard drive without LBA enabled Fsys.ide
you are booting off the drive and your BIOS doesn't support LBA Fsys.ide or Fsys.ata -L
you are booting off the drive and the BIOS is set for LBA Fsys.ata
you are booting off the drive and the BIOS is set for CHS, and the drive supports LBA Fsys.ide or Fsys.ata -L

Note:

Note: If you are installing multiple OSs on the drive, make sure all OSs use a compatible mode. For example, if your drive is >=528M and DOS will also be installed on the drive, the driver should be configured to use LBA.


Manufacturers of IDE drives have collectively endorsed a standards process that defines a common command and cabling specification. The standard they've developed is now a "working draft" of the American National Standard of Accredited Standards Committee X3. For drives that vary from our interpretation of the IBM PC/AT specification and won't work with Fsys.ata, use Fsys.ide.

In order to obtain drive parameters, Fsys.ide examines values established by the BIOS of your computer. If necessary, you can override these default parameters with the -c option.

To define the largest single read or write the driver will support, use the -m maxsize option; the default value for this option is 127.

To help prevent you from unintentionally starting the same driver twice, Fsys rejects the invocation of any driver that has the same version name as a previously mounted driver. So if you wish to run multiple copies of Fsys.ide, you must use the -N version_name option to assign a unique version name to the driver. (You can display the version name of a driver with the sin ver command.) You should also use the -n device_name option to specify a unique device name, since another driver may have already created the default device name.


Note: The Fsys.ide driver does not support CD-ROM drives. See Fsys.eide.

Caveats:

Some IDE drives don't match the draft standard that Fsys.ide assumes (AT Attachment Interface for Disk Drives, Rev 4, March 17, 1993). If a drive won't function with Fsys.ide, please inform our technical support group. We'll need the make, model, and year of purchase of your drive.

Don't use slay to shut down a filesystem driver! If you do, new drivers may not be able to load properly and Fsys itself may experience internal errors.

If you need to shut down a filesystem driver, follow the steps in the "Driver shutdown" section in the documentation for Fsys.

See also:

Blkfsys, Fsys, Fsys.*


[Previous] [Contents] [Next]