maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Games (https://talk.maemo.org/forumdisplay.php?f=12)
-   -   How to calibrate stylus in n900 dosbox? (https://talk.maemo.org/showthread.php?t=42423)

ududud 2010-01-27 16:38
How to calibrate stylus in n900 dosbox?
 
Hi guys, this is my first post (sorry for my english ^^ im spanish)

i was installed the dosbox, with the rover.sys, and all ok after any hours all run ok, i was try play many games.. and i was try play warcraft 1, 2, theme hospital etc etc.. and this game RUN OK .. but the problem is the "stylus" the calibrate is very sux, i cant play with this.. any have any solution for this? (in the config.sys only have 2 options for mouse, the sensibility and the lock=true or false.. i dont have more options..

the question is how can calibrate this?

javispedro 2010-01-27 16:47
Re: How to calibrate stylus in n900 dosbox?
 
There's no calibration.

Allow me to explain the issue: DOS apps expects (most of them) relative mouse coordinates ("mouse moved 10 units to the left, then 10 to the right"). Touch screen gives absolute coordinates ("mouse is at pixel 40 of a 480 pixels screen").

DOS programs then use the relative coordinates to draw a cursor at an absolute position, but you cannot "get" that information easily. Most DOS apps also apply their own mouse speed/acceleration algorithms over the given mouse relative coordinates, and again DOSBox knows nothing of this.

Thus, the touch screen coordinates and the drawn cursor can easily desynchronize.

The only solution is to try to disable any mouse acceleration support in the application, and play with the mouse speed settings (again, in the DOS applications) until they agree with the DOSBox sensitivity.

ududud 2010-01-27 17:02
Re: How to calibrate stylus in n900 dosbox?
 
ok, if any guys was played this games in dosbox have any recomendation for config this? true or false the lock? and the sensibility? how?

javispedro 2010-01-27 17:51
Re: How to calibrate stylus in n900 dosbox?
 
autolock true makes no sense in this device...

ArnimS 2010-01-27 17:52
Re: How to calibrate stylus in n900 dosbox?
 
It makes me cry.

Not easy to fix. IBM PC SUCKS.

It really SUCKS.

janus_0104 2010-03-23 22:11
Re: How to calibrate stylus in n900 dosbox?
 
maybe it's due to a simplistic description, but it seems to me you could just store the absolute position from the last timestep and compute the relative coordinates through that? E.g. I click on [1,1], then on [100,100] and DOSBOX simulates [+99,+99] ?

javispedro 2010-03-23 22:20
Re: How to calibrate stylus in n900 dosbox?
 
You're describing the way it works now.

janus_0104 2010-03-24 21:27
Re: How to calibrate stylus in n900 dosbox?
 
then i dont see why the results are so off?

javispedro 2010-03-24 21:35
Re: How to calibrate stylus in n900 dosbox?
 
If you tap coords 200,200, then point to 100,100, doesn't the pointer move 100,100 "units" to the upperleft corner?

SubCore 2010-03-24 21:39
Re: How to calibrate stylus in n900 dosbox?
 
the DOS games apply their own, additional computation regarding mouse position, speed, acceleration and so on.

dosbox tells it exactly where your stylus went/is, but the games interpret that differently, they make it go further a few pixels so it seems smoother. (considering the quality of ball mice back then not a bad idea actually *g*).

but dosbox cannot know that of course, because it only "feeds" the difference to your stylus' last exact position to the game.
which now differs from the position of the cursor. this adds up over time, resulting in desynchronization.

(feel free to correct me if i understood it wrong :) )

javispedro 2010-03-24 22:41
Re: How to calibrate stylus in n900 dosbox?
 
Na, you got it well.

As a result, the only "possible" calibration is to try to force the drawn pointer into a corner and try to start from there... all while hoping you can get the acceleration settings and dosbox sensitivity to match.

janus_0104 2010-03-25 07:23
Re: How to calibrate stylus in n900 dosbox?
 
Then how about that sort of calibration? imagine a calibration screen for dosbox for any game by key shortcut, it displays a small slide at the top and left screen border. then the software emulates first a click on [1,1] then one at exact center (or right down, which is what? [799,479]?), rinse and repeat. From the way that mouse cursor is displaced from it's intent direction one could then "scale" the mouse movement with the two sliders for vertical and horizontal movement. Once the right calibration is found for the game, just have the software make sure the mouse cursor moves from [1,1] to it's actual position in each game cycle, so the game cant screw it up.... Hmm, I think I mixed two ways to do it, there. Or zero, depending on software capabilities (how deep you can edit dosbox for this device, how much you can change when the game actually runs, etc).

I know it's not as easy as it sounds, but it's definitely possible with a hack. It works for PC,too, doesnt it? The way I get it, the PC doesnt have this issue since it's mouse always has a cursor position and cant "jump" that much, but you could do the same for the n900, the actually stylus tap only giving a direction the mouse cursor should by software move to, not directly click at, speed up clock time/skip so it looks smooth then find a way to slow the actual game itself down so only the mouse movement is working.

Or a simpler idea: just have the mouse cursor move by key press. I remember that's the way I played Zack McKracken back then, and I didn't mind much. You'd probably have to decide for certain games differently which buttons to use, but if you can access the proximity sensor during dosbox runtime, just have proximity_sensor_pressed make the arrow keys move the mouse not execute arrow_up etc. How about that? Would that be easier to do?

SubCore 2010-03-25 16:44
Re: How to calibrate stylus in n900 dosbox?
 
Quote:
Originally Posted by janus_0104 (Post 581434)
I know it's not as easy as it sounds, but it's definitely possible with a hack.
no, it's not.

once again: dosbox has _no_idea_ where the application actually draws the cursor. there's no information "coming back" from the application that would enable this hack of yours, other than screen output. and please don't suggest scanning the screen output for something that might be a cursor :)

the reason it's not such a problem on a PC is quite simple - the desynchronization occurs just as on the N900, but you don't notice it because the PC's mouse gives relative coordinates.
you might have to move it a little more (or less) to compensate for the desynchronization, but it doesn't "feel" wrong. the mouse may seem sluggish, but it follows where you move it.


a keyboard mouse emulation might be a possibility, but i don't know how much work that would be for javis :) (a lot, probably)
also, there could already be something like that available, if it runs and works under dos, it may run on the dosbox as well.

janus_0104 2010-03-25 17:37
Re: How to calibrate stylus in n900 dosbox?
 
i think you didnt get what i meant, but i assume the keyboard as mouse version is still the most optimistic option. If anyone has an idea how to do that I'll definitely be thankful^^

elteclas 2010-05-29 19:50
Re: How to calibrate stylus in n900 dosbox?
 
Stylus finally works!

finally found a solution. I tried different settings on dosbox.conf, here my last config: (sorry my English) I test with X-COM Terror from The Deep and works very nice , i recommend this game

Spanish version:
Finamlemnte he encontrado una solucion. He probado diferentes configuraciones en dosbox , aqui dejo mi ultima configuracion. Lo he probado con X-COM Terror en las Profundidades y funciona bonito. Recomiendo este juego.

Quote:
# This is the configurationfile for DOSBox 0.73.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[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.
# 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.

SDL_Mouse_Relative=0
fullscreen=false
fulldouble=false
fullresolution=800x480
windowresolution=800x480
output=surface
autolock=false
sensitivity=100
waitonerror=false
priority=higher,lowest
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language: Select another language file.
# machine: The type of machine tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=32

[render]
# frameskip: How many frames DOSBox skips before drawing one.
# aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended,the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropouts and lags. Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000)
# 'max' will allocate as much cycles as your computer is able to handle
#
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to increase/decrease with keycombo.
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=auto
cycles=auto
cycleup=500
cycledown=20

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 2048, 4096, 8192, 1024, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use. See README for details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
# sbtype: Type of sblaster to emulate.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, none.
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12.
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none.
# oplemu: Provider for the OPL emulation. compat or old might provide better quality (see oplrate as well).
# Possible values: default, compat, fast, old.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 22050, 49716, 44100, 48000, 32000, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=default
oplrate=22050

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 5, 6, 7.
# ultradir: Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=false
gusrate=22050
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. (false is old style behaviour).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1: set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq.
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms: Enable XMS support.
# ems: Enable EMS support.
# umb: Enable UMB support.
# keyboardlayoutfile: Path to keyboard definition file (keyboard.sys or auto|none).
# keyboardlayout: Code for the keyboard layout (or auto|none).
# codepagefile: Path to codepage definition file (ega.cpi or auto|none).
# codepage: Desired codepage.

xms=true
ems=true
umb=true
keyboardlayoutfile=auto
keyboardlayout=auto
codepagefile=auto
codepage=auto

[autoexec]
# Lines in this section will be run at startup.
mount c: /home/user/MyDocs/msdos
C:
cd xcom
play.bat

javispedro 2010-05-29 20:02
Re: How to calibrate stylus in n900 dosbox?
 
Quote:
Originally Posted by elteclas (Post 688587)
Stylus finally works!
It's not a universal solution. As I was saying, every game will have its own "best" sensitivity settings -- no global solution.

elteclas 2010-05-30 12:40
Re: How to calibrate stylus in n900 dosbox?
 
Quote:
It's not a universal solution. As I was saying, every game will have its own "best" sensitivity settings -- no global solution.
I tried several mouse games with these settings and they work well:
Dune 1
Dune 2
X-Com UFO
X-Com Terror from the Deep
Eye Of The Beholder 1 & 2

Whats is the game does not work for you? I can test. Thanks

GameboyRMH 2010-05-30 12:58
Re: How to calibrate stylus in n900 dosbox?
 
I just added:


SDL_Mouse_Relative=0

And now it works pretty decently on Loom

elteclas 2010-05-30 13:14
Re: How to calibrate stylus in n900 dosbox?
 
I correct my settings for best sound play and cpu clycles, the new config is this:

My last config proposal:
PHP Code:
# This is the configurationfile for DOSBox 0.73.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[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.
#         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.

SDL_Mouse_Relative=0 
fullscreen=false
fulldouble=false
fullresolution=800x480
windowresolution=800x480
output=surface
autolock=false
sensitivity=100
waitonerror=false
priority=higher,lowest
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language: Select another language file.
#  machine: The type of machine tries to emulate.
#           Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
#  memsize: Amount of memory DOSBox has in megabytes.
#             This value is best left at its default to avoid problems with some games,
#             though few games might require a higher value.
#             There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=16

[render]
# frameskip: How many frames DOSBox skips before drawing one.
#    aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
#    scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended,the scaler will be used even if the result might not be desired.
#            Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
#      core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
#            Possible values: auto, dynamic, normal, simple.
#   cputype: CPU Type used in emulation. auto is the fastest choice.
#            Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
#    cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropouts and lags. Cycles can be set in 3 ways:
#              'auto'          tries to guess what a game needs.
#                              It usually works, but can fail for certain games.
#              'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
#                              (Example: fixed 4000)
#              'max'           will allocate as much cycles as your computer is able to handle
#            
#            Possible values: auto, fixed, max.
#   cycleup: Amount of cycles to increase/decrease with keycombo.
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=auto
cycles=800
cycleup=500
cycledown=20

[mixer]
#   nosound: Enable silent mode, sound is still emulated though.
#      rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
#            Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
#            Possible values: 2048, 4096, 8192, 1024, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=44100
blocksize=1024
prebuffer=200

[midi]
#     mpu401: Type of MPU-401 to emulate.
#             Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
#             Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use. See README for details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
#  sbtype: Type of sblaster to emulate.
#          Possible values: sb1, sb2, sbpro1, sbpro2, sb16, none.
#  sbbase: The IO address of the soundblaster.
#          Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
#     irq: The IRQ number of the soundblaster.
#          Possible values: 7, 5, 3, 9, 10, 11, 12.
#     dma: The DMA number of the soundblaster.
#          Possible values: 1, 5, 0, 3, 6, 7.
#    hdma: The High DMA number of the soundblaster.
#          Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
#          Possible values: auto, cms, opl2, dualopl2, opl3, none.
#  oplemu: Provider for the OPL emulation. compat or old might provide better quality (see oplrate as well).
#          Possible values: default, compat, fast, old.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
#          Possible values: 22050, 49716, 44100, 48000, 32000, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=auto
oplrate=22050

[gus]
#      gus: Enable the Gravis Ultrasound emulation.
#  gusrate: Sample rate of Ultrasound emulation.
#           Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
#  gusbase: The IO base address of the Gravis Ultrasound.
#           Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
#   gusirq: The IRQ number of the Gravis Ultrasound.
#           Possible values: 5, 3, 7, 9, 10, 11, 12.
#   gusdma: The DMA channel of the Gravis Ultrasound.
#           Possible values: 3, 0, 1, 5, 6, 7.
# ultradir: Path to Ultrasound directory. In this directory
#           there should be a MIDI directory that contains
#           the patch files for GUS playback. Patch sets used
#           with Timidity should work fine.

gus=false
gusrate=22050
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
#    pcrate: Sample rate of the PC-Speaker sound generation.
#            Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
#     tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
#            Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
#            Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
#    disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
#               2axis (supports two joysticks),
#               4axis (supports one joystick, first joystick used),
#               4axis_2 (supports one joystick, second joystick used),
#               fcs (Thrustmaster), ch (CH Flightstick).
#               none disables joystick emulation.
#               auto chooses emulation depending on real joystick(s).
#               Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
#        timed: enable timed intervals for axis. (false is old style behaviour).
#     autofire: continuously fires as long as you keep the button pressed.
#       swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
#   buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1: set type of device connected to com port.
#          Can be disabled, dummy, modem, nullmodem, directserial.
#          Additional parameters must be in the same line in the form of
#          parameter:value. Parameter for all types is irq.
#          for directserial: realport (required), rxdelay (optional).
#                           (realport:COM1 realport:ttyS0).
#          for modem: listenport (optional).
#          for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
#                         transparent, port, inhsocket (all optional).
#          Example: serial1=modem listenport:5000
#          Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
#          Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
#          Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
#          Possible values: dummy, disabled, modem, nullmodem, directserial.

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
#                xms: Enable XMS support.
#                ems: Enable EMS support.
#                umb: Enable UMB support.
# keyboardlayoutfile: Path to keyboard definition file (keyboard.sys or auto|none).
#     keyboardlayout: Code for the keyboard layout (or auto|none).
#       codepagefile: Path to codepage definition file (ega.cpi or auto|none).
#           codepage: Desired codepage.

xms=true
ems=true
umb=true
keyboardlayoutfile=auto
keyboardlayout=auto
codepagefile=auto
codepage=auto

[autoexec]
# Lines in this section will be run at startup.
mount c: /home/user/MyDocs/msdos
C: 

javispedro 2010-05-30 14:37
Re: How to calibrate stylus in n900 dosbox?
 
Quote:
Originally Posted by elteclas (Post 689730)
Whats is the game does not work for you? I can test. Thanks
Any text mode / msmouse app (which works better with the default sensitivity).

Btw, reducing emulated memory size might help with performance also.

elteclas 2010-05-31 17:38
Re: How to calibrate stylus in n900 dosbox?
 
now I have a small problem, to use the stylus with DosBox. I try to bind a key with the right mouse button. But do not know how to xbindkeys, can you?

żXmodmap need another config? Very thanks

http://img444.imageshack.us/img444/7...0053119310.png

Deafboy 2010-06-05 12:30
Re: How to calibrate stylus in n900 dosbox?
 
I have tried the dosbox.conf posted on page before. First time dosbox crashed after intro of warcraft1, and second time whole device restarted while trying to load saved game. Trird time I saw only black screen and after some time something like in-game screensaver appeared after then the game menu finaly showed up. Whole screen is blinking very often, game is incredibly slow, but yes... the mouse is finaly working like a charm :D
I will play with config later.

ignarus 2010-07-09 08:33
Re: How to calibrate stylus in n900 dosbox?
 
Did anyone who tried X-Com terror from the deep have problems with performance? With the config file which was provided at least for me the game was not very smooth...

Addison 2010-07-09 09:52
Re: How to calibrate stylus in n900 dosbox?
 
Quote:
Originally Posted by ignarus (Post 745823)
Did anyone who tried X-Com terror from the deep have problems with performance? With the config file which was provided at least for me the game was not very smooth...
You'll probably will have to disable all sound.

You need to also have a right mouse click as well.

efekt 2010-07-10 12:24
Re: How to calibrate stylus in n900 dosbox?
 
Anyone bumped into a good settings for X-Com 1 (Enemy Unknown)?
I used the settings which have been posted by elteclas in reply number 19 here, and the game works nice but sometimes it seems that mouse clicks does not always register, so sometimes there's a need to click more than one time in order to the click to register...
And what about mouse right-button clicks, does it work with this .conf file?

baggacfreak 2013-03-10 14:24
Re: How to calibrate stylus in n900 dosbox?
 
Hi,

just tried to boot into kolibri os with boot kolibrios.img and mouse does not work thats a bummer because this os would be so sweet to be used on the n900. Anyone a good hint what I could do to get the mouse to work proberly?


All times are GMT. The time now is 07:51.

vBulletin® Version 3.8.8