esdi_506 boot problem

Clone / NONE
February 5, 2009 at 20:10:37
Specs: Windows 98, amd k6
I have 3 hard drives one has 60 gig the others are all smaller . When I boot the computer it always freezes on the 3rd loading of esdi_506 I think it has something to do with my 60 gig drive but I'm not sure . It will useually work after I push the restart Sometimes twice or if I first boot to DOS and restart to windows. I've checked the regestry and "NoIDE" isn't loaded and and the start key does have a value of 01 . ESDI_506 is used on all the drives. The file version is 4.109.2186 The product version is 4.10.1998 build qfe version 4.0 1988-1998. Is there a solution or do I just have to live with it?

See More: esdi_506 boot problem

Report •


#1
February 6, 2009 at 08:44:18
Googling the error yields many hits. One link below may be of help.

http://www.tomshardware.com/forum/1...


Report •

#2
February 6, 2009 at 12:06:40
Do a google search for 243450USA8.EXE and download and run it. It's an update for ESDI_506.PDR. If that doesn't fix it, the problem may be with the drive.

Report •

#3
February 6, 2009 at 17:13:01
I did just replace this drive because it was "clicking" It was replaced with the same drive a Western Digital 60 gig . I will try your solution Thanks

Report •

Related Solutions

#4
February 6, 2009 at 17:29:01
I tried that already and it worked for a while but now it's doing it again Thanks anyway

Report •

#5
February 6, 2009 at 21:21:34
Check the drive's jumpers. For one drive on a cable the WD setting for master is usually 'no jumper'. For two drives on a cable you'd use master/slave jumpers (unless you're using cable select).

With three hard drives I assume one is connected on the secondary IDE port. Check its drive settings in cmos/bios setup.

Some super socket 7 motherboards had DMA66 capability. Are you using a 40-wire or 80-wire cable?


Report •

#6
February 7, 2009 at 09:52:30
My bios is Award BIOS v4.60PGA 1984-98
its an AMD-K6(tn)-2/500 CPU
Award Plug and Play BIOS Extension v1.8A
Primary Master......Maxtor 92841U4
Primary Slave ......WMC WD600BB-75CAA0
Secindary Master....WMC AC25100L
Secondary Slave.....SONY DVD-ROM DDU1615
In the bios they are listed as
OPT SIZE CYLS HEAD PCOMP LANDZ SECT MODE
2(Y) 20490 2491 255 0 39702 63 LBA
1 20491 39703 16 65535 39702 63 NORMAL
3 20488 4962 128 65535 39702 63 LARGE


Report •

#7
February 7, 2009 at 09:57:08
Im not sure what the actual jumpers are set as but I beleive they are all set to Master and Slave Would it matter if they were set to Cable select? The DVD might be set that way

Report •

#8
February 7, 2009 at 09:59:44
All the drives have 40 pin wires

Report •

#9
February 7, 2009 at 11:26:26
If using cable select then BOTH drives on that cable MUST be set to cable select.

Report •

#10
February 7, 2009 at 20:25:08
Could you check to make sure the bios data for the drives is correct? They don't make any sense.

The maxtor model doesn't show up in a google search but I suspect it's an 8.4 gig. Then you've got the 60 gig WD and a 5 gig WD. But the cylinders/heads/sectors configuration shows 20 gig for each of them.

I think you used the 'auto detect hard drive' option in cmos. That should work OK for the 5 gig and the 8.4 (if that's what it is) but not for the 60 gig.

The maximum C/H/S is 16383/16/63 (8.4 gig) or a drive translation of that. Above that, drives must be detected as LBA. The figures you show are larger than that and, unless you manually changed them, are the bios' attempt to show what the c/h/s would be if the drive could be configured that way. Some will do that, some won't.

Most drives larger than 8.4 gig have the 16383/16/63 figure written to their firmware and can sometimes be fully seen by the bios if you manually enter those figures to ID the drive, even if the bios wouldn't normally see a drive that large.

For the drives you have, when using 'auto detect hard drive' you'd usually use LBA anyway. Most of the time it's best to just use AUTO (instead of auto detect) and let the bios set the drives up but I suspect you may have had problem doing that with the 60 gig.

If the 8.4(?) and 5 gig are working OK with the way they're setup in cmos then go ahead and leave them that way. Sometimes changing those setting will leave a drive unreadable. If you do make any changes, write down the original configuration so you can always go back to it. But consider manually entering the 16383/16/63 data for the 60 gig and setting it as LBA and see if that works. Also when windows comes up, check to make sure it's actually seeing all 60 gig.

Also consider getting an add-on ATA card. A used ATA66 card is probably going to be just a few dollars on ebay. And it will be able to handle the 60 gig drive with no problem.


Report •

#11
February 7, 2009 at 20:33:01
OH, I get the c/h/s data now. You did an 'auto detect hard drive' and those are three possible configurations for one drive. You can choose which one to use and it's recommending the first.

As I said above, it's seeing that drive as 20 gig. Which drive is that?


Report •

#12
February 10, 2009 at 18:16:18
Using Partition Magic 4.0 the Primary Master (Maxtor) is 19539 mb
The Primary Slave (Western Digital) is 57215 mb
And the Secondary Master (Western Digital) is 4918 mb
The Secondary Slave is a Sony DVD

Report •

#13
February 10, 2009 at 19:56:38
OK, that means the maxtor model number was 92041-U4 and not 92841-U4. That's why googling the latter didn't return a maxtor model.

Did you use partition manager when you originally partitioned the 60 gig?

One or more of the following should fix it:

1) Use AUTO to id the drives rather than 'auto detect hard drive'. And set MODE to LBA.

2) Use an 80-wire cable if the IDE port is ATA66 capable.

3) Use an add-on ATA card.


Report •

#14
February 12, 2009 at 17:43:13
The 60 gig drive is my "D" drive 1 partition 32 bit I will try the auto not auto-detect Thanks for your help so far this is a tough problem to solve. Sorry for the slip up on the Maxtor drive (dixclixia)

Report •

#15
February 14, 2009 at 08:24:28
All the driver are currently set to "Auto"
This problem seems to have something to do with the time it takes to boot up . If I just boot normally it usually fails (freezes on the 3rd try to load Esdi_506.pdr)
But if I go to the bios or boot to DOS first (system commander) and than start windows it almost always works . It's like an old car it just wants to warm up first I wonder what information I would get with S.M.A.R.T. enabled ?

Report •

#16
February 14, 2009 at 21:47:54
Look in cmos/bios setup for something like 'hard disk pre delay'. That option gives the hard drives a little more time to spin up and be recognized. A 6 second delay is usually enough.

Report •

#17
February 14, 2009 at 23:28:58
Problem motherboards like mine (chaintech 5ttm1) require a dma "wake up" script be run using debug in order for the drives to then be capable of DMA speeds while using Windows. Perhaps you can benefit from the same approach?
DMA Check Box Does Not Remain Checked

Further info - substitue 2x (DMA) modes as follows
UDMA mode 0 is 40
UDMA mode 1 is 41, etc. In other words, UDMA is 4x where DMA was 2x values.

The debug script is part of my autoexec.bat file so it is run during true DOS mode just like you seem to need?

This might be a method to get your drives recognized with resonable boot up times and at the same time operating at their highest speeds, win-win?

Lee


Report •


Ask Question