Re: DOSBox 0.65 ... ftw
 

Same result??

And you're telling me the dpad does not work there?? Does it work in the DOSBox command prompt? "Up" should recall last entered command (much like any modern unix shell).

Re: DOSBox 0.65 ... ftw
 

Everything now works fine for me. The dpad works in the DOSBox command prompt. And now it functions fine with RubyBox. From what I can tell, when running from a menu RubyBox wasn't loading a default DOSBox config file when launching games. It seemed to fix itself when I ran RubyBox from xterm. Now everything is hunky dory.

Thanks javispedro for all your help, and or course thanks ukki for your help too.

Re: DOSBox 0.65 ... ftw
 

Okay, after reading through these latest posts, I'm still not quite sure how to get all the hardware keys mapped correctly.

Hey Pushwall, could you post the script that I can run in Xterm to create the needed directory that the current version of Dosbox erased along with the old mapper.txt file and where exactly to put that file?

Thanks ahead!

Re: DOSBox 0.65 ... ftw
 

Hey javispedro, were you still thinking of offering us another release in a couple of weeks or is this your final build?

I'm still having difficulty trying to map the hardware keys and I can't seem to make sense of Pushwall's answer on how to correct for this.

Thanks.

Re: DOSBox 0.65 ... ftw
 

I don't really know what's the problem with the hardware keys. They work for me, and there is no reason for /usr/share/dosbox existance to have any effect on this. I suggest you try the test application I put on the previous page and also booting dosbox directly from command line.

The next build will have minimal differences, mostly packaging related, and without nokia.sys for now. I will push that to extras (hopefully RubyBox will be there by then, now that Ruby is being slowly pushed).

The only thing in my todo list is understand how scaling works.

Re: DOSBox 0.65 ... ftw
 

Ukki is waiting on you to upload dosbox first.

Re: DOSBox 0.65 ... ftw
 

Ok, uploaded to extras-devel.

Re: DOSBox 0.65 ... ftw
 

Javispedro is right that you don't need this directory when running DosBox. However, initially for DosBox to work with RubyBox and the mapper.txt file I did need it. If you need it, then download the zip file and you'll see the full directory path in the zip file on where to put it on your tablet.

To get RubyBox to work with DosBox and the mapper.txt file correctly though without that directory above, I ran rbox from the command line. And then after that everything worked fine. Beats me why.

Re: DOSBox 0.65 ... ftw
 

Ok, RubyBox is now in extras-devel. Firstly I want to thank qwerty12. He found the other Ruby-Hildon bindings, uploaded them and all the depedencies it required (there were quite many) and even packaged RubyBox so I only had to upload it. He did an incredible job so everyone using RubyBox, remember to use that Thanks! link on him.

To install the latest RubyBox, please delete the old packages you have once again :) Become root and run:

if that doesn't remove all, you can try more brutal way:

Then enable extras-devel and install RubyBox. Let me know if you encounter any problems, I had to make some changes and remove some stuff as these new bindings aren't identical and they are missing some libs I used.

Re: DOSBox 0.65 ... ftw
 

Well, thank you all guys, you're simply great :)

Re: DOSBox 0.65 ... ftw
 

Worked like a charm. You guys rock! :cool:

Re: DOSBox 0.65 ... ftw
 

Installation went just fine (enabled extra-devel, selected Rubybox 0.4.5 that installed Dosbox 0.73-5 as dependency), apps work with 2 small problems:
1) to make onscreen keyboard work I had to press home key, launch terminal and type something with it, then I went back to the active dosbox session and it was possible to use it
2) HW buttons work included D-pad, but if the screen turns itself off while dosbox is running they get deactivated and you need a couple of taps on the touchscreen before they get back in action :D

I'll try later to wipe any possible old configuration that survived the uninstall process and start with a fresh install of new games to check if these problems are still present.

Re: DOSBox 0.65 ... ftw
 

Where are RubyBox's game .conf's kept?

Re: DOSBox 0.65 ... ftw
 

~/.rubybox

Re: DOSBox 0.65 ... ftw
 

I don't see any such files in root in EmelFM2, just directories (bin/ through var/)

Re: DOSBox 0.65 ... ftw
 

"~" == /home/user

Re: DOSBox 0.65 ... ftw
 

Ah okay, laugh at my expense then :D

Unfortunately I don't see any Rubybox files there. I need to tweak my Daggerfall conf by adding in this after FALL.EXE

fall.exe z.cfg

I've tried a bat, but DOSBox says illegal command.

Re: DOSBox 0.65 ... ftw
 

As much as I would also love to play Daggerfall, it's way too heavy for the tablet. Tablet can only play 286/early 386 games. Also the directory starts with a dot which means it's a hidden directory, so check if there's an option to show hidden directories.

Re: DOSBox 0.65 ... ftw
 

I know but I fig'd it was worth a shot. THanks!

Re: DOSBox 0.65 ... ftw
 

Re Daggerfall I fear Bethsoft will never give us the damn source.

Re: DOSBox 0.65 ... ftw
 

I'm not even able to download it... slow download speed plus corrupted package... :(
Me sad :(

Re: DOSBox 0.65 ... ftw
 

I used a download manager (orbit) to get it. Took me an hour but at least I got it before ukki who had the download running for 8 hours. :p :D

Re: DOSBox 0.65 ... ftw
 

8 hours??? :D
Ok, they give away and old game... but did they really think people were still using analog < 33Kbps connections? :confused:

Re: DOSBox 0.65 ... ftw
 

That's Finland for you, I think there was a polar bear standing on my internet cable or the penguins managed to somehow break the cable :(

EDIT: but it's not like I don't have the original box and cd so I didn't feel like going after the bear.

Re: DOSBox 0.65 ... ftw
 

Dude, penguins live only in the southern emisphere (and maybe in some zoo too...) :D
This is going right to fail blog :D

Re: DOSBox 0.65 ... ftw
 

So I've got Fallout copied over from a PC DOSBox install. I've got the 'Humongous' installation, so all I have to do is mount C and run Fallout.exe, no CD required.

Copied over to the tablet and it says the master DAT couldn't be found, insert CD.

Dunno why there'd be any difference?

Also I know Fallout may not run well on the tablet but let me be curious :p

Re: DOSBox 0.65 ... ftw
 

You'll probably have to make a .bat file (I think) or add in a comment at the end of your dosbox.conf file [autoexec] and mount your game as a virtual CD.

Something along the lines of this:
mount d e:\ -t cdrom
mount d c:\dosgames\fallout -t cdrom

This is a wasted effort on your behalf trying to run this though...

It's going to run so chunky that it will feel like you're playing Fallout, the board game. *lol*

Good luck!

Re: DOSBox 0.65 ... ftw
 

The thing is I can't type anything, N800 and I couldn't get the xkbd to install, something about libpurple... god I can't remember.

I'm using Rubybox but of course I can't do CD-ROMs there

Re: DOSBox 0.65 ... ftw
 

You're not going to be able to do too much without xkbd.

Ukki's Rubybox should be packaged with xkbd if you installed it correctly.

Otherwise, you'll need to go to ArnminS' site and manually install it yourself with the files he has available for download.
Xkbd

Re: DOSBox 0.65 ... ftw
 

*EDIT* Got libxpm4 installed and xkbd. Hate these damn hassles..

Here was my problem with xkbd http://talk.maemo.org/showthread.php?p=273582 can't get libxpm4 to install

Re: DOSBox 0.65 ... ftw
 

Well going by your instructions but tweaked a bit...

DOSBox says MOUNT C "/media/mmc1/DOS/FALLOUT/"

when you run a setup through RubyBox... so I put in the bat file similar syntax for CD-ROM...

mount d "/media/mmc1/DOS/FALLOUT" -t cdrom
fallout.exe

and it still says "Could not find the master datafile. Please make sure the FALLOUT CD is in the drive and that you are running FALLOUT from the directory you installed it to.

aaargh.

Re: DOSBox 0.65 ... ftw
 

I was in your boat more than once.

It's a turd sometimes for a newbie learning to install something that seems like it should be simple enough to do.

If I remember correctly, it took me an hour the first time to get every together for xkbd to be installed. Six months later, when I reflashed my Tablet, it took exactly the same darn time. :D

I think solution is to have that file on your memory card and install it directly from Xterm.

So download the libxpm4 file from the site mentioned previously, you can rename the file if it will make things easier for you, and then transfer it right there on your external memory card.

In Xterm:
cd /media/mmc2
dpkg -i libxpm4.deb (or whatever the full filename is) ENTER

That should get you over the hump.

Even though you'll never get Fallout working, at least you'll have a virtual keyboard. :)

For some interesting keyboard designs, you can check out an old post I made.
Xkbd Keyboards

Best of luck.

Re: DOSBox 0.65 ... ftw
 

I've got xkbd installed and it works although there was some error about umm... something unsupported. But it works. Sorry don't feel like firing my tablet up right now!

Anyway, I noticed how Daggerfall is slow enough I haven't gotten into the 3D world yet, so I'm likely not going to bother with Fallout. Thanks though!

Re: DOSBox 0.65 ... ftw
 

Well, I almost found a really good game to play with Dosbox.

Wizardry 1 (off the archives CD) needs things to be slowed down. Running emulated hardware does just that.

(I suppose I should mention that I am using a N810, I have .73-3, and got the nokia.sys and mapper file from page 41 of this thread)

The game plays almost perfectly. One small really annoying bug:
for some reason the '1' key (Fn-q) causes Wizardry to exit (with a 'Thank You for playing Wizardry message', so I don't think its a crash per-se).

I do not have this problem with the same executable running on DosBox under windows.

I hooked up an external USB keyboard, and the '1' key works perfectly there.

The rest of the numbers (at least 2-6) work fine in Wizardry.

The '1' key works fine from the Dos command prompt.

If I remove the 'keyb nokia.sys us' line from my autoexec.bat file, I lose the ability to type '1' with the nokia HW keyboard, but FN-q still causes the program to exit.

Any ideas?

Is it possible that Dosbox is using that sequence for something else internal? [Like an extra Ctrl-C or ESC or something?]

Schemm

Re: DOSBox 0.65 ... ftw
 

CTRL-q would be "Quit", correct?

Maybe you have set "1" as a hotkey within the game.

Well, I've got some free time today and was going to restore Dosbox and Rubybox back up with the latest updates.

By the way, I always liked Wizardry.

In fact, maybe you should look at the translation patches I made for the Gameboy Color versions.
Wizardry Trilogy

You can run them under the Gameboy Color emulator for the Tablet.

Anyway, I'll look into it and hopefully post back something tomorrow.

Re: DOSBox 0.65 ... ftw
 

This is known, and I'm working on it.

I made the unfortunate decision of mapping the FN key to AltGr, which of course I'm now regretting because of the behavior you described.

I assume pressing Alt+Q on the external keyboard makes the game quit too.

Re: DOSBox 0.65 ... ftw
 

Ok, 0.73-6 is up on extras-devel; or download and install with dpkg (application manager won't install it since i've dropped it from user/): dosbox_0.73-6_armel.deb.
You'll also need newer nokia.sys if you're using it.

For non-N810 users there should be no changes. If there's any, bug me.

This only maps the N810 FN key to the "backquote" key instead of the right ALT key, so keyb can now handle it without interfering with applications.




I've been experimenting with a hildon-input-method compatible DOSBox now that I've got some minor experience tinkering with microb.

The main problem is that DOS applications read keyboard input through two methods: directly through the keyboard controller (method a, which of course gives key scancodes only), and through the BIOS (method b, which gives both scancode and ASCII value).

hildon-input-method sends utf8 strings instead, like "a", "á", "A", or even full words like "absolutely" (produced by the autocompleter).

In order to make applications using a) happy, I'd have to convert each utf8 char back into a scancode. "á"-like chars would need to be converted into the appropriate dead key presses, etcetera. This would be codepage, layout, and locale dependent: a ugly mess.

To make b) applications work, it's just a matter of choosing the appropriate codepage then converting utf8 chars to that codepage. Easier, but may limit compatibility.


There's also the problem with the hildon-input-method window. There's not enough space to even show the hw keyboard one without hiding part of the dosbox window, and from what I've seen so far scaling is SLOW. So it's either partially hide the dosbox window when the virtual keyboard is up or make it slow.

If you think I'm wrong, really want that feature, or have an idea please don't hesitate to reply.

Re: DOSBox 0.65 ... ftw
 

Thanks for the new version. Works good for wizardry! Well, after I slow down the CPU!


Would you be willing to post a link to your version of the source code for dosbox? Also to whatever you are using to setup the nokia.sys file? I'm curious how you handle the keyboard issues in there.

Thanks.

Re: DOSBox 0.65 ... ftw
 

Explanation:
I rewrote the DOSBox "keyb" based on the FreeDOS keyb documentation and my own understanding of the specification, because the original DOSBox keyb was missing some features, like User Modifiers support.

Then I used the KC compiler from FreeDOS (recompiled in Linux instead of DOS, easy since it is standard C) to build the nokia.sys from the following source Key language files:
ptes.key (Portuguese-Spanish layout)
us.key (US English layout)

The FN key is hardcoded in dosbox to the backquote key, and some other mappings I don't remember right now for the Chr and the Menu key.

You can get the pristine DOSBox source & patches in the Debian source package, available at http://repository.maemo.org/extras-d...urce/d/dosbox/ (if you don't have debian or dpkg-source contact me and I'll upload the patches somewhere).

Initially I wanted to push the new keyb upstream but noticed that many just let their "patches" float around in the dosbox world (specially those whose use does not seem clear) so be it.

BTW, I am waiting for permission to upload to the DOSBox garage project svn repository (asked the current maintainer a week ago: must be on holiday :)), since If I create yet another repository on my website DreamHost is going to kill me ;)

Lately I've been reading the DOSemu source code (which I personally prefer but unfortunately it's totally unportable), and seems to have solved the input problem in a totally different & maybe interesting way.

Re: DOSBox 0.65 ... ftw
 

Many thanks again Javis!