Mercurial > hg > Members > kono > nitros9-code
diff docs/nitros9guide/binex.refentry @ 1500:b00cf13c9f61
Major changes for new NitrOS-9 manual
| author | boisy |
|---|---|
| date | Mon, 05 Jan 2004 00:51:19 +0000 |
| parents | 4dae346c4969 |
| children |
line wrap: on
line diff
--- a/docs/nitros9guide/binex.refentry Thu Dec 25 14:19:21 2003 +0000 +++ b/docs/nitros9guide/binex.refentry Mon Jan 05 00:51:19 2004 +0000 @@ -20,17 +20,17 @@ programmers, emulators, logic analyzers and similar devices that are interfaced RS-232 interfaces. It can also be useful for transmitting files over data links that can only handle character-type -data; or to convert OS-9 assembler or compiler-generated -programs to load on non-OS-9 systems. +data; or to convert NitrOS-9 assembler or compiler-generated +programs to load on non-NitrOS-9 systems. </para> <para> -<command>Binex</command> converts "path1", an OS-9 binary format file, to a new file +<command>Binex</command> converts "path1", a NitrOS-9 binary format file, to a new file named "path2" in S-Record format. If invoked on a non-binary load module file, a warning message is printed and the user is asked if <command>binex</command> should proceed anyway. A "Y" response means yes; any other answer will terminate the program. S-Records have a header record to store the program name for informational purposes and each data -record has an absolute memory address which is not meaningful to OS-9 +record has an absolute memory address which is not meaningful to NitrOS-9 since it uses position-independent-code. However, the S-Record format requires them so <command>binex</command> will prompt the user for a program name and starting load address. For example: