Note for mods - I've opted for this forum rather than 'Technical Discussion' as my use case relates specifically to 68K memory mapping but feel free to move if you think it would be more appropriate there. Also please be aware I have a link to my site in the post below, hopefully this doesn't set off your spam-dar! Hey folks, I'm in the process of revamping a section of my site in preparation for a large, long term project and wanted to get your thoughts on the best way to visualise ROM / RAM memory maps along with a bit of feedback on what I've went with so far (if you would be so kind!). You can see what I've went with on the site here: http://www.mybrillgamesite.com/projects/?id=86 and I like to think it is pretty self explanatory. The ROM: section is the section I have updated, the Savestate: section is how it originally looked now updated. Down the line I'll be adjusting the Savestate section as well to be the RAM section, adjusting the offsets as a result, giving it similar headers and functionality along with the ability to show / hide the offsets adjusted for savestates created in different emulators (currently they show only GENS). The layout is based on what I think is useful to have and takes inspiration from the layouts I've seen here at SonicRetro, on the Super Mario World disassemblies and in other people's hacking notes. Nothing is set in cement yet and I'm still not sure about peripheral things like the borders I'm using, what other items will appear in the key, what exactly will appear in descriptions, so if you see anything at all you think is missing / would be useful please let me know. Note also that the 'Opcode / Hexcode' column is intended to be 8 bytes wide because I think that's the longest a typical 68K instruction is, isn't it? I know it can be longer with pre and post statements but in practice I should have enough width to display all code there, right? Links to other sites with good examples also welcome and any questions please ask. Note - The section marked 'Unknown' is still to be populated. I've got the disassembly here and want to get it displayed line by line once the section is expanded. Should be up in the next few days. Additional Note - If you've already saw this topic over at RHDN then don't worry, you don't have to reply twice, I'm monitoring both to get the opinions of both communities and expect there will be a little bit of member overlap.