There are several things to reduce memory footprint on low-memory devices
in the cvs, so not sure why the 0.72 release was chosen as starting point.

wd wrote:

There are several things to reduce memory footprint on low-memory devices
in the cvs, so not sure why the 0.72 release was chosen as starting point.

Eh, most people don't look for the CVS, but just download the latest official release. And the CVS isn't linked to on the download page either.

So I don't find that particulary surprising.

So most developers download the latest official release?

Why would the CVS be linked on the dosbox.com website?

point taken. i actually found a cvs source tree on my hd (been looking at that because of 3dfx support some time ago).
never do mind. i'll move to using the cvs source eventually. think of this 0.72 based build as a "feasibility study" :-)

can you make it so it calls the onscreen keyboard on launch? Or are you using direct screen write?

Wait, just read that there's no API for the virtual keyboard. wtf Nokia?

till there is a keyboard, put the commands to launch whatever you want in the autoexec section of the conf file. (.bat files are your friends)

working on building the dynamic core, and also looking into the cvs code.

the next aim is to get a dos4gw game running (x-com :-)

kolijoco wrote:

the next aim is to get a dos4gw game running (x-com 😀

That's a very admirable goal, I would absolutely love to be able to play X-COM on the phone 😎

fixed some more problems:

dos4gw will now run, so i can run x-com's intro (its a bit slow, but hey :-),

unfortunately the game itself is still crashing :-(

i also changed the shell's video mode to 0x13 (mcga), so now you can actually read console output (i'll make this a configurable option later, for now its hardcoded - easier for me to debug stuff on the device).

also fixed some virtual mouse issues, so the thumb-thingy should now function correctly as arrow keys and enter (pushing the thumb-thingy) when virtual mouse is turned off (needs the stuff in the updated mapper.txt!) arrow keys now respect your orientation setting.

since the provided mapper.txt supports entering numbers, backspace and enter (also cursor movements), if you create numbered bat files (like 1.bat, 2.bat) in your dos root dir, you can actually get some interaction (like launch the game you want). just mod your autoexec in the conf to mount and change to the root drive. once in the shell you can start "typing" :-) [1] [ENTER] to start 1.bat (you get the idea :-)

attached the new version of the sis, and the updated mapper.txt (you'll need the whole pack from the previous post for the deps and the instructions in the readme, if you're just starting)

Wonder if it would work better if one used dos32a instead of dos4gw?

Since you wanted to see what games people would run on your port, here's my phone running http://en.wikipedia.org/wiki/Heartlight_%28game%29!

A little slow, and no way to actually control it, but awesome, so awesome.

Could it work with a Motorola Z8? (Symbian 9.2 & UIQ3)

Edit: I can't deavtivate the security-test for the installation. 🙁

i can run it on my E71

[/img]

nice :-)

OMG... I was waiting for something like that for years!!... Especially to run Magic Candle on it ... and what... today I came across this forum... and a screen of MC played on S60 !!!! Awesome!!!

Gonna try it next hour on my E65...

hm... got memory problems... at 18.5MB RAM free does not want to run... I've installed an advanced tasks/processes manager to be able to kill some in order to free some memory up... however my battery is going down ;/ will try it later on 😀

...

I managed to get 23MB free ram.. still nothing... keep saying "memory full, close some applications and try again" 🙁

I think I can forget about running it on my phone 🙁

please be patient if you have memory issues. as soon as i'm done debugging some compatibility stuff, i'll streamline the code to lose some weight!

ooh, playing on a full keyboarded phone like the E71 must be great!

Nokia just announced the 5603 XpressMusic. What's cool with this device is that it got a 600 MHz ARM11 CPU! Quite a difference to the previous 3xx MHz S60 phones! 😎

kolijoco wrote:

please be patient if you have memory issues. as soon as i'm done debugging some compatibility stuff, i'll streamline the code to lose some weight!

Ok, will be looking forward for that 😀

From what I read on this page one need around 40MB memory to run it (as of now). Is it actually feasible to trim it down to 20MB? Because that's what my nokia E65 offers to the user. I know that it is a bit of crap but except of the memory issue I like my mobile 😉

Thanks!

TLB reduction might give some 10+mb, disabling rarely-used devices as the
gravis emulation might give a few mb as well, all in all 20mb of total memory
might not be enough though.