VioQueryConsole: Difference between revisions
Appearance
mNo edit summary |
m linked to nowhere |
||
Line 1: | Line 1: | ||
This is an undocumented function of the API. | This is an undocumented function of the API. | ||
According to some public discussion | According to some public discussion VioQueryConsole may return a HVIO. Since any other VIO routine will work with a hvio = 0 (with rare exceptions) this might be the reason why that function is of no value. | ||
Looks like IBM tried to implement multiple logical fullscreen video devices (like they did with keyboard and mouse) but didn't quite get to it or didn't see any use in doing so once they defined logical video buffers. | Looks like IBM tried to implement multiple logical fullscreen video devices (like they did with keyboard and mouse) but didn't quite get to it or didn't see any use in doing so once they defined logical video buffers. | ||
[[Category:Vio]] | [[Category:Vio]] |
Revision as of 22:23, 1 January 2020
This is an undocumented function of the API.
According to some public discussion VioQueryConsole may return a HVIO. Since any other VIO routine will work with a hvio = 0 (with rare exceptions) this might be the reason why that function is of no value.
Looks like IBM tried to implement multiple logical fullscreen video devices (like they did with keyboard and mouse) but didn't quite get to it or didn't see any use in doing so once they defined logical video buffers.