VOGONS

Common searches


First post, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Tested using:
DOSBox CVS 4-28-2009
Windows 2008 64bit
Video Card: Intel 4 Series Express

If you have Aero enabled (transparent start menu and Window borders) and execute DOSBox using any output mode in Windowed mode then Aero is enabled and works fine.

If you enter into fullscreen and then go back to windowed mode then transparency is disabled until you close DOSBox.

The only output mode that doesn't have this issue is output=opengl.

I never really noticed this before because I never really cared (nor do I really care now.....but I suppose someone will)

I found this article:

http://dreamlayers.blogspot.com/2008/12/sdl-a … d-sdl-full.html

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 2 of 15, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

WINDIB will fix the issue but you'd have to make it default for Vista+ OS's and if so we may as well make it default for all OS's.

Current DOSBox behavior will cause the DOSBox intro screen to turn red when DOSBox is switched into fullscreen mode from Windowed mode (default DOSBox.conf).

You'll also get the annoying "The color scheme has been changed to Windows Vista/7 Basic" error message when switching back to Windowed mode.

This is due to Aero being switched off when DOSBox switches to fullscreen. This has been the same behavior DOSBox has exhibited since Vista was released.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 4 of 15, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

> and if so we may as well make it default for all OS's.

That would cause performance loss.

You could solve that for Vista (and maybe Windows 7) by using the default SDL.dll that comes precompiled from libsdl.org when the installer detects Windows Vista/7 and using the DOSBox SDL.dll (with the windib/direct x order reversed) when detecting the older Windows.
Normal sdl.dll has windib used before directx, AFAIK DOSBox uses a self compiled sdl.dll that uses directx before windib (so output=ddraw doesn't fail). That is the source of that problem, I think.

But I don't know if the installer is a) able to detect Windows versions and b) can act upon it.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox

Reply 5 of 15, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

That is the source of that problem, I think.

As hal said this is intentional for simple speed reasons. directx was the well-tested
default for sdl for a very long time, and only recently they stopped to update
the directx part but made the (back then very buggy, now at-least-working)
windib the default.

Reply 6 of 15, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

yeah, I know... With Exult we have the problem that our snapshots come with the regular sdl.dll and that the windib default makes fullscreen not work for many Windows 9x users... 🙁

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox

Reply 8 of 15, by nemesisdb

User metadata
Rank Newbie
Rank
Newbie

I am having this problem and often notice that colors are distorted when dosbox is in full screen mode. Can anyone explain what the best/easist way is for me to fix this problem?

Win 7 64, doxbox .73

Reply 9 of 15, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Color corruption will be fixed in next ver. (DOSBox will use 16bit rendering instead of 8bit).
You'll still need to set the sdl_videodriver=windib if you want Aero Glass though.

If you want a fix for the color corruption now just set the variable and it will fix both (You'll still be using 8bit rendering tho), although with Windows 7 you may still experience corruption in some cases. Explorer.exe in Windows 7 causes color corruption in 8bit rendering programs on Windows 7.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 11 of 15, by ADDiCT

User metadata
Rank Oldbie
Rank
Oldbie

I'm not very familiar with this problem, but may I throw D3D output into the discussion? Wouldn't this be a good time to include the patch (Gulikoza's AFAIK) into mainline DOSBox? D3D feels "snappier" than any of the other output methods, and I believe it doesn't have the problems described in this thread. Of course the patch isn't multi-platform, but fixing the Windows display problems by changing DOSBox code and/or adapting the installer wouldn't be multi-platform as well (; . When looking at the posts here on VOGONS it seems pretty obvious that a large majority of DOSBox users are on modern Windows versions - or that Linux users don't have as many problems, or don't like posting in forums (; .

Reply 14 of 15, by ykhwong

User metadata
Rank Oldbie
Rank
Oldbie

ver3 :
1. Added a delay to wait for Windows Aero to be back.
2. Made it work only under Windows Vista / 7 or later. (Aero is not part of WinXP or eariler.)

Attachments

  • Filename
    aero_fix_ver3.diff
    File size
    4.01 KiB
    Downloads
    467 downloads
    File comment
    version 3
    File license
    Fair use/fair dealing exception

Reply 15 of 15, by ykhwong

User metadata
Rank Oldbie
Rank
Oldbie

This patch sets video driver to WNDIB as default. When setting output=ddraw then it automatically resets to DirectX driver.

Attachments

  • Filename
    windib_default.diff
    File size
    6.15 KiB
    Downloads
    493 downloads
    File comment
    WINDIB Default
    File license
    Fair use/fair dealing exception