

FROM:    KEITH HEITMANN   (GVXV90A)

You have to remember DEBUG numbers all files
from 0100 and does NOT have sector numbers like PCTOOLS and
NORTONS that start numbering at 0000 and divide the files
into 512K byte (0FFF) sectors. When DEBUG starts a new
sector the number usually jump 100. Sector 1 (which is the
second sector of a file in PCTOOLS) byte 0000 is actually
0200 in DEBUG. When you see an address for PCTOOLS or
NORTONS posted you just add 100 to the number. Example:
PCTOOLS address: 00AF
DEBUG address: 01AF

You will need to be familiar with hexadecimal numbering
since DEBUG supplies you with considerably less secondary
information about the file you are examinining than PCTOOLS
or NORTONS.

Example:
Normal decimal numbers: 0-15
Hexadecimal number equivalents: 0-F
All numbering starts with 0 as the first byte.
In hexadecimal numbering numbers 10 thru 15 are letters A
thru F. So the numbering goes 1.....9, A, B, C, D, E, F
0 through F is sixteen bytes.
To examine a file with DEBUG you have to type:
DEBUG filename.ext <ENTER>
This loads the target file into DEBUG.
D 0100 <ENTER>
This "dumps" or "displays" the hex code of the file to the
screen starting at byte 0100. This command only displays 128
bytes at a time.

To see the next 128 bytes that follow the ones called above
you press D <ENTER>. If you want to display the file from
the 64th byte lets say onward, you would type D 140 <ENTER>.
This will only display the file starting from the 64th byte
onward. Bytes 0-63 will not appear.
To edit a byte you type E xxxx yy <ENTER> whre xxxx is the
bytes address (location) and yy is the new value you want to
substitute.

I strongly recommend that you have a backup copy of the file
on hand in case you make an error and can't repair it. Or as
you change bytes one at a time, you jot down the original
value you changed, so if your change does not work you can
put the right value back in to its proper place. You should
jot down the address of the byte and the byte's orginal
value.

To save a change to the disk you type:
W <ENTER>
To quit DEBUG you type Q <ENTER>.
These are just the basic commands for DEBUG. There are more
that even I am not totally familiar with. You can hex edit
with DEBUG, but be warned, it is not a "friendly" program to
use.


TIME:    08/03  5:26 PM
FROM:    RICHARD BARCLAY   (KGXC61A)
SUBJECT: SWOTL GROUP

Trent, from one beginner to another, here goes.  First, make
sure you have a copy of DEBUG.COM in your \SWOTL\AC subdir.
The proceedure is as follows:
DEBUG [filename.ext]  <ENTER>
-E [byte address] [value change] <ENTER>
-W <ENTER>
-Q <ENTER>             more.....
What you have done, on a line-by-line basis, is to activate
the debug utility by having it open a specific file.  When
debug has done this you will see a hyphen on the next line,
which is debug's prompt.  On the second line, when you type
"E" (don't type the hyphen), you are telling debug to edit
the file beginning at the address you supply and make the
following value changes, which you again supply.  The third
line, "W" tells debug to write the changes to the file and
save them.  The final line, "Q" ends the debug utility.
   Having said all of that, a debug "patch" for the oil ->
temp/press. of a B17F engine would look like this:
DEBUG B17F.SPC <ENTER>  | This patch increases the engine's
E 117 80 <ENTER>        | coolant level, keeping the guages
W <ENTER>               | out of the red at a high rpm.
Q <ENTER>               |

DEBUG B17F.SPC <ENTER>  | This patch increases the engine's
E 119 DC <ENTER>        | stamina, allowing you to run them
W <ENTER>               | at a higher rpm without burning
Q <ENTER>               | them out.
                   more......
You can accomplish both goals by writing one debug this way:
DEBUG B17F.SPC <ENTER>
E 117 80 00 DC <ENTER>
W <ENTER>
Q <ENTER>
The "00" on line 2 is the default value for byte 118.  It
needs to be included if you're writing a ONE line debug with
MORE than one change because debug begins at the initial
address you specify ("117") and edits subsequent bytes in a
consecutive order.  If the bytes you're editing are not very
close together, then edit each on a separate line such as:
DEBUG B17F.SPC <ENTER>
E 117 80 <ENTER>
E 119 DC <ENTER>
W <ENTER>
Q <ENTER>

This is the same patch written above, only on two lines
instead of one.  When altering the engine's keep this in
mind:  LOWER the value at 117 for more engine coolant and
RAISE the value at 119 for more engine stamina.  Of course,
all of this could be done easier if you have/can get a copy
of PCTOOLS or Norton Utilities, which have hex editors that
allow you to go directly to the byte and make changes.  They
will also allow you to see the file contents and print a hex
dump of them, which you should have for ease of comparison
between planes.  One final note, practice safe debugging.
ALWAYS make backup's of your original files and do your
editing there, NEVER EVER on your originals.  Hope this
helps.  Credit goes to Keith Heitmann, Greg Smith, et. all
who were kind enough to pass this along and create
hexophilic maniacs who've abandoned their families in search
of the ultimate flying sim.  Thanks....I think. <G>
                           Rrik  kgxc61a
 
FROM:    RICHARD BARCLAY   (KGXC61A)
SUBJECT: SWOTL GROUP

Trent, from one beginner to another, here goes.  First, make
sure you have a copy of DEBUG.COM in your \SWOTL\AC subdir.
The proceedure is as follows:
DEBUG [filename.ext]  <ENTER>
-E [byte address] [value change] <ENTER>
-W <ENTER>
-Q <ENTER>             more.....
What you have done, on a line-by-line basis, is to activate
the debug utility by having it open a specific file.  When
debug has done this you will see a hyphen on the next line,
which is debug's prompt.  On the second line, when you type
"E" (don't type the hyphen), you are telling debug to edit
the file beginning at the address you supply and make the
following value changes, which you again supply.  The third
line, "W" tells debug to write the changes to the file and
save them.  The final line, "Q" ends the debug utility.
   Having said all of that, a debug "patch" for the oil ->
temp/press. of a B17F engine would look like this:

DEBUG B17F.SPC <ENTER>  | This patch increases the engine's
E 117 80 <ENTER>        | coolant level, keeping the guages
W <ENTER>               | out of the red at a high rpm.
Q <ENTER>               |

DEBUG B17F.SPC <ENTER>  | This patch increases the engine's
E 119 DC <ENTER>        | stamina, allowing you to run them
W <ENTER>               | at a higher rpm without burning
Q <ENTER>               | them out.

You can accomplish both goals by writing one debug this way:
DEBUG B17F.SPC <ENTER>
E 117 80 00 DC <ENTER>
W <ENTER>
Q <ENTER>
The "00" on line 2 is the default value for byte 118.  It
needs to be included if you're writing a ONE line debug with
MORE than one change because debug begins at the initial
address you specify ("117") and edits subsequent bytes in a
consecutive order.  If the bytes you're editing are not very
close together, then edit each on a separate line such as:
DEBUG B17F.SPC <ENTER>
E 117 80 <ENTER>
E 119 DC <ENTER>
W <ENTER>
Q <ENTER>

This is the same patch written above, only on two lines
instead of one.  When altering the engine's keep this in
mind:  LOWER the value at 117 for more engine coolant and
RAISE the value at 119 for more engine stamina.  Of course,
all of this could be done easier if you have/can get a copy
of PCTOOLS or Norton Utilities, which have hex editors that
allow you to go directly to the byte and make changes.  They
will also allow you to see the file contents and print a hex
dump of them, which you should have for ease of comparison
between planes.  One final note, practice safe debugging.
ALWAYS make backup's of your original files and do your
editing there, NEVER EVER on your originals.  Hope this
helps.  Credit goes to Keith Heitmann, Greg Smith, et. all
who were kind enough to pass this along and create
hexophilic maniacs who've abandoned their families in search
of the ultimate flying sim.  Thanks....I think. <G>
                           Rrik  kgxc61a

 
 
