WINDOWS v3.x
32 Bit Hard Disk Access (32bhda)

Finally !!

(12-01-02) Solved the problem of using a hard disk larger than 540 meg with Windows v3.1 and 32bda.  I had been using 32 bit access of my hard drive until not long ago when I upgraded to an 850 meg Quantum.  The 32 bit refused to function after that.

I have re-gained 32 bit access using a "FastDisk" driver from OnTrack for my Windows 3.1/3.11 OS and I'm loving it!

32bda is limited to hard drives with 1024 cylinders or less (540MB or less).  After installing a larger than 540 MB hard drive, the 32bda doesn't work any more.  When you attempt to start Windows you get the message :

"WDCTL Error WD4 : The Microsoft Windows 32-bit disk driver (WDCTL) validation failed at phase 08, 10. Press any key to continue without using 32-bit disk driver."

Click on >Control Panel>386 Enh>Virtual Memory>

If   32bda  is ON it says - "Type : ... (uses 32-Bit-Access)"

If  32bda is OFF it says - "Type : ... (uses BIOS)"

When using the BIOS Windows has to switch to real mode if it wants to access the hard drive which also takes time slowing accesses even more.

If you are in >Control Panel>386enh>Virtual Memory>, choose "Change" and see a checked "32-Bit Access" box that does not automatically mean that the 32bda is in fact being used.

The Solution

Microsoft doesn't have a driver to solve the problem.  MS instead tells you in its knowledge base articles about the 32bda problem (collected at EmpowermentZone) then tells you to locate a driver from your hard drive manufacturer.

Mfr FastDisk Drivers

SEAGATE (seg32176.exe) Seagate Techsupport FTP

TOSHIBA (eide32.exe) Toshiba FTP

If your drive is not listed there are two ways around that problem.  One solution would be to use the search terms "fastdisk driver" and the name of your hard drive mfr using Google.  There may be one available.  These drivers have not been required since W95 therefore if Google finds a webpage it should be for W31.

Installing FastDisk Drivers

The hard drive mfr drivers normally auto-install the required files for you in the c:\windows\system directory and Windows loads them via the [386Enh] section in SYSTEM.INI.

They replace the windows drivers.

For the seagate driver it would be :

; device=*wdctrl
; device=wdcdrv.386
device=*int13
device=seg32bit.386
32BitDiskAccess=on

Tip : You may want to verify that the old drivers are really REM'd out with "REM" or " ; " in the SYSTEM.INI file.  If not, the error message "there are two devices for int13..." will display.

If the microsoft driver int13.386 (called with device=*int13 or device=int13.386) isn't included in the driver package and you get an error message, you should be able to use notepad to replace that line in the SYSTEM.INI file.

OnTrack Install

Use one of the mfr's FastDisk drivers mentioned above or get the self-extracting Ontrack Disk Manager 398k (or the Zipfile version 383k) (enter "dm714.exe -d" at the command line to allow it to create it's subdirectories) and run the "Advanced hard drive Installation" option then choose "Install Ontracks 32-Bit disk access".  The OnTrack Disk Manager can do nasty things to your existing drive if you aren't careful (read the README).  I recommend getting just the driver auto-install ontrk386.exe and using it.

The Ontrack driver ontrackw.386 is copied to your windows\system directory. Windows loads the driver from the [386Enh] section in SYSTEM.INI :

device=*int13
device=ontrackw.386
; device=*wdctrl
;(Ontrack Fastdisk Replacement) device=wdcdrv.386
32BitDiskAccess=on

Potential OnTrack Problem

Another user has reported that Windows 3.1 will run fine with 32bda but when a DOSbox is requested (window or full-screen) the computer will reboot.  When the "Use 32bda" box in >Control Panel>386enh>Virtual Memory> "Change" is unchecked and Windows is restarted the DOSbox executes without a reboot of the machine.