As I've posted before I've got a Fire Shark board with problems. Attacking the hardware hasn't enlightened me much because of interesting design choices, and the 'well intentioned' POST is actually causing me lots of problems so I decided the best plan was to disassemble the game code, see how it works and then modify it to ultimately produce a test ROM a la Galaxians so that people with a duffer could burn a pair of ROMs and run something to help with diagnostics.
Well, I lost my first disassembly due to full retard mode and shuffling my main Windows install. So I restarted on Friday night from scratch and I've now got an almost fully commented disassembly of the non-game code - the self-test routines and diagnostics, as you can see if you look in the ukvac FB group https://www.facebook.com/groups/ukvac
At the moment I have a full understanding of what the POST does and how it does it, but it's all contained in an IDApro IDB file. Would anybody want to see an export of this that can be viewed without IDA?
Do you want to see how a game works?
(The IDA HTML dump is 70 MB so I need to investigate why it's soooo huge!)
My second objective is to produce some custom ROMs that you can plug into a non-working board that'll do their best to boot, report any faults as accurately as possible and ultimately do their best to run no matter the fault and give you an active board to probe about, instead of something that HALTs as soon as a fault is identified. From looking at the HW in MAME I think these ROMs will help anybody with a same-platform game so hopefully they'll be useful for other games on this HW and not just Fire Shark/Same Same.
So, any interest in this? Is anybody interested in the steps I've taken to patch out the helpfulness of the original code, keep the game running even though the HW has issues, and then the process of designing, creating and packaging the test ROMs?
I'm doing this whether I'm the only person to benefit or whether it appeals to 90% of VACcers but I figure that other than the awesome staff
, people come here because we have technical shizzle that's found infrequently on the internet so let me know whether you'd be interested in some pretty hardcore geek posts on what I've done, why, and how it's worked.
Oh yeah, and I've got an itch that needs scratching about porting a cool game to 68k hardware that a crappo footy-style game runs on. Kind of like a Pac2013.
TL;DR: Interest check in following in the vein of cmonkey but with a different architecture and game. Or choosing a game to see the (hopeful, I'm no macro so no promises) port from r@r3 hardware to common & sucky that people can do by burning ROMs and decimating the original HW price
Well, I lost my first disassembly due to full retard mode and shuffling my main Windows install. So I restarted on Friday night from scratch and I've now got an almost fully commented disassembly of the non-game code - the self-test routines and diagnostics, as you can see if you look in the ukvac FB group https://www.facebook.com/groups/ukvac
At the moment I have a full understanding of what the POST does and how it does it, but it's all contained in an IDApro IDB file. Would anybody want to see an export of this that can be viewed without IDA?
Do you want to see how a game works?
(The IDA HTML dump is 70 MB so I need to investigate why it's soooo huge!)
My second objective is to produce some custom ROMs that you can plug into a non-working board that'll do their best to boot, report any faults as accurately as possible and ultimately do their best to run no matter the fault and give you an active board to probe about, instead of something that HALTs as soon as a fault is identified. From looking at the HW in MAME I think these ROMs will help anybody with a same-platform game so hopefully they'll be useful for other games on this HW and not just Fire Shark/Same Same.
So, any interest in this? Is anybody interested in the steps I've taken to patch out the helpfulness of the original code, keep the game running even though the HW has issues, and then the process of designing, creating and packaging the test ROMs?
I'm doing this whether I'm the only person to benefit or whether it appeals to 90% of VACcers but I figure that other than the awesome staff
Oh yeah, and I've got an itch that needs scratching about porting a cool game to 68k hardware that a crappo footy-style game runs on. Kind of like a Pac2013.
TL;DR: Interest check in following in the vein of cmonkey but with a different architecture and game. Or choosing a game to see the (hopeful, I'm no macro so no promises) port from r@r3 hardware to common & sucky that people can do by burning ROMs and decimating the original HW price