SS.AScrn Set Status
From NitrOS-9
Revision as of 16:24, 5 April 2014 by Glaw16 (Talk | contribs) (Created page with 'Allocates and maps a high-resolution screen into an application address space. {| | colspan="2" | '''Entry Conditions''' |- | A || ''path number'' |- | B || SS.AScrn ($8B) |- | …')
Allocates and maps a high-resolution screen into an application address space.
Entry Conditions | |
A | path number |
B | SS.AScrn ($8B) |
X | screen type |
0 = 640 x 192 x 2 colors (16K) | |
1 = 320 x 192 x 4 colors (16K) | |
2 = 160 x 192 x 16 colors (16K) | |
3 = 640 x 192 x 4 colors (32K) | |
4 = 320 x 192 x 16 colors (32K) | |
Exit Conditions | |
X | application address space of screen |
Y | screen number (1-3) |
Error Output | |
CC | carry set on error |
B | error code |
Additional Information
- SS.AScrn is particularly useful in systems with mininal memory when you want to allocate a high resolution graphics screen with all screen updating handled by a process.
- All screens are allocated in multiples of 8K blocks. You can allocate a maximum of three buffers at one time. To select between buffers, use the SS.DScrn SetStat call.
- Screen memory is allocated but not cleared. The application using the screen must do this.
- Screens must be allocated from a VDG-type device—a standard 32-column text screen must be available for the device.
- This call uses VDGInt (GrfInt is not required).
- The support module for this call is VDGInt.