I don't know if this is a bug or not but is it normal that running Windows 3.1 increases the memory usage so much? Dosbox 7.1 with memsize set to 16 MB and the dynamic core uses 47 MB (checked with the Windows XP Task Manager). If I run Windows 3.1, the memory usage increases to 59 MB. Running a …

red_avatar wrote: Yeah Lemmings copy protection was a tough one I don't think so. If you search for "The Xoanon's Guide to Cracking" you'll see is an easy one.

franpa wrote: hes talking about DOSBox, not native dos. Me too 😀

wd wrote: No. Save/load works perfectly when booting from MS-DOS.

Is there any speed difference between the X86 and the dynamic cores? I ask this because two different builds compiled for Windows (one with C_DYNAMIC_X86 and the other with C_DYNREC) seem to have the same speed tested with the game Blood on my Athlon 1200.

wd wrote: Maybe switch off the two defines in decoder.h: // #define X86_DYNFPU_DH_ENABLED // #define X86_INLINED_MEMACCESS Nope 🙁

VisitntX wrote: It works perfect in dosbox, i'm using it with the emu, but the function to save/load isn't work. The save/load function works if you boot from a real MS-DOS disk. I tried it with a MSDOS 6.22 disk and Zak McKracken and worked.

CPU_Core_Dyn_X86_Run() is reached. But does it already hang then? Can you single-step from that point on? Yes, I can single-step from there, set a breakpoint, etc. I'll try a little program like keyb and trace DosBox from the beginning. Wow! A600, is it possible for you to distribute that compile? …

Where/when? Does it reach CPU_Core_Dyn_X86_Run() ? CPU_Core_Dyn_X86_Run() is reached. The problem is, the Xbox hangs so the debugger losts the connection and the problem can't be traced. Be sure the core is actually compiled in, and the dynamic core is disabled. Select core=dynamic then (=auto …

Hello, Dynamic core never worked on the xbox so after reading this post about using VirtualAlloc (I remember having similar problems with ZDoom) I gave a try and did a quick port from the latest CVS. Sadly, the Xbox and the Visual Studio debugger hangs with the dynamic core enabled so I can't see …