Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VBE executables causing crash with VBE 3.0 card #62

Closed
sofakng opened this issue Feb 11, 2022 · 5 comments
Closed

VBE executables causing crash with VBE 3.0 card #62

sofakng opened this issue Feb 11, 2022 · 5 comments
Labels
bug Something isn't working graphics

Comments

@sofakng
Copy link

sofakng commented Feb 11, 2022

I'm using an ICOP Vortex86DX SOM304RD-VI SOM module that has a built-in XGI Volari Z9s Chipset running MS-DOS 6.22.

According to SciTech Display Doctor (6.53 for DOS), this chip supports VBE 3.0:
IMG_4273

However, when I launch FDOOMVBR.EXE or FDOOMVBD.EXE it crashes with a corrupt screen or a stack trace (?):
IMG_4271
IMG_4272

I can't use UNIVBE because this chip isn't supported but according to VBETEST the card already supports VBE 3.0? (other games such as Duke3D and Quake seem to be working in VBE modes)

@viti95 viti95 added bug Something isn't working graphics labels Feb 13, 2022
@viti95
Copy link
Owner

viti95 commented Mar 28, 2022

Can you check if the 320x200 resolution it's supported in the 8-bit per pixle mode? Also can you try the utility NOLFB to check if the LFB it's the problem?

@sofakng
Copy link
Author

sofakng commented Mar 28, 2022

SDD's VBETEST allows me to test [320x200x8, 128 page, Banked Only]. When it asks for refresh rate I've selected [BIOS Default] (60Hz I think?) and all tests are successful.

If I use the NOLFB utility, FDOOMVBD.EXE stops crashing but has flickering. However, FDOOMVBR.EXE appears to run perfectly!

Will I need to run this utility every time or can you implement a fix (or command-line option?)

Thanks so much for the help!

@viti95
Copy link
Owner

viti95 commented Mar 29, 2022

I'll add a fix, it seems to have problems with the LFB so the idea is to disable it (as NOLFB does). FDOOMVBD.EXE doesn't work without LFB, but at least FDOOMVBR.EXE will be totally usable.

@sofakng
Copy link
Author

sofakng commented Mar 29, 2022

Sounds good. Thanks so much!

viti95 added a commit that referenced this issue Apr 3, 2024
…y it crashes on cards with 16Mb or more. Fixes VESA crash on multiple video cards. Also related to #185
@viti95
Copy link
Owner

viti95 commented Apr 3, 2024

I've released a new version with this issue fixed (better late than never 😅). Thanks for your patience.

@viti95 viti95 closed this as completed Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working graphics
Projects
None yet
Development

No branches or pull requests

2 participants