DOSBox can emulate & execute the program instructions in several different ways. Ways and methods that has changed and has been extended over time. Each of these methods are refered to as 'DOSBox CPU cores': Simple, normal, full, and dynamic are some of the more well-known. Some are more accurate than others, some are faster than others. Dynamic happens to be pretty good, and also the fastest - but currently only officially available when DOSBox is running on a real Intel x86 CPU. It achieves this by by translating the emulated 8086/80186/80286 CPU instructions into real Intel x86 instructions and saving the resulting instruction stream for possible later re-use - a.k.a. the dynamically recompiling core.

I hope I got that semi-correct, wd?

http://en.wikipedia.org/wiki/Dynamic_recompilation

Dalboz wrote:

AWESOME ok Renaming DOSBox to DosBox worked! It no longer loads two DOS Boxes. 😁 yay 😁

Ok that half of the problem is solved.

I thought you mean "Renaming DosBox to DOSBox worked", isn't it? 😉

OK, that's a very interesting solution. I have to RSS that on the project site.

I'll have to look what to do to prevent it from loading twice if it is still "DosBox" not "DOSBox" 😳

DosFreak

OOHHHH!

Tyvm for letting me know 😄 ^_- 😄

I will double check CPU Cycles.

IIGS_User

Uhhhh now actually I am trying to figure out what I did. Ok the name was DOSBox.app. So I renamed it to DosBox.app Then it renamed itself back to DOSBox.app

After I did that it stopped double loading.

I have no idea what happened between the automated and manual renamings but it only loads once now 😁

MiniMax OK! Now I understand.

tyvm 😄

Dalboz wrote:

Then it renamed itself back to DOSBox.app

That's strange. 😳

IIGS_User wrote:

Dalboz wrote:

Then it renamed itself back to DOSBox.app

That's strange. 😳

I can't figure it out, but something definitely happened that "fixed" the problem between that.

Dalboz wrote:

I can't figure it out, but something definitely happened that "fixed" the problem between that.

Luckily not another Security Update which brokes functionality of Dapplegrey in Leopard again (yet 😵 ).