Sprinter/mame
2
0
Fork 0
mirror of https://github.com/holub/mame synced 2025-05-10 08:12:13 +03:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

More notes (nw)

Browse Source
This commit is contained in:
angelosa 2017-06-18 05:09:38 +02:00
parent df2aee136d
commit 60994ee870
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/mame/drivers/terracre.cpp
View File

@ -181,11 +181,12 @@ READ16_MEMBER(terracre_state::amazon_protection_r)
{
if(m_mAmazonProtCmd == 0x37)
{
//m_mAmazonProtReg[4] bit 0 used on hiscore data (clear on code)
//m_mAmazonProtReg[4] bit 0 used on hiscore data (clear on code), 0x29f vs 0x29e (not an offset?)
//its usage is more variable in mightguy for whatever reason.
uint16_t prot_offset = (m_mAmazonProtReg[1]<<8)|(m_mAmazonProtReg[2]);
uint8_t *prot_rom = memregion("prot_data")->base();
//printf("%02x",(prot_rom[prot_offset] - 0x44) & 0xff);
//printf("Mode %02x:%04x %04x R -> %02x (fixed %02x)\n",m_mAmazonProtReg[0],prot_offset,(m_mAmazonProtReg[3]<<8)|(m_mAmazonProtReg[4]),prot_rom[prot_offset],(prot_rom[prot_offset] - 0x44) & 0xff);
return prot_rom[prot_offset & 0x1fff] - 0x44;
}

1
src/mame/machine/nb1414m4.cpp
View File

@ -13,7 +13,6 @@ TODO:
- first byte meaning is completely unknown;
- Ninja Emaki triggers unknown commands 0x8000 & 0xff20;
- Ninja Emaki continue screen is corrupt;
- How to NOT draw the params?
Notes:
- Just before any string in the "MCU" rom, there's a control byte, this meaning is as follows: