https://bugs.winehq.org/show_bug.cgi?id=47359
Bug ID: 47359 Summary: DosBox SVN crashes only when launched through Wine 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: ---
https://bugs.winehq.org/show_bug.cgi?id=47359
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #1 from André H. nerv@dawncrow.de --- Doesn't look like a crash. Maybe it runs through some commands and exits cleanly for some reason
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #2 from Alberto Salvia Novella es20490446e@gmail.com --- What DosBox window says: https://i.imgur.com/73IF6q3.png
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #3 from Alberto Salvia Novella es20490446e@gmail.com --- Compared with running raw DosBox: blob:https://imgur.com/b4a888c1-d23c-42f3-9590-5eba43e275cf
We can see that Wine tries to do many crazy things, like mounting plenty or drives or running in secure mode.
Also the code handling DosBox would benefit from being more modular, from having the functions as short as possible.
Plus most of the auto-configuration is better implemented in DosBox itself.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #4 from Alberto Salvia Novella es20490446e@gmail.com --- Raw DosBox: https://i.imgur.com/CMBjvr1.png
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.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #6 from Alberto Salvia Novella es20490446e@gmail.com --- The installed DosBox version is: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dosbox-svn
If it fails under the simplest scenario, it will fail in more complex ones. Actually it fails with nearly all Dos exes I have tested.
The affected code is: https://source.winehq.org/git/wine.git/blob/HEAD:/programs/winevdm/winevdm.c...
It needs to be slit into the simplest functions, so what the bugs are is obvious. Also it needs to make those special configurations conditional, so they are only used when needed.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #7 from Lantizia s.maddox@lantizia.me.uk --- Translated you just pointed at some code and said... - I don't like it. - There must be a bug there - I don't know where - Make it simpler so we can find the thing I haven't proven yet
But if I ignore how this is meant to be a bug report and treat it as a feature request...
Your request to have 'special configurations conditional' (presumably making the extra commands Wine puts into the DOSBox config optional) undermines the whole point of Wine working with DOSBox altogether.
You should also know DOSBox has received patches to ease Wine using it (such as relocating the default drive Z: that DOSBox uses), you can read about them here... (as well as the real purpose DOSBox serves when Wine is calling it)... https://wiki.winehq.org/DOSBox
Stop using Wine to launch DOS games - just call DOSBox directly!
If you're just after a way of double clicking a DOS EXE in your file manager and having it magically set up DOSBox for you and run it then you could basically do that with something as basic as this (you'll need to turn this into a script, make a launcher & a mime file)...
dosbox -conf $(c=$(mktemp);echo -e "[autoexec]\nmount c $(pwd)\nc:\n$@">>$c;echo $c)
But that isn't really in the scope of Wine, so take this and run with it - it's not really appropriate to talk about that here.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #8 from Alberto Salvia Novella es20490446e@gmail.com --- Lantizia: I can write code in nine languages, I have university training on computer engineering, I have mentored in Google events, I have managed 90% of Ubuntu bugs for 3 years, I'm trained in quality assurance in general, and I have formal training in how to write clean code.
You say I don't know how to read that code, and that it's just personal preference that I don't like how it is written.
Lets we agree in something instead, you are simply unwilling to help. It doesn't matter what we discuss here.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #9 from Alberto Salvia Novella es20490446e@gmail.com --- You are lazy.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #10 from Lantizia s.maddox@lantizia.me.uk --- None of that is material.
You simply have not established the existence of a Wine bug.
It does not matter who you are or what you can do.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #11 from Alberto Salvia Novella es20490446e@gmail.com --- The question simply comes down if you want it fixed, or you prefer to watch movies instead.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #12 from Alberto Salvia Novella es20490446e@gmail.com --- If you prefer the movies, that's legit. But save my time.
https://bugs.winehq.org/show_bug.cgi?id=47359
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #13 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Did you install the DOS application with Wine?
Many DOS application save the install path in a config file. If you installed the DOS application in DOSBox, it was probably installed to a directory mapped as a C: drive. Wine does mount the root path as Z: drive and calls the DOS executable with a Z: path. The DOS application can't find its files if it looks for them on the C: drive as Wine didn't setup any C: drive.
I personally think that the issue is somehow valid: I think it should be supported to use Wine for both installing and running the DOS application. In that case, Wine only serves as a front-end to the linux DOSBox you have installed. Ideally, Wine should setup the wineprefix as C: and mount that as C: drive in dosbox and let the DOS application install. Then when running the DOS executable through wine, the wineprefix should be again mounted as C:. Obviously, You should not mix installing with DOSBox and running with Wine.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #14 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Well it might not be so obvious. Installing the DOS application with DOSBox and running it with Wine is unsupported because Wine doesn't know what the DOSBox configuration was when the DOS application was installed and can't reproduce it.
Installing from Wine and running from Wine should be consistent and use the same wine-generated DOSBox configuration.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #15 from Alberto Salvia Novella es20490446e@gmail.com --- This game has a config.ini, where the installation path is set to C. But if I change it to Z it still doesn't work.
Also tried with other three games: https://www.dosgames.com/game/blood/ https://www.dosgames.com/game/descent-2/ https://www.dosgames.com/game/heretic/
Only the first launches. The other two opens a window that says "file not found". All of those work well using raw DosBox.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #16 from Alberto Salvia Novella es20490446e@gmail.com --- I guess the problem comes when telling is C: should be the Wine C:, or the launched program working directory.
Most likely the solution is:
if the program has been launched by another Windows program: C=wineC D=currentDir otherwise raw dosbox
D should always have the current dir, so any exe that needs a CD will work too.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #17 from Alexandre Julliard julliard@winehq.org --- Thanks for posting the downloads. Next time please do that first, instead of trying to guess the reason yourself, that will save some time.
These games use a DOS extender that causes the binary to not be identified correctly. Once this is fixed they should run fine from Wine.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #18 from Alexandre Julliard julliard@winehq.org --- The first game you mentioned is indeed a bit picky about its configuration, but if you install it correctly in a Wine drive it works fine. I don't see a bug here.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #19 from Alberto Salvia Novella es20490446e@gmail.com --- I posted these links now because it's now when I have tested those games, not when opening this report.
The game I tested when opening this report is: https://archive.org/download/RealmsOfTheHaunting/RealmsOfTheHaunting_archive...
But mostly any game that you will test will fail.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #20 from Alexandre Julliard julliard@winehq.org --- (In reply to Alberto Salvia Novella from comment #19)
I posted these links now because it's now when I have tested those games, not when opening this report.
The game I tested when opening this report is: https://archive.org/download/RealmsOfTheHaunting/RealmsOfTheHaunting_archive. torrent
But mostly any game that you will test will fail.
I see no evidence of that, and it's not useful to have a generic bug for multiple problems.
If there are issues with other games, please file new bugs for them, adding download links. And make sure you install them correctly under Wine first.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #21 from Alberto Salvia Novella es20490446e@gmail.com --- I think that in group is better to discuss the desired outcomes only, and trust the implementation details to the person taking the job.
If that person has a doubt, they can always ask. Meanwhile the rest most likely irrelevant.
So we simply shall agree that if we want Wine to be able to open Dos exes as reliably as DosBox by itself does, or only do for applications executed through a Windows application.
Something to keep in mind is that Dos exes could be started directly on DosBox if this bug is fixed:
https://gitlab.freedesktop.org/xdg/shared-mime-info/issues/109
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #22 from Alberto Salvia Novella es20490446e@gmail.com --- My report was for this latest game.
https://bugs.winehq.org/show_bug.cgi?id=47359
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
--- Comment #23 from Alexandre Julliard julliard@winehq.org --- (In reply to Alberto Salvia Novella from comment #21)
I think that in group is better to discuss the desired outcomes only, and trust the implementation details to the person taking the job.
If that person has a doubt, they can always ask. Meanwhile the rest most likely irrelevant.
So we simply shall agree that if we want Wine to be able to open Dos exes as reliably as DosBox by itself does, or only do for applications executed through a Windows application.
Wine opens DOS exes using the Wine drive configuration, so it's not 100% identical to DOSBox. That's a feature.
If you want raw DOSBox behavior, use DOSBox.
https://bugs.winehq.org/show_bug.cgi?id=47359
--- Comment #24 from Alberto Salvia Novella es20490446e@gmail.com --- Well, probably that's the best answer. Although I feel we have wasted plenty of time in this report.
https://bugs.winehq.org/show_bug.cgi?id=47359
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #25 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla