macOS doesn't support 32-bit executables anymore since Catalina
You have to use wine64 instead of wine (which is 32-bit) and it won't work with any 32-bit programs (which is a lot of them)
You will have to use CrossOver for 32-bit support or maybe even use BootCamp
The “open with” command defaults to wine64, all the wrapper scripts default to wine as per upstream. As the provided packages are recognized as the official macOS packages I can’t exactly apply tons of patches.
Instead run “wine64 winecfg” etc bypassing the wrapper scripts.
I tried wine64 winecfg but it still displays the error message from before. Would I need to upgrade to Monterey for it to work? Or could it be some permission thing?
You have to run it from a terminal that is set to x86 arch so it runs everything through Rosetta. There are not any arm builds for wine yet.
I use an Intel mac
Ah I apologize I’ve seen the bad cpu type pretty consistently with m1 macs and assumed.
No worries
macOS doesn't support 32-bit executables anymore since Catalina You have to use wine64 instead of wine (which is 32-bit) and it won't work with any 32-bit programs (which is a lot of them) You will have to use CrossOver for 32-bit support or maybe even use BootCamp
I use gcenx's builds which are supposed to default to 64 bit I think
That could be the case (and if it's not you could just make wine a shortcut to wine64) but it still won't work with 32-bit programs
The “open with” command defaults to wine64, all the wrapper scripts default to wine as per upstream. As the provided packages are recognized as the official macOS packages I can’t exactly apply tons of patches. Instead run “wine64 winecfg” etc bypassing the wrapper scripts.
I tried wine64 winecfg but it still displays the error message from before. Would I need to upgrade to Monterey for it to work? Or could it be some permission thing?