Hey, figured I'd drop by since I had just noticed this was discussed here. It's my cartridge lol.

The anago_wx.exe I have matches the given MD5.I tried each IPS patch (with Lunar IPS), checked MD5 (if it was different after patching & checked consistency) as well each time with CertUtil -hashfile anago_wx.exe MD5. Each time it was still giving the 0x8000->0x10000 address error.

I'll try to recompile it on my old computer as well, might be able to… or not…

I'd like to be much more around but the studies are eating my time, plus the fact I don't have knowlegde in Famicom emulation.

Anyway, I'm also currently pushing the guy who has the dump to release it might be hopeless but I thought it was worth a try as well. I don't want to bother you guys too much for just one cartridge… But at least it's good to see that anago will get a flaw like that removed (at least in custom builds).

...but it doesn't look like I can successfully emulate it in MAME anyways. The bank at 0x7000 appears to be the extra "BANK 0" that is mentioned within the comments. I combined the main 32K PRG chunk from the NROM readout, put the 32k and 64k chunks first, and the main 32K PRG chunk last to hopefully create a representation of what is in the actual mask ROM. The startup looks to be okay, but after a couple of bankswitches, the emulation freaks out and jumps to data.

So, I'm having an issue with the kazzo. It's been working fine for almost a year now and I've been able to dump all sorts of games with it. However, my computer hasn't been able to recognize it.

- Using Windows 10- Each time I plug it in, Windows says "the last USB device you connected malfunctioned, and Windows does not recognize it"- Anago always displays a Reader open error message- Vendor ID and product ID for the device read "0x0000" and "0x0002" respectively in the inf-wizard- recently replaced the part where you plug the cable in (yay, soldering practice for the n00b!), BUT, even after the repair, it worked- Tried loading the Microsoft OS with driver signature enforcement disabled, tried loading with it enabled- Tried unplugging and replugging-in the dumper- Tried two different computers- Tried different cables

just replied to the ticket you sent me. Curious if it's recognized by windows in boot loader mode and if so, if you PC is able to recognize it when flashed with my firmware.

Just solved the issue! Thank you so much for your quick reply. The PC did recognize it in BL mode. I didn't quite know where to go from there when I first found that out, so I tried reinstalling the firmware and now it runs fine. Thanks so much.

Unfortunately, it isn't yielding a workable ROM and the script only works in the 062 command line version of anago. The crc32 output is 0xcfb3e8b9. Does anyone know where I can find a working script for the game?

Edit: It turns out that it is yielding a ROM that works, but one only to an extent. The title screen shows and I can press start to get past it (with sound effect), but after that there's just a black screen.

Hello. I assembled the dumper according to this conceptual scheme - I use the program - anago_wxThe cartridges are read correctly. Read 0,1,3,4 mappery - all is well!But I can not understand how to record games on cartridges. I need to know where and what signals from FLASH memory need to be connected. I use memory - W29C020. I am very grateful for the help!

Hope I'm not breaking any rules here; it was recommended that I ask in this thread about the following problem.

I just got a copy of Ganbare Goemon Gaiden and it doesn't seem to want to be dumped. I've been trying to use the VRC2 scripts found here and here, but to no avail. The process always goes up to about 15/16 of the way through the CPU dump and then Kazzo gives me the following error:

Code:libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning.

I've tried everything I can think of:- opening and cleaned the cart several times- using both versions of anago (60 and 62)- doubling both the CPU and PPU rom dump ("d22" command in command prompt)- exchanging the commands in the script to "dofile" for the script in the vrc4.ai file- getting rid of the "dofile" line altogether

I've run the game through other scripts (e.g. mmc3.ag) as well just to see if it was only the script. I've also tested another game to see if I needed to reinstall the kazzo's firmware or something. Everything else checks out. Is the game corrupt? And if that's the case, is it just a matter of buying another copy?

Who is online

Users browsing this forum: No registered users and 6 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum