NES Development Forums
https://forums.nesdev.org/
What about this?Espozo wrote:The guy who made it pointed me to it. I don't think a document like this is even on actual mame.
Those are called registers. The 80186 has the following 16-bit registers: AX, CX, DX, BX, SP, BP, SI, DI, ES, CS, SS, DS, FLAGS, IP. Additionally, AX, CX, DX, and BX can be accessed as pairs of 8-bit registers: AL, CL, DL, BL, AH, CH, DH, and BH.Espozo wrote:what things, (I don't know what to call them) are there in the 80186? I mean like accumulator, x and y
MAME names files based on the labels that would be visible to someone repairing their arcade system. The "extension" has nothing to do with the file contents; they're all just dumps of whatever was in the original ROM chips.Espozo wrote:I've never even heard of any of these file types before.
There is one file per chip.Espozo wrote:How can there be so many files?
MAME verifies files for accuracy, and will complain or refuse to run if the file doesn't match what it expects. You have to override this behavior to run a modified game.Espozo wrote:Mame acts like files are missing for some reason, so I remember someone made a .bat file that you run and it opens up some sort of debugging mode, where the game will actually run. Why it doesn't just run in the first place is beyond me, unless it looks and sees that the game isn't actually Super Side Kicks and stops you from attempting to run it.
I'll assume by "number" you mean "immediate", and by "register" you mean "the equivalent to 6502's absolute", which is called "direct". In NASM syntax, immediate values have no prefix or suffix, and direct addresses are inside [] square brackets. (YASM uses NASM syntax by default.)Espozo wrote:Oh, apparently, yasm doesn't recognize "#". How does it tell what's a number and what's a register?
Well, that's a lot... (or do the 65816 and 6502 just have a very small amount of registers? I recall ARM having about the amount you showed.)Joe wrote:Those are called registers. The 80186 has the following 16-bit registers: AX, CX, DX, BX, SP, BP, SI, DI, ES, CS, SS, DS, FLAGS, IP. Additionally, AX, CX, DX, and BX can be accessed as pairs of 8-bit registers: AL, CL, DL, BL, AH, CH, DH, and BH.Espozo wrote:what things, (I don't know what to call them) are there in the 80186? I mean like accumulator, x and y
Joe wrote:Espozo wrote:How can there be so many files?There is one file per chip.
Is each ROM chip kind of like a ROM bank? Why not just have one giant ROM bank?That's a bit silly... Why not just give a warning message but let you continue anyway?Joe wrote:MAME verifies files for accuracy, and will complain or refuse to run if the file doesn't match what it expects. You have to override this behavior to run a modified game.
Yeah, that's what I meant. I've been doing this stuff for almost a year now and I still don't know any of the terminology.Joe wrote:I'll assume by "number" you mean "immediate", and by "register" you mean "the equivalent to 6502's absolute", which is called "direct". In NASM syntax, immediate values have no prefix or suffix, and direct addresses are inside [] square brackets. (YASM uses NASM syntax by default.)Espozo wrote:Oh, apparently, yasm doesn't recognize "#". How does it tell what's a number and what's a register?
Code: Select all
mov [F8800], 1FExcept that you need to specify the size of the operand ... and I don't think you can specify a far address literally? But if you can, you'll have to specify it as a segmented pointer.Espozo wrote:So, If I were to take an "immediate" and store it in a "direct", I'd do something like this?Code: Select all
mov [F8800], 1F
In my experience while building the citations for my list of arcade system boards' pixel clock rates, the web-based source code viewer at mamedev.org appeared to have some sort of throttling on how many source code files I could view in a day, after which point I started getting errors. I might be confused about the cause of this though, and the move to GitHub might have started to fix things.Joe wrote:Why are you linking to the OpenEmu copy of MAME instead of... actual MAME?
What's the preferred way to override this behavior?MAME verifies files for accuracy, and will complain or refuse to run if the file doesn't match what it expects. You have to override this behavior to run a modified game.
For the same reason that several NES games have separate PRG ROM and CHR ROM chips: each one is connected to a separate bus. Also for the same reason that several Super NES games have several PRG ROM chips and very early NROM-128-class boards (RTROM and STROM) had two PRG ROM chips: sometimes two small chips are cheaper than one large chip.Espozo wrote:Is each ROM chip kind of like a ROM bank? Why not just have one giant ROM bank?
Are you asking because you don't know how, or because you want to ask me how I think you should override it? I use a .bat file that contains the following:tepples wrote:MAME verifies files for accuracy, and will complain or refuse to run if the file doesn't match what it expects. You have to override this behavior to run a modified game.What's the preferred way to override this behavior?
Code: Select all
(name of mame exe file here) (game rar name here) -debug -nofilter -video d3d -waitvsync -window
pauseWhich means it'd take about 15 minutes to make a tool to translate them in and out of Super NES 4-bit tile format by reinterleaving the bytes.Espozo wrote:Here's a cool little discovery I made: apparently, the graphics for the BG tiles (I haven't found sprites yet) are spread across 4 chips, one for each bit per pixel.
I recently discovered that MESS has a drum machine emulator in it.The only video output on this drum machine is a single HD44780 LCD, with 16x2 6x8-dot characters.Espozo wrote:-nofilter[...]I actually kind of like it better than Mame normally, because you don't have that dumb filter that makes me feel like my vision is even worse than it is.