nitro322

Thanks for the reply. What you describe makes sense. Just to confirm I'm understanding you, it sounds like you're saying the mirroring setting is inconsequential here as far as playback is concerned because the mapper will control it regardless. However, from an accuracy/preservation perspective, shouldn't the mirroring be set to the mode that's actually used, rather than specifying the "wrong" mode in the header and letting the mapper just correct that upon playback? If the dumper is going to set the mirroring bit in the header, but it sets the incorrect mode, wouldn't that be considered a bug? Obviously this is a minor issue in the grand scheme of things, just trying to learn more about this and, if appropriate, get any bugs fixed for anyone else using this functionality.

Kevtris, I mentioned a while back that I dumped all of my NES games using the CopyNES Mini. I was able to get all of my games dumped and verified against the No-Intro DAT file by stripping the header bytes (their checksums exclude the header). However, looking a little closer, I see that about half of them differ from my previously downloaded/verified ROMs in the header, with the Mirroring bit the differnce for most (if not all). It seems that nearly all the ROMs dumped via CopyNES Mini are set for Vertical mirroring, while most of the download ROMs use Horizontal. Mega Man 2 is one such example. The downloaded ROM uses Horizontal mirroring, and according to http://datacrystal.romhacking.net/wiki/Mega_Man_IIthat's correct (NesCartDB, for comparison, lists mirroring as "Mapper Ctrl" for this game). My dumped version is Vertical, though. The dumped version still plays fine on both the Nt Mini as well as an emulator. So... I'm not sure if there's some bug here or not. The difference doesn't seem consequential, but I'd like to understand what's going on. After going through all this trouble, I'd like my dumps to at least be accurate. :-) Can you weigh in here? I can certainly provide more info if you'd like (eg., see if there's a common mapper/plugin used in all of the game with this difference, etc.).

Thanks for the tip. Just tried your suggestion and got a clean dump. Much appreciated.

@kevtris, have a question and, I think, bug report for you. I just spent a few days dumping all of my NES carts with CopyNES Mini. Generally worked great, aside from some difficulties getting a clean connection to my carts (is it me, or is the Nt Mini more sensitive than a regular NES? I had a number of carts that work fine in my NES that I had trouble getting to boot in the Nt Mini.). Of the 90 or so games that I dumped, I was able to verify all but one against no-intro. The one that failed is Quattro Adventure, and unlicensed cart by Camerica. You appear to include an appropriate plugin for this (Camerica Quattro Carts), but I'm not able to get a successful dump. I'm consistently getting the same dump over and over, but it doesn't verify against no-intro and doesn't load in an emulator. I did some research and found another plugin for the Quattro carts (CAMERIC2.BIN) here: http://bootgod.dyndns.org:7777/plugins.php I don't know if those plugins are supposed to be directly compatible with CopyNES Mini, but I gave it a shot and got an interesting result. The internal checksum of that dumped copy does verify, and I can initially boot the ROM in an emulator to the game selection menu, but selecting any game causes the game to fail. I finally downloaded a ROM for Quattro Adventure and verified/played it. It has the same internal checksum as the dump from the bootgod plugin, but the file checksum between the two is different. Upon further examination, it appears that the different plugins are setting different memory mappers in the iNES header: * The downloaded/working ROM uses mapper 232 * The non-working ROM dumped with the included Camerica Quattro Carts plugin also assigned mapper 232, but as noted the internal checksum is different and the game fails to boot * The partially working ROM dumped with the bootgod CAMERIC2 plugin assigns mapper 1. I'm guessing this is why it initially loads, but then fails as soon as I select a game. So, two related questions: 1. Is there something wrong with the Camerica Quattro Carts plugin that can be fixed? 2. Should it be possible to use the plugins provided by bootgod with the Nt Mini? or is that expected to misbehave? Thanks again for all your work on this. And sorry for the longish post - kind of a weird issue to explain.

FYI, you can manually turn off the controller by holding the start button for 3 seconds.

Oh, one other question - I'm playing with the Game Boy core right now, and I have both DMGBIOS.BIN (original Game Boy) and DMGBIOS2.BIN (Super Game Boy) in the /BIOS directory as instructed. Played a couple test games and they work fine with DMGBIOS.BIN, but I can't figure out how to use DMGBIOS2.BIN. The Game Boy core README says: "You can have an alternate if you wish, such as the Super Gameboy bootstrap which skips the scrolling intro (not sure if this will affect any games but it seems to work). This alternate should be named "DMGBIOS2.BIN" and lives in the /BIOS directory as well." How exactly do I use the alternate? Is there some setting for this that I'm overlooking? or do I need to launch the core or ROM with a different button or something to activate it? Edit: Nevermind. Just read the main README again and noticed that pressing start while a core is loaded will give you core-specific settings. Found what I needed there and it's working fine now.

Thanks, Fafner. It's not easy finding the latest release by just browsing through every page of this thread, but I found this link to view only kevtris' posts and was able to find it that way. Hope it helps someone else (you may need to be logged in to view it): https://atariage.com/forums/index.php?app=core&module=search&do=user_activity&search_app=forums&mid=32195&search_app_filters[forums][searchInKey]=&userMode=content kevtris - obviously you're free to post updates however you'd like, but you may want to consider updating, say, the first post in this thread or perhaps a page on your website with the latest version to make it easier for new users that haven't already been following this thread for weeks to get started. Regardless, the 1.6 update is pretty damn sweet. Thanks. :-) Regarding FDS support, I don't have an EverDrive, but I do have a PowerPak. Will try that out later on. Thanks for the tip. Sorry to hear you're having trouble. I just got my Analogue Nt Mini as well, and it's working flawlessly. Hopefully someone can give you some suggestions to make it work, but if not you may want to reach out to the manufacturer. Mine definitely isn't behaving that way.

Hello, all. I just received my Analogue Nt Mini today, which I bought almost immediately after learning about the jailbroken firmware (only delay was waiting for the Analogue store to get units back in stock). May be kind of a silly reason, but I've been wanting to dump my NES carts for years now, so the software CopyNES built-in to this was the clincher for me. kevtris - thanks so much for your work on this. I already have everything up and running on kevtris' firmware, but I had a couple questions I was hoping someone could clarify: * What's the "official" link for kevtris' firmware updates? I got the 0.9 version from page 48 of this thread, but I have no idea if that's the latest version or not. Is there a single source I can go to to always find the latest version? * I've seen lots of discussion about additional cores, but my copy of the firmware only includes the NES core. Where can these additional cores be downloaded? * Finally, I spot checked a few NES ROMs and they all seem to load fine, but my FDS ROMs are not listed in the NES core menu. Is FDS not supported at this time? I'm guessing that's the case, but wanted to confirm. Thanks in advance. :-)