zezba9000
Well-known member
So I'm having a problem still after adding a disk-drive interface card. It stops reading drive and spits garbage data similar to @bibilit issue he shared here.
FYI: Frogger I loaded above was done via tape input. Many times loading from tapes will have the same/similar issue.
What I do:
* Power on computer with drive and Mario Bros disk mounted with FloppyEmu
* Computer beeps
* Computer beeps AGAIN but spits out junk similar to @bibilit issue he shared.
* Drive stops being read and game never loads
What I've tested:
* Drive works perfect in known fully working Apple II+ motherboard and Apple IIe computer.
* I tested ever single chip with known good ones from Apple II+ motherboard. RAM etc is all good.
* The 74LS283 was not the issue as I hoped like bibilit had.
* If I turn on the computer with no disk mounted THEN mount a disk it SOMETIMES will load BUT text is messed up in some apps
I'm currently deep cleaning the motherboard to see if anything changed.
I'll take a picture of what it displays after its cleaned but if anyone has any ideas what could cause this when all chips are confirmed working.
FYI: Frogger I loaded above was done via tape input. Many times loading from tapes will have the same/similar issue.
What I do:
* Power on computer with drive and Mario Bros disk mounted with FloppyEmu
* Computer beeps
* Computer beeps AGAIN but spits out junk similar to @bibilit issue he shared.
* Drive stops being read and game never loads
What I've tested:
* Drive works perfect in known fully working Apple II+ motherboard and Apple IIe computer.
* I tested ever single chip with known good ones from Apple II+ motherboard. RAM etc is all good.
* The 74LS283 was not the issue as I hoped like bibilit had.
* If I turn on the computer with no disk mounted THEN mount a disk it SOMETIMES will load BUT text is messed up in some apps
I'm currently deep cleaning the motherboard to see if anything changed.
I'll take a picture of what it displays after its cleaned but if anyone has any ideas what could cause this when all chips are confirmed working.
Last edited by a moderator: