nesdev.org

Did anyone ever get Pilotwings working on their PowerPAK? All other DSP1 games I tried (all those released outside Japan) seem to work fine with the PowerPAK with DSP1 upgrade. I'm wondering if figure 2-21-2 on page 2-21-3 of the you-know-what book wasn't taken into account. There's a note stating ...

It may be a little bit off-topic but related to the snes powerpak. I may have missed the reason in all the messages that was posted but want to know: what make it so hard to make the powerpak work on many snes revisions compared to the game doctor that seemed to work on any machine? I'm just curiou...

I see. So there are many cause in this. But is the others ones like the myth (?) one have the same issue? Did the game doctor, super wild card (?) etc had those issue in the past too? I don't know about the Neoflash myth. Floppy drives are mediocre in terms of reliability and speed. And yes, copier...

It may be a little bit off-topic but related to the snes powerpak. I may have missed the reason in all the messages that was posted but want to know: what make it so hard to make the powerpak work on many snes revisions compared to the game doctor that seemed to work on any machine? I'm just curiou...

dude.

wait for your operation to complete. You've got to burn, don't quote me on this, 8 cpu cycles.

no i can't tell you.

but what I can tell you, is that a 29F080 is only 1 megabyte in size,
so only address bits A0 to A19 on the flash chip matter.

And "inverted" is incorrect terminology. I don't see not gates or inverters anywhere. The labels are swapped. Why? No idea.

tairan, we need specifics. Please verify your files are actually rom images, not savegames / .zst's / etc. The most helpful would be to use NSRT http://www.romhacking.net/utils/400 I'm tending to believe the " No Internal Header Found Check the unsupported games list or verify your game file is...

Hey, nobody should be embarrassed right now. None of this stuff is intuitive. For info on the internal header, it's in the official SNES developer manual (google is your friend). The Powerpak log.txt confirms it can't find a viable internal header, so it's either guessing wrong or doesn't know what ...

Have you checked to see if your homebrew rom image has the official "Nintendo" information near where the interrupt vectors are? As in, the information about the Internal Name, checksum, mapper (mode 20, 21, etc), ROM size (power of 2), Battery RAM size, version, etc. Unless we hear from t...

Reading the ram doesn't make it fail, it's the write/erase that causes problems. ... however someone could have used it as extended ram (much like the gba-port ram on nintendo ds) but i don't see why to worry about that btw I just read the datasheet for FM18L08 , don't think it's any good for your ...

yeah, I mean, unless you sit in a tight loop reading or writing the same location over and over again, it's really hard to hit that kind of a limit, but that's what I'm searching for. With the assumption of 10^12 reads of a given byte, 60 times a second, it'll take 528 years to fail. If you read a s...

With some buffering after the CE signal, I connected an access light LED, and in some cases an audible logic probe. Playing different games, I noticed that they are in general very well behaved about accessing the battery RAM (Again, the fear was that it would be reading constantly from the battery ...

....After months of use and abuse, I can report that it actually works without issue, but requires glue logic. Okay, let's back up a second, what am I talking about? No doubt the backup battery in some of your SNES cartridges have gone dead, not allowing your saves to last beyond power off, or, in s...

I know this is completely obvious, but: For all the people who can't get this to work, PLEASE, PLEASE clean your console connector before complaining. It isn't good enough to say that "my other games work fine". I doubt there is a good way to check for marginal physical contact in software...