Intel SE440BX IDE controller with Maxtor/Seagate drive (problem??)

I'm having a rather odd problem with an Intel SE440BX motherboard and the built-in IDE controller.

For some reason I cannot connect a Maxtor 90840D6 as a master on IDE controller 0 and a Seagate ST36451A as a slave on IDE controller 1.  IDE controller 1 also has a ASUS CD-S360 CD-ROM drive as a master.  This is the necessary configuration I require.

With the above configuration, the Seagate is *not* detected!   However, the Seagate can be a master on IDE controller 1 and then all three devices are detected.  The only other configuration that seems to work is if the Seagate is master and the Maxtor is a slave on IDE controller 0.  

The bottom line is that the Seagate must be a master in all cases to be detected!

I've never experienced anything like this before.  What is the problem?   Why can't the Seagate work as a slave on IDE controller 1?

I'm not certain if this is/was an Intel board problem, at least, not until the following error message began appearing:
Expansion ROM not initialized - PCIMass Storage Controller
Configuration Error
BUS: 00, Device: 0D, Function: 00

F1 - continue   F2 - setup

Hitting F1 just yields a blank screen...not even a boot up from a floppy disk.

This error now occurs consistently after any hd/cd configuration.  It began to occur after trying a number of different options.

Help... Any ideas?
Thank you.

p.s. One possible fix is to 'Ghost' the seagate data to another drive and ditch this Seagate....but I want to know why this is happening??????
S ConnellyTechnical WriterAsked:
Who is Participating?
tracycConnect With a Mentor Commented:
We have seen this problem more times that I care to remember.

The problem is the Seagate drive, not the Intel motherboard.  Seagate and Conner drives do not like to be slaves to anything other than Seagates or Conners.

The BIOS update is one of the things you need to do.

You also must download the latest 82371XB *.INF update utility for that chipset from Intel's WebSite.

NOTE: Dissable your sound card and your network card, if exists, before you load the *.INF update utility (this is for headache prevention).

That may let the Seagate ALLOW the Maxtor to be the master, but usually it still doesn't work.  You needed the *.INF update anyway.
Hello sconnell,

>  "This error now occurs consistently after any hd/cd configuration."

Is this board unable to boot at all now?

Have you tried resetting the BIOS?

Has the board ever worked for any period of time?

S ConnellyTechnical WriterAuthor Commented:
Hello Ralph,
You're fast!!
I just finished downloading the latest BIOS upgrade from Intel's web site.  Reseting the BIOS might clear this error.  

The board had work well in the past.  I'm not sure if it still boots actually.  I gave up after that error message began to appear on each boot up.

Unfortunately, there is absolutely nothing on Intel's web site regarding this error message.  Of course, Intel has never been any good at admitting errors in their products. :-(

WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

A new flash might wake it up!
Try to start up without IDE data cables connected to M/B if you still have trouble.
Let me know if it improves.
The Windows patch files for the chipset should have been included with your new motherboard.  But I don't think any files for the operating system are going to help in this case anyway.  Your problem occurs before the operating system is loaded.
Any luck with the flash?
Did you try to boot without the IDE cables attached?

S ConnellyTechnical WriterAuthor Commented:
Thanks for your answer Tracyc.
I've already found a workaround and I was already suspicious of a weird conflict with the Seagate.  #$%@
Since I'm feeling generous get the points!

This is what I did:
Intel actually had a SE440BX addendum in the form of a PDF file.  It identifies my exact BIOS error problem and the fix is to update the flash BIOS to revision 10.  

First I had to reset the BIOS with J8A1 in order to get the floppy to even boot.  The upgrade removed the error message.  The next problem to overcome was the Seagate/Maxtor problem.

I gave in and connected the CD-ROM as the secondary device on controller 0 and made the Seagate a primary device on controller 1.  

All in well now!!

Thanks everyone!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.