SpritesMind.Net

Lab313ru ( DrMeFistO ) , an amazing contributor to the reverse engineering scene has made some awesome Plugins for IDA Pro And Ghidra

The IDA Pro Plugin lets you debug in IDA pro itself with all IDA pros abilities. You are at the same time running the ROM using his modified version of Gens Emulator ...

Awesome work. This is a dream tool of mine to have annotated disassembly and trace logger. Keep up the fantastic work.

Does an annotated disassembled feature or plugin exists for exodus. Using map/ list file it could be done with The Macro Assembler AS or ASM68k. Is Nemesis interested in this idea?

Here is the code in its early stage . You put trace in the scripts directory and name it trace.log. Put list file also in same directory and rename it


TraceFileHandle= assert(io.open("trace.log", "r"))
local TraceLines = TraceFileHandle:lines();
local Output = assert(io.open("Output.txt", "w ...

My script ( hopefully ) works on any disassembly that uses ASW. I could find annotated disassembler feature in an Emulator that works with ASW (AS.exe) . So I wrote a Lua script that takes two inputs. A trace file you made with gens-re-record and the games list file generated by ASW. It outputs to a ...

Anyone know if it is safe or a r57shell backdoor.

Cero-Are you saying because you can go through very line if code and reverse engineer what its doing ? Isn't that painful?"

Is the Gens r57shell mod a r57shell backdoor or is it a safe.

Are some features not available with just snasm68k.ex’s like coff files and:

- SNBUG68K.EXE
- SNLINK.EXE
- SNLIB.EXE
- SCSILINK.EXE
- SNMAKE.EXE
- SNCOPY.EXE

I may not fully understand SN package and Snasm . Are there features you can’t do with just snasm68k.exe alone? Will some snasm68k ...

Are some features not available with just snasm68k.ex’s like coff files and:

- SNBUG68K.EXE
- SNLINK.EXE
- SNLIB.EXE
- SCSILINK.EXE
- SNMAKE.EXE
- SNCOPY.EXE

I may not fully understand SN package and Snasm . Are there features you can’t do with just snasm68k.exe alone? Will some snasm68k ...

Using r57shell . So I have the. 68k debugger with breakpoints enabled. I have the VDP ram window open and if I the debugger hits a breakpoint and following code writes data to vram using the VDP data port , it won’t update it in the VDP ram window unless I scroll the scroll bar in the VDP ram window ...

Thank you very much Miquel. Sorry for late reply been doing disassembly stuff on s3k. I will look at the response tonight. Thanks

The CRAM is 64 9-bit words. We access the memory as a word in format 0000 bbb 0 ggg 0 rrr 0. When they say it is stored in CRAM as a 9-bit word , does this mean that all the zeros are not there and its just bbbgggrrrbbbgggrrr...etc for 72 bytes? The description of a "word" is what confuses me as it ...

Anyone got suggestions comments on emulators that support symbol table mapping to show the run routine and and alike names of labels?

Thanks. So what I had been taught that a # indicated an immediate value , so $FFFF doesn't have a # in front so that is enough to indicate it is an address and not a hex value literally . Why is () necessary for some assemblers if not having a # denotes an address?