Indent starting hex?

Hi,

I’m working on reverse engineering a program and I’ve got an overlay open in 010. I’ve used the Set Starting Address function to set the offset column to mirror where the overlay appears in the system address space, but the problem is that it starts at an address that isn’t a multiple of 16 (specifically dealing with PS1; the starting address is 0x800D61D8.) The editor functions fine, but the column headers in the hex editor no longer match the actual address space (column 0 references addresses 800D61D8, 800D61E8, 800D61F8, etc). Is there functionality in 010 that lets me effectively have eight empty spaces (not nulls) at the start of the editor so that the first byte in the file renders in the 8 column?

I don’t believe there is any way to automatically add in extra bytes at the beginning of the file to make the columns line up. This is something we’d have to add to a future version. You could try setting the starting address to 0x800D61D0 or even copy the data you want to display to a new file and then add 8 extra bytes at the beginning.

Graeme
SweetScape Software

Thanks; for the moment I’ve added the eight extra bytes. I’ve got a bunch of these to go through but being able to eyeball addresses should only be strictly necessary for the very first time I’m dealing with them. For most everything else afterwards I’ll probably end up primarily digging through them with Ghidra and directly jumping to the relevant addresses in 010.

Thanks again!