💾 Archived View for gemini.spam.works › mirrors › textfiles › computers › DOCUMENTATION › 3_drives.t… captured on 2022-06-12 at 06:29:17.
-=-=-=-=-=-=-
3_Drives v2.5 Shareware version Released July 4th 1993
4_Drives v3.0 Registered version Released July 4th 1993
???????? 3_Drives v2.5 ?
? ?????????????????? ??????????????????
? Dustbowl Designs, Inc. ? 426 MB ? ?????0 MB???????
? -=? NOT REGISTERED ?=- ? ?????????????? ? ??????????????????
? "Dedicated to enhancing the ?????????????????? ??????????????????
? world's personal computers." E: Installed 4_Drives only
? (405) 741-2721 BBS
?????????????????????????????????????????????????????????????????????????????
? Copyright 1992 by Dustbowl Designs, Inc. All rights reserved. ?
? 12600 S.E. 38th Street, Choctaw, Oklahoma USA 73020-6107 ?
? See 3_Drives.doc for v3.0 registration information. (405) 741-4705 ?
?????????????????????????????????????????????????????????????????????????????
The universal device driver that lets you add an additional 16-bit
interface to your system. Add up to two **= MORE =** MFM, RLL, ESDI
or AT/IDE hard disk drives regardless of the first interface type.
??????????????????????????????????????????????????????????????????????
???? What's New ??????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
Registered versions now support READ/WRITE MULTIPLE commands on newer
AT/IDE hard disk drives yielding up to a 50% increase in data transfer
rate from the drive.
Registered versions now support new READ/WRITE FAST routines for use
on all other drives yielding up to a 35% increase in data transfer
rate.
Beginning with release v2.50-Shareware and v3.0-Registered, command
line switches are implemented that provide flexibility, compatibility
and speed. (see COMMAND LINE SWITCHES: below)
Beginning with release v2.50, a new utility is provided called
4DRVUTIL.EXE. This is an AT/IDE Identify Drive utility that supports
both the Primary and Secondary Port Addresses. The emphasis with
4DRVUTIL is to help show what advanced features on your AT/IDE drives
are available and then give the appropriate command line switches. for
both 3/4_Drives and our new product, Diskqwik. See 4DRVUTIL.DOC for
details.
Instant Upgrade Satisfaction. Registration/Download of the registered
versions can be accomplished in only one call to our BBS! Using our
custom Credit Card Charge/Download Door you can move into our
program's most advanced features in just a matter of minutes.
??????????????????????????????????????????????????????????????????????
???? Introduction ????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
3_Drives v2.5 is a shareware CONFIG.SYS block device driver that
allows the utilization of a SINGLE hard disk drive on the standard
Secondary Port Address using the DOS operating system giving you the
potential total of FOUR fully functional hard drives in your system!
This unique device drive also permits two incompatible controllers
and/or host adapters to COEXIST in the same system.
* With 3_Drives you can combine MFM, RLL, ESDI, AT/IDE and
SCSI hard disk drives......
Primary Port | Secondary Port
Address | Address
|
Drive 1 Drive 2 |
??????? ??????? | ??????? 4_Drives ???????
? RLL ? ? RLL ? | ? ? 3_Drives ? ?
??????? ??????? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ? IDE ? ? ? IDE ? ?
? MFM ? ? MFM ? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ?ESDI ? ? ?ESDI ? ?
?ESDI ? ?ESDI ? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ? MFM ? ? ? MFM ? ?
? IDE ? ? IDE ? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ? ? RLL ? ? ? RLL ? ?
?SCSI ? ?SCSI ? | ? ? ??????? ? ??????? ?
??????? ??????? | ? ???????????? ?
| ????????????????????????
|
Our systems handle | Any one of these interfaces
this side already. | can be added using 3_Drives
| or 4_Drives.
Any of these works...>>>>> with any of these!
* This means you DO NOT have to retire your older MFM or RLL
drives if you purchase a new AT/IDE hard disk drive!!!
* Allows you to still boot to a SCSI drive in a system
with IDE, MFM, RLL or ESDI.
* If you have two IDE drives that will not work together due
to a manufacturer's Master/Slave incompatibility, 3_Drives
lets them coexist without conflict.
* With 3_Drives you can easily use an AT/IDE, MFM, RLL or
ESDI drive to backup data and/or transport large quantities
of data between systems at hard drive speeds.
??????????????????????????????????????????????????????????????????????
???? Upgrade Offer ???????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
As noted in the screen representation and at the beginning of this
document, 3_Drives shareware v2.5 supports a SINGLE primary partition
on a SINGLE hard disk drive at the Secondary Port Address. In the
event that you may want to activate the High Speed Data Transfer Rate
options, add a SECOND drive to the Secondary Port Address, or desire
access to logical drives in extended partitions, we offer the
programs: registered v3.0 3_Drives and 4_Drives.
Registered version features:
* Ultra-fast program loading without delays or required user
intervention.
* Program supports up to 10 logical drives per physical drive.
* Fast I/O routines: READ/WRITE MULTIPLE sectors or READ/WRITE FAST
commands supported.
* Includes 4_Park, a four drive head-parking/screen-saver utility.
* Discount on version upgrades.
* Access to advanced technical support and registered user sections
of our support BBS.
* Postscript version of the documentation.
??????????????????????????????????????????????????????????????????????
???? System Requirements ?????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
A few simple conditions must be met in order to utilize the 3_Drives
device driver.
They are:
1. Computer system MUST be either a 286, 386sx, 386dx, 486sx or
486dx.
2. DOS level must be v3.0 or higher, including Digital Research
DR DOS 6.0, with a single Primary partition (3_Drives v2.5
shareware version, only).
** Registered 3_Drives or 4_Drives v3.0 also support Extended
partitions with up to 10 logical drives per physical unit.
3. A second Controller or Host Adapter which must have the option
to set a Secondary Port Address to 170h and to disable IRQ14
monitoring. The Secondary Port Address feature is available on
practically every hard drive controller made and the disable
IRQ14 feature is found on about half of the adapters, but is
"do-able" on 100% of them using a simple tape-over method (See
App Note #10 for "Tape-Over Method"). Jumpers and settings for
the Seagate ST-07A, ST-08A, Acculogic SIDE-3 AT/IDE Host
Adapters and Western Digital WD1006-xxx, Adaptec ACB-231x,
Adaptec ACB-237x or Data Technology DTC728x MFM/RLL ST506/ST412
Interface controllers are included in this doc file to show you
how this is done. (See Controller and Host Adapter Setup
Instructions).
??????????????????????????????????????????????????????????????????????
???? Preparing "Secondary Port" Disk Drives ??????????????????????????
??????????????????????????????????????????????????????????????????????
The disk drive that will be attached to the Secondary Port Address
needs to be partitioned and formatted on the Primary Port Address
prior to using the 3_Drives/4_Drives device driver. Use the standard
DOS utilities, FDISK and FORMAT, or automatic installation software to
accomplish the task. This will probably require temporarily removing
the existing hard disk drive controller or preparing the "Secondary"
drive in a different system.
BEFORE disengaging the "Primary" drives, BE SURE to write down the
CMOS drive type(s). If 'User Defined' or 'Custom' drive types are
being used, write down the associated cylinder, head, write precomp,
lzone and sector per track values.
(If the drive you intend to install on the Secondary Port
Address is prepared and ready to go, jump to step #9 below)
The installation steps to take for an unprepared drive without data
are roughly as follows:
.5 Finish reading the rest of this document.
1. Satisfy yourself that BACKUPs of your data are current and in
good condition.
2. Prepare a bootable floppy diskette and copy (or simply have
available on a separate diskette) FDISK and FORMAT to this
floppy.
3. Install (on the default Primary Address) the controller or host
adapter for the drives you eventually intend to use on the
device driver and set the appropriate drive type number in the
system CMOS setup. Remember, each controller will support one or
two drives. The drive jumpers that establish drive selects or
Master/Slave relationships follow the same rules as they would
in a single controller system. Do not set a MFM or RLL to Drive
select three!
4. Boot to the floppy diskette.
5. Use FDISK to define the Partition(s). The system will
automatically reboot to the A: drive after concluding FDISK.
6. FORMAT C: /S (Registered versions: including any other logical
drives in extended partitions without the /s).
7. Confirm that the hard drive boots without the floppy in A: and
can perform reads and writes, and is good working condition.
8. Restore the CMOS drive types to the ones used on the original
1st (and 2nd) drives. Power down the system and reinstall the
controller for the original drives.
9. Set the second Host Adapter for the "Secondary" drive to
Secondary Port Address 170h and disable IRQ14 monitoring. (see
below for examples of popular Host Adapter/Paddle Board and
Controller jumper settings). You do not have to make any changes
to the drive select jumpers or Master/Slave jumpers.
10. Reboot. The system should start in the same way it always has.
11. Copy the 3_DRIVES.HDD program into the root directory of the C:
drive and Edit the CONFIG.SYS file to include the line:
DEVICE=C:\3_DRIVES.HDD
This line should precede any other block device drivers (such a
RAMDRIVE.SYS). If a Disk Manager (tm Ontrack Computer Systems)
partition is installed on the original "Primary" drives, the
DEVICE=C:\3_DRIVES.HDD line should follow after DMDRVR.BIN.
12. Reboot. An 3_Drives installation screen (shown above) will
indicate the loading status of the device driver. The drive
letters assigned to the "Secondary" drive(s) will depend on the
number of partitions on your C: and D: drives.
??????????????????????????????????????????????????????????????????????
???? Command Line Switches ???????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
These switches can be set up in the config.sys file after the complete
driver name and may or may not be separated by spaces or other
delimiters.
The following command line switch has been put into place for BOTH the
SHAREWARE and REGISTERED versions:
No Command Line Switches - Functionally equivalent to our previous
releases v1.1, v1.50, v2.10. Without any
of the Fast I/O options.
ATA - This switch enables new reset and recovery features that are
available on the newer ide 'ata' spec drives. You can try this
switch for improved error recovery on mfm/rll/esdi controllers
as well but if the driver locks up remove this switch.
The following command line switches have been put into place for the
REGISTERED versions:
M(?)(+) - Where M selects the multiple sector data transfer mode and
the ? is either a 0 to select this mode on the first drive
attached to the secondary controller or a 1 to select the
multiple sector data transfer mode for the second drive
attached to the secondary controller. The + is used to set
the block mode to the maximum that the drive can handle.
(CAUTION! use this with care as some drives will reserve
the entire read/write cache ram for multi-block data area.
This will slow the drives overall data xfer to an all time
low.
Examples:
device=driver.hdd M0 - selects multiple or block mode on
drive 0 only.
device=driver.hdd M0+ m1 - selects the multiple mode to be
enabled on both of the driven
drives. The first drive will
utilize the full capacity given
for block mode xfers.
RF(?) - Where RF = Read Fast, and the ? is defined as 0 for drive 0
and 1 for drive 1.
Examples:
device=driver.hdd rf0 - enables the read fast I/O
algorithm for drive 0 only.
device=driver.hdd rf0 RF1 - enables the read fast algorithm
on both of the driven drives.
WF(?) - Where WF = Write Fast and the ? selects drive 0 or drive 1.
Examples:
device=driver.hdd wf0 - enables the write fast algorithm
for drive 0 only.
device=driver.hdd wf0 wf1 - enables the write fast algorithm
for both drives.
Q - This switch enables a Quick driver init without delays usually
generated for display recognition.
P - This switch enables a "press c to continue.." pause after the
driver loads for debug and command switch confirmation.
3* - This switch stops 4_Drives from looking for a non-existent
fourth drive. Normally, the routines can determine the
presence or lack of the fourth drive unit. During our beta
testing, we ran in a drive/controller combination that
stubbornly reported a "phantom" fourth drive, this switch puts
a stop to that nonsense. (to clarify the switch, it is 3
asterisk)
MORE EXAMPLES:
device=driver.hdd m0 rf1 wf1 p
these switches will enable the following:
Multiple mode on drive 0, both Read Fast and Write Fast on
drive 1, the driver will Pause after loading until the letter
c is pressed.
device=driver.hdd wf0 p rf1 wf1 q
these switches will enable the following:
Write Fast on drive 0, a Pause until 'c' is pressed after the
driver loads, both Read Fast and Write Fast on drive 1, no
screen delays will be utilized in the init code.
CONFIRMATION of Device options:
Visual confirmation of the I/O option combinations will be indicated
by the COLOR of the "led" indicator on the 4_Drive banner screen drive
icon....
??????????????????
? 426 MB ?
? ?*???????????? ?
???^??????????????
|
|
RF(?) - will be denoted by a BLUE * (led) indicator for the drive
selected.
WF(?) - will be denoted by a YELLOW * (led) indicator for the drive
selected.
RF(?) & WF(?) - will be denoted by a CYAN * (led) indicator for the
drive selected.
M(?)(+)- will be denoted by a RED * (led) indicator for the drive
selected and the size of the multiple block will be printed
below the drive capacity information. This Kilobyte size
will usually double if the + switch is included.
P - The "Press c to continue", message will be displayed in the
bottom left corner of the yellow text box and the 'c' key
must be pressed before the driver's init code is terminated.
Q - The screen display will not slow to allow recognition of
drive capacity, I/O option configuration confirmation or
Multi-mode buffer size option confirmation. This switch will
have a more noticeable affect on drives that have multiple
logical partitions installed on them.
ATA - Sorry, but we decided not to give a visual indication of the
implementation of this switch.
??????????????????????????????????????????????????????????????????????
???? Background ??????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
In the past, three major factors have stood in the way of achieving
the elusive goal of supporting more than two hard disk drives or even
two disk drives of dissimilar interfaces. First, DOS versions prior
to the v5.0 would support a maximum of two physical hard disk drives.
The v5.0 DOS FDISK supports up to eight physical hard disk drives if
the Host Adapter is designed to follow the FDISK conventions of DOS
v5.0. (Some SCSI interface Host Adapters are now out in the
marketplace which have this support.)
Second, standard interface hard disk drive controllers (except for
SCSI) are limited to two physical drives. In the case of MFM, RLL and
ESDI, the drives usually have a Drive Select 3 and 4 jumper (DS3 &
DS4), but the controllers for these interfaces use the industry
standard "Daisychain" configuration which allows only two drives to be
connected. (The rare "Radial" configuration uses the DS3 and DS4.) In
the case of the new AT interface for hard disk drives, also known as
IDE, the controller is built onto the drive itself and is limited by
design to two physical drives per Host Adapter - Master and Slave.
Third, controllers for these interfaces usually require a drive type
number to be set in CMOS and only two slots are ever given by the
system BIOS.
Until 3_Drives/4_Drives, two AT controllers have generally been unable
to coexist because of a condition known as a "port address conflict."
In effect, both controllers canceled each other out because they
needed to use the same Hard Drive Primary Port Address, 1F0h. In its
default configuration, DOS only recognizes hard disk drives that are
attached to this Primary Port Address and communicates with them
through the system bios and INT13. A block device driver is required
to service drives that are attached to the common Secondary Port
Address, 170h; the 3_Drives/4_Drives device driver serves this
function.
??????????????????????????????????????????????????????????????????????
???? Outline ?????????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
An brief outline of how 3_Drives works is as follows:
After partitioning and formatting in the DOS environment, every hard
disk drive, regardless of interface, controller, or CPU has a very
special sector of information called the Master Boot Record (MBR). The
MBR is always the very first physical sector on the disk (cyl 0, hd 0,
sector 1), the contents of which 1) preserve the defined partition
structure, 2) contain the first executable instruction to begin
loading the active operating system, and 3) a final word signature in
the sector, AA55h, indicating a valid Master Boot Record.
Once a valid MBR is identified, the values stored in the partition
record of the MBR indicate the location of the DOS Boot Record (DBR)
which is generally located at logical cyl 0, hd 1, sector 1. This DOS
boot sector contains two vital components - the BIOS Parameter Block
(BPB) structure and a loader routine for the operating system . The
BPB provides a logical description of the hard disk drive's geometry
(logical blocks, heads, sectors per track, bytes per sector, etc.),
while the operating system loader establishes the names of the system
files IO.SYS and MSDOS.SYS, their root directory locations and then
loads them into memory .
Next, the IO.SYS file is read into memory, followed by the MSDOS.SYS.
These are the names of the two hidden files which accompany
COMMAND.COM after formatting a bootable drive. These programs begin an
initialization routine which establishes the resident character and
block devices found during the Power On Self Test (POST) and
motherboard ROM BIOS initialization. Once the basic hardware has been
identified and the DOS kernel has been positioned into low memory, the
next stage is to run a system module within IO.SYS called SYSINIT. It
is at this time that the first of the Primary Port Address drive
letter designations are assigned (A:, B:, C:, etc.). These block
devices are given special handling at this point. For each, a pointer
to a BPB array is established in memory.
Next, begins the process we are most interested in, namely the
processing of the CONFIG.SYS file. The entire file is read into
memory and analyzed for block and character type device drivers. When
block device drivers are identified, like 3_Drives, their entries
are added to the drive translation table and given the next available
drive letter designation.
Device drivers, like regular programs (but not quite like regular
programs), have initialization code and resident code. The
initialization code in 3_Drives is the display banner and secondary
drive identification, while the resident portion is a collection of
routines handling very specific AT register set commands. The AT
register commands "talk" directly to the Secondary Port Address, 170h,
and therefore to the drive itself, and cover drive specific operations
like Read, Write, Recal, and Reset. It should be noted that the Format
command operation is not supported by 3_Drives, which is the reason
why the drive must be partitioned and prepared in a normal C:/D:
environment.
After all components of the CONFIG.SYS file are processed, SYSINIT's
final function is to load and execute the MS-DOS shell program,
COMMAND.COM. How DOS manipulates the resident (critical error
handling, for example) and transient portions (batch file processes,
COPY, and RENAME, etc.) of the shell are beyond the scope of this
overview.
Thereafter, during the normal course of operation of the computer
system, DOS commands which are directed towards the drive letter(s)
assigned to the 3_Drives block device(s) are executed through the
memory resident portion of 3_Drives.
3_Drives v2.5 will occupy a minimum of 4.1Kbytes of memory under DOS
5.0. In the registered versions of 3_Drives/4_Drives (v3.0), the
amount of memory required for the device driver will climb slightly by
?48 bytes/drive, depending on the number of logical drives in extended
partitions, if any.
??????????????????????????????????????????????????????????????????????
???? App Notes ???????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
Some Application Notes:
1. The effect of the program on the performance of the system is
negligible.
2. The use of 3_Drives on XT's is DISALLOWED, since it relies
exclusively on AT register set commands which are only available
on 286's or higher.
3. If power supply leads are in short supply, a simple "Y" adapter
that splits two leads off of a single, are available at most
computer supply stores.
4. If two controllers are set to the SAME port address or share the
same IRQ, either floppy or hard, the system will hang during the
POST (Power On Self Test).
If both controllers have support for floppy drives, disable the
floppy support on the second. If a specific "disable floppy"
jumper is unavailable, then set the floppy to a secondary port
address (usually 370h) which effectively hides the conflict.
5. 3_Drives can be moved into upper memory under DOS 5 with
DEVICEHIGH=C:\your...path\3_DRIVES.HDD
6. 3_Drives shows all signs of complete stability with Microsoft
Windows (tm). In fact, our entire Windows subdirectory
structure is located on the "Secondary" drive! We have thrown in
everything we can think of to test Windows compatibility, and
all tests have proven successful. If you intend to use the drive
supported by the 3_Drives for the Swap File, then in must be of
the Temporary Swap File Type. (A Permanent Swap File requires
Int13 support.)
7. We've run three of the most popular file defragmenters without
problems. In any case, ALWAYS follow the software
manufacturer's instructions and BACKUP you data first.
8. DOS 2.x and above will run with the same partition and capacity
limits allowed by that version of DOS, however only DOS 3.0 and
above will show the proper drive letters on the 3_Drives
initialization screen.
9. 10 partitions per physical drive are allowed under 3_Drives
support. Registered v3.0 only.
10. "Tape-Over Method": It is possible to install a single MFM, RLL
or ESDI drive on the secondary port address and utilize
3_Drives. This process, however, is not as straight forward as
putting the AT/IDE on the secondary because typical ST412
interface controllers (MFM and RLL) usually do not have the
built-in ability to disable the IRQ14. If no jumper on the MFM
controller exists to disable IRQ14, then the line can usually be
disabled manually where it plugs into the motherboard.
On a 16-bit controller, the IRQ14 line is found on the back side
card edge, on the "short" 16-bit extension. It is the 7th
contact from the left or 12th from the right (D7). Usually,
placing a piece of simple transparent tape over the contact will
cause it to be disabled when the card is plugged into the
motherboard. It is advisable that you refrain from attempting
this configuration unless you have prior experience with
modifications of this sort. See below:
?
? ? Metal Clamp
??????????
? ? 0 ? Perspective: Looking at the backside of the card
??????????
? ? 8-bit long slot 16-bit short slot
? ?_____ 31 total contacts ___ 18 total contacts______
? ??????????????????????????????? ??????????????????
? ?
? D7 (IRQ14) Tape over
count 7 spaces from left or
12 spaces from right
Note: Many manufacturers only plate the contacts that will be
needed on the card. Be sure to count spaces, not
actual plated contacts.
11. As noted earlier, some programs will not operate through
3_Drives (i.e. FDISK, FORMAT). This is because these programs
bypass DOS and do not update the partition's FAT (File
Allocation Table). Other examples of this are usually drive
diagnostics utilities. If programs of this sort are deemed
necessary to run, the drive will need to be reinstated on the
primary port address in order to be "seen" by the program.
12. The DOS ASSIGN utility can be used to set a drive on the
Secondary Port Address to C:, if desired. Simply execute the
command ASSIGN C:=E: E:=C: This will effectively swap the
assigned drive letters. Remember that CHKDSK will not run on
assigned or substituted drives. Running ASSIGN again, without
any command line parameters, will clear the assignment.
13. Popular drive compression programs work well with 3_Drives and
4_Drives. (In fact, this document is being written on drive
number 4, and is a compressed drive.) The important points to
remember are that 3_Drives needs to be loaded before the
compression drivers IF the Secondary Port Address drives are
being compressed. If the system is already compressed prior to
installing 3_Drives, then confusion could arise when it comes
time for the compression driver to assign the drive letter
designations, especially with the drive letter swapping and
reserved drive settings that are typical of compression
programs. To be absolutely safe, BE SURE to backup all data
prior to creating compressed drives.
14. RLL and ESDI controllers usually operate on the Primary Port
Address with an enabled on-board bios. This bios needs to be
disabled when used with 3_Drives on the Secondary Port Address.
The drive does not have to be lo-level formatted with the bios
disabled.
15. The driver installs in it's raw state eg., device=driver.hdd
will set the driver up in the "old", slow but sure I/O mode of
operation. If the driver loads ok with the Old switch but hangs
with data errors use the ATA switch. Use of the ATA switch
implements some of the new drive data error recovery techniques
employed by this version. The omission of the ATA switch is
provided as a bridge between these technologies.
16. The M(?) switch will only be enabled, indicated by a RED *
(led), if the drive selected by the (?) is capable of performing
multiple block mode data transfers. If the * (led) indicator
remains GREEN, then the drive rejected the multi-mode. You will
have to then edit the config.sys file to implement Fast Reads or
Writes as desired or utilize no I/O switches to default to the
old slow but sure mode.
17. Utilization of the M(?)+ plus switch addition to select the
maximum block xfer size will prove to be detrimental to the data
xfer rate on some drives. As the 'AT' world is ever changing,
some early drive models gave totally "unworkable" maximum block
sizes for this selection. If one were to select the size that
the drive offered, some drives would immediately lock up as part
of this overall buffer is utilized as drive firmware scratch
pad! We utilize an algorithm to (hopefully) select a workable
compromise of the total buffer area.
18. Multiple Block mode on some early drives though enabled, will
not work AT ALL with the driver as the early implementations of
this multi mode were faulty in their microcode.
19. Data xfer rates with the use of the Multi-mode will be more
noticed in systems that ask for large blocks of data in a single
request.
20. Fast Reads and Fast Writes are not mutually exclusive. Therefore
any or all combinations of Fast I/O will be allowed.
21. We will check the first 60 bytes of text after the = sign in the
device=driver.hdd line in the config.sys file for command line
switches. This should be adequate for all possible
configurations as described above.
??????????????????????????????????????????????????????????????????????
???? Error Messages ??????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
The device driver may display a small assortment of error messages
during the loading process of the CONFIG.SYS file. These usually
relate to unformatted status, jumper, cabling and power issues.
The most common error messages are descriptive and will explain the
specific problem encountered. (i.e. "No controller found at the
Secondary Port Address" or "No valid DOS boot record found").
The less common errors are listed by number:
Error code #1 : Address Mark not found. cyl=xx hd=xx sect=xx
Drive may need lo-level format. Scan for defects.
Error code #2 : Drive Fails Recal
Check cables and drive select jumpers, etc.
Error code #4 : Aborted Command.
Invalid command request or drive fault problem like a
seek error.
Error code #5 : Write Fault.
Usually caused by power supply voltage fluctuations or
problems with termination resistors.
Error code #6 : Time-out.
General time out.
Error code #7 : Time-out while waiting for drive DRQ.
Error code #8 : Read Fault.
Check cables, connections and drive jumpers.
Error code #16 : Sector ID Not Found. cyl=xx hd=xx sect=xx
May need a lo-level format.
Error code #64 : CRC Error.
Scan for defects.
Error code #128: Block Marked Bad.
??????????????????????????????????????????????????????????????????????
???? Legal Disclaimer ????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????
LICENSE AGREEMENT
3_Drives 4_Drives 4_Park 4_Drive Utilities All versions.
Dustbowl Designs, Inc. provides the accompanying object code software
("Software") and nonexclusively licenses its use on the following
terms and conditions. The Software is copyrighted by Dustbowl Designs,
Inc. with all rights reserved. YOU ASSUME FULL RESPONSIBILITY FOR THE
SELECTION OF THE SOFTWARE TO ACHIEVE YOUR INTENDED PURPOSES, FOR THE
PROPER INSTALLATION AND USE. Dustbowl Designs, Inc. DOES NOT WARRANT
THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, THAT THE SOFTWARE IS
FIT FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL BE
ERROR FREE. Dustbowl Designs, Inc. EXPRESSLY DISCLAIMS ALL WARRANTIES,
WHETHER ORAL OR WRITTEN, EXPRESSED OR IMPLIED, INCLUDING WITHOUT
LIMITATION WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. IN NO EVENT WILL Dustbowl Designs, Inc. BE LIABLE TO YOU,
YOUR CUSTOMERS OR OTHER USERS FOR ANY INDIRECT, INCIDENTAL,
CONSEQUENTIAL, SPECIAL OR EXEMPLARY DAMAGES ARISING OUT OF OR IN
CONNECTION WITH THE USE OR INABILITY TO USE THE SOFTWARE.
3_Drives is a trademark of Dustbowl Designs, Inc. The 3_Drives
software and documentation are Copyright 1992 by Dustbowl Designs with
all rights reserved. The 3_Drives v3.0, 4_Drives v3.0 and 4_Park v1.1
software programs ARE NOT shareware or freeware and unauthorized
redistribution is STRICTLY PROHIBITED.
End of License agreement.