maemo.org - Talk
Page 48 of 81 « First 384647 48 495058 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Games (https://talk.maemo.org/forumdisplay.php?f=12)
-   -   DOSBox 0.65 ... ftw (https://talk.maemo.org/showthread.php?t=5686)

Pushwall 2009-06-21 00:46
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by ukki (Post 298235)
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.
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.

ukki 2009-06-21 07:50
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by Pushwall (Post 298290)
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.
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.

JustNick 2009-06-21 09:17
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by ukki (Post 298341)
@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.
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

Pushwall 2009-06-21 16:27
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by ukki (Post 298341)
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.
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.

ukki 2009-06-21 17:01
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by Pushwall (Post 298420)
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.
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?

Pushwall 2009-06-21 17:39
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by ukki (Post 298432)
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?
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.

ukki 2009-06-21 18:27
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.

Pushwall 2009-06-21 22:25
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by ukki (Post 298456)
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.
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.

javispedro 2009-06-22 01:02
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:

Code:
DOSBox version 0.73
Copyright 2002-2009 DOSBox Team, published under GNU GPL.
---
CONFIG:Loading primary settings from config file /home/user/apps/DOSBox 0.73 Preferences.txt
[...]
key type 2 is 67 [sym=111 scancode=6f]
key type 3 is 67 [sym=111 scancode=6f]
key type 2 is 69 [sym=114 scancode=71]
key type 3 is 69 [sym=114 scancode=71]
key type 2 is 6a [sym=113 scancode=72]
key type 3 is 6a [sym=113 scancode=72]
key type 2 is 6c [sym=112 scancode=74]
key type 3 is 6c [sym=112 scancode=74]
These seem to be the standard scancodes for Linux evdev devices (according to DOSBox source).
What's the result on a N800?

qwerty12 2009-06-22 07:17
Re: DOSBox 0.65 ... ftw
 
Quote:
Originally Posted by javispedro (Post 298518)
What's the result on a N800?
From my N800:

Quote:
Nokia-N800-43-7:~# ./dosbox
DOSBox version 0.73
Copyright 2002-2009 DOSBox Team, published under GNU GPL.
---
CONFIG: Generating default configuration.
Writing it to /root/apps/DOSBox 0.73 Preferences.txt
CONFIG:Loading primary settings from config file /root/apps/DOSBox 0.73 Preferences.txt
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ hw
ALSA:Can't open sequencer
MIDI:Opened device:none
key type 2 is 67 [sym=111 scancode=6f]
key type 3 is 67 [sym=111 scancode=6f]
key type 2 is 69 [sym=114 scancode=71]
key type 3 is 69 [sym=114 scancode=71]
key type 2 is 6a [sym=113 scancode=72]
key type 3 is 6a [sym=113 scancode=72]
key type 2 is 6c [sym=112 scancode=74]
key type 3 is 6c [sym=112 scancode=74]

--

Nokia-N800-43-7:~# osso-pr
osso-prepare-partition.sh osso-product-info
Nokia-N800-43-7:~# osso-product-info | grep RX-34
cal_read_block(sw-release-ver): size zero, block not found?
cal_read_block(sw-release-ver): size zero, block not found?
cal_read_block(sw-release-ver): size zero, block not found?
cal_read_block(sw-release-ver): size zero, block not found?
OSSO_PRODUCT_HARDWARE='RX-34'
Nokia-N800-43-7:~#


All times are GMT. The time now is 17:30.
Page 48 of 81 « First 384647 48 495058 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8