On Wednesday, 17 January 2024 13:54:02 CST Hans Leidekker wrote:
On Wed, 2024-01-17 at 13:05 -0600, Elizabeth Figura wrote:
On Wednesday, 17 January 2024 08:57:14 CST Hans Leidekker wrote:
On Wed, 2024-01-17 at 16:17 +0200, Gabriel Ivăncescu wrote:
On 17/01/2024 01:31, Francois Gouget wrote:
On Tue, 16 Jan 2024, Hans Leidekker wrote:
On Tue, 2024-01-16 at 18:24 +0100, Francois Gouget wrote: > > - Smart cards are supported in the Winscard dll, using the Unix > > PSCSlite library. > > It should probably be noted that this is not supported for 32-bit > Windows applications despite Wine providing a 32-bit winscard.dll.
It is supported for 32-bit applications but currently only in the new Wow64 setup.
And since no one will use that mode the release notes should note that this is not supported in pure 32-bit Wine and for 32-bit applications running in the default old WoW64 mode that every Linux distribution will ship.
Arch is already offering new-style wow64 packages and macOS users have no choice.
So Arch is shipping Wine packages with crippled 3D support?
I guess they do. They don't replace the old-style wow64 packages however. What are our options for fixing this?
I looked just now, and Arch's wine package [1] still uses old-style wow64 (look in "Source Files", navigate to PKGBUILD; there's no --enable-arch usage there.) There's no official package that uses new wow64. There is a wine-wow64 AUR package [2] that uses new wow64, but the AUR is basically for unvetted community packages, and Arch doesn't even provide binaries for those.
[1] https://archlinux.org/packages/multilib/x86_64/wine/ [2] https://aur.archlinux.org/packages/wine-wow64
I was curious about 16-bit support and found that Windows has dropped it recently. One option for Windows users to keep running these apps is a port of winevdm(!) to 64-bit Windows:
https://github.com/otya128/winevdm
I gave it a try on a new wow64 build and to my surprise it worked. I only had to add native overrides for the 16-bit system dlls.
Well, to be pedantic they *completely* dropped support for 16-bit recently (Windows 11, I think?), but it was never supported on 64-bit machines, which is the impetus for winevdm.
winevdm works by emulating segmented code. I don't know how that emulation is done or how accurate or performant it is. I would be wary of just depending on it until that's been tested. And in any case Wine doesn't need to drop 16-bit support yet.
Not being use-able in pure 32-bit Wine sounds pretty bad, I hope it doesn't become a trend.
I don't believee there are many users stuck on pure 32-bit Wine that also need winscard support. Note that it was never usable when pure 32-bit Wine was still the norm. Adding support isn't free unfortunately and I don't think that passing the tests is sufficient reason to pay that cost. I'd rather wait and see if there's real interest.
Isn't it unusable in old wow64 as well?
It is.
Then anyone on old wow64 support is going to have to manually compile Wine just to get winscard support in a 32-bit application.
I do agree that we should wait for real interest before going back and fixing this case, but at the same time I too fear that this sets a dangerous precedent. I think it is a serious mistake to deprecate old wow64 until it offers at *least* the same support, and I also think we should have communicated its limitations clearly in the release notes, regardless of how obscure are the affected areas of Wine.
--Zeb