Well it looks like we really have nailed it. Of course I say we in a very casual way as I contributed next to nothing here. Still I'd like to take a moment and thank everybody who participated in this thread. I can't tell you how refreshing it is to now have a version of DOSBox that I can use in OSX that won't just die on me after ~30 minutes of use.

What's even more impressive is that no developer in this thread actually has an OSX machine and yet they managed to solve the problem.

Thanks a lot guys. I hope you guys realize how much we love DOSBox and appreciate the endless time and effort you have put into it.

On ia32, adding a long int and a float is done as doubles internally.
On amd64, adding a long int and a float is done as floats internally.
(Tested with gcc 4.1 in linux.)

Thanks for the explanation, makes sense 😀
Also thanks for looking into the issue, as well as your patch.

darkgamorck wrote:

Well it looks like we really have nailed it. Of course I say we in a very casual way as I contributed next to nothing here.

What's even more impressive is that no developer in this thread actually has an OSX machine and yet they managed to solve the problem.

Don't see yourself short man. If you hadn't reported it ,it wouldn't have gotten fixed (at least any time soon).

Well technically I didn't report it either 😊

I love your new avatar though DosFreak. Is that from Grindhouse?

darkgamorck wrote:

Well technically I didn't report it either 😊

WTF are you doing here again? 😀

I love your new avatar though DosFreak. Is that from Grindhouse?

Yep, Kurt Russell is one of my favorite actors. Saw Grindhouse the day It came out in theatres. I'm one of those weirdos that prefers DeathProof to Planet Terror though.

Heard they are trying to make full movies out of "Don't" and "Thanksgiving" yesterday....

Things seem ok now, but... Er, another question...

Why cast PIC_TickIndex()'s return type to double in PIC_FullIndex() instead of specifying it in PIC_TickIndex()'s definition? i.e.

1INLINE float PIC_TickIndex(void) {
2	return (CPU_CycleMax-CPU_CycleLeft-CPU_Cycles)/(float)CPU_CycleMax;
3}

instead of

1INLINE double PIC_TickIndex(void) {
2	return (CPU_CycleMax-CPU_CycleLeft-CPU_Cycles)/(double)CPU_CycleMax;
3}

Just curious...

Well that's a nonlocal change so you have to check where else PIC_TickIndex()
is called. Depending on that it might be better/worse.

That is my confusion. PIC_FullIndex is used far more than PIC_TickIndex, although admittedly, one could say that because TickIndex is used by FullIndex, that TickIndex is used slightly more.

I've been having this exact same problem with doxbox
and following this thread. Can someone help with my
dumb question of how to apply the timer precision patch??!

thanks

Checkout the source into, say, ~/dosbox
Get the patch file
Go to ~/dosbox in terminal
Execute: patch -p0 < /path/to/dosbox_timerprecision.patch
Then configure && make
You could update the 0.7 DOSBox.app by copying the new dosbox binary into /Applications/DOSBox.app/Contents/MacOS, but be aware that by default, the binary is not a static build.

Uh ... thanks for your reply, but im not a
progrmammer so i dont really understand what
you just said! could you explain in simpler
terms?! thanks.

Or better yet, just post a compiled version of .70 (UB please) with the fix above.

Has this fix even been committed to CVS yet?

nope

I finally managed to patch the current CVS version and compile it, and it worked just fine for many consecutive hours of play.

Well there is no point in releasing a new version until the fix gets committed to CVS. I mean this isn't just an OSX issue, but also an issue with AMD64 architectures and Linux as well. I supposed it would also be an issue if you used XP64 or Vista 64 and compiled your own version with the appropriate 64 bit tools.

Well there is no point in releasing a new version until the fix gets committed to CVS

Yep.

How do I compile a statically linked version of DOSBox under OSX?

'Ello all. My first post.

Anyhow, I read through this thread to see if the answer to my Mac OsX problem was already solved. Sadly, it wasn't.

My computer is running OSX 10.4, at 900MHz with 384megs of ram.

Sadly, DOSBOX crashes about 10 seconds afters it opens. I can see the black black where, the dosscreen should be some of the time. Most of the time all I see are the menu bars. Then it stops. Then I receive a dialog box stating that only Dosbox was affected and the rest of my programs are fine.

Hello, Welcome to the forums.

What have you tried so far?