WIN 3.1 (32-disk access ERROR)<<-->>PLEASE HELP ME PLEASE !!
antirush
has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
and Get the following error message when I try to run windows with
32 bit disk access enabled
(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
""(Press Any Key To start Windows Without 32-bit Disk access
Enabled..."
WHAT CAUSES THIS DAMN ERROR?
HOW CAN I FIX MY PROBLEM??
I am about to pull my freaking hair out people!!!!!
EMAIL
ANTI...@CRIS.COM
Please HELP me, sorry for those caps on, I'm desperate people......
--------------------------------------------------
-------------------------------------------------
http://www.cris.com/~ANTIRUSH
It sucks pretty bad, but what web page doesn't??
--------------------------------------------------
---------------------------------------------------
Robert Lavin
>From: anti...@cris.com (antirush)
>Subject: WIN 3.1 (32-disk access ERROR)<<-->>PLEASE HELP ME PLEASE !!
>Date: Sat, 30 Dec 1995 13:01:39 GMT
a. Do you have a CD-ROM on the same IDE Controller ?
b. Does your controller support 32 bit access ? Not all are WD compatible.
c. Do you realize that 32-bit DISK access does very little for you ?
32 bit FILE access in WFW 3.11 is a performance booster, 32 bit DISK
is minimal.
Feel free to mail me with questions.
Regards,
Robert
Keith Keefer
says...
>
>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
which
>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>and Get the following error message when I try to run windows with
>32 bit disk access enabled
>
>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>""(Press Any Key To start Windows Without 32-bit Disk access
>Enabled..."
>
>WHAT CAUSES THIS DAMN ERROR?
>HOW CAN I FIX MY PROBLEM??
>I am about to pull my freaking hair out people!!!!!
>ANTI...@CRIS.COM
>Please HELP me, sorry for those caps on, I'm desperate people......
>
>--------------------------------------------------
>-------------------------------------------------
>http://www.cris.com/~ANTIRUSH
>It sucks pretty bad, but what web page doesn't??
>--------------------------------------------------
>---------------------------------------------------
re-install it. It is definately a software problem.
Keith Keefer
Martyn Dean
try and fix this problem.
Including re installing windows, re-formatting the disc, running
norton disk doctor which found many problems with the disc.
In the end I put a hard disk in and this fixed the problem.
You could try a disc doctor utility to check the hard disc.
No doubt this is not what you wanted to hear but it worked for me.
Regards
Martyn Dean EMail mar...@mhdean.demon.co.uk
|---------------------------------------------------------------------------
Darren / Rebecca Mayes
>In article <30e536d...@spectator.cris.com>, anti...@cris.com
>says...
>>
>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
>which
>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>and Get the following error message when I try to run windows with
>>32 bit disk access enabled
>>
>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>""(Press Any Key To start Windows Without 32-bit Disk access
>>Enabled..."
>>
I am assuming thath you DO have a western digital hard drive...right?
lu...@serv.net
the "stoned" virus,,, part of the resident of michalengelo.. might
scan for a virus.. screwed up the fat table.. just a thought... good
luck
On 2 Jan 1996 21:04:52 GMT, kd_k...@pnl.gov (Keith Keefer) wrote:
>In article <30e536d...@spectator.cris.com>, anti...@cris.com
>says...
>>
>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
>which
>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>and Get the following error message when I try to run windows with
>>32 bit disk access enabled
>>
>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>""(Press Any Key To start Windows Without 32-bit Disk access
>>Enabled..."
>>
Mark Turnbull
>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>and Get the following error message when I try to run windows with
>32 bit disk access enabled
>
>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>""(Press Any Key To start Windows Without 32-bit Disk access
>Enabled..."
>
>WHAT CAUSES THIS DAMN ERROR?
>HOW CAN I FIX MY PROBLEM??
>I am about to pull my freaking hair out people!!!!!
I had the same problem with my NEC machine. It turns out the driver
(I think) just didn't support 32-bit access, so I had to turn it off.
Mark Turnbull
Jerry Wise
>I had the same problem with my NEC machine. It turns out the driver
>(I think) just didn't support 32-bit access, so I had to turn it off.
>
>Mark Turnbull
>
The stock driver does not support cylinders over 1023 so the 515 drive size
would not be supported. An aftermarket dirver may be avialable to work with
your disk though.
There is MS KB articles in reference to this.
--
"Jerry Wise" <gew...@infi.net>
http://www.infi.net/~gewkab
David Whitney
>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>and Get the following error message when I try to run windows with
>>32 bit disk access enabled
>>
>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>""(Press Any Key To start Windows Without 32-bit Disk access
>>Enabled..."
>>
>>WHAT CAUSES THIS DAMN ERROR?
>>HOW CAN I FIX MY PROBLEM??
>>I am about to pull my freaking hair out people!!!!!
>I had the same problem with my NEC machine. It turns out the driver
>(I think) just didn't support 32-bit access, so I had to turn it off.
>Mark Turnbull
32-bit disk access was written to give Windows final control of disk
I/O, bypassing the last remnants of DOS interrupt-driven access.
Microsoft, which refers 32BDA as "FastDisk" access, wrote the driver
to accomplish this for Western Digital 1003 and strictly compatible
controllers. That driver is WDCTRL.
Upon Windows startup, WDCTRL will execute a series of tests to ensure
compatibility between itself and the controller with which it
communicates. If it detects a compatibility problem, as it apparently
did in the above example, it reports the problem and kills the
fastdisk driver. Windows will then allow conventional disk access,
which results in no problem - just less than optimal performance.
The message is not really an "error," its really just a report of
incompatibility. Windows, as I mentioned, will still work just fine.
You just won't have 32-bit disk access.
There's no fix; if a controller is not compatible, the vendor of the
controller/disk must write a custom fastdisk driver for it. Check with
the vendor of your drive to see if they have such a driver...
Hope that helps.
David Whitney
intr...@ionet.net
Bob Rich
which is over the 528MB limit of older bios's.
If you can't get the new bios, try getting a disk manager software, like OnTrack (check
http://www.quantum.com/ i believe it's in there somewhere.
Cheers
Bob
Jim Attfield
>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>and Get the following error message when I try to run windows with
>32 bit disk access enabled
>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>""(Press Any Key To start Windows Without 32-bit Disk access
>Enabled..."
<snip...>
I have had a not dissimilar poblem, both the WDCTRL 32 bit driver and
the board's 32 bit driver failed. I was about to give up when I
spotted a buried little hint which was move the line in system.ini
which loads the driver (e.g. *vpd386) to the END of the 366 enhanced
section. BINGO! All was well, and it has worked beautifully ever
since.
Best of luck
Jim Attfield (mic...@dial.pipex.com)
Mike Viscount
Whitney) writes:
>Mark Turnbull <turn...@bnr.ca> wrote:
>
>>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>>and Get the following error message when I try to run windows with
>>>32 bit disk access enabled
>>>
>>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>>""(Press Any Key To start Windows Without 32-bit Disk access
>>>Enabled..."
>>>
This is a lot of really good stuff, but, I am not sure about the part
about there being *NO FIX*. If I am not mistaken this error can also
be caused by a disk drive that has more than 1024 cylinders. WDCTRL
does not understand more than 1024 and therefore freaks out. There is
another wdctrl available on the Western Digital FTP site that replaces
the stock windows 3.x wdctrl. I think that it is supposed to fix this.
There are several documents about this problem on both the Microsoft
WWW site (not sure where it's buried these days - one of the KB's) and
there are also several articles on the WD WWW site. See #15 in the faq
at http://www.wdc.com/support/FAQ/general.html
I agree that if the disk controller is not WD1003 compatible the only fix
may be to buy another controller but given the 515MB listed above I think
that this is probably a drive with >1024 cylinders (at least if it is
a 515MB where 1MB = 1024*1024).
Hope this is helpful rather than snding you on a wild goose chase and
of course if I am wrong I appologize in advance since I most likely won't
see any followups as I don't generally have time to stay caught up with
this group :-(
Mike
mi...@mcnc.org
James C. Owens
>In article <30e536d...@spectator.cris.com>, anti...@cris.com
>says...
>>
>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
>which
>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>and Get the following error message when I try to run windows with
>>32 bit disk access enabled
>>
>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>""(Press Any Key To start Windows Without 32-bit Disk access
>>Enabled..."
>>
>>WHAT CAUSES THIS DAMN ERROR?
>>HOW CAN I FIX MY PROBLEM??
>>I am about to pull my freaking hair out people!!!!!
>>EMAIL
>>ANTI...@CRIS.COM
>>Please HELP me, sorry for those caps on, I'm desperate people......
>>
>>--------------------------------------------------
>>-------------------------------------------------
>>http://www.cris.com/~ANTIRUSH
>>It sucks pretty bad, but what web page doesn't??
>>--------------------------------------------------
>>---------------------------------------------------
>I'm just guessing, but it sounds like your driver (wdctrl) is corrupt. I'd try and
>re-install it. It is definately a software problem.
>Keith Keefer
Some paddle boards for ISA "IDE" ATA, and older MFM controllers have
compatibility problems with the Western Digital 1003 standard that
WDCTRL is written to - they will cause WDCTRL to fail upon validation.
Also, I have seen errors similar to this on machines that have become
infected with a boot sector virus (since many of them "ghost" the
original boot sector to a new location, which means the WDCTRL can't
find it, since it operates in protected mode). Check your machine with
McAfee or another good AV prog.
Regards,
James C. Owens
j...@infi.net
Peter Herweijer
>This is a lot of really good stuff, but, I am not sure about the part
>about there being *NO FIX*. If I am not mistaken this error can also
>be caused by a disk drive that has more than 1024 cylinders. WDCTRL
>does not understand more than 1024 and therefore freaks out. There is
>another wdctrl available on the Western Digital FTP site that replaces
>the stock windows 3.x wdctrl. I think that it is supposed to fix this.
It is. In general, there is no reason why there should be *no fix*.
If there is a *wdctrl replacement (FastDisk driver) that understands
your controller hardware and disks, 32BDA will work. There are
drivers even for some SCSI hardware and ATAPI CD-ROMs
Just to avoid questions I can't answer: the latter work only with a
specific brand of CD-ROM, and I don't know any details.
>There are several documents about this problem on both the Microsoft
>WWW site (not sure where it's buried these days - one of the KB's)
The Microsoft Windows KnowledgeBase would be a good bet :^)
>and there are also several articles on the WD WWW site. See #15 in the
>faq at http://www.wdc.com/support/FAQ/general.html
Need I mention that the Enhanced IDE FAQ also has a few words on the
matter?
>I agree that if the disk controller is not WD1003 compatible the only fix
>may be to buy another controller but given the 515MB listed above I think
>that this is probably a drive with >1024 cylinders (at least if it is
>a 515MB where 1MB = 1024*1024).
It is certainly sufficient to make *wdctrl fail.
- Peter
Jason Bolt
>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
>which
>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>""(Press Any Key To start Windows Without 32-bit Disk access
>>Enabled..."
>>
>>WHAT CAUSES THIS DAMN ERROR?
Have you booted from a clean diskette and checked for viruses lately.
A few stealth viruses will really mess with Windows' 32 bit access.
You might check it out.
R W Jones
raised...but I had similar problm in Win 3.11 (sic) and tracked the cause
to the Adaptec EIDE card which comes with its own driver as the thing
isn't able to converse with the native Win* 32-bit driver (or something to
that effect). So I loaded the PowerIDE driver from Adaptec and still
no joy. Only when I commented out the old driver name from system.ini did
the 32-bit access work. Can't remeber this was expressly said in the
EIDE card docs.
Craig Cockburn
> edited...In article <4crjls$b...@bcarh8ab.bnr.ca>, turn...@bnr.ca says...
>
> >I had the same problem with my NEC machine. It turns out the driver
> >(I think) just didn't support 32-bit access, so I had to turn it off.
> >
> >Mark Turnbull
> >
>
> The stock driver does not support cylinders over 1023 so the 515 drive size
> would not be supported. An aftermarket dirver may be avialable to work with
> your disk though.
>
This is the problem that I am experiencing I suspect, my disk has
1050 cylinders. Does anyone know how I can get a driver which supports
this?
thanks
--
Craig Cockburn (pronounced "coburn"), Edinburgh, Scotland
Find me in "E-mail addresses of the rich and famous" ISBN 0-201-40893-7
Sgri\obh thugam 'sa Gha\idhlig ma 'se do thoil e.
Craig Cockburn
Hi,
I've just run MSD on my disk and both it and my file manager
say my disk is 503Mb. Msd says it has 1023 cylinders. However, the
bios says it has 1050 cylinders and is 544KMb. This is what the
"auto-detect" on the BIOS is finding. Which is right and
is it safe to change the settings in the BIOS to agree with MSD
without trashing the 400Mb of data on the disk?
Craig Cockburn
jimmy.r....@cdev.com (Jimmy R. Thompson) writes:
>
> The WDCTRL deiver does not know what to do with disks having more than
> yes 1024 cylinders. Try the WIN31.EXE from WESTERN DIGITAL and see
> if it doesn't fix the problem.
>
How can I tell if my disk has more than 1024 cylinders? The BIOS says
1050 but MSD says 1023.
Jimmy R. Thompson
Rob Wilson @ The Forum x418
With 32 bit disk access enabled I get the following error after the Windows
startup screen has been displayed:
CPQWDCTL Error WD4: The Microsoft Windows 32-Bit disk driver (CPQWDCTL)
validation failed at phase 04, 3F
To continue starting Windows without using the 32-Bit
disk driver, press any key.
Is this something to do with the hard-disk type because the original was
swapped for a larger one last year. Reading through this thread suggests that
it might be something to do with the number of cylinders. Please help!
Rob Wilson,
Huntingdon, UK.
P.S. Compaq's Tech Support didn't even bother trying to remedy the situation
dispite several mails on the subject.
Thao N Tran
>I too am having problems with a Compaq Prolinea 4/66 with Windows 3.11 (WFWG).
>With 32 bit disk access enabled I get the following error after the Windows
>startup screen has been displayed:
>CPQWDCTL Error WD4: The Microsoft Windows 32-Bit disk driver (CPQWDCTL)
>validation failed at phase 04, 3F
>To continue starting Windows without using the 32-Bit
>disk driver, press any key.
>Is this something to do with the hard-disk type because the original was
>swapped for a larger one last year. Reading through this thread suggests that
>it might be something to do with the number of cylinders. Please help!
Hi,
I had similar problem with my computer, and I fixed the problem by
changing that the number of cylinders. As far as I could tell, my
computer (or Windows 3.1) could not accept the cylinder number as
listed in the specs of my hard disk. I found the appropriate number
by running "msd" in DOS and looking at the hard disk description.
(Sorry, I don't remember the exact menu command to do this). There, I
found that "msd" reported two types of number, one that was the
current setting and one that was the acceptable setting. "msd" used
more ambiguous language that this, however; and I had to do some
creative interpretations. When I changed my CMOS hard disk setting to
correspond to what "msd" wanted, I was able to run Windows 3.1 fine.
A few cautions: I really have no idea what effect resetting the
cylinder number has on the data stored on the hard disk. It could
very well be that the reset will make some of the data inaccessible.
Before I implemented the change, I tried to move my data to the lower
cylinders by running a full defrag on the disk, although once again, I
don't know if this is really the way to do it. Because the difference
in the cylinder numbers was small (1028 vs 1024), and I was only using
about 50% of my disk, I felt some what confident that everything will
be ok, and so far I've experienced no problem.
If the difference in cylinder numbers are large, I would say that you
should look for another solution, else you will be wasting a lot of
your hard disk. I have heard that certain computer designs cannot
take a hard disk that is bigger than 512MB (that number might not be
exact), and you have to change your hardware or change the BIOS (or
something drastic like that) in order to install those 1GB disks.
Also, in one of the previous posts, someone mentioned having success
with the "wdctrl" driver to cure the problem without having to change
the number of cylinders, after following some trick stated in the
"wdctrl" manual. This seems to be the better way of solving the
problem for Windows, although I wonder what still happens in DOS?
Thao
Craig Cockburn
> computer (or Windows 3.1) could not accept the cylinder number as
> listed in the specs of my hard disk. I found the appropriate number
> by running "msd" in DOS and looking at the hard disk description.
MSD says 1023 for me. The CMOS says 1050. I'm proposing the same course of
action that you took and would appreciate some help from someone who knows
how to prevent data loss.
> (Sorry, I don't remember the exact menu command to do this). There, I
> found that "msd" reported two types of number, one that was the
> current setting and one that was the acceptable setting. "msd" used
> more ambiguous language that this, however; and I had to do some
> creative interpretations. When I changed my CMOS hard disk setting to
> correspond to what "msd" wanted, I was able to run Windows 3.1 fine.
>
> A few cautions: I really have no idea what effect resetting the
> cylinder number has on the data stored on the hard disk. It could
> very well be that the reset will make some of the data inaccessible.
> Before I implemented the change, I tried to move my data to the lower
> cylinders by running a full defrag on the disk, although once again, I
> don't know if this is really the way to do it. Because the difference
> in the cylinder numbers was small (1028 vs 1024), and I was only using
> about 50% of my disk, I felt some what confident that everything will
> be ok, and so far I've experienced no problem.
>
> Also, in one of the previous posts, someone mentioned having success
> with the "wdctrl" driver to cure the problem without having to change
> the number of cylinders, after following some trick stated in the
> "wdctrl" manual. This seems to be the better way of solving the
> problem for Windows, although I wonder what still happens in DOS?
>
I seem to have missed that - what was the trick?
Stephanie Lindorff
software is sold via both OEM and retail channels. (i.e. we
either sell it to the drive manufacturer to bundle with the
drive, or we sell it directly to the end user).
OEM versions of Disk Manager (such as the one at the Quantum
web site) will only work on drives made by that specific
manufacturer.
If you are interested in purchasing our software, please send
email to Sa...@ontrack.com. If you have any questions about
the software, please feel free to send email to
te...@ontrack.com.
Stephanie Lindorff
Ontrack Computer Systems
Jim Attfield
>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>and Get the following error message when I try to run windows with
<snip>
BTW, make sure you TURN OFF and IDE block mode settings in your
computer's CMOS settings. If turned on it will screw the driver for
sure.
Cheers!
Jim A*
Damien Stewart
>kd_k...@pnl.gov (Keith Keefer) wrote:
>>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
>>which
>
>>>""(Press Any Key To start Windows Without 32-bit Disk access
>>>Enabled..."
>>>
>>>WHAT CAUSES THIS DAMN ERROR?
>
>Have you booted from a clean diskette and checked for viruses lately.
>A few stealth viruses will really mess with Windows' 32 bit access.
>You might check it out.
>
I am currently having the same problem...I don't have any viruses, (first
thing I checked for when it occured...). Reading directly from the
Windows manual, it says that if in the virtual memory setup it says:
"Using BIOS" it means that your hard disk controller cannot use 32bit
disk access.
I have a DX4-100 Intel motherboard and this option is supported...
What I am thinking is that the HD controller has been partially damaged,
as I short circuited the system accidentally recently when moving a few
things about..
But if this is the case, why does everything else work fine? I haven't
gotten any other errors other than that....
So does anyone out there who reads this message know how I could test the
integrity of the controller? There is a commercial program from Comm Tech
Systems called the Trouble Shooter, which tests all hardware
components...Is there something similar as share or free ware?
Hope anyone can help...
Damien
Jeff Collins
--snip--
> I am currently having the same problem...I don't have any viruses,
> (first thing I checked for when it occured...). Reading directly
> from the Windows manual, it says that if in the virtual memory setup
> it says: "Using BIOS" it means that your hard disk controller cannot
> use 32bit disk access.
> I have a DX4-100 Intel motherboard and this option is supported...
> What I am thinking is that the HD controller has been partially
> damaged, as I short circuited the system accidentally recently when
> moving a few things about..
> But if this is the case, why does everything else work fine? I
> haven't gotten any other errors other than that....
--snip--
One possibility, sometimes overlooked, is when the system.ini file
needs editing. This KB article may have been referred to earlier;
here's its address:
Windows Err Msg: WDCTRL Cannot Load Due to Conflict
<http://198.105.232.6/KB/PEROPSYS/windows/Q81803.htm>
-Jeff
Duane M. Saylor
512 MB in size, you need a replacement driver for the one included with
Windows. The driver should be included with your controller, your
motherboard (if your motherboard has the IDE built in) or in some cases
a driver is provided by the hard disk manufacturer (such as Western
Digital).
Duane Saylor
Chris Stout
>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>and Get the following error message when I try to run windows with
>>32 bit disk access enabled
>>
>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>""(Press Any Key To start Windows Without 32-bit Disk access
>>Enabled..."
[snip]
This is not necessarily a bad error. Windows is attempting to load
the 32-bit access mode but either your hard drive or your controller
won't allow it for some reason. 32-bit access for hard drives is a
very fine and detailed process which relies on a series of things to
click into place at the proper time.
Chances are, your current controller and hard drive worked with 32-bit
access before but now it won't. The reason for this may be that you
installed some piece of software that loads when Windows loads and
conflicts with the 32-bit access mode.
You can continue to pull your hair out even longer by trying to
shuffle through your .ini files and play the ol' trial-and-error game
trying to figure out what happened or you can simply disable 32-bit
access mode.
I strongly encourage you to just disable the 32-bit disk access mode
because it usually causes more problems than it's worth. In my
experiences, it doesn't speed up anything at all and using a good
cache program like smartdrv will negate the need for 32-bit anyway.
Chris Stout
Rodger Lue
> >>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system
> >>which
> >
> >>>""(Press Any Key To start Windows Without 32-bit Disk access
> >>>Enabled..."
> >>>
> >
> >Have you booted from a clean diskette and checked for viruses lately.
> >A few stealth viruses will really mess with Windows' 32 bit access.
> >You might check it out.
> >
>
> thing I checked for when it occured...). Reading directly from the
> Windows manual, it says that if in the virtual memory setup it says:
> "Using BIOS" it means that your hard disk controller cannot use 32bit
> disk access.
>
> I have a DX4-100 Intel motherboard and this option is supported...
>
> What I am thinking is that the HD controller has been partially damaged,
> as I short circuited the system accidentally recently when moving a few
> things about..
>
> But if this is the case, why does everything else work fine? I haven't
> gotten any other errors other than that....
>
> integrity of the controller? There is a commercial program from Comm Tech
> Systems called the Trouble Shooter, which tests all hardware
> components...Is there something similar as share or free ware?
>
> Hope anyone can help...
>
> Damien
I think I had this problem before. Not sure, but....
Are you both using 540 Meg or more hard drive with a BIOS that does'nt
support these drives? If so you both are probably using the drive's software
that fools the BIOS and allows access to the 540+ area of the drive.
This may cause the 32 bit access problem in question. With my Conner drive,
the EZ drive software comes with a file that you have to put in your Windows/System
directory (and some editing of you Windows system.ini file) to correct the problem.
Let me know if this helps.
Rog
Lyle
the support is in the BIOS windows can't do the 32 bit access because that
access is done without the BIOS. So, you need either a sw driver, or a
controller that supports lba's.
Lyle P
In article <31043D...@norfolk.infi.net>, dsa...@norfolk.infi.net
says...
--
-------------------------------------------------------------
"If it ain't broke..." you bought it from me.
lyl...@ix.netcom.com fone 619-945-5953 pfax 619-945-6966
Direct Distributor for Seagate, Fujitsu, Quantum, Conner, Exabyte,
Sony, Yamaha, JMR, CI Design, CMD, Kingston
-------------------------------------------------------------
Kris Tiebos
harddisk you have.
Each HDD manufacturer comes with 32bit disk acces drivers for their
hard disks (check out www.seagate.com and others for more info)
greetingz
Steve Charloff
>>>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>>>""(Press Any Key To start Windows Without 32-bit Disk access
>>>>Enabled..."
>>>>
>>>>WHAT CAUSES THIS DAMN ERROR?
>
dealing successfully with drives having greater than 1024 cylinders -
effectively, this means any drive over 512 MB or so.
WDCTRL is the 32 bit driver created by Western Digital and endorsed as
the standard. It provides the 32-bit access control for drives smaller
than this 512MB limitiation. For larger drives, it must be replaced.
The replacement gets specified in the system.ini.
The driver that replaces it comes from your hard drive manufacturer.
The new Western Digital driver, called WDCDRV26.386, is available at
their web site, www.wdc.com. It works just fine. Other manufacturers,
like Seagate, Connor, etc., will have similar drivers at their web
sites.
Steve Charloff
Right Brain Systems
Raleigh, NC
Gerhard Wallin
This is also very true with Windows95. The 32-bit disk-access,
according to Microsoft, is an early part of Win95 incorporated in Wfwg
3.11. So the drivers from Conner, WD a o (available on their
web-sites) should be used with Win95 to get the system to work with
32-bit disk-access in conjunction with disks larger than 528 Mb
(503,47 as reported by fdisk, or 1023 Cyl). Look at performance-tab
with system-properties and se if 32-bit is reported after file-system
and virtual memory (=disk access).
The system can start (might not even start) but is unstable with large
drives and no driver to correct the problem with WDCTRL and drives >
528 (504) Mb.
The file to get from Conner is 32bit.exe and it contains both the
driver and informatons about installation.
GW
Jon Sundquist
suite, that allows one to change the windows video resolution without
restarting windows 3.1. I've increasingly had to switch resolutions, and
am finding it a pain to always have to exit everything, including
windows, and have been looking for a way to do this on-the-fly. I think
win95 can do this, but I have no interest in making the switch. Anybody
know of any products (commercial or whareware) that can do this?
TIA,
Jon Sundquist
Andy Baxman
>Mark Turnbull <turn...@bnr.ca> wrote:
>
>>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>>>and Get the following error message when I try to run windows with
>>>32 bit disk access enabled
>>>
>>>""(Press Any Key To start Windows Without 32-bit Disk access
>>>Enabled..."
I believe that this error can be also caused by the ANTI-CMOS virus
The latest McAffee software can ( I believe ) detect this virus.
( It causes 32 bit access to cock up on win 3.1 as well )
Andy
Mike Viscount x9212
Your hard disk has more that 1024 cylinders and the stock wdctrl
does not understand more than 1024. There is another wdctrl on the
Western Digital web site ( http://www.wdc.com/ ). Specifically go
to the folowing URL for the specifics of what you need to do to get
32 Bit Disk Access going on Win 3.1x.
http://www.wdc.com:80/support/FAQ/install.html#32bda
Also note that some disk controllers may provide there own "FastDisk"
or "32 Bit Disk Access" drivers. If yours is such you have the option
of using either. See you controller documentation if it exists.
Hope this helps,
Mike
Jeff Feil
: cst...@access.mountain.net (Chris Stout) wrote:
: >Mark Turnbull <turn...@bnr.ca> wrote:
: >
: >>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
: >>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
: >>>and Get the following error message when I try to run windows with
: >>>32 bit disk access enabled
: >>>
: >>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
: >>>""(Press Any Key To start Windows Without 32-bit Disk access
: >>>Enabled..."
: >[snip]
: I believe that this error can be also caused by the ANTI-CMOS virus
: The latest McAffee software can ( I believe ) detect this virus.
: ( It causes 32 bit access to cock up on win 3.1 as well )
: Andy
Blat. Don't scare people with virus threats. Extremely rare on all accounts
unless you're sloppy with where you get your software.
Your hard drive or it's interface may not support the Windows 32-bit
features. Typically, your hardware has to conform to a Western Digital
standard, which isn't really much of a standard.
1) From a C:\ prompt, start Windows using: WIN /D:FC
Windows *should* come up without errors.
2) Once in Windows, open up Main and go into Control Panel. Open up the icon
"386 Enhanced". Click on the "Virtual Memory" button. Then the "Change"
button. At the bottom of this window, you should see a couple boxes, which
are checked. Uncheck the boxes which say "32-bit disk access" and "32-bit
file access". If these boxes are already unchecked, take a deep breath and
scream, then seek out a true guru for how to fix your problem.
3) Accept all the changes as you close out of the virtual memory boxes. Your
problem should now be fixed.
-- Q
--
--------------------------------------------------------------------------
Jeffrey J. Feil - qu...@emf.net http://www.emf.net/~quam
Maxis, Inc. - SimCity and other Software Toys(R) http://www.maxis.com
The opinions expressed in this message are those of the author and do not
necessarily represent those of Maxis or its corporate affiliates.
Jeffrey Dale
Andy Baxman
>Andy Baxman (bax...@tcp.co.uk) wrote:
>: cst...@access.mountain.net (Chris Stout) wrote:
>: >Mark Turnbull <turn...@bnr.ca> wrote:
>: >
>: >>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>: >>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>: >>>and Get the following error message when I try to run windows with
>: >>>32 bit disk access enabled
>: >>>
>: >>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>: >>>""(Press Any Key To start Windows Without 32-bit Disk access
>: >>>Enabled..."
>: >[snip]
>
>: I believe that this error can be also caused by the ANTI-CMOS virus
>
>: The latest McAffee software can ( I believe ) detect this virus.
>
>: ( It causes 32 bit access to cock up on win 3.1 as well )
>
>: Andy
>
>
>Blat. Don't scare people with virus threats. Extremely rare on all accounts
>unless you're sloppy with where you get your software.
>
I'm not trying to scare anyone, just relating a FACT.
Win3.1 on my pc started refusing to use 32 bit access, It was due to the ANTI COMOS
virus, nuff said. This person had a problem, I had the same problem, all I did was
relate what caused it.
As to being sloppy where you get software, viruses have been found on certain well
known ( and shrink wrapped ) software.
By the way, what does blat mean???
Andy
Roger A. Kendall
just beware of the exceptional performance degradation using this
product!!
tom
that will let you get 32 bit disk and file access. I have a
western digital and windows for workgroups and I have both
because of their software. Tom
bcol...@scoot.netis.com
>I know I've read about software products, possibly as part of a utilities
>suite, that allows one to change the windows video resolution without
>restarting windows 3.1. I've increasingly had to switch resolutions, and
>am finding it a pain to always have to exit everything, including
>windows, and have been looking for a way to do this on-the-fly. I think
>win95 can do this, but I have no interest in making the switch. Anybody
>know of any products (commercial or whareware) that can do this?
>TIA,
>Jon Sundquist
ATI cards have built in Winswitch software to do this
But it can eat up lots of memory
Ernst J. Poppen
>cst...@access.mountain.net (Chris Stout) wrote:
>>Mark Turnbull <turn...@bnr.ca> wrote:
>>
>>>>I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
>>>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
>>>>and Get the following error message when I try to run windows with
>>>>32 bit disk access enabled
>>>>
>>>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
>>>>""(Press Any Key To start Windows Without 32-bit Disk access
>>>>Enabled..."
>>[snip]
>I believe that this error can be also caused by the ANTI-CMOS virus
Could be or could not be.
>The latest McAffee software can ( I believe ) detect this virus.
>( It causes 32 bit access to cock up on win 3.1 as well )
>Andy
This error is typically for WDCTRL, and it is just saying it can't do
the 32-bit trick.
The solution to this (minor) problem: Just get yourself the right
32-bit device driver for WIndows to talk to your HDD.
I'm having a 1 Gigabyte Seagate drive which has been jumpered to tell
the bios there are in fact 2 HDD of each 540 Mb
Since DOS can't handle any HDD over 512 (or was it 526) Megabytes,
because of the number of cylinders (which has been restricted to only
1024 cylinders), you get into trouble.
Either you re-fdisk your HDD, reformat it for LBA-use, or you get
yourself the right driver to work under Windows.
That's all there is to it.
But to be on the safe-side, checking for virusses won't do any harm to
your system.
Good luck and let me know of any results.
Bye now
Ernst. J. Poppen (call me Ernie)
Ernst.J...@pi.net
E.Duggan
> <snip>
> <I am running Windows 3.1 on my 486dx4/100Mhz ctyix CPU system which
> > >>>>has AMI bios (American megatrends(Date :1994)) I have ONE 515MB Drive
> > >>>>and Get the following error message when I try to run windows with
> > >>>>32 bit disk access enabled
> > >>>>
> > >>>>(("Validation error in (WDCTRL) Failed at PHASE 03 , 3F"))
> > >>>>""(Press Any Key To start Windows Without 32-bit Disk access
> > >>>>Enabled..."
> > >>[snip]
[SNIP]
> > >( It causes 32 bit access to cock up on win 3.1 as well )
[SNIP]
> > This error is typically for WDCTRL, and it is just saying it can't do
> > the 32-bit trick.
> > The solution to this (minor) problem: Just get yourself the right
> > 32-bit device driver for WIndows to talk to your HDD.
> > I'm having a 1 Gigabyte Seagate drive which has been jumpered to tell
> > the bios there are in fact 2 HDD of each 540 Mb
[AND MORE SNIP]
> To clarify, repalce WDCTRL (the windows 32 bit disk access driver) with a
> aftermarket one that should be available from your drive manafacturer.
> Two good ones are Ontrack (Ontrackw.386) which should work with any
> hardrive, and Western Digitals WDCTRL.386 which will supposedly work with
> any EIDE ATAPI compliant harddrive. However I will tell you now it does
> not work very well with quantum harddrives.
I had similar trouble with my 486/66. I wnet through loads of shit,
difficult documentation, in and out of cmos, busy tech support lines, and
all that stuff ... the guys on the tech line EVENTUALLY talk to me to say
that I can't use 32 bit access with a SCSI hard drive :-|
So: what kind of drive do you have?
Maybe you can't use 32 bit access in windoze at all?
Apparently SCSI is faster anyway (so the techys said).
I know nothing, am technically illierate, a pc bozo, but just telling
what happened to me.
Eddie Duggan
+===========================================================================+
| <E.Du...@uea.ac.uk> |
| * T H E B I G H O U S E O F K N O W L E D G E * |
| Suffolk College, Rope Walk, Ipswich, Suffolk IP4 1LT UK +44(0)1473 296673 |
Steven B Cartier
32 Bit Disk access is only available to Hard Drives that support the standard, and many do not.
Call the manufacturer of yours and ask them if it does or not.. 99 out of 100 this is why
shewontaworka
Kevin Lang
32-bit disk driver available for their cards. I think the only limitation is that
it has to be a fixed disk that conforms to the ASPI API.
Hope this helps.
Kevin