[General Topics] Menneisyys:
In the chart HERE (sorry, it'd be too big to be included in here - you'll need to click the link), I both explained ALL the parameters in the configuration file of n0p's DOSBox and compared the original desktop version to that of n0p, as far as these parameters are concerned. As you'll see, n0p's version uses the values of only very few of these parameters, unlike the original desktop version. (Actually, in this respect, Wall's approach in his pDOSBox 2b2 is better - he has deleted all the non-supported parameters from the config file, making it much more approachable for anyone not having read my description of what is used and what is not.)

The chart also provides an excellent summary of the meaning of these parameters. This is very important because n0p's original documentation (available HERE) is pretty weak (or straight non-existing) and noone else has ecer published anything comparable, as far as his port is concerned.

2.1.4 n0p's DOSBox 0.61

This highly outdated and slow(ish) version should just be forgotten. Always prefer the latest (0.63) version to it.

2.2 Wall's DOSBox port (current version: 2 beta 2), pDOSBox

(Alternative download with the sources HERE (see the bottom of the page) and here)

This, unfortunately, fully discontinued (also see THIS) emulator has some goodies; most importantly, (W)VGA support. It's therefore highly recommended for (W)VGA users wanting to play high-res (CGA hi-res, EGA and VGA hi-res) games. However, no one else should want to use it on a daily basis - (W)VGA device owners only wanting to play low-res (320*200) CGA / EGA / MCGA / VGA games should stick to n0p's port (introduced above) because of the vastly superior speed, sound support, transparent SIP etc. Note that many state Wall’s pDOSBox is faster (see for example THIS) than n0p's emulator. That's certainly not the case, particularly when it comes to sound emulation.

A tip: as the beta is expired, you'll need to set back the internal clock of your handheld before starting the emulator. For example, if you set back just the year to 2006, it'll work just great.

Another tip: the emulator often crashes upon using backspace when you delete something in a previous command taken out from the DOS history. This means don't use the backspace when in the DOS command line with constructs like "cd somegamename / somegamename", where you try to delete "cd" from before somegamename - it'll most probably lead to a crash.

I'd like to thank Michu (author of the well-known EmuPage - a MUST for every emulator fan!) and AximSite forum members heybhouse and Half Decaf for helping me finding this version.

2.2.1 Using pDOSBox 2 beta 2

After downloading and unpacking, you’ll need to transfer the files (along with the subdirectories) to your handheld (a storage card will do just fine). Start the emulator by starting PDBFEND.EXE. As with n0p’s DOSBox, you’ll want to create a shortcut to this file from your Programs menu; this is also explained in the README.TXT in the same directory.

Using the emulator is pretty much the same as with that of n0p’s DOSBox. You mount a directory (which can also be on a card) with a command like mount c "\SD card", go to the new virtual drive and start your favorite apps.

The emulator has a similar on-screen keyboard (SIP) than n0p’s DOSBox. It, however, isn’t transparent; this also means that, if the DOS prompt is already under the (maximized) SIP, you won’t see anything of it, unlike under n0p’s DOSBox. That is, you won’t see what you write. To quickly fix this problem, issue the ‘cls’ (CLear Screen) command (consisting only three letters, it's easy to be entered even if you don't see the prompt); it’ll clear the screen and the prompt will be shown at the top.

Unfortunately, the keyboard, unlike with n0p’s DOSBox, can’t be maximized by clicking the upper left corner of the screen. The only way to maximize it is pressing the Left arrow on the D-pad, while you can switch between the three panels using the Down arrow. This, unfortunately, also means you can’t use the D-pad in, for example, games.

Finally, another disadvantage of this port is the fact that it doesn’t support automatic emulation optimization – that is, built-in fine-tuning the emulation “strength” based on the CPU load. This also means you will also want to keep an eye on the actual CPU load of the given application / game and, if it has reached 100% and is constantly staying around it (not decreasing under 96-97%), just decrease the cycles given to the emulator. This, when done properly (so that the CPU utilization remains between 90 and 95%, but doesn’t exceed, say, 97%, driving the CPU into saturation and leading to (even more) sound problems and, after a while, visible visual performance degradation) maximizes performance. As games / apps are vastly different in their CPU usage, manually tuning the performance can be a real pain in the back. This is why the auto performance tuning in n0p’s app is a godsend – there, all you need to do is decrease or increase the frameskips, which is far easier and requires far less manual work than the cycle emulation fine-tuning in DOSBox ports not sporting auto settings.

2.2.2 The old pDOSBox 1.1

An earlier, release version of the above-introduced pDOSBox. It is clearly weaker than pDOSBox 2 beta 2. Therefore, I don't recommend it at all, unless you, for some reason, want to prefer it over 2b2: for example because you don’t want to set back the clock all the time.

2.3 PocketDOS 1.12

PocketDOS is the oldest MS-DOS emulator for Windows Mobile. It has been around for quite a while - well before the first DOSBox ports. It was, however, only lately that it became a bit more gaming-friendly; for example, it only received VGA support (including high-resolution modes on high-res Windows Mobile handhelds) in 2004.

Unfortunately, in general, it's less suited for generic gaming than n0p's version. Not only because of the non-existing (and, as far as beeper emulation is concerned, vastly inferior to that of n0p's DOSBox) SoundBlaster / AdLib emulation, but also because, in general, fewer titles run under it. A well-known example of this is Civilization, which, as of the latest, 1.12 version, still refuses to run, unlike under n0p’s DOSBox port.

The latest, 1.12 version of the emulator has just been released. The promised emulation speed increase (when using the built-in core and not enabling the other, 286+ cores) is indeed pretty good and, generally, outperforms even n0p's DOSBox in some games and is indeed faster than the previous, 1.11 version. Also see my Norton System Information benchmarks in the main comparison chart, which clearly shows the new version has indeed become faster. Also, some (minor) bugs have also been fixed; for example, the missing toolbar / SIP keyboard issue on the Dell Axim x51v (see THIS screenshot, taken under the old version).

It has some other goodies too. For example, unlike any of the DOSBox ports on Windows Mobile, it does support physical serial ports and printing. You may find this functionality important if you need to run legacy MS-DOS applications collecting data via the handheld's serial port and/or need to print out some stuff.

Also, another definite advantage of the title is being based on a full DOS operating system. This means for example batch files calling even scarcely used DOS commands, using not widely used command-line parameters, the full DOS operating system will know it. This is what the DOSBox ports are clearly weaker at. Note that you can choose from three versions of different DOS versions (that of Caldera (ex-Digital Research), DataLight and, in addition, the default FreeDOS) upon installing the application as can also be seen in this screenshot. You can even install more than one of them and just switch between them in Settings / System / Startup / Boot from (screenshot) when you need to switch (because, for example, a given application or game doesn’t run under the default FreeDOS. An example of these apps / games is Legend's Spellcasting 201, which doesn't run under the default FreeDOS.)

However, in most cases (when you only want to run some programs / games and don’t want to issue delicate DOS commands or run batch files that do depend on some scarce feature of DOS not present in the DOSBox implementation), being based on a full DOS doesn’t deliver much advantage as most games don't make extensive use of the external DOS commands - not even internal (command.com) ones.