https://bugs.winehq.org/show_bug.cgi?id=47355
Bug ID: 47355 Summary: Making running DosBox reliable Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: es20490446e@gmail.com Distribution: ---
Running Dosbox through Wine usually leads to Dosbox crashing, even when using Dosbox SVN.
Ideally Wine shouldn't be the one handling Dosbox, but that be fixed at the Mime level.
That is here: https://gitlab.freedesktop.org/xdg/shared-mime-info/issues/109
Instructions for submitting Mimes at: https://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec/#index...
https://bugs.winehq.org/show_bug.cgi?id=47355
Alberto Salvia Novella es20490446e@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |es20490446e@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47355
Lantizia s.maddox@lantizia.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |s.maddox@lantizia.me.uk
--- Comment #1 from Lantizia s.maddox@lantizia.me.uk --- Perhaps I'm missing something. But are you hoping if Wine encounters a exe/com/pif/bat/etc.. file - that it'll ask the system each and every time what should be running it (even if it is within the bottle) so that if mime-info reports it's a pif or 16-bit com/exe DOS executable - the system will then start up DOSBox itself (or whatever is associated with it)?
Even if the above made sense, how would DOSBox know what to map drive letters to so it can access the bottle or related drives (like CD's) properly?
You've linked my bug: https://bugs.winehq.org/show_bug.cgi?id=46125
But I don't see this solves the issue there... as a setup.exe from a CD is calling another exe that calls a pif that calls a batch file - so DOSBox at a minimum needs to know where drive C: is and where drive D: is for this to actually work.
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #2 from Alberto Salvia Novella es20490446e@gmail.com --- I mean that instead of being Wine who decides if to run DosBox or not, that to be done by the file manager itself, based on the shared mime info.
For that the shared mime info shall be updated accordingly, and then the code handling DosBox removed. Because the file manager will no longer allow opening Dos exes with Wine.
Then there would be no redirection.
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #3 from Alberto Salvia Novella es20490446e@gmail.com --- Dos exes will always open directly on DosBox.
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #4 from Lantizia s.maddox@lantizia.me.uk --- (In reply to Alberto Salvia Novella from comment #2)
I mean that instead of being Wine who decides if to run DosBox or not, that to be done by the file manager itself, based on the shared mime info.
For that the shared mime info shall be updated accordingly, and then the code handling DosBox removed. Because the file manager will no longer allow opening Dos exes with Wine.
Then there would be no redirection.
Right but if this is your point then.... a) Your bug is not with wine at all as it isn't Wine which is deciding what should load when your system/file-manager opens a file b) You are not considering an environment where Wine was initially called (e.g. a 32-bit Windows EXE) and it then goes on to call a PIF or a 16-bit DOS EXE later on. In this situation then yeah Wine needs to go on dealing with DOSBox directly for the reasons I've already given about drive mapping.
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #5 from Alberto Salvia Novella es20490446e@gmail.com --- A) Wine can contribute the Mime file.
B) Shall only do "dosbox $file".
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #6 from Lantizia s.maddox@lantizia.me.uk --- (In reply to Alberto Salvia Novella from comment #5)
A) Wine can contribute the Mime file.
B) Shall only do "dosbox $file".
Neither of these are answers to what I have raised.
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #7 from Alberto Salvia Novella es20490446e@gmail.com --- At what step does your bug happen, and what's the root cause?
https://bugs.winehq.org/show_bug.cgi?id=47355
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG CC| |nerv@dawncrow.de Status|UNCONFIRMED |RESOLVED
--- Comment #8 from André H. nerv@dawncrow.de --- resolving, cause the mime file thing is out of scope for Wine and you ignore the reason for the dosbox integration. If dosbox is crashing when started from Wine, then open a new bug about that.
https://bugs.winehq.org/show_bug.cgi?id=47355
--- Comment #9 from Alberto Salvia Novella es20490446e@gmail.com --- DosBox SVN crashes only when launched through Wine: https://bugs.winehq.org/show_bug.cgi?id=47359
-
wine-bugs＠winehq.org