Donkey Kong Forum
General Donkey Kong Discussion => General Donkey Kong Discussion => Topic started by: ken on June 30, 2018, 03:36:47 pm
-
Hey all,
I just got a new pc and installed wolfmame then dropped in my dkong rom in a roms folder, which I believe is all I did on my last computer. However on this one I'm getting the following error in command prompt:
"diag.bin NOT FOUND (NO GOOD DUMP KNOWN) (tried in dkong dkong)
WARNING: the machine might not run correctly."
The game seems to run fine besides that warning but it's still curious. Could anyone guide me on how to resolve that?
Thanks!
-
This is a new error message in recent versions of MAME. I guess there was supposed to be a diagnostic ROM somewhere, but it doesn't exist. There's nothing to fix and it won't cause any problems in MAME. So, just ignore it.
-
That being said, if you do want to find a good dump, I suggest trying the crap tournament
-
That being said, if you do want to find a good dump, I suggest trying the crap tournament
I see what you did there. Well played.
-
This is a new error message in recent versions of MAME.
Oh good, so they added a reference to a ROM that has never been dumped, and will never be dumped, and that almost certainly never existed, so that this error message can appear for the rest of eternity.
Meanwhile, they refuse to make the bugfixed version of Mario Bros. the parent ROM set, and the DK Junior P-kit is "definitely not from Nintendo" solely because the checksum doesn't match the one printed in the service bulletin.
MAMEdev's infinite wisdom strikes again. ::)
-
they refuse to make the bugfixed version of Mario Bros. the parent ROM set
Oh, that's what I get for not upgrading for 10 months, looks like they fixed this in 0.195. Kappa
Clone "marioo" has finally been upgraded to parent "mario"! The war is over! Kreygasm
-
they refuse to make the bugfixed version of Mario Bros. the parent ROM set
Oh, that's what I get for not upgrading for 10 months, looks like they fixed this in 0.195. Kappa
Clone "marioo" has finally been upgraded to parent "mario"! The war is over! Kreygasm
Thank god. I logged this with MAME Dev back on 2009 and one of the MAMEDevs at the time even said that the marioo set clearly had a defect fix in it that made it clear it was a later release so should be the parent. But took them 9 years to actually change it back to be correct.
-
Why will MameDevs code to verify a ROMSet to have a nonexisting rom file?
It seems they do not use their brains really? Coding in errors that will never be fixed?
Does the original DK machine contain a diag.bin rom chip that should have been dumped?
-
This actually goes all the way back to Radarscope. On the Radarscope boards and DK 4-board stack, there is an empty fifth program ROM socket that appears to have been intended for a diagnostic EPROM (which has never been documented) which would be accessed via a service switch (which has also never been documented).
The switch and the EPROM are actually known to have existed, or at the very least intended, because there is an input port for this mystery service switch, and instructions in the code (at $0075) to jump to location $4000 in ROM space if that switch is pressed. Since the game code ends at $3FFF and is physically limited to that address, this could only be a reference to a location on a fifth EPROM.
In MAMEs prior to 195, hitting the service switch (F2 on the keyboard) would add a credit, which is the behavior we know from the PCB. In 195 and later, this function was demoted to a secondary service switch (9 on the keyboard), and now the missing mystery service switch is the primary (F2) one. When you hit it, the switch behaves "correctly" by crashing/resetting the game, because it's trying to jump to $4000 in ROM space, which isn't there.
If this diagnostic ROM ever actually existed, it was only used internally during development and was never part of any final release. (And by the time the two-board stack came out for DK, there was no longer even a physical socket for it on the PCB).
MAMEdev is just being thorough. The code explicitly implies another EPROM chip, in addition to there being a physical socket for it on the original boards. They know that it was there at some point, or at least planned, so they hooked up the dkong driver to it.
Zero chance that it ever gets found or dumped though, so enjoy the error message forever. :)