index   prev   next RISC OS Notes


see also sections;- BASIC * star commands

# Absolute files

An absolute file contains machine code. When run, it is loaded at address &8000, and this is where execution starts too. Usually these are .aifformat>. They can be put into !Boot.Library or in any directory in the current path. For temporary use put one in the current directory and invoke it by name. Eg see shine

# Choices configuration file

Justin Fletcher document on choices here:

# creating a module

see example code:- ADFS::HardDisc5.$.PROGRAMZ.JRBASIC.mouse.mousekey Basic program by Leo White

# extracting module from ROM

1. use Verma >>Module >Extract >... 2. use StrongED menu on icon bar >>create file >Grab memory... window pops up with option to obtain ROM or RAM modules 3. use ZAP i>> Create> Get Module> CDFSSoftATAPI save from ZAP to disk

# module levels

AppBasic has facilities for comparing ROM and System levels for Toolbox modules

# !Reporter

has good stronghelp help manual- if not started during boot then start with !! - no windows or icons then from task window report if you change the choices file then rerun pgm you can open the config window from the Strong Help manual Perhaps I could just add a bit more detail ... First, !Reporter should be dragged from downloaded zip file to your hard disc somewhere before starting it. You should also have !Confix v0.83 or later installed, and StrongHelp to read the !Help files. And to Configure it (Menu -> Config) to log commands and errors, I would Click Boot in the 'Reporter Customisation' window, and ensure 'Report Commands', 'with Time', 'with Source', and 'Report Errors' are all ticked, and also increase the text size to 500KB. Then Click 'BootLog', and just tick the ' Start Reporter in Boot.!Run' Click 'Save' to store the new configuration and !Reporter will make some changes, then reboot. **** !Run in !Boot may need to be unprotected before saving And you should see after Reboot a window with *lots* of commands in it, with the time issued, who issued them, and with obey commands and errors highlit so they are easy to see. If you try it when you do NOT have a problem, it may be useful when you do! Martin A.

# TRACE using !Reporter

for details see the manual (Strong Help format) but for a get you started in a basic program try :- *ReportTrace Proc Values *ReportTrace ON List *Report a$ See also ADFS::HardDisc5.$.DOCZ.Reporter.!Demo for examples of most reporter commands.

© JR 2013