So from games that I've bought off of Steam that run through DOSBox, that also have modern engine ports to go with it (Doom, etc.), I've learned to just take the new engine EXE, rename it DOSBox and drop it in as a replacement for dosbox.

At least for Dark Forces, and the DarkXL engine, that doesn't seem to work for GOG Galaxy like it does for Steam. I've tried running Galaxy as admin, I've tried running DarkXL in compatibility mode (Win XP SP3, it's needed for DarkXL to work actually), I've tried running DarkXL as admin. I've tried running both Galaxy AND DarkXL as admin. No luck. I get a "execute library in a weird way" error messsage.

As long as it's in Win XP compat mode, I can double click on the renamed EXE, and it runs fine.

I then decided to try changing where the shortcuts pointed to, and took out the unnecessary config commands. I changed both the Launch Settings and the Launch Star Wars - Dark Forces shortcuts to point at DarkXL. When launched from those shortcuts, again, it runs fine.

In the goggame-1421404433.info file I even tried changing the filepaths from the dosbox folder directly to DarkXL.

I can swap out the DOSbox EXE for the DarkXL EXE, and as long as I don't use Galaxy to launch it, it works fine (even from the launch shortcuts). I can change the launch shortcuts to point to DarkXL on its own (not swapped for DOSBox) and it works fine. I can change every config file to point at DarkXL instead of DOSBox.

So how do I get this to work?

If it works without Galaxy, don't use Galaxy.

Hmm... I'm using the launcher because I like it.

But you're telling me to not use the launcher, despite the fact that I like it.

I like the easy, direct interface made specifically for browsing my GOG library and launching the games.

So, you know, I'm gonna keep using it.

How DARE I put effort in trying to figure out how to make it work the way I want it to.

Oh, wait, no. No. How dare YOU come in here and give me a useless answer like that.

Try messing around with .info file harder : D

I don't know for certain, but maybe galaxy temp edits the .exe file to force window mode or somesuch. I know that you can force certain variables if you add commands to properties line. Not sure if that somehow messes with the destination path.