VOGONS


I bricked my XT-IDE card

Topic actions

First post, by Thrackerzod

User metadata
Rank Newbie
Rank
Newbie

I bought an XT-IDE Rev 4.1 from Blue Lava Systems about three years ago and have been using it happily in my Dell 386, until today when I had the genius idea to update the firmware. It always bothered me that the version I had said Beta and it was from 2015 with the latest from 2024 so it seemed like a great idea at the time. Except when I tried to flash it I got the error "eeprom did not return the same byte that was written" and the flash failed. Worse it now would no longer boot up to my CF card, but I could still boot to floppy disks so I figured I'd just put the original firmware I had on a disk, boot up and flash that. Except the flash failed again, and again, then it almost went through but now it's completely hosed. I can't even boot up to a floppy anymore, it tries but then asks for the location of command.com so I can't even try flashing it anymore. Unfortunately I don't have an EEPROM programmer so I guess I'm just up the creek at this point. What's the old saying about not fixing something if it isn't broken? Not sure where to go from here, this is so frustrating. šŸ™

Reply 1 of 8, by paradigital

User metadata
Rank Oldbie
Rank
Oldbie

Where to go from here surely is just buy an EEPROM programmer, they aren’t that expensive and are very handy to have around.

Reply 2 of 8, by mkarcher

User metadata
Rank l33t
Rank
l33t

If the issue is just the EEPROM/Flash contents of the XT-IDE, you should still be able to boot from floppy with the EEPROM removed. After booting, reinstalling the EEPROM chip should allow another flash attempt. Practice hot-inserting the EEPROM without power applied until you feel confident that you won't cause a short before attempting this live, though.

Reply 3 of 8, by tauro

User metadata
Rank Member
Rank
Member

There's a chance the EEPROM may have partially died. Certain parts of the memory can't be written anymore. I had this happen to me after flashing an EEPROM many times.

Getting an EEPROM programmer is a good idea.

Reply 4 of 8, by Thrackerzod

User metadata
Rank Newbie
Rank
Newbie

Thanks for the tips, I never thought of trying it without the chip installed. I may give that a shot later on. I really do need to get a programmer eventually. When I do I'll get some extra EEPROMs in case this one is faulty which it seems like it may be. For now I found something even better that I didn't even remember I had, a DTC EIDE Ultima Pro card. I installed it and it detected my CF card immediately and booted right up; also seems to be much faster than the XT-IDE anyway. I guess that makes sense, it's a 16-bit card after all. I'll try to get the XT-IDE fixed eventually and put it in my IBM 5160 which is what it was really meant for anyway.

Reply 5 of 8, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

Just a reminder that when properly configured, the xtide xub does not care which IDE controller your drive is sitting on. This is not the case with Promise IDE controller bios.

It is this feature which makes an old nic with a bootrom socket an acceptable means of adding the xub to an arbitrary computer.

Consider for instance, a late pentium system, with a pnp bios, and an sb32 with an ide interface.

The pentium system's int13 implementation is just fine, but adding the xub lets you drop 2 more hard drives on the soundblaster's IDE controller, which the system's bios does not look for or set up drives on. They'll be limited to 16bit IO, but that's not a big deal for certain kinds of drive, like LS120 (ata model, not atapi model), or for 'it's bulk storeage, and does not need to be fast' situations.

Reply 6 of 8, by MikeSG

User metadata
Rank Member
Rank
Member

Make sure to disable BIOS shadowing when reprogramming the XTIDE in-system. Had that error a few times.

Reply 7 of 8, by Thrackerzod

User metadata
Rank Newbie
Rank
Newbie

I'm not sure if BIOS shadowing is even an option in this Dell BIOS, it's pretty spartan (Dell 333S/l). Maybe that was causing the problem. I do have a 3COM 3C905B PCI network adapter with a socket, so perhaps I could throw it in my Optiplex and try flashing the chip from it. Probably worth a try.

I thought I had another problem when I realized I couldn't write to my CF card at all from this EIDE Ultima card, it was just working as read only. Any attempt to save a file threw an I/O error. Turned out to be a simple fix, I just had to plug in a berg connector to my CF adapter to power it; apparently this old IDE card doesn't provide what it needs. I also found another post here about a newer BIOS for this DTC card that extends it's support up to 32GB, so yet another reason to get a programmer someday.