fjk61011
Veteran Member
My 1.44 Mb drives are dead. Have to buy new one.
Does the BIOS startup message appear on the 5150 now too?I just tried in a DTK XT clone. It works. F2 came up and I changed drive 0 to 360 k. Was able to boot from a dos floppy. Got mine from Bulgaria too. Seller very helpful.
Will try that laterDoes the BIOS startup message appear on the 5150 now too?
The "D000 ROM" is an error message produced by the power-on self test (POST) of the 5150 motherboard's ROM.Works in the XT clone. Doesn't work in 5150, I get D000 ROM and goes on to post.
And no other cards except for the video card ?Only happens when Sergey's FDD controller is in the 5150.
And no other cards except for the video card ?
The video card is not going to have a ROM starting at address D0000, so confirm for us that the EEPROM in Sergey's card is what is set to start at D0000.Correct
Ah yes. I just reread the thread. At post #19, the OP did not need to reflash the EEPROM.I doubt it's corruption as the controller works in the XT Clone,
If we look at the 'ROM address conflict' hypothesis:Possibly an address conflict ...
I can't think of a flashing related issue that would result in the card's EEPROM operation in an XT clone, and corrupted reads of the same EEPROM when the card is fitted to a 5150 motherboard.... the way the seller is flashing the ROMS ...
In post #18, BarryM's, "No problems with the replacement board in the 5150 and the BIOS did appear with no other cards with ROM sockets plugged in." suggests that a problem is not expected.... Some other issue with the controller that the 5150 falls over on.
Make's senseIf we look at the 'ROM address conflict' hypothesis:
Fact: The only cards in the IBM 5150 are a CGA card and Sergey's card.
Fact: The POST in the IBM 5150 is seeing, at the least, the 55 AA at the start of a ROM at D0000.
Assumption (at this time): The OP's card is set to start its EEPROM at D0000h. (Good assumption - no other cards with a BIOS expansion ROM.)
Conflict possibilities:
- A faulty CGA card that is decoding part, or all, of the D0000-D1FFF address space.
- A faulty 5150 motherboard that is decoding part, or all, of the D0000-D1FFF address space.
In both cases, Sergey's card would have to be 'winning the tug-of-war' conflict for at least the first two bytes (55 AA).
I have seen / Had this issue before, IMO it's worth trying a Re-flash in situ preferably in the 5150 or in the XT clone just to rule it out. Also there is a possibility of a 'borderline' IC in the ROM circuit of the controller which the 5150 post is picking up on.I can't think of a flashing related issue that would result in the card's EEPROM operation in an XT clone, and corrupted reads of the same EEPROM when the card is fitted to a 5150 motherboard.
"replacement board"In post #18, BarryM's, "No problems with the replacement board in the 5150 and the BIOS did appear with no other cards with ROM sockets plugged in." suggests that a problem is not expected.
All worth a try.Changing the video card might be a good first step (easy to do).
Seeing the affect of changing the EEPROM's start address to E0000 (E0000 available in the OP's current 2-card configuration).
Not sure if it's an EEPROM. Don't have a programmer for a EPROMIf you can, Try re-flashing the ROM in your 5150, If not try re-flashing in your XT clone and try the controller in your 5150 again.
I only have one CGA. I use that in the XT clone and Sergey's card works.Make's sense
I have seen / Had this issue before, IMO it's worth trying a Re-flash in situ preferably in the 5150 or in the XT clone just to rule it out. Also there is a possibility of a 'borderline' IC in the ROM circuit of the controller which the 5150 post is picking up on.
"replacement board"
All worth a try.
What does it say on the ROM on your controller ?, Is it an ATMEL AT28C64B ?, If it is you can use XTIDECFG.COM from the XUB download site to flash the ROM in situ and preferably do it on your 5150.Not sure if it's an EEPROM. Don't have a programmer for a EPROM