https://bugs.winehq.org/show_bug.cgi?id=51705
Bug ID: 51705 Summary: 16 bit apps don't run on versions > 6.5 Product: Wine-staging Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mmikeinsantarosa@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Beginning with wine-staging 6.6 my 16 bit applications will no longer run. cardfile.exe ran on wine-staging up to version-6.5. from 6.6 on it will no longer run.
I've posted in the winehq forum about this @ https://forum.winehq.org/viewtopic.php?f=8&t=35349 and have had > 700 views but not one response.
This is what I see when executing cardfile.exe from a terminal
|0c8:err:plugplay:try_add_device Building report descriptor failed, removing device 00c8:err:plugplay:try_add_device Building report descriptor failed, removing device 014c:err:module:import_dll Loading library krnl386.exe16 (which is needed by L"C:\windows\system32\winevdm.exe") failed (error c0000131). 014c:err:module:LdrInitializeThunk Importing dlls for L"C:\windows\system32\winevdm.exe" failed, status c0000135|
https://bugs.winehq.org/show_bug.cgi?id=51705
Mike Purtell mmikeinsantarosa@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win16 Distribution|--- |Debian
--- Comment #1 from Mike Purtell mmikeinsantarosa@gmail.com --- this problem exists for wine-staging(>6.5) on both 32 & 64 systems.
https://bugs.winehq.org/show_bug.cgi?id=51705
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Does it work with vanilla wine? Is that wine built with or without mingw? Is there a link to the program in question? It seems to work for other programs.
https://bugs.winehq.org/show_bug.cgi?id=51705
--- Comment #3 from Mike Purtell mmikeinsantarosa@gmail.com --- cardfile.exe ran fine up to and including wine-staging-6.5 We build it with the same dependencies as the wine-staging in winehq @ https://dl.winehq.org/wine-builds/debian/dists/buster/main/source/
As far as mingw goes, it's not in the winehq Build-depends list so it is also not in our build. I am on the packaging team for a linux distribution called MX Linux.
I created a folder called cardfile that has the Cardfile.exe, Cardfile.hlp and the bash script (runCard.sh) we've been using to run it on linux.
Here's a link from my google drive to these files. https://drive.google.com/file/d/1YmnFdD1cdlRUIwR7HDoIowFVeNSGwBXx/view?usp=s...
Unzip it, move the .sh t somewhere easy to get to. Then copy the cardfile folder to the .wine folder in the .wine/drive_c/ folder.
I change directory to the location where the script exists and run it with ./runCard.sh
And like I said, it's worked just fine until wine-staging-6.6 was released.
https://bugs.winehq.org/show_bug.cgi?id=51705
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine Component|-unknown |-unknown Status|UNCONFIRMED |RESOLVED Keywords| |regression Resolution|--- |DUPLICATE
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- Alright, so this also affects vanilla wine and only when no wingw is used. Marking dupe of bug 51564.
*** This bug has been marked as a duplicate of bug 51564 ***
https://bugs.winehq.org/show_bug.cgi?id=51705
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing duplicate.
https://bugs.winehq.org/show_bug.cgi?id=51705
--- Comment #6 from Mike Purtell mmikeinsantarosa@gmail.com --- Has any progress been made on this bug? This bug has been identified as a duplicate of bug 51564 https://bugs.winehq.org/show_bug.cgi?id=51564 and I don't see it as being resolved either.