For changing to a VESA must I make use of int 10h allways?
Thanks!
VESA
-
j.weeks
RE:VESA
>On 2001-09-29 17:03:58, Stefan wrote:
>For changing to a VESA must I make use of int 10h allways?
Uhm... yeah. VESA's a standard implemented by
the video card! The whole point of it is to
allow a programmer to inter video modes without
having to know what video card it's using, and what
specific port data must be written in order to
set a video mode.
In other words, without int 10h, there is no Vesa.
However, no, you don't need vesa to actually
enter a video mode... but instead, you'll have to
know the "setMode" data port values for every
single video card you plan on supporting. Good luck
j.weeks
>For changing to a VESA must I make use of int 10h allways?
Uhm... yeah. VESA's a standard implemented by
the video card! The whole point of it is to
allow a programmer to inter video modes without
having to know what video card it's using, and what
specific port data must be written in order to
set a video mode.
In other words, without int 10h, there is no Vesa.
However, no, you don't need vesa to actually
enter a video mode... but instead, you'll have to
know the "setMode" data port values for every
single video card you plan on supporting. Good luck
j.weeks
-
Guest
RE:VESA
>On 2001-09-29 19:52:23, j.weeks wrote:
>>On 2001-09-29 17:03:58, Stefan wrote:
>>For changing to a VESA must I make use of int 10h allways?
>
>Uhm... yeah. VESA's a standard implemented by
>the video card! The whole point of it is to
>allow a programmer to inter video modes without
>having to know what video card it's using, and what
>specific port data must be written in order to
>set a video mode.
>
>In other words, without int 10h, there is no Vesa.
>
>However, no, you don't need vesa to actually
>enter a video mode... but instead, you'll have to
>know the "setMode" data port values for every
>single video card you plan on supporting. Good luck
>
>j.weeks
That means, if I want to use VESA, I must switch to rel-address mode,
execute the part with int 10h and then switch back to protected mode?
>>On 2001-09-29 17:03:58, Stefan wrote:
>>For changing to a VESA must I make use of int 10h allways?
>
>Uhm... yeah. VESA's a standard implemented by
>the video card! The whole point of it is to
>allow a programmer to inter video modes without
>having to know what video card it's using, and what
>specific port data must be written in order to
>set a video mode.
>
>In other words, without int 10h, there is no Vesa.
>
>However, no, you don't need vesa to actually
>enter a video mode... but instead, you'll have to
>know the "setMode" data port values for every
>single video card you plan on supporting. Good luck
>
>j.weeks
That means, if I want to use VESA, I must switch to rel-address mode,
execute the part with int 10h and then switch back to protected mode?
-
j.weeks
RE:VESA
>On 2001-09-30 16:47:17, Anonymous wrote:
>>On 2001-09-29 19:52:23, j.weeks wrote:
>>>On 2001-09-29 17:03:58, Stefan wrote:
>>>For changing to a VESA must I make use of int 10h allways?
>>
>>Uhm... yeah. VESA's a standard implemented by
>>the video card! The whole point of it is to
>>allow a programmer to inter video modes without
>>having to know what video card it's using, and what
>>specific port data must be written in order to
>>set a video mode.
>>
>>In other words, without int 10h, there is no Vesa.
>>
>>However, no, you don't need vesa to actually
>>enter a video mode... but instead, you'll have to
>>know the "setMode" data port values for every
>>single video card you plan on supporting. Good luck
>>
>>j.weeks
>
>That means, if I want to use VESA, I must switch to rel-address mode,
>execute the part with int 10h and then switch back to protected mode?
Yep. Either that, or you can have a VM86 task
running that'll run the int 10h calls. I've been
told this is a father method, but I haven't
tried it myself yet.
j.weeks
>>On 2001-09-29 19:52:23, j.weeks wrote:
>>>On 2001-09-29 17:03:58, Stefan wrote:
>>>For changing to a VESA must I make use of int 10h allways?
>>
>>Uhm... yeah. VESA's a standard implemented by
>>the video card! The whole point of it is to
>>allow a programmer to inter video modes without
>>having to know what video card it's using, and what
>>specific port data must be written in order to
>>set a video mode.
>>
>>In other words, without int 10h, there is no Vesa.
>>
>>However, no, you don't need vesa to actually
>>enter a video mode... but instead, you'll have to
>>know the "setMode" data port values for every
>>single video card you plan on supporting. Good luck
>>
>>j.weeks
>
>That means, if I want to use VESA, I must switch to rel-address mode,
>execute the part with int 10h and then switch back to protected mode?
Yep. Either that, or you can have a VM86 task
running that'll run the int 10h calls. I've been
told this is a father method, but I haven't
tried it myself yet.
j.weeks