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

The attachment command_000.png is no longer available

DOSBox-X 0.83.18 with vmemsize=16

The attachment command_000.png is no longer available

DOSBox-X 0.83.18 with machine=vesa_oldvbe

The attachment command_002.png is no longer available

DOSBox-X 0.83.18 with machine=vesa_oldvbe10

The attachment command_001.png is no longer available

DOSBox-staging 0.77.1

The attachment dosbox_000.png is no longer available
Last edited by _Rob on 2021-10-18, 10:36. Edited 1 time in total.

Reply 2 of 5, by llm

User metadata
Rank Member
Rank
Member

Thanks _Rob - i still got sometimes problems with the vendor strings but good infos

Reply 3 of 5, by _Rob

User metadata
Rank Member
Rank
Member

Indeed, the above example with vmemsize=16 is a good example that something is going wrong with printing strings in your code.

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

The attachment command_000.png is no longer available

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

Reply 5 of 5, by llm

User metadata
Rank Member
Rank
Member

thanks for further testing - i will re-add my VESA or VBE inital signature feature later