From 7ae4b63fa326aa9d86ca8caa1ed32d6570ff3ee9 Mon Sep 17 00:00:00 2001 From: Andy McFadden Date: Mon, 19 Oct 2020 14:59:27 -0700 Subject: [PATCH] Tweak wording --- SourceGen/RuntimeData/Help/tutorials.html | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/SourceGen/RuntimeData/Help/tutorials.html b/SourceGen/RuntimeData/Help/tutorials.html index acf888d..479733a 100644 --- a/SourceGen/RuntimeData/Help/tutorials.html +++ b/SourceGen/RuntimeData/Help/tutorials.html @@ -397,24 +397,27 @@ wrong here. This particular file begins with 00 20, which could be a load address (some C64 binaries look like this). So let's start with that assumption.

Click on the first line of code at address $1000, and select -Actions > Remove Analyzer Tags. The $20 got absorbed into a string. The +Actions > Remove Analyzer Tags. This removes the tag that tells the +code analyzer to start scanning for instructions at that point. (By +default, a code start point is placed on the first byte of a new project.) +Note the $20 is now part of a string directive. The string is making it hard to manipulate the next few bytes, so let's fix that by selecting Edit > Toggle Data Scan (Ctrl+D). This turns off -the feature that looks for strings and .FILL regions, so now each -uncategorized byte is on its own line.

+the feature that automatically generates strings and .FILL directives, +so now each uncategorized byte is on its own line.

You could select the first two lines and use Actions > Edit Operand to format them as a 16-bit little-endian hex value, but there's a shortcut: -select only the first line of code, then Actions > Format As Word (Ctrl+W). +select the first line, then Actions > Format As Word (Ctrl+W). It automatically grabbed the following byte and combined them. Since we believe $2000 is the load address for everything that follows, click on the line with address $1002, select Actions > Set Address, and enter "2000". With that line still selected, use Actions > Tag Address As Code Start Point (Ctrl+H then Ctrl+C) to -identify it as code.

-

That looks better, but it's branching off the bottom of the screen -(unless you have a really tall screen or small fonts) because of all the -intervening data. Use Edit > Toggle Data Scan to turn the -string-finder back on.

+tell the analyzer to start looking for code there.

+

That looks better, but the branch destination is off the bottom of the +screen (unless you have a really tall screen or small fonts) because of +all the intervening data. Use Edit > Toggle Data Scan to turn the +string-finder back on. Now it's easier to read.

There are four strings starting at address $2004, each of which is followed by $00. These look like null-terminated strings, so let's make