I don't understand. There are so many easier ways to do what you're trying to do there. Such as using the autoexec section in the config file.

But if you want to point DOSBox to the current directory for dosbox.conf, try:

DOSBox.exe -conf ".\dosbox.conf"

curvedline wrote:

because files are TOO scattered and hard to get there.

What makes you think so? You can just type %appdata%\..\Local\DOSBox if you want.

Anyway, if I'm not mistaken, running DOSBOX.EXE "W:\ZZZ1\ARCADE\3D\BL.EXE" will automatically mount W:\ZZZ1\ARCADE\3D as drive C.

Or just

1%localappdata%\DOSBox

It does look in the current working directory ? (If no configuration file has been specified)

>using the autoexec section in the config
This is the worst way, then i have to put dosbox.conf into every DOS directory, if you have 200 DOS directories and 200 files in each, going to look for every dosbox.conf is unmanagible.

>-c "mount c W:\ZZZ1\ARCADE\3D\" ...automatically mount
thanks for this info, but this line was required in old DOSbox, although i didnt understand why at that time. I will delete them.

>DOSBox.exe -conf ".\dosbox.conf"
thanks for ".\" info which is the drive letter independant.

I will try to wait for DOSbox Ver 0.75, if they don't give an old option, then i will add -conf ".\dosbox.conf" in my 200 batch files.
right now, i use v0.72 for 200 batch files almost and v0.74 for the few programs that need to be tweaked every part of dosbox.conf.

curvedline wrote:

>using the autoexec section in the config
This is the worst way, then i have to put dosbox.conf into every DOS directory, if you have 200 DOS directories and 200 files in each, going to look for every dosbox.conf is unmanagible.

You would have 200 .conf files instead of 200 batch files.

I really don't understand what you are trying to do, but have you considered using a frontend like D-Fend Reloaded?

1. the current way of handling config files is here to stay, it's needed for current Windows. So don't wait for a future Dosbox version to revert this.
2. if you start Dosbox from its folder and it has a dosbox.conf in that, Dosbox will use it
3. don't use 0.72 anymore. Seriously... better use a built of current Dosbox source
4. using purple color on purple background is not making it easier to read but more annoying to read. Better don't color text at all...

>1. So don't wait for a future Dosbox version to revert this.
I am not looking for "revert". just an old option as well as the new option hopefully. an old option is perfectly logical ...that DOSBox looks for the conf file in its own directory too. But it is ok if developers dont see this, I will rewrite my batch files someday.

>2. if you start Dosbox from its folder and it has a dosbox.conf in that, Dosbox will use it
no, DOSbox v0.74 only looks for the dosbox.conf in C:\Documents and Setting area, it denies it from own directory. this was the problem i had to ask in the forum.

the one benefit i can think of putting the dosbox.conf at C:\Documents and Setting area is if you are testing many different versions of dosbox, that use the same shared conf.

1. Dosbox WILL look for the dosbox.conf (with this name) in its folder *unless* its folder is *not* the working folder. in that case Dosbox will look for a dosbox.conf in the working folder first and only then use the config in "Users and Documents\..."

2. it does. It really does. You just need to set the working folder to the Dosbox folder. And it needs to be named dosbox.conf, not dosbox-0.74.conf (and your shortcut shouldn't have "-userconf" in its command). Try it outside of Program Files, on an USB stick for example (to make sure you don't run into a files permission trap).

The reason that it no longer uses the program folder by the default is that on modern Windows (post XP), the C:/Program Files/ folders are off limits to write to for normal users. Which means that every edit if the config file needs to be done with admin rights. AND seperation of user files from program files is actually a good move.

edit: see screenshot

>it does. It really does
you were absolutely right about it. this is now embarrassing and if you do not mind, i like to delete this thread.

dosbox-074.conf works for at C:\Documents and Setting area
dosbox.conf was working where DOSbox.EXE was secretly.

i am sorry for wasting your time about this.