Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://fsebugoutzone.org/objects/a53c15d6-e986-4fcd-84c2-ccd8a1ea412f">pistolero (p@fsebugoutzone.org)'s status on Tuesday, 01-Oct-2024 16:50:49 JST</a><a href="https://fsebugoutzone.org/users/p" title="p@fsebugoutzone.org"><img src="https://gnusocial.jp/theme/gnusocialjp/default-avatar-stream.png" width="48" height="48" alt="pistolero" style="position: absolute; left: 0; top: 0;">pistolero</a><div><a href="https://fsebugoutzone.org/objects/2e9fd46d-5719-4b4e-8afe-07778cce35f0" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/265863" title="silverdeth@fsebugoutzone.org">SilverDeth</a></li></ul></div></section><article><a href="https://fsebugoutzone.org/users/SilverDeth">@SilverDeth</a> 620 locations have 0x1b in them and it turns out that the memory map is kind of complicated ( <a href="https://www.nesdev.org/wiki/CPU_memory_map">https://www.nesdev.org/wiki/CPU_memory_map</a> ) but if I just guess based on the format having a 16-byte header ( <a href="https://www.nesdev.org/wiki/INES#iNES_file_format">https://www.nesdev.org/wiki/INES#iNES_file_format</a> ) that the 0x1b at 0x98d6 in the ROM is not a coincidence and change it to 0xee (a one-byte NOP, apparently there are lots of NOPs aond some of them ar two bytes:  <a href="https://www.nesdev.org/wiki/CPU_unofficial_opcodes">https://www.nesdev.org/wiki/CPU_unofficial_opcodes</a> ) then *this* version runs in at least NEStopia.<br><a href="https://fsebugoutzone.org/media/01a7d2d6-df78-4173-b7ba-ad2c2c46ac45/100.nes?name=100.nes">100.nes</a></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3720357#notice-7351577">In conversation</a><time datetime="2024-10-01T16:50:49+09:00" title="Tuesday, 01-Oct-2024 16:50:49 JST">about 2 months ago</time> <span>from <span><a href="https://fsebugoutzone.org/objects/a53c15d6-e986-4fcd-84c2-ccd8a1ea412f" rel="external" title="Sent from fsebugoutzone.org via ActivityPub">fsebugoutzone.org</a></span></span><a href="https://fsebugoutzone.org/objects/a53c15d6-e986-4fcd-84c2-ccd8a1ea412f">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3245070">100.nes</a></label><br></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://www.nesdev.org/wiki/CPU_memory_map">CPU memory map</a></h5><div></div></header><div></div><footer></footer></article></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://www.nesdev.org/wiki/INES#iNES_file_format">INES</a></h5><div></div></header><div>The .NES file format (file name suffix .nes) is the de facto standard for distribution of NES binary programs, with use even in licensed emulators such as commercialized PocketNES and Wii Virtual Console. It is often called the iNES format, as it was created by Marat Fayzullin for an emulator called iNES. The format was later extended with NES 2.0 to fix many of its shortcomings.</div><footer></footer></article></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://www.nesdev.org/wiki/CPU_unofficial_opcodes">CPU unofficial opcodes</a></h5><div></div></header><div>Unofficial opcodes, sometimes called illegal opcodes or undocumented opcodes, are CPU instructions that were officially left unused by the original design. The 6502 family datasheet from MOS Technology does not specify or document their function, but they actually do perform various operations.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
pistolero (p@fsebugoutzone.org)'s status on Tuesday, 01-Oct-2024 16:50:49 JSTpistolero
in reply to
- pistolero
- SilverDeth
@SilverDeth 620 locations have 0x1b in them and it turns out that the memory map is kind of complicated ( https://www.nesdev.org/wiki/CPU_memory_map ) but if I just guess based on the format having a 16-byte header ( https://www.nesdev.org/wiki/INES#iNES_file_format ) that the 0x1b at 0x98d6 in the ROM is not a coincidence and change it to 0xee (a one-byte NOP, apparently there are lots of NOPs aond some of them ar two bytes: https://www.nesdev.org/wiki/CPU_unofficial_opcodes ) then *this* version runs in at least NEStopia.
100.nes
In conversationabout 2 months ago from fsebugoutzone.orgpermalink
Attachments
1. 100.nes
2. No result found on File_thumbnail lookup.
  CPU memory map
3. No result found on File_thumbnail lookup.
  INES
  The .NES file format (file name suffix .nes) is the de facto standard for distribution of NES binary programs, with use even in licensed emulators such as commercialized PocketNES and Wii Virtual Console. It is often called the iNES format, as it was created by Marat Fayzullin for an emulator called iNES. The format was later extended with NES 2.0 to fix many of its shortcomings.
4. No result found on File_thumbnail lookup.
  CPU unofficial opcodes
  Unofficial opcodes, sometimes called illegal opcodes or undocumented opcodes, are CPU instructions that were officially left unused by the original design. The 6502 family datasheet from MOS Technology does not specify or document their function, but they actually do perform various operations.

Public

Embed Notice

HTML Code

Corresponding Notice