I think I found a serious bug in the Windows version of Dosbox, using Windows 10 and tested with 0.74 stable and latest svn release.

When I try to load a custom config using the command-line option -conf, the config is not loaded and only the standard default config is used.

Reproduce:
- create custom .conf file
- start cmd.exe
- cd into dosbox dir
- execute the command
dosbox -conf "name of custom conf file"

The config file is not loaded. It does not seem to matter what the name, content or location of the custom config file is. It is as if dosbox is just ignoring the -conf option.

I also tried using a shortcut (that's how it started) and launching dosbox.exe -conf "my config file" via a shortcut, and that didn't work either.

Dragging a .bat file onto dosbox works. All other command line options work. The -conf option works as expected under OSX Yosemite. It seems to only be a problem under Windows 10.