Matthew Noel

My workaround for this is so dumb. Please help. I made a custom EXE that just redirects to DOSBox-x and overwrote the built-in one. Yes, I know I could just put DOSBox-x in the built-in folder and rename the EXE, but I'm stubborn. Here's the code if anyone's interested: EDIT: Code cleanup.

I Have a custom DOSBox version set for all my MS-DOS games (DOSBos-X), but when I try to run a configuration application for a game it uses built-in DOSBox 0.74. Also the "Open DOSBox..." menu option is the same. It's important to run the config programs in the same DOSBox as the game itself, especially if it lets you test or auto-detect hardware.