Notices

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.

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.

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.

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!

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

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.

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.

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.

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.

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.

Many thanks again Javis!