Difference between revisions of "83Plus:BCALLs:401E"
From WikiTI
m (→Inputs: Linked flags) |
|||
| Line 11: | Line 11: | ||
=== Inputs === | === Inputs === | ||
| − | * AppAllowContext, (IY + APIFlg) = 1 to allow Mon to pass context keys, like | + | * [[83Plus:Flags:28|AppAllowContext, (IY + APIFlg)]] = 1 to allow Mon to pass context keys, like |
* kYequ to the cxMain routine. | * kYequ to the cxMain routine. | ||
| − | * CurLock, (IY + curFlags) = 1 to lock the cursor off | + | * [[83Plus:Flags:0C|CurLock, (IY + curFlags)]] = 1 to lock the cursor off |
=== Outputs === | === Outputs === | ||
Revision as of 07:40, 26 April 2005
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 it’s own monitor vectors with AppInit before calling Mon. Control of the application will never be returned from Mon.
Inputs
- AppAllowContext, (IY + APIFlg) = 1 to allow Mon to pass context keys, like
- kYequ to the cxMain routine.
- CurLock, (IY + curFlags) = 1 to lock the cursor off
Outputs
- none
Registers Destroyed
- ??
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.
