search

Winetricks / winetricks

Winetricks is an easy way to work around problems in Wine
GNU Lesser General Public License v2.1
2.81k stars 407 forks source link

dotnet 472 doesn't work corrrectly #2138

Open RHimadiiev opened 1 year ago

RHimadiiev commented 1 year ago

Hello!

I am not sure if it's correct place to report, but my reports to Wineskin didn't help and I suspect something wrong with winetricks. Since MacOS 13.5.2 one app (AATranslator 2) stopped working correctly. It uses dotnet 472. Why am I thinking it's related to winetricks? Here is what I do with Wineskin:

  1. Create a wrapper with any engine. You can use WS11WineCX64Bit23.5.0 (D3DMetal-v1.0 wip)
  2. Winetricks — install dotnet472
  3. Try to change the wrapper's engine to another version. You'll get this while it tries to change it: image

So it can't start. And in the same time it cannot install the app that needs dotnet472. Installer gets aborted.

Any ideas?

austin987 commented 10 months ago

I'm not familiar with Wineskin..can you attach the terminal output. That may have a hint.

FYI if wineskin is using the new wow64 mode, that's likely the reason.

mirh commented 10 months ago

"This application could not be started" sounds like the good old as the hills problems with missing dotnet20 that started after the first 5.0 versions. IIRC it was fixed as of lately (though you might need a new prefix), but go figure out what hellish versions those wrappers ship.

Gcenx commented 2 months ago

"This application could not be started" sounds like the good old as the hills problems with missing dotnet20 that started after the first 5.0 versions.

The rundll32.exe prompt is indeed resolved by installing dotnet20.

IIRC it was fixed as of lately (though you might need a new prefix) but go figure out what hellish versions those wrappers ship.

The wine version OP used was wine-8.0 (crossover-sources-23.5.0) using upstreams new wow64 mode as that’s all that can be used on modern versions of macOS.

This still occurs in wine-9.0 using new wow64, not gotten around to testing newer versions just yet but I’d assume it still occurs and might be more a new wow64 bug if the reg key changes works on Linux using more classic wine(64).