https://bugs.winehq.org/show_bug.cgi?id=47359
Lantizia s.maddox@lantizia.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |s.maddox@lantizia.me.uk
--- Comment #5 from Lantizia s.maddox@lantizia.me.uk --- If you want it to run with DOSBox, why are you intentionally running it with 'wine MYEXE.exe'?
And even if you prefer to be able to double-click MYEXE.exe and let a mime file determine you'd need DOSBox SVN to run it... Then write one!
It may be that a non-SVN version of DOSBox packaged for your distribution may even come with a mime file that you could use as a template, but if you've compiled DOSBox yourself it may not have that integration in mind.
Running applications that are solely DOS through Wine is crazy.
The only reason Wine has DOSBox integration is so bottles with a combination of both DOS/Windows executables can call each other. Early Win9x-era (and earlier) applications would often have 16/32-bit Windows EXEs that would use 16-bit DOS EXEs or batch/pif files etc... stuff that would often pop up in a 'Command Prompt' window momentarily (i.e. command.com from DOS not cmd.exe from NT).
Your DOS application likely just doesn't like being ran from drive Z or something about the path, The securemode option isn't anything that would affect it. But if you want it to be C: then it's going to need to be in a bottle.