DOS ain't dead - HX/OGLTEST error

HX/OGLTEST error (Users)

posted by Doug , 26.05.2011, 08:01

Japheth -

> I know what VESA32 does, so I might be able to help.

You da man!

> I guess you're calling ogltest from a text mode.

Yes. I never thought to call it from a graphics mode!

> OTOH, the crash dump tells me that VESA32 erroneously thinks it
> has access to the frame buffer.

Now that's interesting. I'm successfully using your VESAMTRR...
here are results from VSPEED (benchmark included with John
Hinkley's FASTVID):

VESA mode 0101h reports LFB address: F0000000
VESA mode 4101h reports LFB address: F0000000
PCI config10 reports possible LFB address: F0000000
PCI config14 reports possible LFB address: E8000000

VSPEED will use VESA mode 4101h and F0000000h as the LFB address.

32-bit protected-mode video benchmark version 1.10. (640x480x8bit)

Default:

Copy DRAM to banked VGA: 50.14 million bytes per second
Copy DRAM to linear framebuffer: 53.08 million bytes per second

After VESAMTRR:

Copy DRAM to banked VGA: 50.14 million bytes per second
Copy DRAM to linear framebuffer: 79.99 million bytes per second

That's about a 50% increase for LFB Write Combining (i'm assuming
that's what the second measurement means) and no improvement for
Banked VGA. (This is in a P4, 2.8ghz, i865G system.)

> So the test is to call vesa int 10h, ax=4F01h, current mode is
> TEXT (video mode 3) and then see if
>
> - the call succeeds

Ok, i did a "quickie" with DEBUG, assembling some code then using
P command to proceed thru it and looking at the registers.
Setting CX = 3 (video mode 3), after calling Int 10h, AX returned
014Fh. According to RB's interrupt list, the function is
supported (AL = 4Fh), but it failed (AH = 01h). So there you
have it! (Just to double check, i did the same but with CX =
0101h -- a standard VESA mode -- and the call succeeded: AX =
004Fh.)

> - field MemoryModel (offset 1Bh in structure below) is zero.

I guess no sense in doing this, as the call failed.

> SVGAINFO struct
> ...
> SVGAINFO ends

Thanks -- this will be helpful in future projects!

> I also added a missing check in VESA32. When trying to save the
> vesa state, it always assumed that int 10h, ax=4f01h succeeded
> (it perhaps might fail for standard VGA text modes on your
> system).

Looks like a definite possibility. So i wonder if it's universal
VESA behavior or just my BIOS? I have some other systems i can
also test it on.

> EDIT: I uploaded a new HXRT217.zip which contains the modified
> VESA32.DLL.

Downloaded it... and OGLTEST now works ok with SAVE=1 in
HXGUIHLP.INI file.

> MS-DOS forever!

YES!!!

- Doug B.

Post reply

Complete thread:

HX/OGLTEST error - Doug, 19.05.2011, 18:37 (Users)
- HX/OGLTEST error - Rugxulo, 19.05.2011, 22:34
  - HX/OGLTEST error - RayeR, 20.05.2011, 01:11
    - HX/OGLTEST error - Doug, 20.05.2011, 06:31
- HX/OGLTEST error - Japheth, 20.05.2011, 06:35
  - HX/OGLTEST error - Doug, 23.05.2011, 07:54
    - HX/OGLTEST error - Japheth, 23.05.2011, 09:25
    - HX/OGLTEST error - RayeR, 23.05.2011, 19:10
      - HX/OGLTEST error - Doug, 24.05.2011, 18:55
        HX/OGLTEST error - RayeR, 25.05.2011, 00:04
        HX/OGLTEST error - Doug, 25.05.2011, 17:42
        HX/OGLTEST error - RayeR, 26.05.2011, 00:48
        HX/OGLTEST error - Japheth, 25.05.2011, 07:06
        HX/OGLTEST error - Doug, 26.05.2011, 08:01
        HX/OGLTEST error - Japheth, 26.05.2011, 19:26
        HX/OGLTEST error - RayeR, 26.05.2011, 21:35
        HX/OGLTEST error - Doug, 26.05.2011, 22:40
        HX/OGLTEST error - Japheth, 27.05.2011, 07:05
        HX/OGLTEST error - Doug, 28.05.2011, 00:51
        copying buffer contents to protected mode - ecm, 28.05.2011, 01:09
        HX/OGLTEST error - Japheth, 28.05.2011, 08:31