VOGONS


First post, by llm

User metadata
Rank Member
Rank
Member

started as a UniVBE question but morphed into a VESA Info Question

Re: Do anyone know how UniVBE detects that its already loaded?

Reply 1 of 5, by _Rob

User metadata
Rank Member
Rank
Member

DOSBox-X 0.83.18 with default machine type

command_000.png
Filename
command_000.png
File size
8.16 KiB
Views
270 views
File comment
DOSBox-X default machine type
File license
Public domain

DOSBox-X 0.83.18 with vmemsize=16

command_000.png
Filename
command_000.png
File size
8.3 KiB
Views
259 views
File comment
DOSBox-X vmemsize=16
File license
Public domain

DOSBox-X 0.83.18 with machine=vesa_oldvbe

command_002.png
Filename
command_002.png
File size
7.61 KiB
Views
270 views
File comment
DOSBox-X machine=vesa_oldvbe
File license
Public domain

DOSBox-X 0.83.18 with machine=vesa_oldvbe10

command_001.png
Filename
command_001.png
File size
7.61 KiB
Views
270 views
File comment
DOSBox-X machine=vesa_oldvbe10
File license
Public domain

DOSBox-staging 0.77.1

dosbox_000.png
Filename
dosbox_000.png
File size
5.33 KiB
Views
270 views
File comment
DOSBox-Staging
File license
Public domain
Last edited by _Rob on 2021-10-18, 10:36. Edited 1 time in total.

Reply 4 of 5, by _Rob

User metadata
Rank Member
Rank
Member

With the fixed binary posted by @Falcosoft, it now renders much better on DOSBox-X and -staging.

Is it normal that the init signature is still VBE2 when emulating VBE 1.2 or 1.0? And should it still probe for VBE2 when the VbeVersion is not at least 0x0200?

Here is a screenshot of DOSBox-X 0.83.18 with machine=vesa_oldvbe10 and vmemsize=16

command_000.png
Filename
command_000.png
File size
10.78 KiB
Views
197 views
File comment
DOSBox-X vmemsize=16 machine=vesa_oldvbe10
File license
Public domain

Also note how regular DOSBox and -staging both return 0 for capabilities while -X returns a different result.