Hmm... No traffic here for nearly four years... I wonder if anyone is still using DOSBox on their N900s...

Never mind, it might be worth a shot. Posting costs nothing (yet ).

As mentioned in another thread, I have recently rediscovered some old PC games. After playing for a while I noticed some... let's say interesting effects. The list is short but the blurb is rather long-winded. Sorry about that:

• Running DOSBox sucks the battery dry in no time. 30 minutes of DOSBox is like 8 hours on standby. 2 hours and the phone is dead. But that is hardly surprising, DOS is not really optimized for idling.
• When the screen timeout kicks in, DOSBox loses the mouse. Tapping on the screen is no longer registered. The screen does not need to blank out completely: it dims first for a few seconds before switching off, but the mouse is lost the moment is starts dimming. It had bugged me for a while - I went through hoops to kill and restart the application to get the mouse back - until I found that simply turning the screen on again by the slider on the side solves the problem.
  This effect can be observed immediately. Start DOSBox and wait for 30 seconds for the screen to time out.
• After a few hours of play and then leaving the game and exiting DOSBox (legally, through menu options and the "exit" command), I get back to the Maemo desktop, but the screen is all wrong: the wallpaper is gone, the icons descriptions are gone, the rotation lock setting is gone... I have to reboot the phone to get back to normal.
  This is accumulative. It does not need to be a single, several hours long session. I can play for two hours, exit, start again, play for 30 minutes, exit... After a few cycles like that, usually taking 2-3 days, I am guaranteed to get into the described situation. The best way to avoid it is a prophylactic reboot after every day of play, then the leak or whatever there is never has a chance to accumulate enough to trigger the effect.
  The fact that it accumulates over multiple instances of running and exiting DOSBox and the game makes me believe that it is not a leak in the game itself, but in something that keeps running after the game and DOSBox is terminated. Hildon desktop? The kernel?
• Sometimes,if ignored for long enough, the above effect can accumulate enough to corrupt the graphics inside DOSBox itself. Once that happens, it may no longer be possible to exit the game normally, it may need to be killed by brute force.
• A more lasting effect: the browser history is corrupted, although I have observed that in the past in unrelated circumstances. Any unexpected reboot can corrupt the browser history. You need to clear it.
• By far the most serious: I lost the receiver speaker. The phone rings, I answer - silence. Switch to a loudspeaker, OK. Switch to Bluetooth, OK. Switch back to the receiver, silence.
  I suspect a corrupt file in some package, but which one? How do I find out?