There’s also mechanisms on Winetricks itself to not run incompatible formulae on a 64-bit prefix, like the IE TLS 1.1/1.2 patch, so it shouldn’t be a problem. I know that the official solution would be await for a WineHQ PE Executable, but while it didn’t release, the Winetricks could detect if it’s macOS, shows a warning (like PlayOnMac does), create a 64-bit prefix anyway and run the scripts. That 'experimental mode' is what #2030 is about. There’s also a experimental wow64 mode on wine64 from WineHQ that allows some 32bit GUI applications to run, as I was able to run iexplore.exe (IE8 32-bit) through it (it didn’t load any page though, but loaded its GUI, while IE8 64-bit worked as expected). However, as I said, to my knowledge, a 64-bit only wine isn't supported upstream, so IMO, this is not a bug. The 64-bti binary works, which is great if you really only need 64-bit binaries, but that isn't true for all/most users. While WineHQ ships a 32-bit binary, the error message indicates that the OS can't run that binary. ![]() ![]() ![]() #2030 is using a 64-bit Wine binary, while official WineHQ packages have a 32-bitīinary (wine) and a 64-bit binary (wine64). This issue is slightly different than #2030. Note: I don't have a mac, so please correct me on the below if I'm wrong (really, correct me on anything if I'm wrong, but particularly mac/OSX particular things :) ).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |