[Al ex]

OK, that explains it, I guess. Your phone has a Snapdragon 200, which is very low end. Doom might sort of run, as well as any other 286/386 game. Wing Commander 1&2, Ultima 7, Ultima Underworld, there are many great you can run more or less well. But Daggerfall is too demanding, that sinply won’t work, sorry.

But I’ll try it on my tablet, it’s pretty much in the same league: an entry-level quad core cpu @1.3 GHz. It scores ~3900 realtics in the Doom timedemo.

Speaking of which: just follow my post above. Download the shareware version from here, unzip to your DOS game folder.
Launch Magic Dosbox. Start the Doom shareware version with the following parameters:
“doom -timedemo demo 3” (without the quotes, of course).
This will start an automated demo, which will run in slow motion on your phone. At the end, you will be dropped back to the DOS prompt, and at the top, there’ll be your result: “Scored 2134 gametics in […] realtics”. The realtics value measures how fast your phone can run the demo. Lower values are better.

[Al ex]

Daggerfall doesn’t need that much power, a 486DX2 was enough back in the day. So I guess there are three possible reasons why it’s not running properly:

1. Wrong configuration in mDosbox: you need to set cycles=max to get ideal performance

2. old/weak hardware: I don’t think your phone is too old, even my old Galaxy Note 2 (S3 hardware) is easily capable of running Daggerfall.
I strongly suspect you’re trying to run Dosbox on a Snapdragon chipset. As a rule of thumb, Snapdragon cpu’s are really bad for emulators in general.
My Note 4 (Snapdragon 805 @2.7 GHz) was barely capable of running any demanding DOS games. Snapdragons are horrible when it comes to NEON instructions, which, unfortunately, are of extreme importance for fast Dosbox emulation.

The Snapdragon 410 for example, which is “powering” recent phones like Galaxy A3 or A5, as well as many Huawei and HTC phones, is a good cpu in everyday use, but it only reaches a meagre 4100 realtics in the Doom Shareware timedemo. Even my Galaxy S1 was faster 6 years ago, with a 1 GHz single core Exynos cpu.

3. Conservative kernel settings:
Again, that’s mostly a Snapdragon thing. This is because of their bullshit cpu design, that requires them to downclock the cpu whenever possible, to prevent overheating. BUt it might affect other chipsets, too. If you are rooted, you can try to tweak your kernel settings. Ideally, you’ll set the cpu governor to “performance” prior to running Dosbox. Or you try different governors, and tweak their up- and downclock values. Beware that you can damage your phone, if you don’t know what you’re doing.

If you want to do some testing, download the Doom Shareware v1.9 from here. Set cycles=max in mDosbox, leave everything else at default, and run Doom with these parameters:

C:\>Doom -timedemo demo3

The resulting score shows you exactly how fast your emulated DOS machine on your phone is. You can compair it with real PCs in this list: https://www.complang.tuwien.ac.at/misc/doombench.html

For comparison:

A5 stock kernel settings: 4100 realtics (486 33 MHz)
A5 performance governor: 3600 realtics (486 40 MHz

Note 4 stock kernel settings: 2100 realtics (Pentium 75 MHz)
Note 4 performance governor: 1400 realtics (Pentium 90-100 MHz)

S7 Edge stock kernel settings: 760 realtics (Pentium 166 / AMD K6 233 MHz)
S7 Edge performance governor: 640 realtics (Pentium MMX 250 MHz)

[Al ex]

Hm, I haven’t upgraded to Nougat yet, so I can’t verify this. I have experienced a similar behaviour with Samsung SideSync, though: whenever I switch from remote control via PC back to direct control on my phone, I’m dropped back into mDosbox main menu. I thought this was related to the SideSync app switching my phone’s screen on/off, and doing some weird stuff in the background.
I’ll try my own bluetooth keyboard and gamepad.

*EDIT: at least my gamepad is working fine. I can disconnect and reconnect it without any issues. I don’t have my BT keyboard with me, so it’ll take some time before I can check.

[Al ex]

No, haven’t experienced this issue before. What exactly is happening? Magic Dosbox resets itself right in the middle of a game? Or do you enter the bluetooth menu on your device? Because that could put mDosbox into background, and depending on your devices memory, Android kills (and thus effectively resets) running apps, to free up memory. This would be especially likely if you set a large memsize in mDosbox (e.g. 128).
Or, simply put: does this also happen with other memory-hungry games or emulators?

[Al ex]

That’s a really cool layout. Well done! ?

[Al ex]

That’s pretty impressive. ??

[Al ex]

Running emulators inside an emulator is pretty nerdy stuff. But fun nonetheless. ?

[Al ex]

Yes, v2.4 works. But I found it to be slightly more unstable than 2.2.
v3.0 and 2.3 on the other hand are completely broken for me.

Lol, I just tried Fellow (Amiga), and it’s running full speed in mDosbox on my phone. ?

[Al ex]

Fantastic list, kudos for that.?
Small addition regarding C64:
The most recent version of VICE is v3.0. But in mDosbox, 3.0, 2.4 and 2.3 are broken or running badly. v2.2 is the best here, it’s running 100% stable in mDosbox.

[Al ex]

Thanks.?
That font is from Planescape Torment. I really like it, and will probably use it for my Ultima layouts, too.

[Al ex]

Not a Dosbox problem. At least not Magic Dosbox. The mouse works just fine, even if I restart the game several times.
Strange, but this seems to be related to the game version somehow.

[Al ex]

Standard Dosbox answer: don’t use pirated versions of the game. Most rips are woefully broken. ?
You can get an official version over at GOG.com for 5,59 EUR.

I can confirm that Jagged Alliance is working 100% without any tweaks in Magic Dosbox. The mouse cursor is visible, both relative and absolute mnouse emulation modes are working flawlessly. All you need to do is add a new game profile, select JA.EXE as “Main Program”, SETSOUND.EXE as “Setup”, configure sound (SB 16 for Midi and Digital), then run the game. ?

[Al ex]

Best of luck. ?

Basically, the expert settings in Magic Dosbox are the same as the normal Dosbox .conf file every Windows/Linux user has to fiddle with. Magic Dosbox makes it a lot easier to set up most games with its UI optioms. DKeeper was only a very weird and special case.

So as a general piece of advice, I’d suggest you read the readme that comes with the Windows version of Dosbox.

[Al ex]

In my case, all these files are in the same folder as the keeper02.ogg, keeper03.ogg etc sound files:

|-DKeeper (with keeper.exe, game.gog, keeper02.ogg, dosboxDK.conf, etc)
|–data
|–ldata
|–levels
|–SAVE
|–SOUND

[Al ex]

…which means, the keeper.exe is missing. I suspect it’s also located in the /data folder.
Now this is getting rather complex, because your directory structure seems to be different from mine.

Two options:

1. Try this:

[autoexec]
mount c: /storage/emulated/0/Dkeep1/data
imgmount d /storage/emulated/0/Dkeep1/data/game.gog -t iso -fs iso
c:
keeper

2. or copy keeper.exe, dos4gw.exe, keeper.cfg, game.inst and game.gog to /DKeep1, and use this:

[autoexec]
mount c: /storage/emulated/0/Dkeep1
imgmount d /storage/emulated/0/Dkeep1/game.gog -t iso -fs iso
c:
keeper

[Author]

Posts