Post by jjbPost by PaulPost by EdmundIs it possible to get a working wine in mint 21.3 if so HOW?
I think that you ask for too much. More than half of all the program worked with glitches and problems/work arounds in the original windows environment, and WINE is an amazing undertaking.
WINE has a lot of moving parts.
Of course it's not easy.
It would be easy if it had instructions.
Paul
Running Mint 21.3.
sudo apt install --install-recommends winehq-stable
Works for me with all Windows stuff I have (not much, though).
Well, that's part of the problem.
WINE is the "never-ending journey". There is no such
thing as a "I have done a complete and thorough test".
Because I can tell you haven't.
You can enter WINE. You can "have an adventure". You come
out the other side, either with broken WINE or working WINE.
Microsoft can create new gubbins, faster than you can detect
they've done that, and then you find a way of testing. Would
a Metro.App work ? Would a UWP work ? Would a ClickOnce work ?
It's the same sad situation I have with NTFS file systems.
Can anyone list all the files on an NTFS file system ?
No, they can't :-) Sorry. Try again.
I have this big bruise on my forehead, from trying
some of this stuff.
As an example, two utilities I have for listing the
contents of an NTFS volume, they differ by... oh... 100,000 files.
That is all. Not much when you think about it. Inspires confidence.
At one time, Microsoft had a couple files in the System32 folder,
which used an exotic UTF character set of some sort. A couple of
the characters in the filename string were "not representable"
and when pasted into Thunderbird (which is normally pretty good
about this stuff), you could not tell that a couple of characters
were missing from what you pasted. Now, the idiots did remove that
stuff a few months later, and the developer on acid is likely
locked in a broom closet.
*******
I've just come back from my adventure.
Summary:
1) Synaptic in good shape. Bravo. Selecting the "wine" metapackage
really does work. That's probably the first time I've seen that
in eight or ten years. Whoever did that, good work!
2) Winetricks has broken download refs in it. Microsoft is constantly
removing stuff from their server that should be left there.
Winetricks even resorted to archive.org references (which were also
missing), so you know some monkeys have been in a knife fight again.
To install .NET, I use 3.5.1SP1 (gives 2.0, 3.0, 3.5 versions).
Next, you should install .NET 4.0 , because the other dotNET offerings
are not really cumulative. When you go to install .NET 4.7.2 ,
the download ref is busted, so you instead just download
one of a similar name but different SHA256 and run
that using "wine" directly.
wine ./ndp472-kb4054530-x86-x64-allos-enu.exe
When it appears to be stuck, open a second terminal window,
and run "top". The action of running "top" seems to break
a deadlock somewhere, and the installer will then finish up.
I ran Aaron Stebners "netfx_setupverifier_new.zip" to check.
wine ./netfx_setupverifier.exe
and it passed as intended 2.0,3.0,3.5,4.0,4.7.2 . That would
cover a certain percentage of .NET applications, but not necessarily
all of them. .NET is up to 6 or higher now, and I didn't check
the Winetricks to see if it has caught up.
Since mscoree has JIT capability, the fact that the
mscoree scan of the file system does or does not complete,
is not supposed to matter. As an executable will cause
it to run "Just In Time" when you start the loader on the executable.
If you run "top", you can at least see the mscoree for dotnet
2.0,3.0,3.5 attempting to run.
This means I've tested about 5% of the attack surface.
I don't have enough games, to test that part of it.
Paul