It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
so I know there's a thread on this already but it doesn't have the answer i'm looking for. I'm so confused right now. I want to play World of Xeen (M&M 4-5) I own Might and Magic VI Limited Edition from gog.com, I copied over the game folder into my micro sc card and still can't get the right command to run the game. I'm trying to run the VOICED version of the game which has all the audio enabled. this is the dir of my game in the sc card is:

/storage/sdcard1/Roms/DOS/Xeen
can anyone please help me get this running on both dosbox turbo & dosbox manager (to have it's own profile)

any one who can write or record a tutorial would help me out the best because i pretty much know NOTHING of dosbox =(.

Lost :(
Attachments:
computer.gif (274 Kb)
I've never used DOSBox on Android, but I have a GUESS as to what your problem might be. When you install the game on Windows, the GOG installer creates a shortcut on the desktop that runs the game. This shortcut specifically tells DOSBox to use a special configuration file (which I believe is called dosboxmm4-5.conf, or something like that) in the game's install directory. This configuration file (also provided by GOG) tells DOSBox what settings to use, and has some commands that automatically launch the game.

When you copy the install folder over to your Android device, this no longer works. First of all, you don't have the shortcut which tells DOSBox which configuration file to use. Second, the path to the game is now different, so the commands in the configuration file that launch the game won't work properly.

Now, you could try to run the game manually, and build your own configuration file, but that's probably really annoying. What's preferable is to find some way to recreate the shortcut that tells DOSBox to run the game with the configuration file provided by GOG. Then you'd just have to edit the configuration file to have the correct path (the one from GOG will have the old, PC path listed, you just need to change it to your new Android path of /storage/sdcard1/Roms/DOS/Xeen).

So: Does anyone know how to set up shortcuts / alternate configuration files for DOSBox on Android?
Wouldn't it be easier to just get the cfg file, rename it to default name (dosbox.conf) and put it in default location (on android I guess it will be program directory?)?
avatar
WTF: Wouldn't it be easier to just get the cfg file, rename it to default name (dosbox.conf) and put it in default location (on android I guess it will be program directory?)?
That might work. Silly me for making things complicated. The path to the game executable would still need to be fixed in the file, though.
avatar
WTF: Wouldn't it be easier to just get the cfg file, rename it to default name (dosbox.conf) and put it in default location (on android I guess it will be program directory?)?
avatar
Waltorious: That might work. Silly me for making things complicated. The path to the game executable would still need to be fixed in the file, though.
Probably, yeah. And path to different cd data for talkie version probably too. And maybe the hotkey thing for switching cds (I have no idea how it's done on android). But the rest should work.
I don't know if any one needs this answer but today I wanted to do the same thing and had the same problems as mentioned. So I solved it that way:

1) I copied the gog folder to my android device and renamed it to MM4 which is just a good idea when you are working with shells. (to Download folder which seems to be the default on kitkat and DBT)

2) I saw a common problem when I'm using dosbox on a linux device as android is. The folder/file names are UpperCase
and the config files refernce it as LowerCase and vice-versa. So I took a look at the filestructure of this gog package. The *.inst files are CUE files and the *.gog files are iso or bin (don't know exactly). I think I don't have to do that but I changed file ending of *.inst to cue

3) I opened the cue files in a text editor and mentioned that the cue file refernces the MUSIC folder as music. And the GAME*.GOG files as game*.gog files. I changed the game1.gog to GAME1.GOG and all music\ refernces to MUSIC\. I did this for both cue files

4) In DBT-Manager I added the following commands for autoexec.bat

mount c: "/storage/emulated/0/Download/MM4"
IMGMOUNT.COM d "C:\GAME1.cue" "C:\GAME2.cue" -t iso
c:
cd world
xeen.exe

5) In DBT-Manager changed the memory to 16 mb ram as the original gog_db.conf requires

6) enjoy the running game ;)

7) Ok there is still a bug. It seems that you only reach the main screen when you watch the whole intro. If you use special keys 'ESC' the game quits whit a 'Not enough Memory' error. This fix works only for the first time. When the WoX Intro is played it will quit with the same error. So I've been playing for one hour on my Android device. When I restarted the game I mentioned this behaviour. :(

8) Ok A google user solved this problem and gave hints within his DBT Review. Change your autoexec section this way:

mount c: "/storage/emulated/0/Download/MM4"
IMGMOUNT.COM d "C:\GAME1.cue" "C:\GAME2.cue" -t iso
c:
cd world
LH xeen.exe

Explanation: LH stands for Load High so the programm should loads it's content into dos High Memory. After some research I found out that the *.CC files are XORed archives that will hold the whole game data including - Cutscenes, Sprites, Maps, SaveGames a.s.o. . When the Programm starts it has to 'decrypt' those data - by XORing every word with a fix value - to do that all data has to be loaded into the RAM. DARK.CC seemed to work cause it is about two MB smaller than the INTRO.CC which seems to be a modified Version of DARK.CC with additional Cutscenes for the world of xeen

Hint:

1) Install GamePad from the same developers as DBT and use this instead of your ordanary android virual keyboard. So the game really makes fun.

2) To avoid those sound clitches set Audio PreBuffer to 35 or a little bit higher. Everithing eles worked with the standard DBT configuration.

3) Set mouse tracking to absolute - now you can use the screen touch functionallity which makes gaming even much more fun

As it works on my device now which is Nexus 7 on KitKat this Topic should be solved. Since this is my first Post I don't know how to suggest this post status
Post edited March 09, 2015 by bluewestshadow