Press CTRL+F1 to map the keys. I don't have Railroad Tycoon so I can't test to see if it works for that game.

Thanks. But I don't get it running. Would you like to check it out? Contact me at mail_at_hori.ch and I will send you the game for testing. It's just about 500kB.

Hmm, I'm not sure what I did. It is working now. Is it possible that there is a bug in default key map?
I removed a "hold" on the right arrow - maybe I put it there earlier. Anyway, thank you very much.

the game works if you use the numeric keyboard with shift.

The problem seems to be in the area how dosbox handles extended keys.
Will retest those codes on a real pc.

Qbix wrote:

the game works if you use the numeric keyboard with shift.

The problem seems to be in the area how dosbox handles extended keys.
Will retest those codes on a real pc.

I could save you some trouble about DOSBOX v0.63 if you refer to this older VOGONS post about DOSBOX scancode handling.

The link is: Scan Codes: DOSBOX vs DOS/XP

Hope this helps,

dvwjr

hmm yes. I see it again.
Well there was nothing wrong in the keys used by game.
our extended key handling is perfect when it comes to railroad tycoon. I can only imagine you had numlock turned on... (as numlock reverses the effect of shift)

A few of those keys by dvwjr are indeed wrong. those undefined keys we know of. Some keys don't make much sense though.

I downloaded RRT jesterday from the official HP. First everything was ok. I built my first tracks and so on. Suddenly I could not build or remove tracks anymore. (I had enough money!) Some minutes later everything went fine again. Than, everytime i moved the cursor with the num-keys a track was build (with shift not pressed).
During the Game I changed several times to other Programs like ICQ, Explorer etc. using Alt-Tab or the Windows-Key.
Later i quit the game.
Now every time i start the game, i have the problem georg descibed in the first post.
But i recognized one more thing: Time is not running. It is always the January of the first Year (I changed the gamespeed often!). So i dont think its a problem of the key-map.
I use DosBox 0.65, it comes with the download of the game. I did no changes to the Programm.

yes. The switching to other programs confuses dosbox a bit.
The problem is related to the numlock setting. DOSBox resets it to off if you switch to a different program. (semi bug in dosbox)
numlock and shift are mutually exclussive when it comes to building tracks.

When i dont switch to other programms the 2 problems still remain:
1. I cannot build tracks
2. Time is not running

My DosBox.conf[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 to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if dosbox has an error.
# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest.
# Second entry behind the comma is for when dosbox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.

fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language -- Select another language file.
# memsize -- Amount of memory dosbox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

language=
machine=vga
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.
# Supported are none,normal2x,normal3x,advmame2x,advmame3x,advinterp2x,advinterp3x,tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: simple,normal,full,dynamic.
# cycles -- Amount of instructions dosbox tries to emulate each millisecond.
# Setting this higher than your machine can handle is bad!
# You can also let DOSBox guess the correct value by setting it to auto.
# Please note that this guessing feature is still experimental.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.

core=dynamic
cycles=6000

Set speed to something other than pause?

If you are talking about the Game Speed, the date remains Jan, 1830, no matter if i change the game speed to turbo or anything else.
In Pause-mode i should be able to build tracks.