ROM Fiend: A DeclROM, Extended DeclROM, and System ROM parser
- Thread starter eharmon
- Start date
As a tree? Sadly no. You can copy individual property values, or the data sections they point to and export that way.
That and highlighting spans in the hex are really features Hex Fiend is lacking.
What do you mean by highlighting spans? It will highlight a length of bytes that is the size of the item selected in the template.
I've created forks for these:
GitHub - joevt/68k-mac-rom-maps
Contribute to joevt/68k-mac-rom-maps development by creating an account on GitHub.
github.com
- Add more ROM Maps (including some for PowerPC Macs).
GitHub - joevt/rom_fiend: Macintosh ROM file template for Hex Fiend
Macintosh ROM file template for Hex Fiend. Contribute to joevt/rom_fiend development by creating an account on GitHub.
github.com
- Map more ROMs to existing and new ROM Maps.
- Use ROM Map to label pointers and offsets.
- Parse ForeignOS.
- Parse Dispatch Tables.
- Parse Universal Tables.
- Fixes and improvements.
GitHub - joevt/HexFiend: A fast and clever hex editor for macOS
A fast and clever hex editor for macOS. Contribute to joevt/HexFiend development by creating an account on GitHub.
github.com
- Copy nodes as text.
- Hex view uses a different shade for bytes that might not be part of the selected section in the template view.
- Add a
sectiondepthcommand. - View selection range and size in hex and decimal.
Attached a list of ROMs. Each ROM may have M and/or U flags.
- M = has ROM Map (the ROM Map being used is also listed)
- U = has Universal Tables
