Difference between revisions of "83Plus:BCALLs:401E"

From WikiTI
Jump to: navigation, search
m (it's -> its, link to AppInit, minor formatting change)
Line 1: Line 1:
 
[[Category:83Plus:BCALLs:By Name:Monitor|Mon]] [[Category:83Plus:BCALLs:By Name|Mon]] [[Category:83Plus:BCALLs:By Address|401E - Mon]]
 
[[Category:83Plus:BCALLs:By Name:Monitor|Mon]] [[Category:83Plus:BCALLs:By Name|Mon]] [[Category:83Plus:BCALLs:By Address|401E - Mon]]
 +
{{missinfo|Destroys}}
 
== Synopsis ==
 
== Synopsis ==
 
'''Official Name:''' Mon
 
'''Official Name:''' Mon
Line 18: Line 19:
  
 
=== Registers Destroyed ===
 
=== Registers Destroyed ===
* ??
+
* unknown
  
 
== Comments ==
 
== Comments ==
 
The system NEVER returns from this B_CALL.  The programmer should find alternative methods of regaining control and exiting such as hooks, cxMain, etc.
 
The system NEVER returns from this B_CALL.  The programmer should find alternative methods of regaining control and exiting such as hooks, cxMain, etc.

Revision as of 19:05, 5 February 2008

This article is missing some information (namely Destroys). You can help WikiTI by filling in the missing information.


Synopsis

Official Name: Mon

BCALL Address: 401E

Starts the system monitor. The system monitor will take over the system, and report events to the application via the monitor vectors. The application must set its own monitor vectors with AppInit before calling Mon. Control of the application will never be returned from Mon.

Inputs

Outputs

  • none

Registers Destroyed

  • unknown

Comments

The system NEVER returns from this B_CALL. The programmer should find alternative methods of regaining control and exiting such as hooks, cxMain, etc.