Difference between revisions of "83Plus:BCALLs:4FF9"

From WikiTI
Jump to: navigation, search
m (Formatting)
m
 
(2 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
[[Category:83Plus:BCALLs:By Name:Hook|RunTracerHook]]
 
[[Category:83Plus:BCALLs:By Name:Hook|RunTracerHook]]
 
[[Category:83Plus:BCALLs:By Address|4FF9 - RunTracerHook]]
 
[[Category:83Plus:BCALLs:By Address|4FF9 - RunTracerHook]]
{{missinfo|Destroys}}
+
 
 
== Synopsis ==
 
== Synopsis ==
 
'''Unofficial Name:''' RunTracerHook
 
'''Unofficial Name:''' RunTracerHook
Line 14: Line 14:
 
=== Inputs ===
 
=== Inputs ===
 
The block for the Trace Hook must be set up correctly.
 
The block for the Trace Hook must be set up correctly.
<!-- What does this mean? -->
 
  
 
=== Outputs ===
 
=== Outputs ===
*HL points to the start of the hook. <!-- The hook block? -->
+
*HL points to the start of the hook.
*F is 6A if the hook was not run.  <!-- And if it was run? -->
+
*F is 6A if the hook was not run.   
  
 
=== Destroys ===
 
=== Destroys ===
''Unknown''
+
*A
  
 
== Comments ==
 
== Comments ==

Latest revision as of 13:25, 6 February 2008


Synopsis

Unofficial Name: RunTracerHook

BCALL Address: 4FF9

Checks the first byte of the block for the Trace Hook. If the byte is 83, the hook is run. Otherwise, the active flag for the hook is set to zero.

Inputs

The block for the Trace Hook must be set up correctly.

Outputs

  • HL points to the start of the hook.
  • F is 6A if the hook was not run.

Destroys

  • A

Comments

This BCALL is known to be present in OS 1.13, and is undocumented.

Credits and Contributions

  • Michael Cimino