Dosbox On Zaurus :)

[muddog]

Which version were you trying to build and compile yourself?
The feed I put up there is extremely old, and probably newer builds should be faster.

If you use GCC flags appropriate to your system, and an SDL that's optimized for your cpu/video, you'll have the best results overall.

I've seen both right and left mouse buttons fail in some applications; hard to track down, but it looks like an obscure emulation bug.

If the RMB never works, its possible your system is not generating them properly in the first place.  Cacko/pdaXrom/opie/etc all have different ways to generate RMB.

Also... there *are* some problems with touchscreen calibration. I've been investigating this for awhile, and am.... closer to a fix, but don't have one working yet. I'll let you know when I have a chance to test it some more.

HRW: I *was* working on a 0.65 .bb;  sorry, but I got sidetracked.  I'll look into it, when I get a working OE build system back up.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=133074\"][{POST_SNAPBACK}][/a][/div]

I build the dosbox-0.65 by the [cross-sdk-armv5tel-cacko-linux-3.4.6-2.2.5-softfloat] cross compile enviorment. I think that SDL must already be optimized for Zaurus. And about the CCFLAG, any sugguestiong? or you can give me a sample for that.
Thanks  Also about the keymap.

[Hrw]

Thx raduga!

dosbox 0.65 works now - in next week I will add it into 3.5.4 upgrades

[fooman]

Dosbox 0.65 crashes immediately on my poodle running Hentges-opie-3.5.4.1 and the 17-Jul-2006 2.6.17 kernel.  When I run strace on dosbox, this is what I get:

# strace /usr/bin/dosbox
execve("/usr/bin/dosbox", ["/usr/bin/dosbox"], [/* 24 vars */]) = -1 ENOMEM (Cannot allocate memory)
+++ killed by SIGKILL +++

So it dies without even being loaded.  Do you know what could be causing this?

Thx raduga!

dosbox 0.65 works now - in next week I will add it into 3.5.4 upgrades
[div align=\"right\"][a href=\"index.php?act=findpost&pid=133538\"][{POST_SNAPBACK}][/a][/div]

[anunakin]

I just have tested, dosbox 0.65-1 from pdaXrom 1.1.0r121, and it works nice with Master of Orion ONE, not tested with MOO2, but X-wing works too....  

[zodttd]

I'm currently working with DOSBox developers to make an ARM Dynarec for DOSBox. I have a Zaurus pdaXrom build of DOSBox made that runs pretty well! Let me get the build to you now. It's based on the latest CVS revision.

Keep an eye out for the DOSBox dynarec for ARM gadgets.

EDIT: Attached is the latest CVS revision of DOSBox. It's the build only, as it required no modification to the CVS source available at http://pcnwstage.phys.rug.nl/dosboxcvs.tgz
There are some issues with this build:
1. The config file must be used. Run DOSBox as so:
./dosbox -conf ./dosbox.conf
2. The key mapping is wrong. It must be reconfigured. Either "borrow" a keymap file from another DOSBox build for the Zaurus...  ...or to configure it yourself run:
./dosbox -conf ./dosbox.conf -startmapper

The third issue is the touchscreen calibration mentioned by raduga.
Raduga, if you have fixed this issue, could you please let me know what changes were required so I can foward that to the DOSBox developers? Or you can goto vogons.zetafleet.com and post to the Development board. Thanks!

Time to get working on that dynarec...

[Civil]

Cool! It is a lot faster then standart (runs a bit faster then old dosbox with CPU overclocked to 624MHz).
But issues with keymap (down key and right key needs to be remaped after restarting dosbox)

Update:
Sorry. It is faster then 0.63 (a lot) and only 2-3% faster then default 0.65... (maybe becouse of settings). But it is still less usable then 0.63... Keymap is terrible (fn repeats last command for example)

[daniel3000]

Could anybody please post a good keymapping config file publicly?
I have tried with -startmapper, but when I've set all the keys, when I press a key, I get the old character plus the new character!
Also, I could not find a solution to get the colon, semi-colon etc.

Thanks!
daniel

[dougeeebear]

This should help with the colon and semi-colon.

I can't help you with the other keys.

Regards,
Doug

[raduga]

I'm currently working with DOSBox developers to make an ARM Dynarec for DOSBox. I have a Zaurus pdaXrom build of DOSBox made that runs pretty well! Let me get the build to you now. It's based on the latest CVS revision.

The third issue is the touchscreen calibration mentioned by raduga.
Raduga, if you have fixed this issue, could you please let me know what changes were required so I can foward that to the DOSBox developers? Or you can goto vogons.zetafleet.com and post to the Development board. Thanks!

Time to get working on that dynarec...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143458\"][{POST_SNAPBACK}][/a][/div]

thank you, thank you
(and double thankyous to qbix for fixing all the other problems  )

There are three issues I've seen with mouse calibration;
two are easy to fix, the third I haven't resolved yet.


1) mouse mapped to relative movement, not absolute TS coordinates

Code: [Select]

src/ints/mouse.cpp line 423
s/emulate/!emulate/
(there is probably a better place to fix this!)
2) mouse buttons not working in some programs; work fine in others

Code: [Select]

build with --enable-fpu
3) mouse loses calibration when it hits edge of touchscreen

Code: [Select]

no idea.  I've spent hours digging through the code, but I'm still not sure why it does this.
Toggling in and out of full-screen mode seems to reset, so there's a work around at least.

[Reaper]

Just one question before I download and try it:

What's with sound? Really badly want   at least Adlib/SB mono sound on my Z and acceptable gaming speed.

[ScottYelich]

I still want to see steel panthers via dosbox.

[daniel3000]

[try 'dosbox -startmapper' for some fun.
 Mod1= CTRL
 Mod2 = ALT
 Mod3 = Fn
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71168\"][{POST_SNAPBACK}][/a][/div]

Have done so now, with dosbox 0.65 IPK.
I was at least able to assign most character and number keys and enter, so I can enter basic commands.
I had to find out myself that I have to delete the default key assignment first before adding a new one. Didn't know that, so I got double characters on first attempt  

however, it is very difficult (don't know if it is even possible) to assign characters like the single quote, question mark, or the F keys.

Using the Mod* keys in the mapper as suggested above does not even allow to assign a key to a shifted-key because the tappable "Mod1" to "Mod3" fields do not represent the Shift key.

Did anyone find a good mapping scheme for pdaXrom yet?

Why is it so difficult in pdaXrom? Not a single key is assigned correctly without remapping. This seems to be a systematical problem. Maybe fixable easily in the sources.
For example,
key A gives 1,
key B gives 2,
key C gives 3
and so on. Just a wrong keycode offset sonewhere?

Any idea?

This dosbox 0.65 version I installed seems to run well otherwise.
I have successfully started some of the old HP 200L Xapplications, even Lotus 1-2-3 v2.4 runs well.
Only the keymapping is giving me headache.

Thanks
daniel

[Meanie]

[try 'dosbox -startmapper' for some fun.
 Mod1= CTRL
 Mod2 = ALT
 Mod3 = Fn
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71168\"][{POST_SNAPBACK}][/a][/div]

Have done so now, with dosbox 0.65 IPK.
I was at least able to assign most character and number keys and enter, so I can enter basic commands.
I had to find out myself that I have to delete the default key assignment first before adding a new one. Didn't know that, so I got double characters on first attempt  

however, it is very difficult (don't know if it is even possible) to assign characters like the single quote, question mark, or the F keys.

Using the Mod* keys in the mapper as suggested above does not even allow to assign a key to a shifted-key because the tappable "Mod1" to "Mod3" fields do not represent the Shift key.

Did anyone find a good mapping scheme for pdaXrom yet?

Why is it so difficult in pdaXrom? Not a single key is assigned correctly without remapping. This seems to be a systematical problem. Maybe fixable easily in the sources.
For example,
key A gives 1,
key B gives 2,
key C gives 3
and so on. Just a wrong keycode offset sonewhere?

Any idea?

This dosbox 0.65 version I installed seems to run well otherwise.
I have successfully started some of the old HP 200L Xapplications, even Lotus 1-2-3 v2.4 runs well.
Only the keymapping is giving me headache.

Thanks
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143833\"][{POST_SNAPBACK}][/a][/div]

that's because dosbox assumes everyone is using a US 101 keyboard which is not the case with the Z

[jeana]

I found the bug of the mouse.

It comes from SDL library when hidding the mouse cursor.

I commented all the lines in the dosbox source where the hide instruction is used.

Find the modified package and source at New Packages topic

[Meanie]

I found the bug of the mouse.

It comes from SDL library when hidding the mouse cursor.

I commented all the lines in the dosbox source where the hide instruction is used.

Find the modified package and source at New Packages topic
[div align=\"right\"][a href=\"index.php?act=findpost&pid=154328\"][{POST_SNAPBACK}][/a][/div]

thanks for that. i assume you also mapped all the keys as well since you provided a mapper file. i never had the time to figure out how to do it. now i can just use it i guess