Jump to content

VioQueryConsole: Difference between revisions

From EDM2
No edit summary
Ak120 (talk | contribs)
mNo edit summary
Line 1: Line 1:
{{Legacy
This is an undocumented function of the API.
|RepFunc=
|Remarks=This page list the older version of the function for reference.
}}
This is an undocumented functions of the API.


According to some public discussion [http://comp.os.os2.programmer.misc.narkive.com/1z1GBX5t/undocumented-apis] 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.
According to some public discussion [http://comp.os.os2.programmer.misc.narkive.com/1z1GBX5t/undocumented-apis] 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.

Revision as of 23:15, 7 June 2019

This is an undocumented function of the API.

According to some public discussion [1] 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.