Problem entering numbers on Motorola Milestone

[GoogleCodeExporter]

What steps will reproduce the problem?
1. there is no way of typing in numbers
2. alt-key for alternative buttonlayout doesn't work

What is the expected output? What do you see instead?
output should be a number, alt-key not working

What version of the product are you using? On what operating system?
0.1alpha on Android 2.0.1 (Motorola milestone)

Please provide any additional information below.

Original issue reported on code.google.com by tim.sero...@gmail.com on 1 Mar 2010 at 11:12

[GoogleCodeExporter]

It is possible to enter #s via the mapper.txt file that dosbox uses. 
Copy the mapper.txt file to the main directory of SDcard where dosbox.conf 
exists.

The Left-Alt does not work, but Right-Alt does.  It is Key-Code 0.
IE.  I set mod3 to "key 64" and "key 0"  (@ and Rt-Alt respectively)
#s are:
key_1 "key 113 mod3" 
key_2 "key 119 mod3" 
key_3 "key 101 mod3" 
key_4 "key 114 mod3" 
key_5 "key 116 mod3" 
key_6 "key 121 mod3" 
key_7 "key 117 mod3" 
key_8 "key 105 mod3" 
key_9 "key 111 mod3" 
key_0 "key 112 mod3" 

So When I press Right-Alt and then q.  I get 1. Right-Alt and s is 2, so on.
I set the Function keys f1 through f10 with the homerow keys.

Attached is the mapper.txt file I set-up.

Original comment by cddark...@gmail.com on 15 Apr 2010 at 9:13

Attachments:

• mapper.txt

[GoogleCodeExporter]

I also have this problem on a Droid. I cannot get the above mapper.txt file to 
work.

Original comment by pboy...@gmail.com on 9 Jun 2010 at 9:26

[GoogleCodeExporter]

Same problem on a Droid. I also cannot type the ~ character, which it seems I 
need to mount a directory. Mapper file also didn't do anything for me.

Original comment by jillkolsrud on 11 Jun 2010 at 4:07

[GoogleCodeExporter]

Got the mapper file to work on Droid.  The numbers only work with the right 
alt, the left alt still does its own thing.  Just noticed that holding shift + 
right alt will get symbols sometimes in more familiar places (the "*" is 
shift-right alt-8).

In order to get around the ~ character, either map something to it (not 100% 
sure how) or rename all of the folders in your virtual drive to be 8 characters 
or less.  Something called "Thisisafolder" will be automatically renamed to 
"THISIS~1" but a folder called "FOLDER" will be left alone.

In order for the mapper.txt to work, add the following to your dosbox.conf 
file, in the [sdl] section:

mapperfile=mapper.txt

Hope this helps...

Original comment by ewals...@gmail.com on 17 Jun 2010 at 3:24

[GoogleCodeExporter]

Hey all, I have the moto Droid 2.0 and numbers don't work for me either. I have 
mapper.txt which has...........
key_1 "key 113 mod3" 
key_2 "key 119 mod3" 
key_3 "key 101 mod3" 
key_4 "key 114 mod3" 
key_5 "key 116 mod3" 
key_6 "key 121 mod3" 
key_7 "key 117 mod3" 
key_8 "key 105 mod3" 
key_9 "key 111 mod3" 
key_0 "key 112 mod3" 
..............................................
in my conf file, which starts like this
.................................................
[sdl]
#       fullscreen: Start dosbox directly in fullscreen.
#       fulldouble: Use double buffering in fullscreen.
#   fullresolution: What resolution to use for fullscreen: original or fixed 
size (e.g. 1024x768).
# windowresolution: Scale the window to this size IF the output device supports 
hardware scaling.
#           output: What video system to use for output.
#                   Possible values: surface, overlay, opengl, openglnb.
#         autolock: Mouse will automatically lock, if you click on the screen.
#      sensitivity: Mouse sensitivity.
#      waitonerror: Wait before closing the console if dosbox has an error.
#         priority: Priority levels for dosbox. Second entry behind the comma 
is for when dosbox is not focused/minimized. (pause is only valid for the 
second entry)
#                   Possible values: lowest, lower, normal, higher, highest, 
pause.
#       mapperfile: File used to load/save the key/event mappings from.
#     usescancodes: Avoid usage of symkeys, might not work on all operating 
systems.
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=false
..................................continues on for a while
does this look correct? I've tired left and right shift and alt, i get no 
numbers, i get no function keys...
on an unrelated note, if anyone cares, I got the Fallout 1 load screen to come 
up, and it would let me to a small and medium install, but i found somewhere if 
i modify the install by adding 999 to it I can install it fully (which led me 
to my problem of the numbers not working). The point is, hey, Fallout 1 might 
work on the Moto Droid!

Original comment by Hy0tt...@gmail.com on 27 Jun 2010 at 7:13

[GoogleCodeExporter]

well, progress, I still can't get the numbers to work on my Droid, BUT I've 
been running dry runs of DOSBox on my comp and finally was able to do a 
complete install. Evidently DOSBox uses 105 MB of HD space when you mount a 
directory, so you have to add a line that tell it to dedicate a larger amount. 
The credit goes to a guy named ErikGG. 

Use mount c c:\ -freesize 1024 for 1GB of HD space. 

so for my droid when I initially mount for the install I put in "mount c 
/sdcard/falloutinstall -freesize 1024" Someone might want to test if dedicating 
extra space speeds up the play of games they're running. Hope this helps anyone 
else, cause I had a hell of a time tracking this down lmao!

Original comment by Hy0tt...@gmail.com on 27 Jun 2010 at 8:37

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I got the mapper work on my Droid 2. However, the keyboard is still horrible. 
Bad response.  Multi-tapping (tap once = 3 or 4 taps).  I hope there's an 
option to disable that.  Please let me know how.

Original comment by civsucc...@gmail.com on 26 Sep 2010 at 8:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Milestone froyo 2.2
same problem
solved by mapper.txt
thanks to Comment 1 and Comment 4

Original comment by gwpc...@gmail.com on 26 Feb 2011 at 9:30

[GoogleCodeExporter]

Original comment by grea...@gmail.com on 24 Apr 2011 at 7:26

• Changed state: Invalid

[GoogleCodeExporter]

Can't use the alternate keys on the LG Ally. These incluse extra characters and 
specifically the colon and slashes forward and back

Original comment by cyberwol...@gmail.com on 20 Sep 2011 at 8:18