VOGONS


First post, by typh0id

User metadata
Rank Newbie
Rank
Newbie

Hi there!

I recently upgraded my GPU to an nVidia 5060 TI (16GB) and ever since doing so, Windows 3.11 no longer displays stretched to full screen in DOSBox like it always has before.

- I have my GPU set for Aspect Ratio scaling handled by the GPU and overriding individual app settings (see attached)

- My display settings for Windows 3.11 are S3 Trio 64V 1.70.04 800x600 C SF (see attached)

- I've also attached pertinent DOSBox settings (see attached)

This issue only occurs with Windows 3.11 within DOSBox and not any of the DOS programs (which still display full screen with proper aspect ratio scaling). I have tried various different settings at all three locations (nVidia control panel, Windows 3.11 display settings, and DOSBox configuration) but nothing has fixed it. Please let me know if you have any advice or need any further information.

Thanks!

typh0id

Reply 1 of 9, by Mov AX, 0xDEAD

User metadata
Rank Newbie
Rank
Newbie
typh0id wrote on 2026-07-06, 16:37:

Windows 3.11 no longer displays stretched to full screen in DOSBox like it always has before.

No info what it displays currently

Reply 2 of 9, by typh0id

User metadata
Rank Newbie
Rank
Newbie
Mov AX, 0xDEAD wrote on 2026-07-06, 16:48:
typh0id wrote on 2026-07-06, 16:37:

Windows 3.11 no longer displays stretched to full screen in DOSBox like it always has before.

No info what it displays currently

I put everything I could think of in the attachments, including DOSBox settings and Win3.11 display settings. What else would help that I missed?

It looks to be displaying Windows in 800x600 without scaling it to my monitor's full screen. Again though, it's ONLY Win3.11 that's doing this. Everything else in DOSBox scales correctly.

Reply 3 of 9, by MagefromAntares

User metadata
Rank Member
Rank
Member

Hi,

While this is unlikely to affect only Win 3.11, but some video card/driver combinations have problem with aspect ratio correction with certain configurations, try to change output=overlay to output=ddraw if running DOSBox on Windows or output=opengl if running DOSBox on Linux.

EDIT: If none of these works you might also try appending "forced" to the scaler configuration variable.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 4 of 9, by typh0id

User metadata
Rank Newbie
Rank
Newbie
MagefromAntares wrote on 2026-07-06, 19:12:

Hi,

While this is unlikely to affect only Win 3.11, but some video card/driver combinations have problem with aspect ratio correction with certain configurations, try to change output=overlay to output=ddraw if running DOSBox on Windows or output=opengl if running DOSBox on Linux.

EDIT: If none of these works you might also try appending "forced" to the scaler configuration variable.

So that technically DID work (the ddraw thing - thank you for that!) however now the picture quality looks worse. By that I mean the pixels no longer look uniform giving everything a distorted appearance. I tried the forced scaler too but still distorted.

Reply 5 of 9, by MagefromAntares

User metadata
Rank Member
Rank
Member
typh0id wrote on 2026-07-06, 20:45:
MagefromAntares wrote on 2026-07-06, 19:12:

Hi,

While this is unlikely to affect only Win 3.11, but some video card/driver combinations have problem with aspect ratio correction with certain configurations, try to change output=overlay to output=ddraw if running DOSBox on Windows or output=opengl if running DOSBox on Linux.

EDIT: If none of these works you might also try appending "forced" to the scaler configuration variable.

So that technically DID work (the ddraw thing - thank you for that!) however now the picture quality looks worse. By that I mean the pixels no longer look uniform giving everything a distorted appearance. I tried the forced scaler too but still distorted.

I would guess that you are running DOSBox on Windows 11 (or some of the later updates broke it on Windows 10 too), sometimes the ddraw setting behaves weirdly on that version of Windows, however if overlay also doesn't work I now don't have an idea how to make it work with regular DOSBox. You can try DOSBox-X, that version has a new output setting output=direct3d that might work even on Windows 11, it uses the Graphics Cards 3D pipeline instead of the 2D acceleration to display.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 6 of 9, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

OpenGL is an option in Windows, it's just a matter of host driver support, and Nvidia is almost certain to support it, so definitely do try output=opengl. You might or might not prefer a blockier appearance with output=openglnb, which uses irregular virtual pixel sizes rather than interpolation. Also, in DOSBox SVN you can use output=opengl scaler=none glshader=sharp for nicely sharp scaling that is offloaded to the video card.

Reply 7 of 9, by typh0id

User metadata
Rank Newbie
Rank
Newbie
ripsaw8080 wrote on 2026-07-07, 03:08:

OpenGL is an option in Windows, it's just a matter of host driver support, and Nvidia is almost certain to support it, so definitely do try output=opengl. You might or might not prefer a blockier appearance with output=openglnb, which uses irregular virtual pixel sizes rather than interpolation. Also, in DOSBox SVN you can use output=opengl scaler=none glshader=sharp for nicely sharp scaling that is offloaded to the video card.

=opengl looks a lot better! The picture is overall a little bit "softer" than I'm used to (pixels aren't quite as crsip) but I it looks way better than how it did with ddraw (openglnb looks similar to that). I admit that in well over a decade that I have been using DOSBox, I have never ventured outside of the vanilla builds. I've spent so much time fine-tweaking the performance of every single game I run that I've always bee afraid if I were to switch versions, some of them suddenly not might run the same and I'd have to go back through them all again. Also I looked up DOSBox SVN and there are even multiple different versions of that that which come up in Google so I don't really know where to start.

Reply 8 of 9, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author
typh0id wrote on 2026-07-07, 11:24:

Also I looked up DOSBox SVN and there are even multiple different versions of that that which come up in Google so I don't really know where to start.

A good (compared to EmuCR) Windows SVN build via IA: https://web.archive.org/web/20240430023008/ht … SBox%20r4482.7z

Reply 9 of 9, by typh0id

User metadata
Rank Newbie
Rank
Newbie
ripsaw8080 wrote on 2026-07-07, 12:07:
typh0id wrote on 2026-07-07, 11:24:

Also I looked up DOSBox SVN and there are even multiple different versions of that that which come up in Google so I don't really know where to start.

A good (compared to EmuCR) Windows SVN build via IA: https://web.archive.org/web/20240430023008/ht … SBox%20r4482.7z

Much appreciated! I'll check this out.