That's because you're building the DEBUG build, which is slow, clumsy, lots of unneccessary checking and no optimization. The warning message that you mentioned in earlier thread only happens with DEBUG build, it doesn't complain about it with RELEASE build. The RELEASE build I got with MSVC6 is ~ …

Hi Jbillena, You can download SDL and SDL_net from http://www.libsdl.org/. You need the development libraries, not just the runtime. The rest of them (png, libpng, zlib, pdcurses) can be downloaded from http://sourceforge.net/projects/gnuwin32. If you know how to use VC6, you should already know how …

Budokan has screen artifacts when using DOSBox dynamic CPU core. Normal CPU Core is OK though, and run wonderfully.

After several attempts to fix DOSBox CVS code to build under MSVC6+SP5, finally, I made it...... Here let me summerize the reasons why MSVC6 build is broken after DOSBox 0.60. I used the source I grabbed with CVSGrab at March 19, '04. The re-write of rendering code using C++ template is the major …

After reading a few threads regarding VCPI/EMS and DPMI, I am wondering that are these two interfaces really needed if the sole purpose for DOSBox is to run DOS-based games..... Here I provide some background about VCPI and DPMI, why they exist and hope that DOSBox developers will come back and …

The debug build is broken,too, and in the same way. There is no optimization turned on with debug build. Yeah, you're right, I re-compiled DOSBox CVS using core_normal CPU core, and re-gained back the speed I used to have with DOSBox 0.60, after reading some input from other from my other thread …

Any plan to implement similiar MT2GM or GM2MT mapping as the one available in VDMSound? It sounds to me that DOSBox MIDI implementation doesn't currently perform such mapping, as Music from Roland/MT-32 options from a few games that I tested(GODS, G-Force, XWing etc.) sound quite different from …

Done, still doesn't work. Yesterday, I started with DOSBox 0.60 source which is OK with MSVC6 build, and gradually merge each module from DOSBox CVS. I merged most of the changes and found out that only the rendering code is breaking MSVC6 build. I left a few files unmerged, which is: render.cpp …

By the way, what's the difference (speed, stability etc) between CPU core, core_dyn_x86, core_normal and core_full??

Yes, I'm building DOSBox CVS with the minimum support DLL. So far, only SDL is linked. I don't have write access to CVS currently. I am using CVSGrab from behind firewall. I guess I will post the changes as a patch. For the meantime, I'm going to debug the MSVC6 build before I post them. My guess is …

Just verified my MSVC6 changes with MinGW. Even with the MSVC6 modification, MinGW still produces a good build. Strange......

First of all, great job to all DosBox developers. DosBox is indeed a wonderful piece of marvel. I can now play some old DOS gooddies in XP in windowed mode. Believe me, it really helps for some games to be able to open up notepad to take some notes during gameplay rather than resort to pen and paper …