Readme File For EZ-Drive 9.09W Rev. 1.01
Please read the appropriate section(s) in this file before installing
your WD Caviar hard drive with EZ-Drive 9.09W.
Section 1: Upgrading from an older version of EZ-Drive.
Section 2: Migrating from Ontrack Disk Manager to EZ-Drive.
Section 3: Creating FAT32 partitions with EZ-Drive.
Section 4: Copying drives with multiple partitions.
Section 5: Notes on the Backup/Restore Track 0 feature.
Section 6: BIOS boot options.
Section 7: BIOS POST error messages.
Section 8: Notes on setting partition sizes manually in EZ-Drive.
Section 9: Disabling Floppy Boot Protection on drives when using
Windows NT (3.51, 4.0) or OS/2 Warp (3.0, 4.0).
Section 10: IBM AntiVirus for OS/2 and EZ-Drive.
Section 11: Compaq Personal Diagnostics and EZ-Drive.
Section 12: Quarterdeck Partition-It and EZ-Drive.
Section 13: Quarterdeck QEMM 8 and EZ-Drive.
Section 14: Symantec Norton Disklock and EZ-Drive.
Section 15: Symantec Norton Utilities and EZ-Drive.
Section 16: Symantec Norton Your Eyes Only and EZ-Drive.
Section 17: Touchstone Software PC-cillin 95 and EZ-Drive.
Section 18: V Communications System Commander and EZ-Drive.
Section 19: Using Windows 32-bit Disk Access with Enhanced IDE drives.
Section 20: Using Windows for Workgroups 32-bit File Access.
----------------------------------------------------------------------------
Section 1: Upgrading an older version of EZ-Drive to 9.09W.
You can upgrade an older version of EZ-Drive on your hard drive to the
current 9.09W version by following these steps:
Note: This procedure will only update the EZ-BIOS code in the boot sector of
the hard drive. It will not repartition or reformat your existing
drive(s).
1. Place a bootable DOS or Windows 95 startup disk in drive A:
and reboot the computer.
2. When the DOS prompt appears, place the EZ-Drive disk in drive A:. Type
EZ/MBR and press {ENTER}. EZ-Drive will begin updating the EZ-BIOS code
in the boot sector of the hard drive with the current version. When
finished, it displays the message:
"EZ-Drive re-installed on drive 1"
"Press any key to continue"
Press any key on the keyboard. EZ-Drive repeats the above process
if other drives in the system have EZ-BIOS code installed.
3. Press any key on the keyboard when EZ-Drive finishes updating all
drives in the system. At the DOS prompt, remove the EZ-Drive disk
from drive A: and reboot the computer. Press <CTRL> when EZ-BIOS
initializes. The EZ-BIOS status screen displays the version as 9.09W.
----------------------------------------------------------------------------
Section 2: Migrating from Ontrack Disk Manager to EZ-Drive.
If you have Ontrack Disk Manager software installed on your hard drive,
you can migrate to EZ-Drive without setting up a new drive or reformatting
an existing drive by following these steps:
1. Place the EZ-Drive disk in drive A: and reboot the computer.
2. After EZ-Drive loads, press {ENTER} twice to display the Main Menu.
3. Choose "Advanced Options," then choose "EZ-BIOS Setup." If EZ-Drive
prompts you to select a drive, choose the boot drive (usually Drive 1).
4. EZ-Drive displays the following message:
"This drive does not have EZ-BIOS installed."
"Press Y to install EZ-BIOS now."
Press Y.
5. EZ-Drive displays the following message:
"EZ-Drive has detected a drive with Disk Manager installed.
Since Disk Manager is not compatible with EZ-Drive you may not
setup any drives until Disk Manager is removed."
"Press Y to replace Disk Manager with EZ-BIOS"
Press Y.
6. EZ-Drive displays the following message:
"Disk Manager replaced with EZ-BIOS."
Remove the EZ-Drive disk from the floppy drive. Press <ESC> four times,
then press {ENTER}. The computer reboots and EZ-BIOS loads instead of
Disk Manager.
----------------------------------------------------------------------------
Section 3: Creating FAT32 partitions with EZ-Drive.
EZ-Drive 9.09W fully supports Microsoft's FAT32 file system, however, the
option for creating FAT32 partitions with EZ-Drive is only available if
system files that support FAT32 are detected (e.g. system files for
Windows 95B or Windows 98). FAT32 partitions must also be 512 MB or greater
in size.
----------------------------------------------------------------------------
Section 4: Copying drives with multiple partitions.
Under certain circumstances it is possible to get EZ-Drive to copy multiple
FAT16 partitions from an existing hard drive into one FAT32 partition
on another hard drive. Even though the software allows this we do not
recommend doing so as only the data in the first partition will be copied over
and/or the copy procedure may fail altogether.
----------------------------------------------------------------------------
Section 5: Notes on the Backup/Restore Track 0 feature.
During EZ-Drive installation, EZ-Drive automatically creates a backup of
track 0 and stores it on the hard drive. You can create backups at any time
by using the Backup/Restore Track 0 feature found under the Advanced Options
menu. However, the total number of stored backups is limited to 10
(0 through 9) for each hard drive in the system. EZ-Drive must also reserve
a cylinder at the end of the drive in order to store the backups, the utilized
space in this cylinder will not be reported as user addressable capacity.
----------------------------------------------------------------------------
Section 6: BIOS boot options.
Some BIOS' feature a 'Boot Order' option which allows the computer to boot
from other hard drives in the system. With this feature enabled, a particular
hard drive in the system can be designated as the bootable drive which will
cause the computer to boot from this drive even if it is moved to another
position (e.g. primary slave or secondary master). If your BIOS supports
this feature then you must remember to update the Boot Order option whenever
drives are switched or reconfigured.
----------------------------------------------------------------------------
Section 7: BIOS POST error messages.
Some BIOS' are not capable of supporting hard drives that are 8.4 GB
in size or larger. This may cause the BIOS to display various POST
(Power On Self Test) error messages during the boot process when such a
drive is connected to the system. Even if EZ-BIOS is installed
on the hard drive the BIOS may still continue to display POST error messages
during the boot process. POST error messages are often caused by incorrect BIOS
settings. However, if these error messages continue to be displayed after
eliminating all other possible causes, it may be due to the BIOS having trouble
in detection of your 8.4 GB or larger drive.
If you believe this is the case, try using the Alternate Jumper Settings
for your WD Caviar hard drive. If the POST error disappears, it may be capacity
related. You can then reinstall EZ-Drive (Please refer to the Installation Guide
included with your WD Caviar hard drive for more information on the Alternate
Jumper Settings).
----------------------------------------------------------------------------
Section 8: Notes on setting partition sizes manually in EZ-Drive.
When specifying partition sizes manually during an EZ-Drive installation,
keep in mind that EZ-Drive is limited to creating no more than 10 partitions
on a drive. However, any free space left on the drive can still be
partitioned using another utility (e.g. the Fdisk utility in MS-DOS or
Windows 95).
----------------------------------------------------------------------------
Section 9: Disabling Floppy Boot Protection on drives when using
Windows NT (3.51, 4.0) or OS/2 Warp (3.0, 4.0).
If EZ-BIOS is controlling your hard drive(s) and you are using Windows NT
(3.51, 4.0) or OS/2 Warp (3.0, 4.0), you must disable Floppy Boot Protection
for each drive set up with EZ-Drive. If Floppy Boot Protection is not
disabled, Windows NT and OS/2 Warp will not be able to see the EZ-Drive
created partitions.
----------------------------------------------------------------------------
Section 10: IBM AntiVirus for OS/2 and EZ-Drive.
If EZ-BIOS is installed on your hard drive, the IBM AntiVirus software
version 2.5 for OS/2 detects the EZ-BIOS code in the boot sector of the
drive as a possible virus. If this happens, you can choose "Close" to
end IBM AntiVirus without taking any action, or choose "Ignore" to tell
IBM AntiVirus it has incorrectly identified the boot record as having a
virus and not report it as infected in the future. Do not choose "Replace".
This will overwrite the EZ-BIOS code, making your drive unbootable.
Should this happen, you can restore the EZ-BIOS code by using the
"Back Up/Restore Track 0" feature in EZ-Drive. (Please refer to the
Installation Guide included with your WD Caviar hard drive for
more information.)
--------------------------------------------------------------------------
Section 11: Compaq Diagnostic Partitions and EZ-Drive.
EZ-Drive 9.09W now supports Compaq systems that have the Personal Diagnostic
software preinstalled onto the hard drive (which is used for diagnostic
testing and system setup). This software resides in a special partition on the
hard drive and is accessed by pressing a key during the computer boot
sequence. EZ-BIOS can coexist with these partitions only when installed in
a two-drive system (i.e. master/slave), or when using EZ-Copy to transfer
data from an existing hard drive with the diagnostic partition to another
hard drive (the existing hard drive can then be removed without affecting
access to the diagnostic partition on the new hard drive). If EZ-BIOS is
installed in a single-drive system it will overwrite Compaq's code preventing
access to the diagnostic partition.
--------------------------------------------------------------------------
Section 12: Quarterdeck Partition-It and EZ-Drive.
Quarterdeck Partition-It software is not compatible with EZ-Drive,
and will not run if EZ-Drive is present.
--------------------------------------------------------------------------
Section 13: Quarterdeck QEMM 8 and EZ-Drive.
The Quickboot feature in Quarterdeck QEMM 8 software is not compatible
with EZ-Drive. It can create a memory conflict with EZ-Drive and
overwrites the EZ-BIOS code in the boot sector in some systems. To avoid
this, disable the Quickboot feature. (Please refer to the QEMM 8 manual
for more information.)
--------------------------------------------------------------------------
Section 14: Symantec Norton Disklock and EZ-Drive.
EZ-Drive does not recognize partitions on hard drives that have been
locked with Symantec Norton Disklock software. To copy such a partition
with EZ-Drive, first uninstall Norton Disklock. (Please refer to the
Norton Disklock manual for more information.)
--------------------------------------------------------------------------
Section 15: Symantec Norton Utilities and EZ-Drive.
If EZ-BIOS is installed on your hard drive(s), you may not be able to run
certain features of Symantec Norton Utilities, specifically Norton Disk Doctor
and Norton Speed Disk.
--------------------------------------------------------------------------
Section 16: Symantec Norton Your Eyes Only and EZ-Drive.
EZ-Drive does not recognize partitions on hard drives that have been
locked with Symantec Norton Your Eyes Only security software. To copy such
a partition with EZ-Drive, disable the Bootlock option. (Please refer to
the Norton Your Eyes Only manual for more information.)
--------------------------------------------------------------------------
Section 17: Touchstone Software PC-cillin 95 and EZ-Drive.
If EZ-BIOS is installed on your hard drive, PC-cillin detects the EZ-BIOS
code in the boot sector of the drive as a GENERIC virus. If you cleaned
the boot sector of the drive using PC-cillin 95, you can restore the
EZ-BIOS code by using the "Back Up/Restore Track 0" feature in EZ-Drive.
(Please refer to the Installation Guide included with your WD Caviar
hard drive for more information.)
--------------------------------------------------------------------------
Section 18: V Communications System Commander and EZ-Drive.
The current version of System Commander (version 4.0) is not compatible with
EZ-Drive and will overwrite EZ-BIOS if installed. V Communications is
working on a fix for this which should be available in the next System Commander
update.
--------------------------------------------------------------------------
Section 19: Using Windows 32-bit Disk Access with Enhanced IDE hard drives.
If using Windows v3.1 or Windows for Workgroups 3.11, you cannot use the
built-in 32-bit Disk Access driver named *WDCTRL because this driver was
written prior to the introduction of Enhanced IDE drives and it therefore
does not recognize drives with more than 1,024 cylinders (540 MB). A
replacement driver, MH32BIT.386, is included on this diskette to provide
32-bit Disk Access on WD Caviar Enhanced IDE hard drives.
However, some third-party software can interfere with 32-bit Disk Access.
Below is a partial list of software that has been identified as having an
adverse impact on 32-bit Disk Access drivers. There may be other software
not listed that might also prevent MH32BIT.386 from loading.
The following lists some common reasons why MH32BIT.386 may not load,
or may lock up the system in Windows 3.1 and Windows for Workgroups 3.11.
1. HIGHSCAN is present on the emm386.exe command line.
Remove the HIGHSCAN option.
2. There is another Virtual Device Driver (VxD) loaded in SYSTEM.INI, or
a DOS device driver loaded in CONFIG.SYS, that is also talking
directly to the hard disk drive. This includes but is not limited to
the following:
* VL-bus IDE controllers with drivers.
* PCI-bus IDE controllers with drivers.
such as DTC2130.SYS and DOSEIDE.SYS for Gateway 2000
PCI Bus Computers.
* SYMEVNT.386 from Symantec Norton Desktop and
the Norton Utilities version 8.0.
For MH32BIT.386 to work, you must remove the other drivers from
the SYSTEM.INI and/or CONFIG.SYS files.
3. DOS Undelete is in use (it uses Int 26h).
Do not use UNDELETE.
4. "NoEMMDriver=ON " in the SYSTEM.INI file causes 32BDA driver to
lockup and prevents 32-bit File Access from working in Windows for
Workgroups 3.11.
You may have other software that *requires* this entry. However,
you must check the documentation for your other software to
determine what impact removing this line will have on your system.
MH32BIT.386 does not work with ATAPI (IDE) CD-ROM's attached on the
primary IDE port due to conflicts between MH32BIT.386 and the ATAPI
CD-ROM device driver which are both trying to access the primary port.
For 32 bit Disk Access under Windows 3.1x to work, place the ATAPI
CD-ROM on the secondary IDE port.
If converting Disk Manager partitions to EZ-Drive partitions and
you are using WDCDRV.386 to obtain 32 bit Disk Access under
Windows 3.1x, you must also replace WDCDRV.386 with MH32BIT.386.
The WDCDRV.386, supplied with Disk Manager 6.03 is not compatible
with EZ-Drive. You can automatically replace WDCDRV.386 with
MH32BIT.386 by running Setup.exe from the EZ-Drive disk. You can only
run Setup.exe from within Windows 3.1x.
MH32BIT.386 is not necessary under Windows 95 and should not be run.
Windows 95 already includes built-in support for all the
functionality of MH32BIT.386.
-----------------------------------------------------------------------
Section 20: Using Windows For Work Groups 32-File Access.
Windows 32-bit File Access will not load if a file is open when you
start Windows for Workgroups. Some TSR programs maintain an open file
for Print caching (the program PrintCache does this) and virus checking.
Windows 32-bit File Access will not load if you use disk compression.
32-bit File Access works with Stacker 4.0 and Doublespace 6.2 by
replacing the following line in the [386Enh] section of SYSTEM.INI.
device=*BLOCKDEV
with the following two lines
device=ios.386
device=VxDLdr.386
In addition, the file RMM.D32, the Real Mode Memory Mapper, must exist
in the \WINDOWS\SYSTEM subdirectory. The line
device=C:\WINDOWS\IFSHLP.SYS
must exist in the CONFIG.SYS file and the file IFSHLP.SYS must exist
in the Windows subdirectory.
The line
NoEMMDriver=ON
must NOT appear in the [386Enh] section of the SYSTEM.INI file as it
prevents RMM.D32 from loading, which prevents 32-bit File Access from
loading.
-----------------------------------------------------------------------
End of File Readme.txt
Rev. 1.01 09/24/98 -- Cosmetic Changes in vocabulary, support 9.09W.
Rev. 1.00 04/22/98 -- Initial Release for 9.06W
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.