Mike Smith wrote (1999/08/11):
Yes, thanks. Information reported by 0x4F01 function about any video
mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
program for VESA support...
Bleagh. Have you tried ignoring that attribute in our code and seeing
what happens
Yes, thanks. Information reported by 0x4F01 function about any video
mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
program for VESA support...
Bleagh. Have you tried ignoring that attribute in our code and seeing
what happens when you select one?
I hate VESA
It seems Cejka Rudolf wrote:
Soren Schmidt wrote (1999/08/09):
It seems Kazutaka YOKOTA wrote:
There is a good possibility that the VESA BIOS extension for this card
is provided in a DOS TSR program and the VESA BIOS entry in the ROM
BIOS is just a stub. Such implementation is
Soren Schmidt wrote (1999/08/09):
It seems Kazutaka YOKOTA wrote:
There is a good possibility that the VESA BIOS extension for this card
is provided in a DOS TSR program and the VESA BIOS entry in the ROM
BIOS is just a stub. Such implementation is allowed in the VESA spec.
Actually
On 08-Aug-99 Cejka Rudolf wrote:
I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92
with 8 MB RAM a I have noticed that VESA module doesn't work with this
graphics card on my -current box - I can't use VESA_XXX console modes now.
Command kldstat says there is loaded
It seems Kazutaka YOKOTA wrote:
I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92
with 8 MB RAM a I have noticed that VESA module doesn't work with this
graphics card on my -current box - I can't use VESA_XXX console modes now.
Command kldstat says there is loaded
