-
-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vcrun2005 and vcrun2008 seems to fail to install on a win 32 prefix via winetricks #2205
Comments
Good evening, I read on the internet that vc_redist.x86.exe (vcrun family) requires wine32 to run. I tried to install wine, wine32 and wine64 which were not installed on my computer. Wine and Wine64 are in conflict. So I installed wine and wine32. Well, vcrun2019 installed without any problem. A solution for you, I think ... |
i have wine32 or 32 bit wine installed and i can run 32 bit apps on 32 bit prefix this is most likely a winetricks issue as i can install vcredist 2010 and above and 2005 and 2008 can be installed manually but fails with cli install with -q |
I'm having similar issues on Fedora 40. I have three ideas that I'll start trying tonight when I am finished with the work day: Idea 1: The script comments remark that there is a difference between Idea 2: Based on #2167 it's possible the argument order of cabextract is relevant. Running Idea 3: Somehow the Temp directory is getting screwed up. I don't think it's this, but it's nice to be thorough. (There's a line about "temp" vs "Temp" in the script, and this failure seems to occur right after creating a temp folder.) That line Other possibilities:
(Of course, these same thoughts apply to vcrun2008, and I am so focused on 2005 because—selfishly, I admit—it is the package that affects me.) Notes:
Rabbit hole:
Is it possible this is not a winetricks issue but rather a regression in wine or even wine-mono? (If testing on an old version of wine or winetricks works and someone can drum up reproduction steps, I would do the bisect footwork.) Alternatively, do these packages (2005 and 2008) install correctly inside a Docker container—ideally one hosted remotely, e.g. in a GitHub pipeline? If so, what is the best way to find the differences between the Docker and native installation? Now the same questions, but for lutris or playonlinux or proton or bottles or any of the other emulator environment managers… |
Also, a different issue from a few years ago had the same exit code (1603) and was evidently resolved by replacing mono with .NET 4.0. I'll give that a shot as well as random probings based on my previous comment—ideally tonight. |
this may be a fedora issue(not sure) as i didnt encounter it when i was using kubuntu mantic and endeavor os(arch) but that was with an older winetricks too cant test since i have no disk space to install/emulate another distro via vm or baremetal i switched to nobara as it has better gstreamer packages than arch and kubuntu from my experience tried both on wayland and x11 no difference still broken as of today winetricks --version tested it on build from this repo the tkg build staging 9.6 |
It seems I get an error about mfc80.dll while using "win7" but not "winxp". I'll investigate further but here are logs: (log) winxp vcrun2005
(log) win7 vcrun2005
|
im on nobara fedora 39 and i have libxml2 so i have no idea what the issue is
The text was updated successfully, but these errors were encountered: