When you do a "mount c c:/dtestf", the folder C:\DTestF has to exist for real, that is on your real hard drive. I suspekt that the real folder is actually C:\ProgramFiles\DTestF, so try this instead:

mount C "C:\ProgramFiles\DTestF"

(remember the quotes)

Duuu
OK when I type quotes " I get nothing in the DOSBOX window. Another keboard problem?
if I type mount c c:/programfiles/dtestf/. it doesnt work.
if I type mount c c:/program files/dtestf/. directory program doesn't exist.

If I create C:/dtest (in the root) and type mount c c:/dtest the mount works!!!
YEA

Conclusion DOSBOX works best with old DOS file name limits. That is no spaces and 8 char limit.

MANY THANKS

The mount command works fine with any real path that you give it, including paths with spaces, - BUT you have to quote them!

If you try to do a mount C C:/Program Files/DTestF the mount command sees the path as "C:/Program" and the "Files/DTestF" becomes just another unrecognized (and ignored) option.

You should be able to do all your mounting in the dosbox.conf file btw. Open with Notepad and stick your mounts in the autoexec-section.

Or you can do it when you launch DOSBox:

dosbox.exe -c "mount C 'C:\Program Files\DTestF'"

Edit: Changed the quoting as per Qbix instructions. First a double quote ("), then single ('), then single, and finally the closing double.

think you have to switch the quotes around.

Again many thanks for your help.

As I said my double quote does not appear in DOSBOX so now what (again)?

Also, when I tried to edit the .conf file in notepad Vista would not let me save changes. Something about needing permission. I am the sys adm so now what?

Tried holding alt and typing 92 but nothing happens. Is that the correct action?

Oh DOS how simple it was.
I use a dos shell called directory scanner by Nat Marino from the 80's.
Works in DOSBOX but cannot make path changes because of \ problem.

john1w wrote:

but cannot make path changes because of \ problem.

use / instead.

On reflection, the root of the problem is the keyboard. In the readme it said it was a known problem with non US keyboards.

Here I am with my new HP desktop with a US keyboard (PS2-lots of extra keys). When I first saw the problem I thought is was this keypad so I went upstairs and brought down my old noname keyboard (PS2- keysonic?) same problem.

One of the other threads had some screen snapshots, which lead to a keyboard layout shown on the screen. I was able to get to that same screen and it showed proper key placement.
Somewhere in DOSBOX there must be a key map which takes the keypress and assignes it to an (ascii?[back in the DOS days that should be all that is needed]) code.

From other threads it seems that an old fix was keyb US. Could someone create a US2 that has alternate key definitions to adress this (common) problem? Are there DOS commands to show the native code from each key that is then mapped etc (inverse of alt)?

the DS program doesn't like the / works with the \
I'll try again later

well vista (some keyboard drivers) mess up a lot for you. There is a thread on the development forum about it.
the mapper you want is hidden under ctrl-f1

john1w wrote:

Also, when I tried to edit the .conf file in notepad Vista would not let me save changes. Something about needing permission. I am the sys adm so now what?

The DOSBox installer is not Vista-aware and installs the configuration file inside the Programs folder, and that leads to a lot of problems.

Solution #1: Copy that dosbox.conf to somewhere in your Documents folder. You can even make multiple copies and name them according to which game or configuration you want. E.g. CommanderKeen-dosbox.conf.

Next, edit your DOSBox shortcut (or make a new one, call it CommanderKeen) and change the target into something like
C:\path\to\your\dosbox.exe -conf "C:\path\to\your\CommanderKeen-dosbox.conf"

Solution #2: Install one of the DOSBox frontends that makes it a breeze to edit and create game-specific configurations.