Hoping someone can help me with this.
I've fired up my Kazzo on my Windows XP machine finally. Followed all of the installation steps; everything seems to have gone smoothly, but the only difference is that even after changing the device's firmware to the Kazzo's (for dumping), it still appears as INL-Retro Prog in Device Manager (EDIT: Did a re-install and it now appears as Kazzo). I didn't think much of it because the whole installation process went otherwise problem-free.
I decided to get on with backing up some games. I have Blades of Steel and Duck Hunt North American carts for testing. BoS appears to be backing up fine, but it turns up a different checksum for the ROM every single time; of course, the ROMs don't work when testing on an emulator (update: some of the several more attempts created ROM files that do work in emulators, but again, they're different each time and also different from the known retail checksum). The cartridge has no issues and I've selected the correct script (UNROM). Duck Hunt simply won't be dumped at all, giving the error:
AN ERROR HAS OCCURED [the index 'ppu_rom' does not exist]
*FUNCTION [dump()] dumpcore.nut line 
-When the cartridges are inserted, they are fitted, but can still wobble back and forth a fair amount. I'm fitting them with the orientation shown here: http://www.neogaf.com/forum/showthread.php?p=72806661
-What does the red light indicate? It turned on during the installation process, but hasn't since then.
Any help is appreciated.
UPDATE: I have now successfully dumped both cartridges. It turns out the culprit was the anago gui; command line version dumped both without a hitch. The BoS cart was being dumped incorrectly in the gui anago because I chose the unrom.af script (which was the only one); the folder for the command line version had the unrom.ad, so I copied that into the former's folder and checked if that would fix the issue. Instead, it gave the same error as for using nrom script. So it seems I'll have to settle with using the command line. Others have reported using the gui version without this problem, so perhaps I need to roll back my Kazzo firmware even further...?