Qbasicnews.com

Full Version: FB (dos) and QB list of quirks and oddities (nice read)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I just did a quick read through of this and it seems like there is quite a bit of good stuff. Thanks for the link!

-gunder
makes me want to pull out dos for a second and try coding Tongue
This is untrue:

Quote:also, in text mode, you seem to be stuck with 80x25 for now, if there is another way to change the text resolution, width does not appear to work the same way.

WIDTH 80, 50 should work on any VGA-compatible display adapter; it does not require gfxlib.

If anybody could report instances of this not working, I'll fix it.

BTW, the DOS gfxlib2 driver is progressing steadily - I've implemented ModeX (320x240x8), and linear and banked VESA drivers are on the way. (Linear VESA mode should be essentially as fast as the Win32 gfxlib without hardware acceleration with well-written code, i.e. code that does not draw to the visible page but uses page flipping instead.)
interesting rel

edit: and awesome, dr, didn't read your message Smile
they say on there about peek and poke not being available in fb. they are through the djgpp/dpmi interface but dont ask me to explain, im still figuring it out myself! my vesa and mouse librarys are sitting static at the moment cause no bugger seems able to explain __tb and segment use. just a simple thing like getting vesa mode info is a big headache

Sub GetModeInfo(mode)
dim c as integer

_farsetsel(_dos_ds)

for c=0 to len(ModeInfo)-1
_farnspokeb(((__tb)+c) AND &H000FFFFF, 0)
next c

Regs.x.AX = &H4F01
Regs.x.CX = mode
regs.x.di= __tb AND &H0F
regs.x.es=(__tb shr 4) AND &HFFFF
__dpmi_int &H10, @regs

dosmemget(__tb, len(ModeInfoBlock), @modeinfo)
End Sub

doenst work, wont work, isnt working etc!