possible execution fix

[Jayian1890]

Relatively new issue where games will not execute when using normal methods. This change resolves that issue.

[mattgallagher]

I feel like the problem is that the current directory needs to be set. Perhaps /unix is doing this automatically but is it really the most compatible option?

Edit: don't get me wrong, this would fix my problems trying to run programs, also.

[Jayian1890]

That would be my guess. It used to work flawlessly. It stopped working some time back after a merge(frankly a useless merge) that changed the directory paths into something more windows-like, which is why I switched to crossover. but most of my titles work better with whiskey, so I just use my own build with the change that fixes it, simply because I honestly don't expect it to get fixed.

[IsaacMarovitz]

Adding the Unix flag indicates that you are supplying Wine with a Unix style path, not a Windows style path. If the Windows path is causing problems, this is an issue with how the path is generated, and is the real root of the problem. The current directory shouldn't matter, as the Windows path will be found relative to the bottle supplied in the environment variable. I switched to Windows paths for programs installed within bottles in order to make logs clearer and remove a bunch of unneeded visual noise within the program path.

[Jayian1890]

Adding the Unix flag indicates that you are supplying Wine with a Unix style path, not a Windows style path. If the Windows path is causing problems, this is an issue with how the path is generated, and is the real root of the problem. The current directory shouldn't matter, as the Windows path will be found relative to the bottle supplied in the environment variable. I switched to Windows paths for programs installed within bottles in order to make logs clearer and remove a bunch of unneeded visual noise within the program path.

If that flag insinuates that the path being supplied is unix style, that begs the question, why does it work? Shouldn't it still not work? Obviously the path isn't unix if it's formatted for windows. Either something isn't working as intended, or I'm vastly misunderstanding what a unix style path is.

Either way, seems like being able to modify shortcuts would be another reasonable resolution. End users can't control how the paths are generated, only the program and installers do that(If I'm understanding it correctly).