kexplo / adosbox Goto Github PK

Will there be an update to the emulated dosbox to v0.74 from v0.73?

I love the idea of adosbox, but for some reason whenever I try to install 
Commander KEEN it gets only to the installation progress screen, but before one 
percent is reached I get this error:
Cannot create file S:\KEEN\file.
Press Enter to quit.
(it isn't "file", but more often than not when I try to type "\" it becomes 
some other character, so I couldn't reach the error message screen again, but 
this is what I remember).

I've tried installing KEEN 4, too, but I got the same error. Is there something 
wrong with my adosbox installation, or can I install it in some other way?

Your disccusion group has been removed by google

I actually managed to load the game Star Control 2 in adosbox after finding the 
":" key and "1" key input so that i could change to my mounted drive and change 
to my directory for Star Control 2 that was labled starco~1 do to the 
truncating nature of old DOS. Then i ran into the problem of starting the game 
from the new game menu. I managed to get past it by using the " " (space) key 
and then the return key. That put me in the game starting point in the sol 
system. Once their i couldn't manage the menu to the right or control the ship 
since there is no direction arrows on the keyboard. Maybe the microphone key 
can be changed to a button that loads a keyboard with direction keys and some 
programmable keys?

I'm running adosbox v0.1 wvga version on Droid X.

I know that adosbox doesn't currently support sound, but hopefully in the next 
release it will?

I hope work is continued on adosbox and that it becomes available as an open 
source project for community developers to add support.

What steps will reproduce the problem?
1. I have xt720(motoroi, proyo version and 854x480 display) and aDosBox 
multitouch version.
execute is successed. but mouse touch is only correct in horizontal area.

-------------------------------------------------------------
-   can"t touch this row area                     -
-            can                                          -
-            touch                                         -
-            this                                           -
-            area                                          -
-   can"t touch this row area                     -
-------------------------------------------------------------

2. display touch is only mouse move. not click
if want mouse touch. i always move one display touch with another multitouch.
that is very hard thing.

3. please build and upload WVGA last version please : )


What is the expected output? What do you see instead?
1. can touch any location excetly.

2. display touch == mouse click that point
   display long touch == mouse right click that point
   display touch move == mouse move

What version of the product are you using? On what operating system?
aDosBox_mulittouch_patched.apk. don't know version number.

Please provide any additional information below.

sorry. i can not write english well.:)

Hi there, 
Thank you for porting Dosbox onto android, I've been waiting for this 
for a long time ! 

I have an HTC Dream device (which is the same hardware as the G1, but 
it was renamed in Canada). 

I got my hand on the WVGA APK file, and my app manager complains 
this : 
 "aDosBox could not be installed on this phone." 

Do you have an idea? In your videos, it works fine on  the G1, I 
wonder what could cause this. 

BTW I tried using both ASTRO and AndroZip as the installer, and have the same 
issue. 

Thanks and keep up the good work ! 

[email protected]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1.Open OnScreen Keyboard.
2.Change input system to T9.
3.Try to write some chars or digits.

What is the expected output? What do you see instead?
Writing could behave as normal (without T9). No chars appears on screen, only 
digits are recognized.

What version of the product are you using? On what operating system?
aDosBox-v0.2.4
Samsung Galaxy S (GT-I9000) with Froyo 2.2.1

Please consider the fact that some phones (e.g. Galaxy S I9000, which is the 
one I have) don't have a search button. Currently the only way for me to change 
settings in aDosBox is to go to settings, select apps, select aDosBox from the 
list and delete the data that way.

(I'm thinking a way to store different configs and switch between them at will 
might be to use MyBackup Root to make backups only of the data for the aDosBox 
app and restore the one Ineed. Not great but at least that way I don't need to 
set the controls and settings from scratch every time I want to play a 
different game.)

My idea for a solution to this problem is quite simple: Add an option in the 
menu to change the back button from the current escape shortcut (which seems 
handy if your device has enough buttons to support it) to the/a menu button.

What steps will reproduce the problem?

Start aDosBox, navigate to the game (bundesliga manager hattrick), start the 
game.

What is the expected output? What do you see instead?

I expect to be able to move the mouse freely, but I can only use it in a square 
in the middle of the screen of roughly 2/3 the size of the screen, thus 
rendering lots of ingame buttons useless and the game unplayable.

What version of the product are you using? On what operating system?

beta on Android GB 2.3.3

Please provide any additional information below.

Anything else seems fine! The more's the pity!

What steps will reproduce the problem?
1. Open adosbox.
2. Start a game that uses mouse. (I used Lands of Lore: Throne of chaos, and 
Leisure Suit Larry 2.)
3. Try moving mouse. LOL will only let the mouse on the right half of the 
screen, LSL2 only the left half.

What is the expected output? What do you see instead?
Mouse should traverse the entire screen. Going into settings and calibrating 
screen does not help.

What version of the product are you using? On what operating system?
beta version on 2.3.3 Vegan Rom.

Please provide any additional information below.
I'm willing to test any changes or experimental versions on my tablet to help 
resolve issues.

Hi

I've made several updates to the SDL port at
https://github.com/pelya/commandergenius
so I advise you to merge the changes.

The changes include:
Fully user-configurable on-screen keyboard (you can set button layout and 
button scancodes returned via SDL)
Two-button mouse emulation (via several methods - multitouch, screen pressure, 
button click, so it should be available on any device)
Multitouch support (zoom/rotate events will be reported by SDL as keypresses)

What steps will reproduce the problem?
1.Key tapping in games (e.g. arrows) has problem.  This happens in any game.

What is the expected output? What do you see instead?

I tap the up key once, it moves up 3 space instead of 1.

What version of the product are you using? On what operating system?

This is aDOSBox WVGA(480x800) 0.1 alpha on Android 2.2. My phone is droid 2.

Please provide any additional information below.

What steps will reproduce the problem?
1. Installed program with known requirement ("Karnov" for DOS)
2. Mapped keys for numbers 2,4,6 and 8 to keys 1,2,3 and 4.
3. Started program.

What is the expected output? What do you see instead?
Expected result was for the keys to move the figure up (8, or key number 4), 
down (2, or key number 1), left (4, or key number 2) and right (6, or key 
number 3).

The figure did not respond.

I then mapped the keys to the letter "X" (the fire button for this program), 
and they functioned as they should. I mapped them back to the numbers and they 
would not work.

What version of the product are you using? On what operating system?
0.2.4 is the version I'm using, on a Samsung Galaxy i9000 (Vibrant) with 
Android 2.2.

Please provide any additional information below.
This program -- along with a few others -- would only accept numeric input from 
the numeric keypad for some reason: arrow keys wouldn't work and the number 
keys on the top row of the keyboard wouldn't work either. Of course, this also 
happens to be one of my favorite weird little games so it's one of the first 
things I try. ;) Also, the on-screen joystick didn't work either.

Tested everything with another game ("Mah Jongg", an old DOS game but the only 
thing I had on-hand), and the keys and joystick worked perfectly.

What steps will reproduce the problem?
1. Installing adosbox on droid x
2. Running adosbox on droid then mounting a drive example: mount c 
/sdcard/adosbox
3. Then trying to change the drive to C: by typing C: however it always comes 
up as C> and won't change drives.

What is the expected output? What do you see instead?
Expected output ":" the colon mark, instead getting ">" greater than mark.

What version of the product are you using? On what operating system?
adosbox v0.1 wvga version on Droid X by Motorola

Please provide any additional information below.

Hi Sir,

I have my adoxbox on HTC dream working now, but it still have problem. Since 
HTC Dream does not have actually keyboard, no matter what I set property value 
to keyboardlayout inside dosbox.conf, software keymapper cannot be shown for 
use. Dos box become a dummy and cannot be remove unless reboot system. Cannot 
take any input into it. Any suggestion ?!

I set keyboardlayout to: none, auto. I also check ( 
http://www.dosbox.com/wiki/KEYB ) to see if we can activate software keymaper 
in HTC Dream. None of this can be done to work. Can anybody help me how to 
popup keymapper inside HTC Dream ?!

I follow instruction as follow,
================================================================================
==
Installation:

1.Download and unzip the tarball.
2.Connect your Android phone to computer
3.Install the the apk to your phone using command: 
adb install name_of_apk_file
If you see output message like "[INSTALL_FAILED_ALREADY_EXISTS]", it means the 
apk has been installed. Use following command to uninstall it: 
adb uninstall org.hystudio.dosbox
or directly use command 
adb install -r name_of_apk_file (-r means reinstall)

4.Copy file dosbox.conf to SD card of your phone using following command:
adb push dosbox.conf /sdcard/dosbox.conf
If you don't have a SD card, use following command
adb push dosbox.conf /data/data/org.hystudio.dosbox/files/dosbox.conf 
5.Have fun! Don't forget to leave feedbacks (Personal feedback, aDOSBox group)
================================================================================
==
I put my dosbox.conf inside folder /sdcard, and it's not working, AND I didn't 
see /data/data/org.hystudio.dosbox/files/ folder inside directory tree. Should 
I create those folder list and put doxbox.conf into it and try again ??

[email protected]

Message send failure
Traceback (most recent call last):
  File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/__init__.py", line 517, in __call__
    handler.post(*groups)
  File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/mail_handlers.py", line 58, in post
    self.receive(mail.InboundEmailMessage(self.request.body))
  File "/base/data/home/apps/androiddosbox/1-3.346967010761778669/handle_incoming_email.py", line 30, in receive
    self.send2mail(message)
  File "/base/data/home/apps/androiddosbox/1-3.346967010761778669/handle_incoming_email.py", line 68, in send2mail
    self.store(sender, to, subject, db.Text(decoded_body, 'utf-8'))
  File "/base/python_runtime/python_lib/versions/1/google/appengine/api/datastore_types.py", line 999, in __new__
    raise TypeError('Text() with a unicode argument '
TypeError: Text() with a unicode argument should not specify an encoding


occured this error.

Hi guys,

Great work on this port! I just wanted to let you know that sound does not work 
on my Milestone 2.  I tried DOS apps that use PC speaker, SB, SB16, and GUS. I 
changed config for SB2 and SB16. No luck for anything.

The QEMU-based emulator's sound works fine, if that's of any help.

Any ideas? 

Thanks!

What steps will reproduce the problem?
1.Modify the config file
2.Open aDosBox

What is the expected output? What do you see instead?

Instead of changing settings, it doesn't do anything.

What version of the product are you using? On what operating system?

I'm using version 0.74, on the HTC Desire S, running 2.3.3 Gingerbread

Please provide any additional information below.

I may be doing something wrong, if so, sorry.
But it appears that the config file doesn't effect the program at all.
I'm assuming that the correct config file is the one in 'app-data/org.hys...
It didn't appear to change memsize values, so I tested it by changing the 
autoexec commands.
These were also not effected.
Just thought I'd let you know.

Thanks, Lucy

What steps will reproduce the problem?
1. To get an "~", we need to press ALT + @
2. It does not register the press (either simultaneously or when entered 
one by one).

What is the expected output? What do you see instead?
Instead of getting a "~", we get nothing displayed on the screen.

What version of the product are you using? On what operating system?
DosBox 0.1 Alpha. On a HTC Dream/G1 physical keyboard, using Cyanogen Mod 
4.2.14.1

Please provide any additional information below.
None.

What steps will reproduce the problem?
1. Installed from download
2. Copied configure file over via adb
3. Ran program

What is the expected output? What do you see instead?
Boot up was expected, black screen was all i got.

What version of the product are you using? On what operating system?
WVGA version

Please provide any additional information below.

I tried both version and both CFG files and tried various settings but I cannot 
run this application. Display only black blinks. With CFG file from WVGA 
shortly, with CFG file from HVGA longly.

It would be superb if in any future version it could be possible run this 
application on low-res phones. I think they has enough memory and calculation 
power to show command prompt and even run easy 2D DOS game.

Priority is of course low.

What steps will reproduce the problem?
1. Motorola Atrix 1.5.7  AT&T (Froyo 2.2)
2. Motorola Lapdock
3. Standard USB 2.0 mouse

What is the expected output? What do you see instead?
Sideloaded aDOSBOX (no other midifications to OS apart from sideloading).
Copied Master of Orion 1 to internal memory.
Started game, left click works, but mouse only works if i left click and drag. 
The mouse cursor is also not accurate.  

What version of the product are you using? On what operating system?
Android 2.2 Froyo. 

Please provide any additional information below.
It seems like there are two mouse cursor, one within DOS, which doesn't really 
move unless i left click and try to move. It does not move much and left 
clicking does not always work. There's also the normal cursor, looks like it is 
outside of DOSBOX. 

Thanks and keep up the great work!

What steps will reproduce the problem?
1. Trackball setting in aDosBox, whether it's on or off
2.
3.

What is the expected output? What do you see instead?
Trackpad should be able to move directional arrows like a keyboard 
up/down/left/right and be able to emulate the trackpad click as a mouse 
left-click, but none of these work

What version of the product are you using? On what operating system?
HTC Desire Z on Android 2.3.3

Please provide any additional information below.

What steps will reproduce the problem?
1.Open, close, open aDosbox


What is the expected output? What do you see instead?
Black screen after tap aDosBox icon and crash

What version of the product are you using? On what operating system?
aDosBox 800x480 Xperia X10 Android 2.3.3 CM7

Please provide any additional information below.

Hi! I have problem when I closed app and try open it again. I se only black 
screen and app crash. I have to wait some time when it will run again. I added 
aLogCat Log as attachment.

Best Wishes
Resset

What steps will reproduce the problem?
1. Turning adobox on

What is the expected output? What do you see instead?
Black screen with mouse cursor in upper left corner flashes 3 times, after 
that dosbox starting screen (dos screen with welcome text in blue border) is 
shown for about half a second. After that app closes itself

What version of the product are you using? On what operating system?
HTC Dream with 2.6.29.6-cyanogenmod

What steps will reproduce the problem?
1. On command Line:>Copy con test.txt 
2. Or Copy a file to another name.
3.

What is the expected output? What do you see instead?
The Expected output of Copy Con test.txt 
(Would allow you to enter information and save by ctrl-z)
Instead I recieve:
Copy failure : test.txt
  0 File(s) copied.

What version of the product are you using? On what operating system?
Version aDOSBox-WVGA-0.1alpha.zip

Please provide any additional information below.
Since many programs use File I/O, it would be greatly beneficial to have 
write access.  Thanks for the hard work.

Hi, If we could add a menu option to change the config within DOSbox this would 
make things much more easy to use and mobile friendly. For example:

1. I boot up Dosbox
2. Hit menu and say "select pre made config etc"
3. Dosbox pulls up a file manager page to naviagte through and select a config 
that the user has premade to mount and play a specific game with the config 
settings tailored to play that game perfectly
4. Once selected Dosbox restarts and loads using the new config

It would also be handy if Dos box allowed us to rename those configs to 
something like "duke Nuke Em 3D" so the whole process is essentially selecting 
a game to automatically boot. 

The only hard part for users then would be setting the game config file up the 
first time BUT as things become more mainstream people could easily share 
premade made configs etc to boot games no problem

What steps will reproduce the problem?
1. Install DosBoxMain-debug.apk
2. run aDosBox
3. Screen flash and app drop

What version of the product are you using? On what operating system?
SVN trunk version. Android 1.6 emulator

Please provide any additional information below.

I/ActivityManager(   58): Starting activity: Intent { 
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] 
flg=0x10200000 cmp=org.hystudio.dosbox/.DosBoxMain }
I/ActivityManager(   58): Start proc org.hystudio.dosbox for activity 
org.hystudio.dosbox/.DosBoxMain: pid=1062 uid=10020 gids={3003, 1015}
I/WindowManager(   58): Setting rotation to 1, animFlags=0
I/WindowManager(   58): Config changed: { scale=1.0 imsi=0/0 loc=en_US 
touch=3 keys=2/1/2 nav=3 orien=2 layout=18}
W/WindowManager(   58): performLayoutAndPlaceSurfacesLocked called while 
in layout
W/WindowManager(   58): performLayoutAndPlaceSurfacesLocked called while 
in layout
D/StatusBar(   58): updateResources
D/dalvikvm( 1062): Trying to load 
lib /data/data/org.hystudio.dosbox/lib/libdosbox.so 0x4392f6b0
D/dalvikvm( 1062): Added shared 
lib /data/data/org.hystudio.dosbox/lib/libdosbox.so 0x4392f6b0
D/dalvikvm( 1062): No JNI_OnLoad found 
in /data/data/org.hystudio.dosbox/lib/libdosbox.so 0x4392f6b0
E/libEGL  ( 1062): couldn't load <libhgl.so> library (Cannot load library: 
load_library[984]: Library 'libhgl.so' not found)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libwebcore.so' 
for 'nativeInit' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libexif.so' 
for 'nativeInit' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libFFTEm.so' 
for 'nativeInit' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libmedia_jni.so' 
for 'nativeInit' (wrong CL)
I/ActivityManager(   58): Displayed activity 
org.hystudio.dosbox/.DosBoxMain: 1454 ms (total 1454 ms)
D/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/debug/debug.cpp:2340:  DEBUG_ShowMsg: 
DOSBox version 0.73
D/dalvikvm( 1062): +++ not scanning '/system/lib/libwebcore.so' 
for 'nativeResize' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libexif.so' 
for 'nativeResize' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libFFTEm.so' 
for 'nativeResize' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libmedia_jni.so' 
for 'nativeResize' (wrong CL)
I/libSDL  ( 1062): resize w=480 h=320
D/dalvikvm( 1062): +++ not scanning '/system/lib/libwebcore.so' 
for 'nativeRender' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libexif.so' 
for 'nativeRender' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libFFTEm.so' 
for 'nativeRender' (wrong CL)
D/dalvikvm( 1062): +++ not scanning '/system/lib/libmedia_jni.so' 
for 'nativeRender' (wrong CL)
I/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/gui/sdlmain.cpp:2047:  Copyright 2002-
2009 DOSBox Team, published under GNU GPL.
I/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/gui/sdlmain.cpp:2048:  ---
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:157:  video driver 
(null) is to be used
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:215:  video driver 
android is to be used actually
D/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/debug/debug.cpp:2340:  DEBUG_ShowMsg: 
Failed to init joystick support
D/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/gui/sdlmain.cpp:2103:  config 
file: /sdcard/dosbox.conf
D/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/debug/debug.cpp:2340:  DEBUG_ShowMsg: 
CONFIG:Loading primary settings from config file /sdcard/dosbox.conf
D/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/debug/debug.cpp:2340:  
DEBUG_ShowMsg: "" is not a valid value for variable: inactive.
D/adosbox ( 1062): It might now be reset it to default value: normal
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:603:  trying to set 
video mode: w:640; h:400; bpp:0; flags:0
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:623:  Current video 
info: w:0; h:0;
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:643:  Query video mode: 
w:640; h:400; bpp:16
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:405:  Testing support 
at bpp: 16
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:430:  Testing size 480 
x 320
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:430:  Testing size 320 
x 240
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:430:  Testing size 320 
x 200
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:405:  Testing support 
at bpp: 16
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:430:  Testing size 480 
x 320
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:430:  Testing size 320 
x 240
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:430:  Testing size 320 
x 200
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:405:  Testing support 
at bpp: 15
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:409:  No sizes 
supported at bpp: 15
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:405:  Testing support 
at bpp: 32
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:409:  No sizes 
supported at bpp: 32
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:405:  Testing support 
at bpp: 24
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:409:  No sizes 
supported at bpp: 24
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:405:  Testing support 
at bpp: 8
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:409:  No sizes 
supported at bpp: 8
D/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:479:  Cannot find video 
mode by adjusting bpp
W/adosbox ( 1062): 
apps/adosbox/project/jni/sdl/src/video/SDL_video.c:646:  Failed to 
retrieve correct video mode
I/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/misc/support.cpp:185:  bad 
modification!!!
I/adosbox ( 1062): 
apps/adosbox/project/jni/dosbox/src/misc/support.cpp:186:  Could not 
initialize video: No video mode large enough for 640x400
E/libEGL  ( 1062): validate_display_surface:534 error 3008 
(EGL_BAD_DISPLAY)
I/DEBUG   ( 1050): *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
*** ***
I/DEBUG   ( 1050): Build 
fingerprint: 'generic/generic/generic/:1.6/Donut/eng.root.20091129.134126:e
ng/test-keys'
I/DEBUG   ( 1050): pid: 1062, tid: 1069  >>> org.hystudio.dosbox <<<
I/DEBUG   ( 1050): signal 11 (SIGSEGV), fault addr 450bb000
I/DEBUG   ( 1050):  r0 450bb000  r1 08610861  r2 0004afe0  r3 08610861
I/DEBUG   ( 1050):  r4 00000861  r5 450bb000  r6 00000001  r7 0004b000
I/DEBUG   ( 1050):  r8 00023e54  r9 424c7f7c  10 424c7f6c  fp 00000001
I/DEBUG   ( 1050):  ip 08610861  sp 44fd9cdc  lr 08610861  pc afb0454c  
cpsr 20000010
I/ActivityManager(   58): Process org.hystudio.dosbox (pid 1062) has died.
I/WindowManager(   58): WIN DEATH: Window{43b00250 
org.hystudio.dosbox/org.hystudio.dosbox.DosBoxMain paused=false}
I/WindowManager(   58): WIN DEATH: Window{43aaef10 SurfaceView 
paused=false}
I/DEBUG   ( 1050): tid 1069 not responding!
I/DEBUG   ( 1050): debuggerd committing suicide to free the zombie!
D/Zygote  (   30): Process 1062 exited cleanly (1)
I/DEBUG   ( 1072): debuggerd: May  7 2010 16:50:39
D/dalvikvm(   58): GC freed 1127 objects / 58688 bytes in 296ms
I/WindowManager(   58): Setting rotation to 0, animFlags=0
I/WindowManager(   58): Config changed: { scale=1.0 imsi=0/0 loc=en_US 
touch=3 keys=2/1/2 nav=3 orien=1 layout=18}
W/WindowManager(   58): performLayoutAndPlaceSurfacesLocked called while 
in layout
W/UsageStats(   58): Unexpected resume of com.android.launcher while 
already resumed in org.hystudio.dosbox
D/StatusBar(   58): updateResources
W/InputManagerService(   58): Got RemoteException sending setActive(false) 
notification to pid 1062 uid 10020
W/InputManagerService(   58): Window already focused, ignoring focus gain 
of: com.android.internal.view.IInputMethodClient$Stub$Proxy@43ab2e18
D/dalvikvm(   58): GC freed 910 objects / 44304 bytes in 134ms
D/dalvikvm(   99): GC freed 9364 objects / 524384 bytes in 192ms

What steps will reproduce the problem?
1. Load conquest of the new world or game that uses a mouse
2.
3.

What is the expected output? What do you see instead?
With the laptop trackball option enable the cursor will only work in the bottom 
right hand quater of the screen. With all mouse options turned off (set when 
first running) the cursor will move but returns to centre of screen and does 
not accurately track finger on touch screen

What version of the product are you using? On what operating system?

Adosbox 0.2 Motorola Xoom
Please provide any additional information below.

Thanks. Great work

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.

What steps will reproduce the problem?
1. On installing
2.
3.

What is the expected output? What do you see instead?
INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION

What version of the product are you using? On what operating system?
COBY KYROS MID7015 , ANDROID 2.1

Please provide any additional information below.
ADB can't install the aDOSBox-WVGA-0.2beta.apk , it returns a error 
INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION , and the 0.1alpha returns a BLACK 
SCREEN.

What steps will reproduce the problem?
1. Drag the mouse pointer on the screen OR
2. Tap on the screen

What is the expected output? What do you see instead?
Tapping: 
Expected: Mouse pointer moves to that point, and invokes an 'onclick' event 
there.
Instead: Mouse pointer stays on position, 'onclick' event invoked.

Dragging: 
Expected: 'drag' event started.
Instead: First an 'onclick' event is invoked, then the pointer changes posion 
with the amount dragged. 

Alternative solution/function:
- When dragging, the mouse pointer moves, but no onclick event is invoked. 
- To invoke an onclick event, a slightly longer tap is required. 

What version of the product are you using? On what operating system?
I have an Archos 43 with Android 2.2. I installed the latest Adosbox (0.1 
alpha) and made it automatically start the dos version of settlers of catan 
(www.boardgame.de/).


Please provide any additional information below.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

It's not that I have a problem. I recently managed to figure out how to get 
adosbox to work properly and run high seas trader, very smoothly I might add. 
However, having a samsung galaxy s and no knowledge of using source codes I 
cannot get a virtual keyboard. Is it possible for someone to compile and post 
an sdl thing so I can use an onscreen keyboard? Also, is it possible to map 
volume up and volume down as left click and right click?

What steps will reproduce the problem?
1. set Separate thread for video
2.
3.

What is the expected output? What do you see instead?
after that app crash every time on start


What version of the product are you using? On what operating system?
HTC Hero android 2.2 

Please provide any additional information below.
had to clear data for application menu, to start program 

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Not all dos games are tested.

Please list the games you tried, Adosbox version, phone model, android version, 
completion of the game, and issue.  This will help adosbox future compatibility.

e.g.
1. Star Control 2
2. Adosbox WVGA 0.1 alpha
3. Droid 2
4. Android 2.2
5. Unable to complete.
6. Issue: Errors while "press <enter>" screen. Error message: "Run-time error 
R6003 - integer divide by 0"

1. Pal (mandarin game)
2. Adosbox WVGA 0.1 alpha
3. Droid 2
4. Android 2.2
5. Unable to complete.
6. Issue: Errors on 1st frame. Flashing in red.  Not responsive afterward.

1. Rich 3 (mandarin game)
2. Adosbox WVGA 0.1 alpha
3. Droid 2
4. Android 2.2
5. Unable to complete
6. Issue: Won't load. Screen blank.

1. Rich 2 (mandarin game)
2. Adosbox WVGA 0.1 alpha
3. Droid 2
4. Android 2.2
5. Unable to complete
6. Runs fine but can't complete due to problem with saving the game.
6. Issue: Can't save. Error message: "Error 75 occurred in module SUB at 
address 0E78:B9F4"

Hey all, I have the moto Droid 2.0 and numbers don't work for me. 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 install screen to 
come up, and it would let me to a small and medium install, but i found 
somewhere if i modify the install I can install it fully (which led me to my 
problem of the numbers not working). well, 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, and I hope someone else 
knows what I'm doing wrong w/the numbers not working lmao!

What steps will reproduce the problem?
1. Attempt to calibrate touchscreen by touching 4 corners followed by menu 
button (also touchscreen).
2. Restarted aDosBox.

What is the expected output? What do you see instead?
Whole touchscreen is responsive, but mouse only travels within a box covering 
about 70% of the screen. Unable to reach edges of screen with the mouse 
pointer. Mouse pointer does not match finger position.

What version of the product are you using? On what operating system?
Using Android 3.0 Honeycomb on a Acer Iconia A500 Tablet. Screen is 800x1280. 
Using aDosBox 0.2Beta.

Please provide any additional information below.
Willing to help you troubleshoot/test new code for tablet/honeycomb.

What steps will reproduce the problem?
1. Press the Fn (function) key on the phone's hardware-keyboard
2.
3.

What is the expected output? What do you see instead?
The Fn (Function) key on the phone's hardware-keyboard is used for typing in 
special characters (e.g. *()/ etc. etc.) but they do not work

What version of the product are you using? On what operating system?
HTC Desire Z on Android 2.3.3

Please provide any additional information below.

What steps will reproduce the problem?
1. Launch the game in full audio mode

What is the expected output? What do you see instead?
You can see very poor performance, game is not playable. Sound is hearable but 
with huge fps drop, lots of cracks are heard.


What version of the product are you using? On what operating system?
Android 2.2.1 (Froyo) on Samsung Galaxy S.
aDosBox 0.2beta

Please provide any additional information below.
In reduced audio mode or with sound disabled game is fully playable.

What steps will reproduce the problem?
1. Install adosbox on a Milestone with a German Keyboard Layout
2. Try to enter a ':'

What is the expected output? What do you see instead?
output should be a ':', instead it's '>'

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.
I tried to set the locale to 'gr' via keyb. That maps the './:' key to the
actual ':' but still all the other special characters are unreachable. I
guess additional keymaps for non-english phones are required.

What steps will reproduce the problem?
1.-
2.-
3.-

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Please support wyvga resolution, I have Samsung Galaxy 3

What steps will reproduce the problem?
1. copy a working dosbox image file to sd card
2. start adosbox
3. imgmount c <imagefile>

What is the expected output? What do you see instead?
Excepted: imgagefile mounted
Instead: There is an error, saying the image is wrong or cannot be reached.

What version of the product are you using? On what operating system?
aDosBox alpha 1 - Android 2.1

What steps will reproduce the problem?
1.Running a game that uses a mouse.
2.
3.

What is the expected output? What do you see instead?
The touch screen should be able to move the mouse anywhere on the screen.  It 
partially works, but seems to only move the mouse around above the transparent 
arrows and the transparent number keys.  It seems to only move on the top part 
of the screen.

What version of the product are you using? On what operating system?
I am using Android 2.2.1 on a Droid X phone.

Please provide any additional information below.
The game starts up fine and the transparent keys seem to work okay.  The big 
problem is with movement of the mouse.  It is inconsistent and will not move 
over the whole screen.

Thanks for the effort and I will do some other tests with my phone.

What steps will reproduce the problem?
1.compiling the source code Ex: gcc test.cpp
2.compiling using rhide(IDE),cpp, etc
3.

What is the expected output? What do you see instead?
source code being compiled,

gcc.exe: Internal error: (null) (program cc1plus)
please submit a full bug report.

What version of the product are you using? On what operating system?
adosbox 0.2-Beta

Please provide any additional information below.

first it asked that it needed cwsdpmi, I've got it and all executables worked,
but got error on compilation,

WI was wondering if it would be possible to make a game selection menu/ui that 
perhaps runs a custom CFg for any game someone adds. Dosbox emulators require a 
lot of tweaks from one game to the next in controls and in cycles. It would be 
ideal to make a custom setup the first time a game loads and then have the app 
remember to load the custom controller config. Settings. And directly boot the 
game.

What steps will reproduce the problem?
1. I moved aDosBox.apk and dosbox.conf to sd card on Motorola Milestone
2. Installed aDosBox
3. Mounted DOS game Hidden Agenda, executed agenda.com

What is the expected output? What do you see instead?
Expected output - game's intro, instead an error "Problem with default drive. 
Please correct."

What version of the product are you using? On what operating system?
aDOSBox WVGA(480x800) 0.1 alpha on Android 2.1

Please provide any additional information below.

What steps will reproduce the problem?
1.Its like this by default (at least for me), I haven't changed any settings

What is the expected output? What do you see instead?
Normal keyboard functions, instead most keys don't work and some are mapped to 
random keys (Space is "o", v is "b")

What version of the product are you using? On what operating system?
Latest version on Android 2.2

Please provide any additional information below.
I've tried this with both the software keyboard and and usb keyboard that I 
plugged into my tablet, both have the same problem with the same random 
mapping. I've never had this issue with any other program, including another 
Dosbox app.

What steps will reproduce the problem?
1.  Run adosbox
2.  Execute Telengard
3.

What is the expected output? What do you see instead?
The screen blinks slowly (possibly once or twice per second) between two 
versions of the in-game screen; one is the current image, and the other is the 
game screen as it appeared prior to the last button press.

What version of the product are you using? On what operating system?
I'm using the released alpha apk (.1?)

Please provide any additional information below.

T-Mobile G2