It is a known problem with DOSBox using too much CPU resources on OS X. But no one knows how to help it.

OK, at least i can stop trying to find a fix, then. 😉

It might be OK just having DOSBox pause when not focused. The only trouble is that the time freezes too.

Would it be possible to use a TSR that keeps the system clock synchronised to the CMOS clock?

(Sorry, I don't have enough knowledge of the inner workings of DOSBox to know whether the equivalent of the CMOS clock exists... or whether it keeps running when DOSBox is paused... or whether it updates itself from the host systems clock... or...) 😕

Stewart.

I remember having that issue a long time ago with Linux:
Post 83384

So it's likely nothing internal to DOSBox but likely the video rendering.

Oh well, I tried a TSR ("uptim410") to keep the DOS time in sync with the CMOS time.

It seemed to be doing its job but it was quite weird when I ran the "Clock" program in Win3.11 -- after having DOSBox on pause and then un-pausing, the clock was jumping between the correct time and the pre-pause time (jumping there and back every second).

Hmm. 😕

Stewart.

hi, i'm new here. dosbox is awesome btw.

i have had this similar problem in my experience with developing mac apps. it had something to do with a main loop that was not executing anything (polling for something). theoretically it would not be using that much cpu cycles, but in the mac, it has a high cpu % when idle. we solved it by stopping the loop, and retriggering it when the event to be polled is available again.

it may be a different problem, but just my 2 cents.