================================================================================
Windows FAQ Sheet 
(Covers Windows 3.1x)
Western Digital Technical Support (http://www.wdc.com/support)
This document was last modified on Saturday, 01-Mar-97 14:06:56 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: Windows Setup tells me to run ScanDisk in MS-DOS, but ScanDisk does not find 
any 
errors. Can I run Setup without running ScanDisk? 
4: What are some of Wdcdrv.386 (Western Digital Fastdisk driver) error messages? 
5: I have installed the WDCDRV.386  driver for 32 bit disk access, but how do I 
remove 
the sign on  message regarding this driver when Windows starts?
6: What is the difference between the WDCTRL and the WDCDRV.386 drivers.

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

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 from Western Digital Online Services: 

Web server [http://www.wdc.com/] 
FTP site [ftp.wdc.com] 
Western Digital's forum on America On-line, Keyword: Western Digital or 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: 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. 

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

4: 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 32-bit 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 Vxd 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 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 hard disk 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 hard disk 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 Parameter 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 Parameter 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 

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

5: I have installed the WDCDRV.386  driver for 32 bit disk access, but how do I 
remove the sign on message regarding this driver when Windows starts?

Edit your System.ini file. Go down to the bottom of the [386Enh] section and add 
in a new section called [WDCDRV]. Then add a line just below the new section that 
reads NoSignOnMessage=True. For example the section should read as follows:

[WDCDRV]
NoSignOnMessage=True

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

6: What is the difference between the WDCTRL and the 
WDCDRV.386 drivers.

The WDCTRL driver is a 32 bit disk access driver that was created by Microsoft to 
work with hard drives that were 528 Mb and lower in capacity. The WDCDRV.386 driver 
is Western Digitals version of a 32 bit disk access drive to work with hard drive 
larger than 528 Mb.

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