OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: alfie on March 16, 2005, 11:30:13 am
-
I'm an old game freak. Got tons of my XT games all nicely archived, was hoping to play them on my zaurus (C-700)
I've been reading around and realise dosbox and most of the dos emulators work only on X, so I'm venturing on getting pdaXrom installed instead of cacko-rom. (I dun use my zaurus as a pda anyway, more of a platform for code editing (joe) and viewing files.
Anyone knows of any good sites for dosbox on the zaurus ?
-
Basically just download dosbox of the feed and use it. Not much to setup you need to make a config file - do a search people have discussed it before but don't expect miracles. Its hard to emulate x86 but without sound it runs okay i think.
-
Anyone knows of any good sites for dosbox on the zaurus ?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=70968\")
Eh...
This one? -
or this - [a href=\"https://www.oesf.org/forums]https://www.oesf.org/forums[/url]
DOSBox will run in SDL on Sharp-based roms, as well as X,
so it's not a technical requirement; but most of the other interesting
emulators require X, so if you want to emulate things *other* than DOS,
as well, go with pdaXrom.
Additionally, I've noticed some keyboard quirks under SDL-framebuffer
that I don't see under X11, in DOSBox, so it may be a good idea anyway.
Now... DOSBox builds prior to 0.62 seem to run fine, but >0.61 are BROKEN
by default, due to memory alignment problems. I'll post a patch for 0.63 if
you're interested; but I build binaries for pdaXrom only.
DOSBox IS SLOW. Games that are largely CPU-bound (or which halt on user
input frequently) have a subjective feel of a high-end 286, or low end 386.
Games that are heavily graphics-intensive have performance about that of an XT
or worse. Think "80286-12" on average.
-
Basically just download dosbox of the feed and use it. Not much to setup you need to make a config file - do a search people have discussed it before but don't expect miracles. Its hard to emulate x86 but without sound it runs okay i think.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=70976\"][{POST_SNAPBACK}][/a][/div]
thanks for the feed, Laze!
But I see you're still using 0.61. Who maintains DOSBox for pdaXrom,
that I can send a 0.62/0.63 arm patch to? Or should I build a new ipk myself?
0.62 has interactive keyboard mapper.
0.63 is reputed to be faster, but I haven't seen much improvement.
0.63 has some sound bugs; fixed in CVS
0.64 *may* have patch for ARM cpus in the main distribution. (not done yet by far)
Also, some keys are problematic, because of hardwired US-english BIOS
(you can assign Fn-G to Key_Semicolon but you have to press Shift-Fn-G to get colon)
I'll probably make a Zaurus keyboard BIOS patch, too. I *think* this is what LordDavon did, but haven't found his sources....
-
rad --
is there a binary for 0.63 for pdaXrom somewhere?
Scott
-
I'm already reflashing to pdaXrom Will be very happy to get the latest dosbox 0.63 from you.
I'll be running stuff w/o sound. Hoping for the best.
Does the dosbox for pdaXrom uses X11 or SDL ? Is it possible to start it w/o starting X Then if its using SDL-framebuffer ?
Alf
-
Eh...
This one? -
or this - https://www.oesf.org/forums (https://www.oesf.org/forums)
DOSBox will run in SDL on Sharp-based roms, as well as X,
so it's not a technical requirement; but most of the other interesting
emulators require X, so if you want to emulate things *other* than DOS,
as well, go with pdaXrom.
Additionally, I've noticed some keyboard quirks under SDL-framebuffer
that I don't see under X11, in DOSBox, so it may be a good idea anyway.
Now... DOSBox builds prior to 0.62 seem to run fine, but >0.61 are BROKEN
by default, due to memory alignment problems. I'll post a patch for 0.63 if
you're interested; but I build binaries for pdaXrom only.
DOSBox IS SLOW. Games that are largely CPU-bound (or which halt on user
input frequently) have a subjective feel of a high-end 286, or low end 386.
Games that are heavily graphics-intensive have performance about that of an XT
or worse. Think "80286-12" on average.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=70983\"][{POST_SNAPBACK}][/a][/div]
-
Qn: If DosBox is an SDL app, why does it need X ? Or does it ?
-
Qn: If DosBox is an SDL app, why does it need X ? Or does it ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71118\"][{POST_SNAPBACK}][/a][/div]
Its an SDL app, it doesn't need X11, but seems to work rather better with it.
With SDL-fb some keys appear to be misfunctional, mouse doesn't work,
and consequently you can't use the GUI keymapper.
It may or may not be possible to manually remap extended key combinations in framebuffer mode. I haven't succeeded.
Despite all this it *may* run faster, due to less overhead.
Also, you'll have more free memory, which could help for some things.
-
rad --
is there a binary for 0.63 for pdaXrom somewhere?
Scott
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=71020\")
[a href=\"http://zaurus.spy.org/feeds/raduga/]http://zaurus.spy.org/feeds/raduga/[/url]
I'll post a source patch (alignment fix) in a bit.
try 'dosbox -startmapper' for some fun.
Mod1= CTRL
Mod2 = ALT
Mod3 = Fn
Do you know if Lord Davon secreted the source to his mods anywhere?
I'd really like to see what he did with the 0.61 sources to fix the Zaurus keyboard-
brute-hacking the BIOS or something more elegant.
-
no.
and he seems to be gone, again.
-
Ok. I can't get 0.63 to work (libasound.so.2 missing. )
and pressing Fn still generates '1s' .. so how do you compile it yourself? anyone have the alignment patch for .63 ?
This is what needs to be done for the '1s' fix
replace the following lines in src/gui/sdlmain.cpp
/* Special Keys */
default:
code=KBD_1;
LOG(LOG_KEYBOARD,LOG_ERROR)("Unhandled SDL keysym %d"...
break;
/* change KBD_1 to something like KBD_leftshift */
/* or change 313 to just skip and go on? */
I will try to compile dosbox myself, I guess, but I have no idea what to do about the alignment patch and I haven't had great success doing that in the past.
Wendell
-
http://zaurus.spy.org/feeds/raduga/ (http://zaurus.spy.org/feeds/raduga/)
I'll post a source patch (alignment fix) in a bit.
try 'dosbox -startmapper' for some fun.
Mod1= CTRL
Mod2 = ALT
Mod3 = Fn
Do you know if Lord Davon secreted the source to his mods anywhere?
I'd really like to see what he did with the 0.61 sources to fix the Zaurus keyboard-
brute-hacking the BIOS or something more elegant.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71168\"][{POST_SNAPBACK}][/a][/div]
The feeds of dosbox is greate!, works fast than the binary which i build from offical source by myself.
But the problem is the rigth mouse click is not vaild. And the touch screen does not work fine. Any patch or total patches for dosbox on Zaurus?
-
raduga: can you finally share a patch?
-
raduga: can you finally share a patch?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=133035\"][{POST_SNAPBACK}][/a][/div]
I don't think I have the original patch anymore, but 0.64+ has support for ARM
in the main tree (0.65 is current)
when configuring, --disable-unaligned-memory
also, --disable-fpu --disable-opengl may help performance
also, --disable-sdltest --disable-alsatest --disable-debug may help avoid some problems when building and/or running
If the keyboard layout is all wonky, you may need to enable/disable
"usescancodes" in the dosbox.conf file
Some keys ( ex: ":" still needs <shift><fn>g ) need extra work-
a patch to make them work "right" on the zaurus hasn't yet been written.
If you use the current source, or CVS, it should work pretty much good.
-
http://zaurus.spy.org/feeds/raduga/ (http://zaurus.spy.org/feeds/raduga/)
I'll post a source patch (alignment fix) in a bit.
try 'dosbox -startmapper' for some fun.
Mod1= CTRL
Mod2 = ALT
Mod3 = Fn
Do you know if Lord Davon secreted the source to his mods anywhere?
I'd really like to see what he did with the 0.61 sources to fix the Zaurus keyboard-
brute-hacking the BIOS or something more elegant.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71168\"][{POST_SNAPBACK}][/a][/div]
The feeds of dosbox is greate!, works fast than the binary which i build from offical source by myself.
But the problem is the rigth mouse click is not vaild. And the touch screen does not work fine. Any patch or total patches for dosbox on Zaurus?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=133031\"][{POST_SNAPBACK}][/a][/div]
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.
-
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.
-
Thx raduga!
dosbox 0.65 works now - in next week I will add it into 3.5.4 upgrades
-
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]
-
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....
-
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 (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...
-
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)
-
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
-
This (https://www.oesf.org/forums/index.php?showtopic=15580&view=findpost&p=140855) should help with the colon and semi-colon.
I can't help you with the other keys.
Regards,
Doug
-
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
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
build with --enable-fpu
3) mouse loses calibration when it hits edge of touchscreen
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.
-
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.
-
I still want to see steel panthers via dosbox.
-
[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
-
[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
-
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 (https://www.oesf.org/forums/index.php?showtopic=18415&view=findpost&p=154327)
-
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 (https://www.oesf.org/forums/index.php?showtopic=18415&view=findpost&p=154327)
[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
-
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=154331\"][{POST_SNAPBACK}][/a][/div]
hehe, same here: I simply suspended my dosbox configuration project due to the mapper problems.
Will try your package, jeana. Many thanks!
daniel
-
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=154331\"][{POST_SNAPBACK}][/a][/div]
Unfortunately I modified only few keys (as you said : US 101 keyboard is the default map for dosbox)
Here is my few mappings :
Key hitted Character
[Fn] [E] =
[Shift] [Fn] [E] +
Explanation : on a US keyboard, when you click on [Shift] with [=] you will obtain a [+]
[Fn] [T] [
[Shift] [Fn] [T] {
[Fn] [Y] ]
[Shift] [Fn] [Y] }
[Fn] [F] \
[Shift] [Fn] [F] |
[Fn] [G] ;
[Shift] [Fn] [G] :
[Fn] [Ctrl] [1] : Gives the keyboard mapper
[Fn] [Ctrl] [Backspace] : Shutdown dosbox
For information, the US Keyboard layout : [ You are not allowed to view attachments ]