nesdev.com

I'd recommend checking the controller ports to make sure all of the pins are making proper contact - a dirty connection on the D0, OUT, or CLK pins could cause a wide variety of problems, likely including what you're observing.

the PC will also seamlessly cross from one bank into the other if you let it reach the boundary (e.g. $DFFF->$E000). My recollection was that NESASM did not allow that, that trying to put more than 8KB in a single bank would either throw an error or silently discard everything past the end of the b...

Simple Vs. System games typically only support two 8KB CHR ROM pages, so it'd be fairly trivial to convert them to CNROM unless they rely on 4-screen VRAM (which most cartridges don't support).

Might I suggest finding a VT03/VT09 emulator rather than using an NES emulator?

Also, did you really need to resurrect a 3+ year-old thread rather than posting in the VTxx thread you already made?

In theory, the MMC1 could be initialized to any mode, which would require placing valid reset code at the end of every 16KB bank (in order to handle mode 2 as well as 0/1).

Всем привет белокожие друзья, нашла очнь интересный сайт, любителей животных. А увас есть такие фантазии по поводу вязки с человеком? напиши мне,хочу найти таких же людей чтоб вместе эксперементировать. Желательно с умелым кобельком. Ятемненькая девушка с афрканскими корнями, сейчас живу в России. ...

nocash wrote: ↑

Fri Jan 08, 2021 9:25 pm

Also have a look at a NES hardware reference (spam warning: try my own everynes.htm document, for example).

That's not spam - that's on-topic self-promotion, and there's nothing wrong with that.
For further convenience, here's a hyperlink to the relevant section of that document.

How does most emulators act when there is a unknown console type id? NintendulatorNRS and Mesen run it as a standard NES/Famicom. I do not know about any other emulators, but expect them to not react to that field at all. As of a few minutes ago, [standard] Nintendulator will display an error messa...

Juanreina wrote: ↑

Wed Jan 06, 2021 7:29 am

Sorry about that, I ment with having the vrc6 chip enabled. I can post the mml so you can see what I mean.

I take this to mean that having the VRC6 enabled makes it impossible to set the NES's builtin noise channel to the 93-bit "looped" mode (as opposed to the 32767-bit "standard" mode).

I'd be interested to know what the date code was on that MMC3C, since this new picture from furrtek's GitHub repo pretty conclusively illustrates that the MMC3C was CMOS (with 2 metal layers, no less), and the MMC3's been around for a lot longer than the MMC5 (which lidnariq seemed convinced was NMO...

However if some are willing to do the die analysis themselves, I can do plastic package decaps easily for almost no $. Imaging of dies smaller than 5x5mm is also possible but will take longer. My setup doesn't provide the best image quality so don't expect anything useful for finer processes (say b...

01:EDAA:EE 06 20 INC PPU_ADDRESS = #$00 Hm. Normally that would read the PPU internal open bus (pre-seeded to 0 by the above STX), then write 0, then write 1. Minor nitpick: the PPU's internal bus would be initialized by the "01:EDA5:AD 02 20 LDA PPU_STATUS = #$00" instruction immediately beforehan...

Those ROM images aren't copyrighted, are they? Because if they are, I'm pretty sure it's very against the forum rules to post them here.

I'd actually be interested to see the die picture, assuming it's available anywhere - regardless of how "very large and ugly" it might be belived to be, I have a feeling I'd be able to make more sense of it than the "wiring" SVG.

Someone added raytracing into a SNES chip. The SNES is from 1990 and uses mainly sprite graphics with 3d software rendering sometimes. But the PS4 and Xbox One, which are from 2013 can't do raytracing? Why? Someone explain this to me? Had you bothered to read the thread (and watch the linked videos...