http://bugs.winehq.org/show_bug.cgi?id=27297
Summary: Wine launcher redirect to DOSBox fails Product: Wine Version: 1.3.20 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: emulava@gmail.com
Hello.
I noticed that Wine now attempts to launch DOSBox for specific (.exe) executable files if they aren't supported internally.
The problem? Well the Dosbox window will flash on screen for a moment, but then just close out.
The following message is the one recieved if I use wine to launch the DOS exe through a cli. ie - 'wineconsole *.exe'.
MIXER:Got different values from SDL: freq 44100, blocksize 940 ALSA:Can't subscribe to MIDI port (65:0) nor (17:0) MIDI:Opened device:none
Simply launching the exact same executable though DOSBox yields no issues, but it necessitates launching through the cli instead of double-clicking.
http://bugs.winehq.org/show_bug.cgi?id=27297
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |integration
--- Comment #1 from Austin English austinenglish@gmail.com 2011-05-27 13:04:56 CDT --- I don't suppose this exe is publicly available? What happens if you use 'wine foo.exe' or 'wine start foo.exe' from a terminal?
http://bugs.winehq.org/show_bug.cgi?id=27297
--- Comment #2 from Andrew Nguyen arethusa26@gmail.com 2011-05-27 13:12:16 CDT --- I suspect it's bug 26423.
http://bugs.winehq.org/show_bug.cgi?id=27297
--- Comment #3 from emulava@gmail.com 2011-05-27 17:38:26 CDT --- Sure.
Here's an example DOS executable: ftp://ftp.idsoftware.com/idstuff/doom/doom19s.zip
http://bugs.winehq.org/show_bug.cgi?id=27297
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #4 from André H. nerv@dawncrow.de 2011-05-28 10:16:58 CDT --- (In reply to comment #2)
I suspect it's bug 26423.
or Bug 25887
Did you placed your App into drive_c of the wine directory or did you tried to start it from some other linux path?
http://bugs.winehq.org/show_bug.cgi?id=27297
emulava@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.20 |1.3.21
--- Comment #5 from emulava@gmail.com 2011-05-28 16:44:54 CDT --- Yes. I've attempted it with the directory placed in the wine path, and from an entirely different partition with the following path.
/media/Data2/DOOM/
Obviously the executable is named DOOM.EXE, so I fail to see how the path/file names wouldn't conform to the 8.3 standard.
PS - I modified the version number to reflect wine '1.3.21', where the issue is still present.
http://bugs.winehq.org/show_bug.cgi?id=27297
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |ftp://ftp.idsoftware.com/id | |stuff/doom/doom19s.zip
http://bugs.winehq.org/show_bug.cgi?id=27297
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Version|1.3.21 |1.3.20 Resolution| |DUPLICATE
--- Comment #6 from André H. nerv@dawncrow.de 2011-05-29 06:26:28 CDT --- please leave the version on the first version you noticed this bug. This is a duplicate, move the app into your drive_c folder and try again.
*** This bug has been marked as a duplicate of bug 25887 ***
http://bugs.winehq.org/show_bug.cgi?id=27297
--- Comment #7 from emulava@gmail.com 2011-05-29 15:08:45 CDT --- Very well, and sorry. This is my first time with bug reporting.
http://bugs.winehq.org/show_bug.cgi?id=27297
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from André H. nerv@dawncrow.de 2011-05-30 11:49:40 CDT --- (In reply to comment #7)
Very well, and sorry. This is my first time with bug reporting.
no problem, for that reason i told you for future bug reports. you're welcome to report more :) But also try searching through bugzilla for the name of the app or the error message to see if there's already a bug, even if i have to admit that it wasn't that easy for this one.