XTale: Sounds like maybe you're using different dosbox.conf options than some people? Might try running with no dosbox.conf to see what the default options do.

i'm doing the same as you - take the zip, decompress it and start dosbox.exe - no conf at all

Hi guys,

I noticed that the alt-tabbing issue is related to sdl.dll, at least, for me. When I replaced the dll from may 7th with the dll from oktober 2004 (the one that goes with 0.63), the problems went away.
Can anybody confirm this?!

Regards,

Ronald

yes it seems the problem was with sdl.dll.
which source did you use for sdl.dll Xtale ?

I checked their cvs and not that much has changed.

was the official 1.2.8 zip.. weird... seems to went something wrong on compiling, I'll rust replace the dll in the zip

Someone got dosbox working GOOD with a SDL1.2.8 dll?

If I build a sdl.dll version 1.2.8 there are some possibilities:
- I build without directx support -> I get the dll where alt+tab doesnt work (the one i bundled with my builds last time)
- I build with directx support -> I get a dll, where I can't enter fullscreen on my laptop (no output found - or something similar - as error message), no difference if I do the changes to sdl-souce mentioned by hunterz or not.
- I build agains 1.2.8 headers and put the official compiled sdl.dll from libsdl.org in the directory -> I get an error on starting and no working dosbox at all

Either sdl is a bit buggy or my laptop doesn't like sdl

Try the one I posted in the Munt+DOSBox thread.

Any way to lower the sound buffer? It's like, a whopping second delay. Speaking of which, what other config stuffs can we do?

Open your DOSBox.conf and find out. There are lots of descriptive comments in there that tell you what the settings are for.

Hello,
first of all, i'm a new user of DOSBox - but I'm deeply impressed how good it works !!! 😎

Ok. I have some things I observed with the latest version of this build:
1) Crucial for me - i need serial support. Is it not implemented? I found an (older? other?) cvs here in this forum that worked ... and W311 in MSDOS runs with that version. Anyway ...
2) Try to boot a MSDOS 6.22. Open the DOS-Editor. Close it - background color changed. No big deal unless you have black letters on black background 😖 .Starting the Editor 'blind' again and close it (also blind) and the background color is changing again. Some kind of color-cycling???? In the log window there are also some messages concerning 'XGA unsupportes multiread ...'. Unfortunately I'm on another PC at the moment and can't tell exactly the message ...

Keep up the good work !!!

.... sorry, wanted to write white letters on white background ...

I just posted a new build - with a freshly setup mingw/msys
If the problems with sdl are still there, it's my laptops fault 😉

Why hasn't the the page providing the "not patched up" cvs-builds (cvs builds by AEP) not been updated since march? That was well before the 0.65 release.

Because you didn't pay enough.

Can you please explain this to me again?

He's (She's?) mess'n with ya.

There probably haven't been dramatic changes since the release build 0.65 so there's no point to posting it yet. Those that need the special features of the unofficial builds have those available. Don't use the AEP build on 0.65, as it's made for 0.63.

those builds are created for free. So don't expect anything and be happy with the ones you got.

Well.. there's a world beyond the internet, and that one is taking a lot of my time at the moment.

Nevertheless I put a new build online (no screenshots support as libpng is bitching around)

Forgive my ignorance, but what does AEP stand for or imply regarding the DosBox CVS(s) ?

[I've got over a decade of DOS experience, I think I predate "AEP"] 😜

http://www.aep-emu.de/modules.php?op=modload& … aq=yes&id_cat=1