I've read VBE 3.0 document and others' topics here.
I've noticed u guys use VBE via int 10. but I can't make sense.
cos it says in VBE 3.0 document that call VBE func via int 10 when it's in real mode.
So I thought I should use "Protected Mode Entry Pointer" instead of it.
cos after loading kernel, the mode is changed to Protected Mode.
It no longer goes to Real mode.
But the example code and u guys call VBE func via int 10.
Did I misunderstand something?
About VBE Specification.
Re: About VBE Specification.
VBE 3 is not very supported yet. Because of this, alot of systems dont support the protected mode interface that it provides. You can use VBE 3, but most examples and tutorials still use VBE 2 as it is most used.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: About VBE Specification.
Also the pmode interface is 16bit pmode (as per the VBE 3, spec), half way to realmode, i find going back to realmode just as easy, as 16bit pmode.
Re: About VBE Specification.
It is the discrapancy between theory and practice. Historically, VBE3 was too little, too late. With the advent of Win3.11 and Win95, it became more or less obsolete, although VBE2 is still supported by most video card manufacturers.Charlie wrote:Did I misunderstand something?
JAL