====================================================================
Western Digital Technical Support
Windows FAQ Sheet 
(Covers Windows 3.1x, Windows 95 and Windows NT)
This document was last modified on Wednesday, 20-Nov-96 09:01:46 PDT
====================================================================


 1: My drive is no longer bootable after restoring my data using DOS Backup. 
What Can I do? 
 2: ScanDisk reports it can not repair bad allocated clusters. How can I repair 
these clusters? 
 3: Can I install Windows 95 on my Caviar drive that dual-boots Windows NT 
and MS-DOS? 
 4: Can I install Windows 95 and still boot MS-DOS and Windows 3.1? 
 5: Can I install Windows 95 on a computer running IBM OS/2? 
 6: Can I remove Windows 95? 
 7: After installing Windows 95, I can no longer boot from a different hard drive. 
What has changed? 
 8: Can I install Windows 95 over Windows NT? 
 9: After I install Windows 95 on a computer with Windows NT, how do I start 
Windows 95? 
 10: During the first boot of Windows 95, I get "Invalid System Disk" error 
message. What does this mean? 
 11: Can I dual-boot Windows 95 and OS/2 Warp? 
 12: Windows Setup tells me to run ScanDisk in MS-DOS, but ScanDisk does 
not find any errors. Can I run Setup without running ScanDisk? 
 13: Will Windows 95 Setup work if I compressed my hard disk with disk 
compression utilities? 
 14: Will Windows 95 install correctly on a drive with Ontrack Disk Manager? 
 15: I have "Brand X" system and my hard disk is using MS-DOS compatibility 
mode. What is the problem? 
 16: Disabling Protected-Mode disk driver(s), hides the partition table when I run 
Fdisk? What can I do? 
 17: What are some possible scenarios under which Windows 95 might run in 
MS-DOS compatibility mode on my EIDE hard drive and how can I fix the 
problem? 
 18: Why don't I get 32-bit disk access on my 1GB hard drive running Windows 
95? 
 19: How do I install Windows 95 with Disk Manager already present on my hard 
drive? 
 20: How do I install my new drive in a Windows 95 system?
 21: Windows 95 reports that I am operating in DOS Compatibility Mode. What 
is the problem and how can I fix it? 
 22: I use Western Digital's FastDisk driver WDCDRV.386 for 32-Bit Disk 
Access in Windows 3.1x. Do I need to use this driver with Windows 95? 
 23: Does ScanDisk in Windows 95 support drives with cluster sizes larger than 
8K? 
 24: Can I use third party software utility packages, like Norton Utilities with my 
Western Digital hard drives under Windows 95? 
 25: Can I use my pre-Windows 95 memory manager with Windows 95 to 
manipulate where Disk Manager driver loads? 
 26: Do I need to use Disk Manager or EZ-Drive to support large Enhanced IDE 
hard drives under Windows 95? 
 27: What version(s) of Disk Manager will function properly with Windows 95?   
 28: I installed Microhouse Fastdisk driver, Mh32bit.386 and now Windows 95 
reports DOS Compatibility mode. What can I do to fix this? 
 29: What are some of Wdcdrv.386 (Western Digital Fastdisk driver) error 
messages? 
 30: My Caviar drive automatically powers down after a few minutes. What can I 
do to stop this? 
 31: My DriveSpace 3-compressed slave drive does not boot after I made it my 
master drive. I get "invalid drive" error message. What is wrong? 
 32: I am adding a new Caviar drive but DriveSpace 3 is unable to decompress my 
existing Caviar drive. What should I do?

====================================================================


1: My drive is no longer bootable after restoring my data using DOS Backup. 
What Can I do? 

This problem occurs when Backup is not configured to restore the system files. To 
correct this problem, restore your root directory with the System Files, Hidden 
Files and Read Only Files checked or start your computer with the MS-DOS 6.x 
Upgrade Setup Disk 1 or Windows 95 Startup disk (Emergency Boot Disk) in 
drive A, and use the SYS command to make drive C bootable. For example, type 
the following command at the A: prompt: 

sys c: 

If you have used data compression on drive C, you need to use the SYS command 
to make the host drive for drive C bootable. 


2: ScanDisk reports it can not repair bad clusters. How can I repair these clusters?

To resolve this situation, follow these steps: 

 Download Allstar Utilities (Allstar.exe) from Western Digital Online Services: 

 Worldwide Web, www.wdc.com
 FTP site, ftp.wdc.com
 Western Digital's forum on America On-line, Keyword: WDC
 BBS, (714) 753-1234

 Boot from a clean boot diskette and run Wdclear.exe. Select the Clean Drive 
option. This utility will clear all data fields on the media. 

NOTE: This procedure is data destructive. Be sure to have a full back up of your 
system before commencing. 

 Backup your data and run Wdatide.exe from the floppy drive to perform 
Comprehensive Surface Scan. 

NOTE: This procedure is data destructive. Be sure to have a full back up of your 
system before commencing. 

 You can now partition and format the drive for data storage. 


3: Can I install Windows 95 on my Caviar drive that dual-boots Windows NT and 
MS-DOS? 

Yes. To install Windows 95 on a computer that dual-boots Windows NT and MS-
DOS, start the computer in MS-DOS mode and run Setup either in Windows 3.1 
or at an MS-DOS prompt. You cannot install Windows 95 in a directory with a 
shared Windows 3.1 and Windows NT configuration. In this situation, you must 
install Windows 95 in a different directory. 

If your computer boots Windows NT, you must configure the computer to dual-
boot MS-DOS and Windows NT and then follow the instructions in the paragraph 
above. If you start the computer from an MS-DOS disk and then run Setup, you 
will no longer be able to boot Windows NT. However, you can restore Windows 
NT by starting the computer from the Windows NT Boot/Repair disk and then 
selecting the Repair option. 


4: Can I install Windows 95 and still boot MS-DOS and Windows 3.1?

Windows 95 supports booting the earlier version of the operating system if you are 
using MS-DOS version 5.0 or later or IBM PC-DOS version 5.0 or later. You 
cannot boot an earlier version of DR DOS. When you install Windows 95 in a 
new directory, Setup automatically makes the required adjustments so the 
computer can dual-boot Windows 95 and MS-DOS. To boot MS-DOS on a 
Windows 95 computer with dual-boot enabled, press F4 or F8 when you see the 
"Starting Windows 95" message. 

If you install Windows 95 in a new directory, you must re-install all your 
Windows-based programs for them to run properly in Windows 95. However, if 
you upgrade your earlier version of Windows to Windows 95, you do not need to 
re-install your Windows-based programs because the registry information is 
transferred to Windows 95. 


5: Can I install Windows 95 on a computer running IBM OS/2?

Setup does not run in OS/2. However, you can install Windows 95 on a computer 
running OS/2 if you boot to MS-DOS and run Setup from the MS-DOS prompt. 
You cannot install Windows 95 in the same directory as OS/2. Because Windows 
95 cannot access HPFS partitions, a FAT partition must be available to install 
Windows 95. You can also run Windows 95 Setup if you boot from a MS-DOS 
diskette. 

Windows 95 Setup disables Boot Manager to ensure that it can restart the 
computer and complete the installation. You can re-activate Boot Manager by 
running the Fdisk tool that is shipped with Windows 95. 

If you do not use OS/2 Boot Manager, you must configure your computer to use 
Boot Manager and then follow the steps above. 


6: Can I remove Windows 95? 

Yes. During Setup, you are prompted whether you want to save your computer's 
system files. If you choose to save the system files, Setup saves them in a hidden, 
compressed file on the hard disk. You will not be asked to save the system files if 
a)you are installing Windows 95 in an empty directory, b)you are not running MS-
DOS version 5.0 or later or c)you are re-installing Windows 95 over itself. 

To remove Windows 95, follow these steps: 

Click the Start button, point to Settings, and then click Control Panel. Double-
click the Add/Remove Programs icon. On the Install/Uninstall tab, click Windows 
95, and then click Remove. 

You can also remove Windows 95 by starting your computer with the Windows 95 
Startup Disk and then typing uninstall at the command prompt. 


7: After installing Windows 95, I can no longer boot from a different hard drive. 
What has changed?

Windows 95 Setup program checks all the hard disks in your computer to make 
sure that only one contains 80h in the DriveNumber field of the boot sector. Setup 
makes this change so that Windows 95 can find the boot disk when you start the 
computer and recognize the other drives. 

You can use either of the following methods to correct the DriveNumber field: 

- Use the Fdisk program that is included with Windows 95 to set the primary 
active partition.
- Use a disk editor to change a disk's DriveNumber field so that you can boot from 
that hard disk. 


8: Can I install Windows 95 over Windows NT?

You cannot install Windows 95 in the same directory as Windows NT. To install 
Windows 95, boot to MS-DOS, then run Windows 95 Setup. After you install 
Windows 95 to a different directory, you can boot either Windows 95 or Windows 
NT. 


9: After I install Windows 95 on a computer with Windows NT, how do I start 
Windows 95?

When you start your computer, you are given a choice to run Windows NT or MS-
DOS. Choose MS-DOS to load Windows 95. 


10: During the first boot of Windows 95, I get "Invalid System Disk" error 
message. What does this mean?

If during the first reboot in Windows 95 Setup or when you boot from the start-up 
disk, you receive the following error message: 

Invalid system disk
Replace the disk, and then press any key


your system may be: 

- infected with a boot-sector virus
- running virus-protection software
- using hard disk management software (such as Disk Manager, EZ-Drive, or 
DrivePro) for Logical Block Addressing (LBA) support. These tools provide 
support for hard disks with more than 1024 cylinders. 

To correct the problem if the system is Infected with a Virus, use an anti-virus 
program to detect and remove the virus, and then re-install Windows 95 system 
files. 

If the systems is running Virus-Protection Software, Boot the system using the 
startup disk created during Windows 95 Setup. Use the SYS command from the 
startup disk to restore the system files to the hard disk. 

Windows 95 may not detect disk management software and may overwrite the 
master boot record (MBR). Refer to the documentation for the disk management 
software you are using for information about restoring the MBR. 

To re-install the Windows 95 system files, follow these steps: 

1. Boot the system using the Windows 95 Emergency Boot Disk.
2. At the MS-DOS command prompt, type the following lines:

c:
cd\windows\command
attrib c:\msdos.sys -h -s -r
ren c:\msdos.sys c:\msdos.xxx
a:
sys c:
del c:\msdos.sys
ren c:\msdos.xxx c:\msdos.sys
attrib c:\msdos.sys +r +s +h

3. Remove the Emergency Boot Disk and reboot the system. 


11: Can I dual-boot Windows 95 and OS/2 Warp?

To dual boot between Windows 95 and IBM OS/2 you must reset or re-install the 
OS/2 Boot Manager. Please consult your OS/2 documentation for information 
about enabling Boot Manager. 


12: Windows 95 Setup tells me to run ScanDisk in MS-DOS, but ScanDisk does 
not find any errors. Can I run Windows 95 Setup without running ScanDisk?

To run Setup without running ScanDisk, run Setup with the /IS switch. However, 
we recommend that you make certain your Caviar hard disk is free of errors before 
you use this switch. 


13: Will Windows 95 Setup work if I compressed my hard disk with disk 
compression utilities?

Windows 95 is compatible with Stacker version 2.0 and higher, and with all 
versions of SuperStor. Before you start Setup, make sure there is enough free hard 
disk space on the host drive. For further details, please consult your compression 
utility software documentation. 


14: Will Windows 95 install correctly on a drive partitioned with Ontrack Disk 
Manager?

Windows 95 is compatible with Disk Manager versions 6.03 and later, however, if 
you are currently using version 6.03 thru 6.03c of the Disk Manager, download 
Dmpatch.exe to update the Disk Manager drivers. If you use version 6.03d of Disk 
Manager, Windows 95 automatically uses its protected-mode driver. 


15: I have "Brand X" system and my hard disk is using MS-DOS compatibility 
mode. What is the problem?

Windows 95 may use DOS Compatibility Mode on large EIDE hard disks (hard 
disks with more than 1024 cylinders) in some computers. This situation may occur 
because of invalid drive geometry translation in the system ROM BIOS that 
prevents the protected-mode IDE device driver from being loaded. Please contact 
your system manufacturer for information about obtaining an updated BIOS. 


16: Disabling Protected-Mode disk driver(s), hides the partition table when I run 
Fdisk? What can I do?

If this is happens in your system, do not use the "Disable all 32-bit protected-mode 
disk drivers" option, or upgrade your computer's BIOS to a later version. 


17: What are some possible scenarios under which Windows 95 might run in MS-
DOS compatibility mode on my Enhanced IDE hard drive and how can I fix the 
problem?

The IOS.INI file, located in the Windows directory, contains a list of device 
drivers that Windows 95 can safely remove from the Config.sys file and replace 
with its protected mode IDE device driver(ESDI506.PDR.) If the real mode device 
driver name is not present in the IOS.INI file, Windows 95 will use the real mode 
device driver in the Config.sys file and the devices attached to the controller will 
operate in MS-DOS Compatibility Mode. 

If you add the name of the real mode device driver for the Enhanced IDE controller 
to the Ios.INI file to get Window 95 to operate the device in protected mode, you 
may risk data loss, data corruption and performance degradation. 

The Windows 95 protected mode IDE driver needs to use the Int13 hardware 
interface to communicate with the IDE controller. If another device driver is 
intercepting these calls, the Windows 95 protected mode driver will not be able to 
communicate directly with the device. As a result all devices attached to the 
controller will use MS-DOS Compatibility Mode. 

To check if there is a device driver or if any other program is intercepting Int13 
calls: 

 Download Getcmos.exe to determine Int13h, Int41h and Int46h values. Unpack 
and run this program at the command prompt to determine which driver is the I 
nt13 hooker. 
 Open the Ios.log file located in the Windows directory with any text editor. You 
will only find Ios.log only if there is a device using MS-DOS Compatibility Mode. 
 Search for the line MBRINT13 to determine which device driver is intercepting 
calls to Int13: 
 Boot the system and press the F8 function key to display the boot menu Choose 
step-by-step Confirmation to selectively load drivers. This will help you to 
determine which driver may be responsible for the problem. 


If you are not able to locate the driver in question, it is possible that a virus is 
interfering with protected-mode support. If a virus is present on the system, or in 
its Master Boot Record (MBR), Windows 95 will receive incorrect information 
about the EIDE controller and the device(s) connected to it and will fail to load the 
protected mode device driver. 

Run a virus detector to clean the system. If your MBR is not infected by any 
viruses, It is possible that the manufacturer of the EIDE controller has drivers for 
32-bit Disk Access for Windows 3.1x. 

Lastly, your EIDE controller itself may be causing the compatibility issue. It is 
possible by selecting different modes of operation (i.e. Normal, Fast, Turbo, etc.) 
you may be able to correct the problem. Please contact your controller card 
manufacturer for further instructions. 


18: Why don't I get 32-bit disk access on my 1 GB hard drive in Windows 95?

Make sure there is no conflict between the motherboard CMOS setup and the 
controller BIOS settings. (i.e. if both the motherboard and the controller have 
settings for Logical Block Addressing, LBA, make sure only one is in use.) 


19: How do I install Windows 95 with Disk Manager already present on my hard 
drive?

The following information applies only to Disk Manager version 6.03 and later. 
An end-user with a version earlier than 6.03 will not benefit from the following 
information. They will need to upgrade to a version 6.03 or later. 

There are four possible configurations when installing Windows 95 in a system 
using Disk Manager: 

1.A single hard drive using Disk Manager 2.A master drive using Disk Manager in 
a dual drive system 3.A master and slave drive using Disk Manager in a dual drive 
system 4.A slave drive using Disk Manager in a dual drive system. 

The first three configurations, where a master or single boot drive utilize Disk 
Manager, should experience no problems when installing Windows 95 onto the 
drive. The overlay will load, revealing the familiar Western Digital blue banner as 
usual, and Windows 95 will acknowledge the presence of the overlay and 
recognize the drive accordingly. Entering Windows 95 Control Panel and choosing 
Performance under the System option reveals a file system in running 32-Bit 
Protected-mode. 

The last configuration functions properly except for a few exceptions. According 
to Ontrack test results, the Windows 95 file system does not function properly 
under three unique conditions where only the slave drive has been set up using 
Disk Manager: 

1.When a Windows 3.1x virtual driver replacs the Windows 95 Protected-mode 
driverWDCDRV.386 included) 2.When the cylinder count in the CMOS for the 
slave drive is greater than 1024 cylinders. 3.When the CMOS setting for the slave 
drive are set to auto-detect. 

Windows 95 ensures that all essential drivers in the system files, function properly 
even though Windows 95 does not recognize or have an equivalent. Both hard 
drives will now strictly use the BIOS for access with a reduction in system 
performance. 


20: How do I install my new drive in a Windows 95 system?

The standard Fdisk and Format procedure is adequate to configure a drive for use. 
There is no graphical equivalent of Fdisk in Windows 95, therefore DOS is still 
the only interface to manipulate the partitions on the drive. You can run the Fdisk 
command from the Run option under Start on the Taskbar. Create your partition(s) 
then press ESC. Unlike DOS, Windows 95 does not reboot the system at this 
juncture. Exit the DOS window, restart the system. 

Once the system has booted back up, proceed to format the drive. There are a 
number of ways you go about doing this. You can format the hard drive using the 
Format command. Type 

format [drive letter] /[switch] 

at the RUN option under Start. You can also format the drive by double-clicking 
the MY COMPUTER icon, and then click the icon for the disk you want to 
format. Be sure not to double-click the disk icon, because you cannot format a 
disk if it is open in MY COMPUTER or Windows Explorer. On the File menu, 
click Format. 


21: Windows 95 reports that I am operating in DOS compatibility Mode. What is 
the problem and how can I fix it?

DOS Compatibility Mode is invoked by Windows 95 whenever the system loads a 
real mode driver. This would happen when Windows 95 does not have an 
equivalent 32 bit protected mode driver to replace the real mode driver. Click on 
Performance tab under the System icon for details on what devices are affected 
when there is an irreplaceable device driver. Highlight the message in the details 
box and click the Details button for information on that particular issue. The first 
place to check for questionable driver(s) is your CONFIG.SYS and 
AUTOEXEC.BAT files. Once you discover these drivers, contact the 
developer/manufacturer of the driver for updated Windows 95 compliant driver(s). 


22: I use Western Digital's FastDisk driver WDCDRV.386 for 32-Bit Disk Access 
in Windows 3.1x. Do I need to use this driver in Windows 95?

Windows 95 has built in 32 bit protected mode support for your Western Digital 
hard drives and other EIDE peripherals. Hence, you do not need to load 
WDCDRV.386 in Windows 95. If Windows 95 has not removed any reference to 
32-Bit Disk Access or WDCDRV.386 from System.ini file, you should manually 
edit this file and remove any reference to 32-Bit Disk Access or WDCDRV.386. 


23: Does ScanDisk in Windows 95 support drives with cluster sizes larger than 
8K?

Yes, the new Windows 95 version of ScanDisk supports large EIDE drives and 
large partitions with greater than 8KB per cluster size. 


24: Can I use third party software utility packages, like Norton Utilities with my 
Western Digital hard drives under Windows 95?

Absolutely, but you should upgrade to "Made for Windows 95" versions of these 
software packages before running them under Windows 95. Please contact the 
respective manufacturer of your favorite utility software for their Windows 95 
version. However, we recommend Wddiag.exe as it is better prepared to recognize 
and report any issues with your hard drive. 


25: Can I use my pre-Windows 95 memory manager with Windows 95 to 
manipulate where Disk Manager driver loads?

Windows 95 runs in a virtual memory environment and the Disk Manager driver 
will not create any conflicts with this setup. Each DOS sessions is assigned its 
own virtual machine that simulate a conventional real mode memory scheme. The 
amount of memory allocated to a particular application can be modified by the 
user. This allows even your most memory intensive DOS programs to run well 
within Windows 95. For details on how your memory package interacts with the 
Window 95 environment and how to properly configure your system for their use, 
contact the manufacturer of the software. Quarterdeck can be reached at 310) 392-
9701 and Qualitas (386MAX) at 301) 907-6700. 


26: Do I need to use Disk Manager or EZ-Drive to support large Enhanced IDE 
hard drives under Windows 95?

To get the full capacity of your hard drive under Windows 95, you must have 
either hardware support (a translating system BIOS or an Enhanced IDE controller 
card), or software support such as Disk Manager. Windows 95 does support and 
recognize Disk Manager versions 6.03 and greater. The Disk Manager driver, is 
loaded from the Master Boot Record (MBR) when the drive is in the master 
position, or in the Config.sys as a device driver when the drive is in the slave 
position. 


27: What version(s) of Disk Manager function properly with Windows 95?

Disk Manager versions 6.03 or higher will function properly with Windows 95. 
Western Digital recommends downloading Dmpatch.exe from our Online Services 
and updating the Dynamic Drive Overlay to 6.03d. 


28: I installed Microhouse Fastdisk driver, Mh32bit.386 and now Windows 95 
reports DOS Compatibility mode. What can I do to fix this?

Disable the line that loads the Mh32bit.386 device driver in the System.ini file. To 
do so, follow these steps: 

1.Use any text editor (such as Notepad) to open the System.ini file in the 
Windows folder. 2.Locate the line that loads the Mh32bit.386 device driver. 
3.Place a semicolon (;) at the beginning of the line. 4.Save and then close the 
System.ini file. 5.Restart Windows 95. 


29: What are some of Wdcdrv.386 (Western Digital Fastdisk driver) error 
messages?

NOTE to Windows 95 Users 

The following ONLY applies to Windows 3.1x users. Wdcdrv.386, Western 
Digital Fastdisk driver should only be used in Windows 3.1x environment and its 
installation in Windows 95 would most likely lead to some complications, namely 
DOS Compatibility Mode. If you have installed Wdcdrv.386 in Windows 95, edit 
your System.ini file (in \windows directory) and remove any reference to 
Wdcdrv.386. 

1.WDCDRV can not load due to conflict with another virtual device. 2.WDCDRV 
can not load. Unrecognized disk software installed. 3.WDCDRV Validation 
Failed At Phase 01,00. 4.This program tried to access your hard disk in a way that 
is incompatible with the Windows 32bit disk access feature (WDCTRL). This may 
cause your system to become unstable. 5.WDCDRV Validation Failed at Phase 
09,1F. 6.Application Error: Control Caused a Load Segment Failure in module 
CPWIN386.CPL at address 0001:3CCA. 7.WDCDRV Validation Failed at Phase 
0A,1F. 8.No visible error message. Windows For Workgroups locks up after the 
customer exits WFWG and then restarts it. 9.No visible error message. WFWG 
locks up when the customer starts Windows. 10.Fatal Error #2 - Turn Off Your 
Computer Now! 11.WDCDRV Validation Failed at Phase 07,2F. 

1. WDCDRV can not load due to conflict with another virtual device 
Probable Cause: 

1. The line 
device=*int13 
is probably missing from the [386Enh] section of SYSTEM.INI or
2. There is another VxD (Virtual Device Driver) loaded through the [386Enh] 
section of SYSTEM.INI. This is probably the SYMEVNT.386 driver from the 
Norton Desktop for Windows or the Norton Utilities v8.0. This driver must be 
removed for 32bit disk access to load or 
3. The CMD Windows VxD CMD640x.386 or the CMD DOS TSR driver 
CMD640x.SYS is loaded. If using these two drivers. WDCDRV.386 is redundant 
and should not be loaded. This is seen on the Gateway BATIP-3 Anigma 486 PCI 
motherboard. These drivers provide EIDE functionality and 32-bit Disk Access. 

Action: 
1. Insert the line 
device=*int13 
in the [386Enh] section of SYSTEM.INI or 
2. Remove the SYMEVNT.386 driver from SYSTEM.INI file. Or contact 
Symantec for an updated version of this driver or 
3. Try to identify other recently installed VxDs or other device drivers that attempt 
to program the hard disk controller I/O ports directly. Remove them if you want to 
continue using WDCDRV.386. 

2. WDCDRV can not load. Unrecognized disk software installed. 

Probable Cause: 
1. The most probable cause is STEALTH mode in QEMM v7.0x or 
2. This error can also mean that a DOS device driver has hooked the ROM BIOS 
Int 13h incorrectly. WDCDRV checks for correct hooking of the interrupt by 
looking at the address of the interrupt handler. If it is not in conventional memory, 
and WDCDRV is loading , WDCDRV considers the address incorrect. Begin 
removing device drivers that hook Int 13h until you can successfully enable 
FastDisk. These device drivers can be identified by most diagnostic programs. If 
you still have problems, verify that all device drivers that hook Int 13h are up to 
date and follow Microsofts guidelines for hooking disk interrupts. 

Action: 

1. Removing the option ST:M (or ST:F) from the QEMM command line will 
disable STEALTH completely or 
2. Use the command line options XSTI=13 X=ssss-nnnn, where ssss is the 
segment address of the Int 13h handler and nnnn is the offset address. Information 
on obtaining the correct numbers for ssss and nnnn are contained in the file 
XSTI.TEC on the Quarterdeck BBS and on their Compuserve forum or 
3. Download the driver 32BDAFIX.SYS from the Quarterdeck BBS or the WD 
BBS at (714) 753-1234. The file name is 32bda.com or 
4. Run FINDHOOK.COM (available in the Hard Drives Software Library in the 
compressed file FHOOK.COM) to identify the software hooking Int 13h. 
Determine if this software is critical to proper system operation. If it is not, remove 
it. If it is critical, do not use 32bit disk access. 

3. WDCDRV Validation Failed At Phase 01,00 
Probable Cause: 
1. The values returned by Int 13h Function 8h (Read Drive Parameters) do not 
match the values stored in the Drive Parameter Table or Enhanced Drive Parameter 
Table pointed to by Int 41h (drive C:) or Int 46h (Drive D:). This can happen if the 
STEALTH feature of QEMM v6.0 and above relocates the DPT or EDPT to 
protected mode memory. Since the FastDisk device is in its initialization phase 
and running in real mode, it cannot access the DPT or EDPT and cannot verify the 
the values contained therein match the BIOS Int 13h Function 8h values or 
2. The BIOS is operating the drive in LBA (Logical Block Addressing) mode but 
has not built a valid Enhanced Drive Parameter Table. Either the signature is 
invalid (does not conform to the Axh pattern) or the checksum is invalid. 

Action: 
1. Removing the command line option ST:M (or ST:F) from the QEMM command 
line will disable STEALTH completely or 
2. Customer can also use the command line options XSTI=13 x=ssss-nnnn, where 
ssss is the segment address of the Int 13h handler and nnnn is the offset address. 
Information on the correct numbers for ssss and nnnn are found in the file 
XSTI.TEC on the Quarterdeck BBS or their Compuserve forum. These options 
prevent Stealth from relocating the Drive Parameter Tables and the Int 13h handler 
or 
3. Download the driver 32BDAFIX.SYS from the Quarterdeck BBS or the 
Software Library page in the compressed file 32BDA.COM . The file name is 
32BDA.ZIP. This driver from Quarterdeck allows WDCDRV.386 to work even 
with Stealth loaded or 
4. Run WDTBLCHK.EXE to determine if the BIOS is operating the drive in LBA 
mode and whether it has created a valid EDPT. If there is no valid Enhanced Drive 
Parameter Table, WDCDRV cannot determine the translation mode and therefore 
cannot load. A BIOS upgrade is necessary in this case. 

4. This program tried to access your hard disk in a way that is incompatible with 
the Windows 32bit disk access feature (WDCTRL). This may cause your system to 
become unstable. 

Probable Cause: 
A device driver, TSR, or application tried to access the harddisk controller ports 
directly while WDCDRV was loaded. WDCDRV returns an error code without 
performing the operation. This is probably a Virus Checker writing directly to the 
drive. This also occurs with the DOS UNDELETE program when run from a DOS 
window. 

Action: 
Find the application or device driver that attempted to program the harddisk 
controller ports directly. If you discover that the offending application or device is 
essential to the operation of your system, your only alternative is to disable 
FastDisk. Disable the 32bit disk access checkbox in the Change Virtual Memory 
Settings dialog in the 386 Enhanced section of the Control Panel. 

Do not run the DOS Undelete program from within Windows. Exit Windows and 
run the program from DOS. 

5. WDCDRV Validation Failed at Phase 09,1F 

Probable Cause: 
1. You attempted to use WDCDRV.386 in a system with no Western Digital high 
capacity drive installed. WDCDRV.386 will only load if there is at least one 
Western Digital drive in the system or 
2. The drive is connected to a caching controller. 
Action: 
1. Remove the line 
device=WDCDRV.386 
from the [368Enh] section of SYSTEM.INI or 
2. Obtain a 32-bit Disk Access driver from the manufacturer of the caching 
controller. 

6. Application Error: Control Caused a Load Segment Failure in module 
CPWIN386.CPL at address 0001:3CCA 
Probable Cause: 
WDCDRV.386 has a Block Count set which is greater than 0 and Windows For 
Workgroups is using 32Bit FIle Access which uses Scatter/Gather DMA. This 
only occurs under the following conditions: 
Windows For Workgroups is in use
32-bit File Access is enabled
WDCDRV.386 is loaded
ROCKET.BIN is loaded in config.sys 

Action: 
1. Run the CAVIAR.EXE program and set the WDCDRV.386 Block Count to 
zero (0). If the customer has the older version of CAVIAR.EXE have them insert 
the following line in the [WDCDRV] section of SYSTEM.INI: 
BLOCKINGFACTOR=0 
or 
2. Place the command line option /W=1 (or /W=1,1 for a two drive system) on the 
device=rocket.bin command line. This disables block writes in rocket. 

7. WDCDRV Validation Failed at Phase 0A,1F 
Probable Cause: 
The BIOS has built an invalid Enhanced Drive Parmeter Table. 
Action: 
1. Run WDTBLCHK to verify that there is an invalid EDPT or no Enhanced Drive 
Parameter Table. 
2. A BIOS upgrade is necessary. 

8. Windows For Workgroups locks up after the customer exits WFWG and then 
restarts it. 
Probable Cause: 
Customer is running WFWG on top of Novell Netware 3.12 and using the 
Microsoft supplied ODI support layer VxD MSODISUP.386 (in the [386Enh] 
section of SYSTEM.INI). WDCDRV.386 v2.5 is incompatible with the Microsoft 
supplied ODI support driver MSODISUP.386. 
Action: 
1. Disable WDCDRV.386. This allows network drivers to load. 
2. Start WFWG with the /N command line option. This prevents the network 
drivers from loading and allows 32-bit Disk Access but no network access. 

9. WFWG locks up when the customer starts WFWG. 
Probable Cause: 
Customer is running WDCDRV with DMA transfers set to "Auto-Detect" and the 
motherboard PCI-EIDE chipset does not properly implement DMA transfers. 
Action: 
1. Start Windows with the command line option /D:F to prevent WDCDRV.386 
from loading. 
2. Run CAVIAR.EXE and disable DMA transfers and Scatter/Gather DMA. 

10. Fatal Error #2 - Turn Off Your Computer Now! 
Probable Cause: 
Machine has a Phoenix BIOS v4.03 dated prior to July 1994 (7/94). This BIOS 
does not build a valid Enhanced Drive Parmeter Table yet it performs LBA 
translations. 
Action: 
1. Start Windows with the command line option /D:F to prevent WDCDRV.386 
from loading. 
2. Disable WDCDRV.386. 
3. Obtain a BIOS upgrade from the motherboard/system OEM. One is available 
from Phoenix, but only to the OEM. 

11. WDCDRV Validation Failed at Phase 07,2F. 
Probable Cause: 
1. Disk Manager is being used in a system which auto-detects the drive's correct 
CHS geometry and which supports the drive at full capacity. Since the BIOS in 
this system is performing translation, the effect of loading Disk Manager is to have 
double translation or 
2. The drive is attached to a caching controller. Caching controllers return their 
own ID in response to an Identify Drive Command from WDCDRV.386. Since 
WDCDRV.386 is looking for a Western Digital drive ID (e.g., AC31000-00H), it 
assumes that the drive is not a WD drive and refuses to load. 
Action: 
1. Remove Disk Manager. It is not needed or 
2. Disconnect the drive from the caching controller or do not use WDCDRV.386 

30: My Caviar drive automatically powers down after a few minutes. What can I do 
to stop this?

Most likely the "Power Management" option in the system ROM BIOS is enabled. 
Access your CMOS and look for "Power Management" options and disable them. 
If even after disabling these options in the BIOS, your drive spins down, please 
contact the motherboard manufacturer for further instructions. Your Caviar drive 
*ONLY* spins down when a command has been issued by the BIOS. Caviar 
drives do no spin down until such a command has been issued by the system. 


31: My DriveSpace 3-compressed slave drive does not boot after I made it my 
master drive. I get "invalid drive" error message. What is wrong?

Use the Sys command to transfer the system files to the "host" drive (the non-
compressed drive, C drive *is* compressed/"invalid"). 


32: I am adding a new Caviar drive but DriveSpace 3 is unable to decompress my 
existing Caviar drive. What should I do?

There is one small but vital INI file which needs to be corrected to reflect the new 
configuration. It is a hidden, read-only file called DBLSPACE.INI. It is located in 
the root directory of the host drive. Most likely, DBLSPACE.INI is still referring 
to the host drive as H: (or another label which is no longer valid since a new drive 
has been added to the system). As a result, DriveSpace 3 looks for the host drive 
that is no longer there. Simply change the read-only and hidden attributes on 
DBLSPACE.INI, replace any reference to the old host drive with the new drive 
letter designation, save the file, restore the R and H attributes, and restart 
DriveSpace 3.
