Hello, Next week I will receive Ballon Kid prototype game on GameBoy. It come from original 1stparty Nintendo prototypes. Did you think this game will be different than commercial Ballon Kid? Anyone know this cart? Best Regards, Trevormacro I just receive the proto. How can I dump the eprom? with my LPC-32 device? What is the size can i chose on Smartchip appz? to dump it.
I have FM27C010 with buffer 128 Ko is it good? It's very hard to remove the eprom from cart why? Removed OK I dump with my device (27C010) in .bin file but when i want to read with an emulator don't work why? Here is the Hex: Why the proto don't work? nb. on the dev cart we have a chip named DMG MBC A too. This chip is soldered on the cart. Perhaps It's for that we can dump the eprom 128 ko. I have Flash Linker device and GB bridge like that http://www.eagb.net/advance/hardware_review_images/hr13_02.jpg Is it possible to dump ballon kid proto with my device?
Doesn't look like there is anything there. Just 0s and 1s. Really, like I said before, you shouldn't be dumping these chips with an EPROM reader if you don't know what you are doing, because there is a real risk you could damage the EPROM.
Hello badinsults, It's not damaged, look: The game running on my GBA advance (Asia version). Who can see any differences with the final version?
The point is that if you don't know what you are doing, you can wreck the data on the EPROM with the EPROM reader. You of all people should know this, considering that you own that damaged Estpolis II prototype. There are far safer ways to dump prototypes than with an EPROM reader, and if you plan on getting a lot of these, you should look into getting a standard cart dumper, like the Retrode (I believe they have an adapter for the Game Boy). I mean, it is pretty clear you don't really know what you are doing, because you didn't dump the chip properly.
Seeing as how it says "Sample" it probably has few if any differences from the retail version. As for why it did not dump correctly, it could be many reasons. Perhaps the chip was not seated well in the programmer socket when you attempted to read it. Perhaps you have a problem with your reader device. Perhaps you have a software problem.