ESDI BIOS read failure?

Here's my problem:
After upgrading a Win98 SE system by putting in a new
motherboard (Intel D845GVSR) and processor (Celeron 2.6
GHz), confirming installation and functionality of all the
chipset drivers (including integrated Intel Extreme
Graphics and USB 2.0), I believe I've been able to resolve
all upgrade-related issues (there's always a few) except
for one: The Primary IDE controller (but not the
secondary!) insists on running in Compatibility mode.

Here's what shows in the Device Manager:

Intel(R) 82801DB Ultra ATA Storage Controller - 24CB
(Working properly according to Device Manager)
Primary IDE controller (dual fifo)
(Exclamation point: Code 10)
Secondary IDE controller (dual fifo)
(Working properly according to Device Manager)

I have also tried, by the way, using the Windows standard
drivers (something along the lines of "PCI Standard Dual
IDE controller") but this results in a blue-screen
(apparently, one controller working and the other one not
is an "unsupported configuration") and creation of the
infamous "NOIDE" registry key.

Here's an interesting (and probably very relevant) excerpt
from Bootlog.txt:
[000B3EED] Initing hsflop.pdr
[000B3EF3] Init Success hsflop.pdr
[000B3EF5] Initing esdi_506.pdr
[000B3F07] Init Failure esdi_506.pdr
[000B3F0A] Initing esdi_506.pdr
[000B3F13] Init Success esdi_506.pdr

Now, I understand that the same driver is being loaded
twice because it's loaded once for each IDE controller.
What I don't understand is why that same driver would fail
the first time and then succeed the second time.

A search of the Microsoft KB yielded no useful advice,
aside from informing me that Windows usually creates an
ios.log file when there's a failure of this kind. Sure
enough, I checked the Windows directory, and there was a
freshly-created ios.log file that began with this
interesting tidbit of information:

ESDI BIOS read failure
Unit number 02 going through real mode drivers.

Okay, so apparently the problem is in the "ESDI BIOS".
What do I do now?

Looks like the problem was that I had an older version of
the ESDI_506.PDR file. Once I installed the version
mentioned in this KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-
us;243450&Product=w98

....the problem was apparently solved. No more exclamation
points in device manager, and no more compatibility-mode
paging or related warnings.

This also seems to have solved the problem of the computer
locking up when trying to shut down or reboot. I suspected
that this was related to the other issue but there was no
real evidence linking the two. (There's a bootlog.txt but
not really a shutdownlog.txt, is there?)

StevenRoy



-----Original Message-----
Here's my problem:
After upgrading a Win98 SE system by putting in a new
motherboard (Intel D845GVSR) and processor (Celeron 2.6
GHz), confirming installation and functionality of all
the
chipset drivers (including integrated Intel Extreme
Graphics and USB 2.0), I believe I've been able to
resolve
all upgrade-related issues (there's always a few) except
for one: The Primary IDE controller (but not the
secondary!) insists on running in Compatibility mode.

Here's what shows in the Device Manager:

Intel(R) 82801DB Ultra ATA Storage Controller - 24CB
(Working properly according to Device Manager)
Primary IDE controller (dual fifo)
(Exclamation point: Code 10)
Secondary IDE controller (dual fifo)
(Working properly according to Device Manager)

I have also tried, by the way, using the Windows standard
drivers (something along the lines of "PCI Standard Dual
IDE controller") but this results in a blue-screen
(apparently, one controller working and the other one not
is an "unsupported configuration") and creation of the
infamous "NOIDE" registry key.

Here's an interesting (and probably very relevant)
excerpt
from Bootlog.txt:
[000B3EED] Initing hsflop.pdr
[000B3EF3] Init Success hsflop.pdr
[000B3EF5] Initing esdi_506.pdr
[000B3F07] Init Failure esdi_506.pdr
[000B3F0A] Initing esdi_506.pdr
[000B3F13] Init Success esdi_506.pdr

Now, I understand that the same driver is being loaded
twice because it's loaded once for each IDE controller.
What I don't understand is why that same driver would
fail
the first time and then succeed the second time.

A search of the Microsoft KB yielded no useful advice,
aside from informing me that Windows usually creates an
ios.log file when there's a failure of this kind. Sure
enough, I checked the Windows directory, and there was a
freshly-created ios.log file that began with this
interesting tidbit of information:

ESDI BIOS read failure
Unit number 02 going through real mode drivers.

Okay, so apparently the problem is in the "ESDI BIOS".
What do I do now?
.