Can't reproduce it -> can't debug it.

That's at least a plausible statement ... 🙁

Ok, this win3.x of mine is bloated anyway. So I guess I will install a "fresh" version once the official 0.66 dosbox is out and just hope that the problems do not appear again. Maybe it is relates to the fact that I originally installed this 3.x "system" using dosbox 0.63 cvs-builds - which were less compatible -, this resulting in some weird errors of the win 3.x installation that have appeared only recently (????).

Still, a very strange issue.

With dosbox 0.66 release candidate 3, my win31 installation seems to be stable again.

But ... a new problem has occurred:

The Win3x sound-system seems broken now. I can play Midi files, but no digital sound. No start sound, too.

This does not happen with any games I have tested yet (dott, gp2, doom2), but seems to be a windows-only problem.

It does not happen with dosbox 0.66 release candidate 1 (though that one had other problems with my win31, as most of you know ...)

When I replace the new sblaster.cpp with the previous one (which is, I think, from 2007.01.08) the problem disappears.

Windows does not seem to like the "improved sb-mixer".

Anyway, good work.

we'll take that information to the back. Thanks

kruwi which drivers for the soundblaster are you using ?

I'm using the sbpro2 drivers.

from original windows disks? which windows version?

from the original sbpro2 discs. Windows version is 3.1 (not 3.1.1).

try the different sbtype= settings in dosbox.conf (especially sbpro...)
and reinstalling the drivers

I've used the sbtype=sbpro2 type setting for more than a year now. The drivers are ok, as they work with with the "old" sblaster.cpp and with every cvs-build from before yesterday.

I didn't question the integrity of the drivers but asked to test if reinstalling
those drivers helps.

Kruwi, can you catch log of mixer commands(registers)/values that the driver attempts to write/read from sb registers?

E.g., in sblaster.cpp (debug build) for that you can put

1static void CTMIXER_Write(Bit8u val) {
2+ LOG_MSG("write mixer %x : %x",sb.mixer.index,val);

and

1static Bit8u CTMIXER_Read(void) {
2+ LOG_MSG("read mixer %x",sb.mixer.index);

Or if you can point location of drivers that you use (or PM them..)

OH, and does it work if you try other settings, like: sbpro or sb16? (as wd already wrote, but I'm especially interested for sb16 option)

Changing the sbtype to sb16 or sb did not solve the problem.

Reinstalling the drivers did not help either.

Srecko: Your suggestions are a little bit to technical for me. I do not know much about this debugging stuff. How do I compile a build with debugging features anyway?

I thought that you compiled dosbox yourself, but if you just use CVS builds, than please just ignore my last post:)
Don't bother if you aren't familiar with debug builds either because it can take time to set up all dependencies.

But if you are willing to try:
In Linux/Mingw (AFAIR) you add --enable-debug (or similar switch-see ./configure --help) to configure command. You need ncurses devel & runtime libraries installed (maybe it's pdcurses for mingw).

In Visual Studio there is a config.h file and a debug-related #define in in visualc_net dir (needs correctly installed pdcurses libs for VS, for me it took a while to get them installed in correct places).

To log messages to file, create new config file - for debug build it has extra [log] section (e.g. in dosbox, config -writeconf dosbox.conf) and there is configuration option for it.

I might try to find those drivers myself as well (there was a website with huge list of many SB driver variants with downloads somewhere).

EDIT: this one?: http://www.winsite.com/bin/Info?500000032731

What Srecko posted:

static void CTMIXER_Write(Bit8u val) {
+ LOG_MSG("write mixer %x : %x",sb.mixer.index,val);

means search for something like "void CTMIXER_" or so (the first line)
and add (the +) that LOG_MSG line, then recompile and re-run.

I have ncurses and ncurses-devel installed.

Still, I get the following error message:

kruwi@linux-xi5p:~/Desktop/dosbox> ./configure --enable-debug checking build system type... i686-pc-linux-gnu checking host syst […]
Show full quote

kruwi@linux-xi5p:~/Desktop/dosbox> ./configure --enable-debug
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for sdl-config... /usr/bin/sdl-config
checking for SDL - version >= 1.2.0... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for unsigned char... yes
checking size of unsigned char... 1
checking for unsigned short... yes
checking size of unsigned short... 2
checking for unsigned int... yes
checking size of unsigned int... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking for unsigned long long... yes
checking size of unsigned long long... 8
checking for int *... yes
checking size of int *... 4
checking if environ can be included... yes
checking if environ can be linked... yes
checking for powf in -lm... yes
checking if compiler allows __attribute__... yes
checking if compiler allows __builtin_expect... yes
checking for ALSA CFLAGS...
checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread
checking for libasound headers version >= 0.9.0... found.
checking for snd_ctl_open in -lasound... yes
checking whether byte ordering is bigendian... no
checking curses.h usability... yes
checking curses.h presence... yes
checking for curses.h... yes
checking for initscr in -lcurses... no
checking for initscr in -lpdcurses... no
configure: WARNING: Can't find curses, debug mode disabled
checking for target cpu type... x86 compatible
checking whether x86 dynamic cpu core will be enabled... yes
checking whether fpu emulation will be enabled... yes
checking whether x86 assembly fpu core will be enabled... yes
checking whether to enable unaligned memory access... yes
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for png_check_sig in -lpng... yes
checking SDL_net.h usability... yes
checking SDL_net.h presence... yes
checking for SDL_net.h... yes
checking for SDLNet_Init in -lSDL_net... yes
checking whether opengl display output will be enabled... checking for main in -lGL... yes
checking for main in -lopengl32... no
checking GL/gl.h usability... yes
checking GL/gl.h presence... yes
checking for GL/gl.h... yes
yes
checking SDL_sound.h usability... yes
checking SDL_sound.h presence... yes
checking for SDL_sound.h... yes
checking for Sound_Init in -lSDL_sound... yes
checking for Sound_Seek in -lSDL_sound... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking for mprotect... yes
checking for setpriority support... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/cpu/Makefile
config.status: creating src/cpu/core_full/Makefile
config.status: creating src/cpu/core_normal/Makefile
config.status: creating src/cpu/core_dyn_x86/Makefile
config.status: creating src/debug/Makefile
config.status: creating src/dos/Makefile
config.status: creating src/fpu/Makefile
config.status: creating src/gui/Makefile
config.status: creating src/hardware/Makefile
config.status: creating src/hardware/serialport/Makefile
config.status: creating src/ints/Makefile
config.status: creating src/libs/Makefile
config.status: creating src/libs/zmbv/Makefile
config.status: creating src/misc/Makefile
config.status: creating src/shell/Makefile
config.status: creating src/platform/Makefile
config.status: creating src/platform/visualc/Makefile
config.status: creating visualc/Makefile
config.status: creating visualc_net/Makefile
config.status: creating include/Makefile
config.status: creating docs/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

for those LOG_MSG you don't need the enable-debug flag.

Just run dosbox like this
./dosbox > dosbox.log
and look if something appears in the file dosbox.log

Nothing appearing in dosbox.log ... . 🙁

you added that LOG_MSG ?