Re: DOSBox 0.72 update
 

I just found this post on DosBox, and I don't know where else to ask my question, which is:

On the N900, and using the key mapper, is Dosbox now working with all of the keys accessible? I mean, is DosBox fairly stable and quick on the N900, and can I use any key from the N900's keyboard, including the numbers keys and + - / \ : ; etc. and will all keypresses be understood by any program running in DosBox?

Thanks.




[

dosbox now running on Nokia 770!



:D

Download at http://pupnik.de/dosbox.html

Changes: Packaged to .deb, updated to 0.72+ cvs with new alignment fixes. Support for xkbd autostart. Mouse auto-calibration should work in some games - drag stylus slowly across all four corners of the game screen.

Update Feb 16: New N800/N810 version up - should install without dependencies - fixed N810 keyboard problem - should install on OS2007 also (not tested).

Update Feb 27: Thanks to ukki we now have Rubybox! a dosbox frontend launcher specifically for maemo/ITOS.

Rubybox requires two ruby packages:
ruby1.8
ruby1.8-maemo
To install these on OS2008, click on the following link to the .install file for the GPL Systems Repository (repository containing ruby) then in application manager go to the section 'programming' and install the ruby packages.

[

Update March 04: New dosbox bundled with vertical/left-hand-side keyboard map. You can now change the .xkbd map by editing /usr/bin/dosboxkbd to point to whatever .xkbd layoutfile and -geometry positioning you want.[/QUOTE]

Re: DOSBox 0.65 ... ftw
 

looks stable... i have never used it tho... youtue it you'll see a bunch of ppl using to emulate win3.11/win95 etc.

Re: DOSBox 0.65 ... ftw
 

Recently, I got a strange problem with Dosbox on N900. When i try to use it with:
...in config, Dosbox crash with segfault. Here is output I get, when running it from within terminal:
I thought it is something sound-related, but messing with sound emulation settings doesn't help, and just setting:
..."fixes" the problem. Ho ever, surface doesn't allow scalling, so I get original resolution (even in fullscreen) = most games are unplayable, or too small to be enjoyable.

The most weird thing is, that it worked with same setting ~2 months ago. I haven't used dosbox in meantime, nor changed it's settings. Ho ever, for sure I've updated some packages - I got no idea, which one may be related. I'm using latest CSSU and kp48 (also was updated in time between last use of dosbox, and today failure)

I tried to search this thread for similar issues, without any luck. Help *much* appreciated...

/Estel

Re: DOSBox 0.65 ... ftw
 

Ok, some new research data about "problem":

output=overlay still result in segmentation fail, no matter of settings. ho ever, I "discovered", that error lines just before segfault - about alsa, snd etc - are not related to problem. They appear also, when using output=surface.

It seems now, that surface is only one working mode for N900. Ho ever, it's possible to use it with image stretched to full screen - using <any scaner>2x (3x ones result in segfault, probably for resolution reasons). It seems ok - still I think surface=overlay with scaler=none and fullscreen resolution set to 800x480 could be faster, but it isn't working. And, I'm not sure about any speed advantage, it's just guesswork (hardware scaling).

It seems that I might be mistaken - maybe it was surface, that worked month or two ago. It's possible that I experimented, and by accident, left output=overlay for a long time, resulting in "me thinking" that such settings worked before.

Re: DOSBox 0.65 ... ftw
 

Shameless bump, + another small question - is there a way to achieve right mouse click in dosbox? I got it working in Maemo by using alt_gr(also called - wrong - FN, aka blue arrow) + tap, but dosbox ignores Maemo settings...

Thanks for help in advance, if, by any chance, someone is still reading this. Which, I'm beginning to doubt ;)

Re: DOSBox 0.65 ... ftw
 

What about the volume rockers? :)

tbh, I use DosBox within NITDroid, works much smoother.

Re: DOSBox 0.65 ... ftw
 

To be honest, unless someone give rationale why it should run smoother on incomplete (for N900) OS, I count it as placebo effect. I remember, that you were advocating aDosbox as "faster" few months ago - then, after requests for source code (due to adosbox violating GPL), it turned out to be worth of *none* speedup changes, compared to real dosbox. So, it worked exactly the same way as normal dosbox.

If this time You're using regular dosbox on Android, it is also placebo, cause code is exactly same.

---

Anyway, volume rockers are F8 and F7, respectively. Finally, I found a way to assign F10 and other non-standard keys - without need for external keyboard. I was interpreting mapper wrong way - keyboard show on it is virtual, and pressed keys are "real", hardware ones. I thought it is the way other (displayed keys real, pressed is binded virtual).

So, it was just matter of choosing F10 on screen, pressing key I like to assign as F10 (lets say x), then, deleting binding virtual x to real x (otherwise, pressing x would result in casting x and F10 at the same time).

Still, I have no idea how to assign right mouse button in dosbox - it is crucial in some programs and games.

/Estel

Re: DOSBox 0.65 ... ftw
 

While it might not be sexy, I use xbindkeys with xmodmap.

/usr/bin/left
xmodmap -e "pointer = 1 2 3"

/usr/bin/right
xmodmap -e "pointer = 3 2 1"


/home/user/.xbindkeysrc
"usr/bin/left"
F8

"usr/bin/right"
F7

To find the correct key code to change the bindings
xbindkeys -k

To start the key bindings
xbindkeys

To end it
killall xbindkeys

Cheers. :)

Re: DOSBox 0.65 ... ftw
 

I asked this awhile ago to make it easier but never got a response.
http://talk.maemo.org/showthread.php...ys#post1065744

Re: DOSBox 0.65 ... ftw
 

I think you mean anDosbox, not adosbox.
And yes, if you do compare them, you WILL see that it IS much smoother then the Maemo version.

Also, the use of special keys are just working VERY well on anDosBox. I will make a video where you can see that it IS actually MUCH better then the original Maemo port.

I'll be back with a video comparison.

Re: DOSBox 0.65 ... ftw
 

Hey, I also use xbindkeys (right click is for me "blue arrow" + tap), and it works on Maemo and ED. Still, it doesn't work on dosbox (due to keyb rover.sys, I suppose - it's using "blue arrow" other way).

Have You achieved right click functionality in dosbox with Your method? If yes, what I'm missing? sorry for dumb question, but I'm quite lost in this case.

Keep in mind, that I'm using N900, on Diablo it may look a little different.

/Estel

Re: DOSBox 0.65 ... ftw
 

Ok, here you go, a video comparison with DOSBox on Maemo 5, anDosBox on NITDroid, and anDOSBOX also on NITDroid.

See for your self and stop wasting time using DOSBox on Maemo 5...
It really is more usefull with anDOSBox

YouTube video:
http://www.youtube.com/watch?v=rIy4DQY4aFA

Edit:
Somehow, I typed the last video as "DOSBox on Maemo 5", that should be "anDOSBox on NITDroid".
Corrected with an annotation

Re: DOSBox 0.65 ... ftw
 

Sorry, but this doesn't comply for "why it should work faster, from technical point of view". Show me parts of source code from dosbox for android or andosbox, that make it faster - if it is true, I'll immediately suggest including it in mainstream dosbox ;)

To be honest, with correct settings in dosbox config, frequency range 500-900 and swap on microSD, performance on Maemo is outstanding - even System Shock (1) is *almost* playable. Try that on Nitroid ;)

It always wonder me, how easily a little "marketing" ramble, with 0% meritocratic value, can make people "fanboys" of certain things. Really, is it *so* hard to understand, that any "miracle" speedup in source code inside dosbox for Android, would be immediately included in mainstream?

Stop wasting Your time with GPL violations/adware/fail platforms - or, stay with it, if You want (it's free world) - but, please, don't advocate depreciated things, unless You can meritocrately argument rationale for it.

---

On the other hand, my question about right mouse click is still actual... Any help - even explanation of methods from Diablo - would be *very* appreciated - I would love to use programs/games that include right mouse click.

/Estel

Re: DOSBox 0.65 ... ftw
 

You have to know that it's just optimizing so it works better on the mobile device.

I showed that a right mouseclick can be accomplished with a simple app :)

I'm going to try out System Shock (1) to show you the differences ;)

Edit:
Found the (old) source of anDosBox:
anDOSBox1.1.0 Source

Re: DOSBox 0.65 ... ftw
 

Ok, after briefly examining anDOSBox sources (checking for differences), I don't see *any* reason, why it should work faster. In fact, it may be even less reliable, in case of some games (it seems that is "dumped down", breaking support for games that would not run with playable speed on most android devices).

So, my question "how it is better" is still open. We already know, how it is worse (GPL violation, changing code in non-documented way, that should be smashed with fire).

/Estel

Re: DOSBox 0.65 ... ftw
 

As I already said, it is the old version. I should find the newest version for you.

As a "default user", I just look how usefull it is and if it's just working with my old dos games.
I just cant play my old games with all the other ports...

Why isn't the DosBox on Maemo and even aDosBox (the other opensource port for android) so much crappier than anDosBox?

By the way, you can get the source of anDosBox by just mailing the guy

Re: DOSBox 0.65 ... ftw
 

I'm non-experienced as coder too, but even user should - IMO - take much care, to filter out placebo effect, from regular gain. Also, it's possible, that andosbox got some options "locked" (no matter of config) for maximum performance, hence dropping support for games requiring other settings.

With dosbox, One can - like me - tweak settings for max performance, and, for games that have specific needs, just keep other customized config files too.

My question "if it is so miraculous and Open Source at the same time, why You think magic code would not be included in mainstream by dosbox devs, working hard on achieving best performance?" still remains. That is why I ask for rationale, not subjective user experience.

/Estel

Re: DOSBox 0.65 ... ftw
 

http://www.youtube.com/watch?v=PUqmioQO-H0

:) :) :)

Re: DOSBox 0.65 ... ftw
 

OK, I admit that SystemShock work on anDosbox with similar performance to dosbox on Maemo, with correct settings.

By the way, andosbox is doing pernament framedrop (see sources) - normally, You can set this value in dosbox settings. This is how many frames dosbox skip (without processing) before drawing one. Setting 1-3 give quite a boost to performance, without much visible effects - higher start to being visible.

So, basically, Andosbox is doing framedrop constantly = constantly lowering output graphic quality, no matter if it is needed or not. That's all the "mystery". Sure, You may not notice it on Android device, but, why to use it, if You can set exactly same things on normal dosbox (or tweak it exactly to Your likings)?

/Estel

Re: DOSBox 0.65 ... ftw
 

Be my guest and improve the DosBox on Maemo...
Because all I want is just playing old dos games (without much tweaks.. anDosBox doesn't need any tweaks to run any game)

That's the only reason why I just use anDosBox... It just works very well..

Re: DOSBox 0.65 ... ftw
 

I see Your point. If You could point me to most-demanding (in terms of performance) dos game, that is at the same time fully playable in andosbox, I could prepare settings for it, to work the same (or better) on Maemo, and publish it here. Maybe it is going to need some after-tweaking or testing, so Your help - as tester pointing out where it could be better - would be also appreciated ;)

I thought about dos-version C&C, but maybe You know more demanding (yet, playable) title?

/Estel

Re: DOSBox 0.65 ... ftw
 

I really love playing Skunny Kart on my N900 :) It's playable on andosbox.

Demo can be downloaded from here:
http://www.copysoft.com/skunny_kart.php

Re: DOSBox 0.65 ... ftw
 

For us that still run Diablo, no complaints. :)

It could be a faulty xmodmap. I just now remember reading about this awhile ago on this site. Try searching for xmodmap here.

What behavior do you get after typing this in Xterm?
xmodmap -e "pointer = 3 2 1"

Re: DOSBox 0.65 ... ftw
 

Hi guys,

I wanted to ask if anyone can help me configure my dosbox to run Mortal Kombat 3 smoothly?

I managed to make game run and screen size is perfect but I couldn't make it smooth by editing my dosbox.conf.

The game loads very slowly and it is very choppy, in fact it's unplayable.

I disabled the sound to make it more playable but it didn't help.

I attached my dosbox.conf (had to rename it to .txt to be able to upload, also removed commented lines to make it smaller).

Got the game form Abandonia:
http://www.abandonia.com/en/games/29...+Kombat+3.html

Any help would be appreciated :)
P.S. If I posted in the wrong section, please move the post, or point me in the right direction. Thanks.

Re: DOSBox 0.65 ... ftw
 

You may want to update dosbox for maemo - 0.74 is latest version (it requires You to have extras-devel enabled, at least for this single update)

After update (remember, You will get new config with 0.74 in it's name - changes in 0.73 won't be used in 0.74 version, unless specified as startup argument!), change the following lines (I'm posting, how they *should* look, not how they look now):

... by the way, are You insane man?! Putting 64 MB into dosbox emulated machine? It doesn't work like that, increasing it below sane limits, actually slow things down. And, actually, never ever use more than 32 MB, even on desktop computer. On N900, use max 16MB, for most games 8 or 4 is sufficient. Games from that era won't (most of the time) use additional memory, but You're still taking it out from Maemo reserve.

...now, if You want to have sound, use:
...otherwise, use:
And report back about Your findings. Also, using overclocked max frequency is recommended (900 upper limit, i don't recommend going higher than this).

If You still got problems with fluidity, first thing to do is disabling sound. Then, You may try increasing frameskip (by 1 on every try). I don't recommend going higher than 5 frameskip, cause it's going to cause tear-down look, no matter of performance.

Also, keep in mind, that in dosbox 0.74 output=overlay doesn't work, but output=surface does. That's why I changes it in config. If You insist on using dosbox 0.73, You can leave it as overlay, but keep aspect=true, and change scaler to scale=none

/Estel

Re: DOSBox 0.65 ... ftw
 

An Corp! As I posted on another thread, I just got my hands on N900 and started to mess around with it. Got frustrated for the lack of right click in DOSBox, and decided to give it a swing. I set up SDK, downloaded Javis Pedro's sources for 0.74 in extras-devel and added functionality for right click when you hold down shift. Cool, but it eats away one button from already small keyboard, so I changed it so it works when you cover proximity sensor, same way as in JA2 (looked into its source code, so thanks go to Janne Mäkinen on this one :)). No buttons sacrificed. Packaged, and tested to be working, just need to do little tidying.

Anyone interested? Any way my changes could get implemented in package in extras-devel? Where to go from here? :o

Re: DOSBox 0.65 ... ftw
 

If you can make the feature optional (say configurable from the config file) I will add them to my patchset and publish a new version.

Re: DOSBox 0.65 ... ftw
 

Hi Javispedro, have you seen latest version of Dosbox Turbo for Android? It works really well, is there any improvement that might worth to port to Maemo version?

Re: DOSBox 0.65 ... ftw
 

I do not have any love for Android *ware. Considering my past experiences, that software probably is a payware, gpl-violating ripoff of someone else's port that either does nothing new at all -- apart from the necessary bells and whistles to be featured on the payware store -- or just has a different set of defaults that works better for a few games at the cost of several thousand others.

So, no, I'm not touching that :).

Re: DOSBox 0.65 ... ftw
 

Done. Currently reads useproxsensor boolean from dosbox.conf under SDL section and sends its value to sdl mouse struct. All changes I have made are in sdlmain.cpp.

Re: DOSBox 0.65 ... ftw
 

After playing couple of battles in X-Com, it would seem like a good idea to add some sort of toggle to switch in a mode where touchpad presses aren't registered and you can just move your "mouse" freely without worrying about accidental clicks (as suggested by ArnimS). Already put some code together to get it working (holding down shift allows you to roam free), but this needs a bit more thought on where to bind it, and how it should actually work - only when key is pressed, or toggle or whatnow.

Any suggestions?

Re: DOSBox 0.65 ... ftw
 

Toogle sounds ideal. Having a toogle key configurable would be also best - allowing it to fit in any layout.

/Estel

Re: DOSBox 0.65 ... ftw
 

ive waited two years for this yay right click on dosbox win for the n900,
on a side note id like left click and right click to be on volume up and down respectively with mouse free to roam but to be fair thats just for anvil of dawn lol.
cheers for the hard work hope looking forward to this

Re: DOSBox 0.65 ... ftw
 

Could this new feature also become available for the Diablo build as well?

Re: DOSBox 0.65 ... ftw
 

Yeah, I was thinking about making toggle right click and roam use few possible values like none, proximity sensor, shift, ctrl etc so it could be configured as one chooses, and make it work better with specific apps. Also gonna take a look how volume keys can be read, and see if stooobs could use them in Anvil of Dawn ;)

As for Diablo build, well.. I'll look into it, but as I don't have device myself, I cant test it that well. Codewise, it shouldn't be too hard. Gonna see if I can set up SDK for it, and look into possible keys to be used. Suggestions needed.

Having some friends over to have boozytime on weekend, so there won't be too much progress till next week. If anyone wants to try the current build (cover proximity sensor for right click, hold shift for free roam), you can use deb found here, just remove current dosbox installation before installing it with dpkg -i. You can remove it with dpkg -r dosbox. Included are my conf file I use to play X-Com (sound disabled, otherwise it plays like a charm :)) and javispedros rover.sys and us.key files. I haven't tried packaging (or any Linux programming besides some python & bash scripting) before, so be gentle. :p

Post any ideas if you got them, I'd appreciate it. :)

Re: DOSBox 0.65 ... ftw
 

Put the patches somewhere!

Re: DOSBox 0.65 ... ftw
 

Prolly gonna screw this up, but attached should be sdlmain.diff saved as .txt file, this only adds proximity sensor for right click, defaults off, but can be set on in config file.

Re: DOSBox 0.65 ... ftw
 

Couldn't resist the urge. You can now set toggle right click and roam to ctrl, shift or proximity sensor from conf. Patch, and new deb for anyone who wants to try it out. Use togglemouseright and togglemouseroam in sdl section of conf to set wanted keys.

Re: DOSBox 0.65 ... ftw
 

You were able to prepare correct debs, so could You also upload new version to extras-devel? It's what the -devel is for, and I'm pretty sure, that in case of bugs it's much bigger chance to find them. It's unbelievable how much of a download boost package gets, when it's uploaded to repos, even -devel.

Thanks anyway!

/Estel

Re: DOSBox 0.65 ... ftw
 

gonna try it now cheers ill report back how happy or sad i am lol.

i also agree with uploading to devel because if there isnt much action in a thread it can easily be missed