Re: DOSBox 0.65 ... ftw
 

That's the "rightfull.xkbd" layout if I'm not mistaken... yes, that's exactly what I see, but it doesn't work, pressing keys doesn't do anything...
Launching Rubybox from terminal gives me this output:

~ $ rbox
DOSBox version 0.73
Copyright 2002-2009 DOSBox Team, published under GNU GPL.
---
Sorry - server Keyboard map doesn't contain either 2 or 4 KeySyms per Keycode - unsupported!
CONFIG:Loading primary settings from config file /home/user/.rubybox/Games/commander_keen_-_episode_4.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ hw
ALSA:Can't open sequencer
MIDI:Opened device:none
MAPPER: Loading mapper settings from /home/user/.rubybox/.mappers/mappercsa.txt
X connection to :0.0 broken (explicit kill or server shutdown).
killall: dosboxbin: no process killed

I guess "Sorry - server Keyboard map doesn't contain either 2 or 4 KeySyms per Keycode - unsupported!" is the part that tells me something is wrong with the virtual keyboard, but I don't know how to use this piece of information...
Launching xkbd from terminal (no rubybox or dosbox involved) gives me the exact same error, except that upon exit it kills my D-pad and makes impossible to "click and run" or "click and select" using the touchscreen in any application (on a stylus click the whole line I'm on is selected... weird...)

If it is of any help I'm using an N800 with the latest diablo release, installed apps mostly from Extras (except latest Abiword and of course Rubybox and Dosbox) and using Qole EasyDebian (even if I don't think this can do anything to the system itself...)

Re: DOSBox 0.65 ... ftw
 

I honestly have no idea on what's happening there, JustNick.

First time hearing about your problem in quite awhile.

We all encountered the exact same thing you're describing, but that was like a year and a half ago.

Oh, and the "Sorry - server Keyboard map doesn't contain either 2 or 4 KeySyms per Keycode - unsupported!" is nothing. We all get the same message and it's completely unimportant. Don't even worry about that.

Best I can offer is to uninstall Xkbd, Ruby, Rubybox, and Dosbox. Keep Unzip if you have that though.

Then head over to Ukki's page and fire up the one click install. I'm thinking maybe you picked up an older version of Xkbd when you grabbed it from the extras repository.
Rubybox

Try that and post back when you have the chance.

Cheers.

Re: DOSBox 0.65 ... ftw
 

Thanks Addison, I'll check the Xkbd version I have installed and see if there's a newer one around ;)

Uhm, the xkbd package in Rubybox repository is xkbd_0.8.15m-2_armel.deb, that's exactly the one downloadable from http://pupnik.de/xkbd.html
Oh, well, I'll just remove everything ruby/dosbox related and start over :D

Re: DOSBox 0.65 ... ftw
 

Bunanson seems to have the same problem on his end with Xkbd as well.

Please post back if you find a solution.

Re: DOSBox 0.65 ... ftw
 

I haven't had a chance to test DOSBox much yet, but after reading this thread though I thought I'd give it try. I've found that I've got the same problem as JustNick on my N800. I can't even get the D-pad directionals to work properly in games. I've run 'dosbox -startmapper' and redefined the directional keys,....but nothing. I've run 'keyb nokia.sys us' thinking that this might help,...nada. I've found that Addison's keyboard does work with RubBox but I still can't get RubyBox to load a custom mapper.txt file and have it work. BTW, JustNick.....to get that little XKBD keyboard to work, you have to tap the CAPS key first before you do any input. Addison,....I'm guessing yours is working since you've got both the new and old DOSBox programs on your N800. I'm seriously thinking about deleting the latest DOSBox and going back to the previous version to see if things are hunky dory again.

Re: DOSBox 0.65 ... ftw
 

Good news: remapping the D-pad works
In an active session of Dosbox (i used the one I created to launch windows 3.1 with rubybox) ctrl+F1 will start the mapper, just remove the printscreen and the right alt bindings (they are mapped with the Up and Right directions of the Dpad) and then assign the four directions to the four arrows key.
Bad news: you can't save this, I don't know why (probably Dosbox points to a location that needs root privileges to be written), so this works only in an active session...
I just tried once though, so it could be possible that with some fine tuning of the dosbox config file one could be able to point to a different location where to save the mapping... or I was just lucky and I won't be able to make it work a second time :D

Re: DOSBox 0.65 ... ftw
 

Well I just got RubyBox to work with the latest DOSBox. I'm able to use my custom mapper.txt file....woohoo! :D (My redefined functions keys don't work properly so I still have to fix the function keys like javispedro suggested,...but that's no biggie.) Plus the directional keys now work too. How? I had a backup of '/usr/share/dosbox'. That directory was gone after installing the latest DOSBox version. But copying that directory back now fixes the problems with RubyBox and DOSBox, plus games seem to be running normal again instead of being so s-l-o-w. I don't know how or why this fixes it, but it does. It's probably not a proper fix but it will do for now.

Re: DOSBox 0.65 ... ftw
 

D'oh! the small keyboard killed my Dpad again...

Re: DOSBox 0.65 ... ftw
 

Not in 0.73... I've configured it to save it to ~/apps/mapper.txt, which is user writable. (Unless you override it in the config file!)

I think this is more a scancode-or-keysym issue. There's an option in DOSBox Prefs.txt called "usescancodes": try switching that on and off and remapping.
Nokia.sys will do nothing here, it's just for N810 FN-keys.

I will provide a debug-enabled build of DOSBox later this week (I hope).

The d-pad keys work with the default configuration for me (at least in QBASIC). And I can assure you I have no /usr/share/dosbox/ directory (WHAT do you have there?).

Re: DOSBox 0.65 ... ftw
 

I think I'm going crazy...
Small summary of all the little problems:
1) XKBD launched from terminal or .desktop file works if CAPS is ON (thanks for the hint pushwall), but kills Dpad upon exit and makes impossible to "click and select" or "click and run" in some apps
2) Rubybox seems to forget settings previously modified (thus making impossible to proceed by trial and error in fine tuning Dosbox)
3) there are some xkbd keys with weird bindings, ALT is recognized as SHIFT and ENTER as DOWN
4) the Dpad UP is interpreted as a Prtscrn, the LEFT as RIGHT ALT, the other 2 directions as "unknown keys" and binding them only works for one session

I'm starting to think my N800 is possessed :D

Re: DOSBox 0.65 ... ftw
 

Hey JustNick.

First off, Pushwall wasn't correct on what he said earlier. All keys work perfectly including both upper and lower case with no issues.

So yeah, I might be on the boat with you thinking that your tablet is indeed possessed.

By any chance did you click the xkbd.install file over at the pupnik.de/xkbd.html webpage?

Looking at the contents inside, it's saying gregale as the OS for the installation which is pretty ancient and shouldn't be used.

Try to see if you can't install these two dependencies:
libxpm4
and
Xlibs

You might have to manually install them from your memory card though.

Re: DOSBox 0.65 ... ftw
 

Hey no trash talk about Pushwall! :D

The XKBD keyboard I was referring to is that small qwerty keyboard that is in the original XKBD installation. The Addison keyboards still work great and kick a-s-s! When I run XKBD by itself, I get the broken qwerty keyboard and not any of the Addison A-s-s-kickers. I was guessing that JustNick was referring to the old broken qwerty keyboad too.

Re: DOSBox 0.65 ... ftw
 

Uhm, no, he is right :D I'm referring to the small white keyboard that I wished to use with the Snes, but it seems not feasible due to all the trouble it creates... Your XKBD layouts work great though (ok, maybe I'm having minor glitches, but they're fine)

(wearing a black priest robe, having the Bible in my left hand and a silver Crucifix in my right one, shouting)
The power of Christ compels you. The power of Christ compels you. The power of Christ compels you. The power of Christ compels you. :D

Uhm, no, I didn't use the link on the pupnik.de/xkbd.html webpage, I've found that the one in the Rubybox repository is the newer one
http://nakkiboso.com/knots/pool/diablo/, I just have to check the xlibs version...
Uhm... xlibs is nowhere to be found... Once in red pill mode it should be possible to see every package installed, am I right?
If this is the case xlibs is not installed nor is in any repository I have active, the only xlib-ish packages are in Extra-devel (xlibmesa-gl) and something tells me it's not intended for diablo...

By the way I've already removed and reinstalled (checking all the packages version) twice with no luck...

I never meant to cause all this havok :D

Re: DOSBox 0.65 ... ftw
 

That comment took me back to the time when I was in high school and played football for the Mona Shore Sailors.

What position did I play you're probably wondering?

A-s-s-back.

Yeah, that's right.

A-s-s-back.

You see, every time I would run on the field, my coach would scream at me saying, "Hey chump! Get you a-s-s-back here!!!!" :D

JustNick, if you want something for whatever it is that you're doing with SNES, might I suggest making your own keyboard.

Look at the file Mono.xkbd using Emelfm2. It should be in
/home/user/.rubybox/.xkbd_layouts/

Delete, overwrite, and change the height of that file to make a keyboard of your own.

Only rule is that Xkbd will crash if you tell it to use a lowercase letter for output.

The way to get around this is to send a capslock uppercase letter instead to trick it.

It would have been nice if someone fixed that bug, but for now, it's the only way to get around this program from regurgitating on your tablet 360, fully rotated, pea soup style.

May I ask when the last time your tablet had confession?

Hey Push, did you check out Executive Suite yet that I posted in the other Dosbox thread?

That game totally is something I think you would get a kick out of playing in your free time. Since it's freeware, maybe you could even upload it over at Ukki's site.

Cheers.

Re: DOSBox 0.65 ... ftw
 

I don't think my tablet has ever had confession :D
Let say I'll leave snes+XKBD alone for now... but what about Rubybox+Dosbox? I read the entire XKBD thread, I saw you suggested the installation of bash2 (don't know what it does though, you said it helped :D) and there's a little confusion around libxpm4 and/or xlibs installation (the one you linked is in maemo 3 repository, but the "debian guys" alway told me not to mix repositories nor install something that is not requested as a dependency... so i'm a bit confused too :D)...
Man what an headache... considering I just wanted the ALT to be ALT and not SHIFT and the Dpad to work as reported... D'oh! :D

Re: DOSBox 0.65 ... ftw
 

Okay, real quick.

Fire up one of the side keyboards and then open up Notes under Utilities. Try typing with the vertical keyboard and see if they all are work correctly. I'm guessing that they should.

If it's typing capital letters right from the start, press the Capslock button, close Xkbd, and try again.

Are you loading a mapper.txt file in Rubybox?

On my screen it's showing a blank, so I guess it's not loading anything on my end.

I just now noticed that my Dpad is also not working either.

Maybe all we need is a working mapper.txt file.

I can look into tomorrow night when I get back home.

Otherwise, maybe Pushwall can find the answer for this.

Cheers.

Re: DOSBox 0.65 ... ftw
 

Just a note about the new hardware (N900): The Pandora folks are saying that DosBox runs between 2000-3000 cycles on their hardware, and it is very similar to the N900, so I suspect you'll be able to get the same speeds on the new device. That seems to be at least 100% faster than what you can do now, and maybe even up to 200% faster!

Re: DOSBox 0.65 ... ftw
 

Side keyboard works wonderfully, as I expected, only minor nuisance is the ALT key which is interpreted as SHIFT even in Notes (so it needs to be remapped under Dosbox)

I used mappercsa.txt, then tried mapper.txt generated within Dosbox (it is mandatory to remove mappercsa.txt because it seems that Rubybox doesn't save your preferences... at least not always :D): keyboard works, but while in notes it is perfect (with the ALT exception) in Dosbox some keys are misplaced (for example: pressing Enter key while remapping shows "down_button" :confused: )

Tan tan taaan!

(this is the best way I can express myself regarding the Dpad woes)

I've tried that way... the problem is that half of the Dpad directions appears to be interpreted as "unknown_key", so when mapped they work only during an active session... reloading Dosbox with the custom mapper.txt gets only half Dpad :mad:

Re: DOSBox 0.65 ... ftw
 

Nice catch.

For some reason, and I'm sure I had a good one at the time, but I mapped the ALT key as Meta_L.

So go ahead and change the keyboard using Emelfm2 from:

default ALT
default_ks Meta_L

to

default ALT
default_ks Alt_L

Again, I'll double check the mapper.txt file and look back over the keyboards tomorrow to see what other bone head things I did.

Re: DOSBox 0.65 ... ftw
 

Indeed. I think the Cortex A8 has much faster non aligned memory accesses.

Re: DOSBox 0.65 ... ftw
 

Hey JustNick.

Okay, I see exactly what you're talking about now.

Everything you mentioned previously about mapping the hardware keys, I'm getting the exact same results on my end.

I can't figure this one out so I'll just wait until I hear something from either Pushwall or Javispedro on this.

Re: DOSBox 0.65 ... ftw
 

So I'm not crazy after all :D

Re: DOSBox 0.65 ... ftw
 

Hey now. No one ever said that. :D

Re: DOSBox 0.65 ... ftw
 

RubyBox and my custom mappercsa.txt file work fine with the latest DOSBox and my N800, remapped keys and all (Ctrl, Shift, Alt, etc.)! The trick was to copy the file directory '/usr/share/dosbox' from the prior DOSBox version back to internal memory. The install of the latest DOSBox erased this directory, and it seems that something in that directory is needed for the remapping to work correctly. A zip file that has the contents of that directory from my tablet can be downloaded from here.

Re: DOSBox 0.65 ... ftw
 

Uhm... I guess that Rubybox still searches configuration files in that position...

Re: DOSBox 0.65 ... ftw
 

I still believe whatever you're experiencing is related to the usescancodes option in DOSBox Prefs.txt

Indeed, it seems that older builds had usescancodes==false, while this build has usescancodes==true by default. In my short experience I can map all N810 keys only if it's true. Having it set to false causes problems like the one someone describe a few pages ago (the DOSBox mapper accepting mappings for a single session then "forgetting" about them instead of saving them), but, as I said, this is based on my experience only. So it may work better with usescancodes==false on N800 or whatever.

Re: DOSBox 0.65 ... ftw
 

I just now tried setting that to false (and deleted the '/usr/share/dos' directory), and that does allow the N800 keys to be remapped for Ctrl, Alt, Del. The problem I'm having is with the D-pad. I'm going to work with it this weekend and see if there's something I'm missing. I did notice too that without the '/usr/share/dos' directory that the game I was testing (BioMenace) wasn't as smooth and the sound was sputtering somewhat. Strange stuff.

Re: DOSBox 0.65 ... ftw
 

Javispedro usescancodes==false had no effects for me... :(

Re: DOSBox 0.65 ... ftw
 

New RubyBox release, small fix for the new dosbox version where config wasn't used when launching an app. This was a stupid mistake from me, sorry guys.

Re: DOSBox 0.65 ... ftw
 

Thanks a lot Ukki, I'll test it in a couple of minutes :D

Updated, it crashed a couple of times while saving/editing settings with this output:

"X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 129 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Resource id in failed request: 0x1c00010
Serial number of failed request: 579
Current serial number in output stream: 580
killall: dosboxbin: no process killed
ruby1.8[5434]: GLIB ERROR ** GLib-GObject - file gsignal.c: line 652 (emission_pop): should not be reached
aborting...
Aborted"

Now config works, but returning to dos prompt leaves you with no working virtual keyboard (it's there but it doesn't do anything, like its functionalities where limited to the program you just exited)
To have a working Dpad usescancodes==false appears to be the only way.

Re: DOSBox 0.65 ... ftw
 

ukki there's something else that was in the old '/usr/share/dosbox' besides the config file that RubyBox is missing. The D-Pad still doesn't function properly in launched games from RubyBox unless I have the old '/usr/share/dosbox' directory installed.

Re: DOSBox 0.65 ... ftw
 

Can you copy the old config over the new one and the remove the old /usr/share/dosbox directory? and test again? I only read the config file so the problem must be the difference between the new and old config.

@JustNick, yes, that's the Ruby crash i mentioned earlier, it started happening with the new packages, but I bet I can somehow avoid it, if it would happen when I'm trying to debug it.

Re: DOSBox 0.65 ... ftw
 

Well, 3 times out of 4 when it crashed Dosbox was closed using the "home" button -> click on X procedure (because of the non functional virtual keyboard) while keeping the Rubybox session alive and then trying to make settings adjustments.
Hope this piece of information can help you make it crash in a controlled way so that you can easily debug it :D

Re: DOSBox 0.65 ... ftw
 

I tested the latest RubyBox 3 ways:

1. Removed the old /usr/share/dosbox directory and used the old dosbox.conf file as the new DOSBox 0.73 Preferences.txt file in the directory /home/user/apps. Result -- D-Pad doesn't function properly in games launched from RubyBox.

2. Kept the old /usr/share/dosbox directory and left the new DOSBox 0.73 Preferences.txt file as is. Result -- D-Pad functions properly in games launched from RubyBox.

3. Kept the old /usr/share/dosbox directory and renamed the dosbox.conf in that directory to another name. Result -- D-Pad doesn't function properly in games launched from RubyBox.

So the only thing I can figure is that RubyBox is still looking at the old dosbox.conf file in /usr/share/dosbox directory, or that the configuration file I changed in step 1 above is the wrong one.

Hope you can figure this out, ukki.

Re: DOSBox 0.65 ... ftw
 

Sounds odd, can the problem be in the mapperfile? RubyBox searches for mapper files from /usr/share/dosbox and /home/user/.rubybox/.mappers. So if you copy the mapper.txt to /home/user/.rubybox/.mappers and make sure the game uses it, does it work then? If RubyBox can't find /usr/share/dosbox/dosbox.conf, it uses the new one and if you replace the new one with the old one, it should work like the old one. You did update to 0.4.4 btw?

Re: DOSBox 0.65 ... ftw
 

Yes I'm using 0.4.4,...just checked the version.

I'll test that mapper.txt theory in a bit. Here's one thing I found. If I have the /usr/share/dosbox directory and the line in the dosbox.conf file is 'usescancode=false' then the D-pad works, if it is 'usescancode=true' then the D-pad doesn't function properly,....just like javispedro surmised. Without the /usr/share/dosbox directory, I've got the configuration file in /home/usr/apps set with 'usescancode=false' and the D-pad doesn't function. So I'm guessing Rubybox is finding some other configuration file that has that parameter set to true.

I've got some grass mowing to do,...so more testing later.

Re: DOSBox 0.65 ... ftw
 

Run rbox from xterm and see if Dosbox says it's using the new config when you startup a game. Can you do vice versa then and copy the new config to /usr/share/dosbox/dosbox.conf and see if it works from there? Maybe Dosbox fails to use the config when given in the commandline (with the spaces in the filename) and then just uses defaults + the game specific settings.

Re: DOSBox 0.65 ... ftw
 

I did what you said and ran rbox from xterm. If /usr/share/dosbox directory is not there it shows it is using the config file from /home/user/apps. And if /usr/share/dosbox directory is there, it uses the config file from that directory. And here's a strange thing,...the D-Pad worked fine. So I thought to myself that maybe it only works when running rbox from xterm. Then I tried running RubyBox from the menu with /usr/share/dosbox directory removed, and lo and behold the D-Pad now works! WTF?! Maybe RubyBox just needed a good xterm session to get its butt in gear. I don't know, but now everything seems to work properly.

FWIW, I did get the D-Pad one time (and one time only) to not function when running rbox from xterm (with the /usr/share/dosbox directory removed). Xterm showed that a regular config file was not loaded at all, but the one from the .rbox directory was.

Re: DOSBox 0.65 ... ftw
 

A quick look at the sdlmain.cpp reveals that, in order to find config file, DOSBox tries:
1. Whatever file is specified in command line (-conf argument)
2. dosbox.conf in current directory
3. User config (aka ~/apps/DOSBox 0.73 Preferences.txt)

Maybe #2 is causing problems? ($PWD when launching dosbox is /usr/share/dosbox)?


Either way I'm interested in why the N800 D-Pad is not working in plain DOSBox, so I'm attachinglinking a test version that should log both keyboard and stylus output to standard out. (It's just the gzipped binary, no package to install)
Pressing Up, Left, Right and then Down on my N810 produces this:

These seem to be the standard scancodes for Linux evdev devices (according to DOSBox source).
What's the result on a N800?

Re: DOSBox 0.65 ... ftw
 

From my N800: