Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

HX/OGLTEST error (Users)

posted by Japheth Homepage, Germany (South), 28.05.2011, 08:31

> Cool that the mystery is solved, but now i'm a bit confused.
> (This is where my lack of video-hardware and programming
> knowledge shows up!)
>
> > VESA32 cleared the buffer located in real-mode,
>
> Ok, maybe i'm misunderstanding, but my code *was* all real mode
> (16-bit)... and the interrupt did *not* clear the buffer -- the
> call failed and it didn't change the buffer at all! I set the
> buffer up with 256 bytes of "x" characters, ran the VESA BIOS
> 4F01h Int 10h call, and then looked at the buffer -- no change,
> still 256 bytes of "x" characters.

Sorry for my very sloppy usage of terminology! cm described what I "meant" already, but I want to add that my fragment "copy the contents back to protected-mode" is absolute nonsense if taken literally. In fact, with "protected-mode" I meant "extended memory used in protected-mode", and "real-mode" is to be translated to "conventional memory used in real-mode".

>
> CHIPSET/CARD                  VBE  RETRN  DESC  ES:DI BUFF
> ----------------------------  ---  -----  ----  -----------
> Intel 865G                    3.0  014Fh  fail  unchanged
> Intel 845G                    3.0  014Fh  fail  unchanged
> NVidia GeForce4 MX440 (NV18)  3.0  004Fh  succ  data filled
> NeoMagic MagicGraph 256AV     2.0  014Fh  fail  unchanged
> Cirrus Logic GD-5436/46       1.2  014Fh  fail  0-filled
>


Thanks! Very unsurprisingly I tested the VESA stuff on a NVidia machine. I guess I should change this habit.

---
MS-DOS forever!

 

Complete thread:

Back to the forum
Board view  Mix view
22762 Postings in 2122 Threads, 402 registered users (0 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum