TW ROM does a JSR to print routine and then provides in-line vertical row,
length byte and then string in high ASCII.
6502bench has done a pretty good job determining strings in TW ROM, but
needed a little help for a couple of sequences. I think a $0d in the code
may have been interpreted as a CR and caused the interpretation to fail.
Anyway, I don’t mind that, but I’m having trouble cleaning it up.
Why does ‘Strings prefixed with 1 byte length’ display the string as comma
separated hex bytes (see screenshot)
https://www.flickr.com/photos/10917598@N06/51446203131
I would expect a display like .str
Why can’t I use ‘Display As’ to elect how it should be displayed?
(Despite reading the help, I don’t understand why the operand dialog shows
‘Display As…’ Hex for a .str operand - that doesn’t make sense to me)
(Needing to select all the data for the string had me scratching my head
for a while after the last enquiry resulted in using Tag/hints sparingly,
but I got there in the end)
Thanks,
Andrew