While commands like
Code: Select all
wine64 notepad
wine64 explorer
Code: Select all
% wine64 7z1900-x64.exe
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.
Code: Select all
wine64 notepad
wine64 explorer
Code: Select all
% wine64 7z1900-x64.exe
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.
Code: Select all
wine64 start /unix 7z1900-x64.exe
It’s very uncommon to require start let alone start / unix. Also this won’t help if the software is bundled within a 32Bit installer, if the installer is actually 64Bit it’s more lightly a permissions issue assuming they have 7z1900-x64.exe in ~/Downloads (enhanced permissions for apps now require permissions to access the location)JoseskVolpe wrote: ↑Wed Oct 27, 2021 3:22 pm Use "start /unix" arguments in your command
This will start the application using it's Unix location like in Windows Explorer. Some applications doesn't work without it.Code: Select all
wine64 start /unix 7z1900-x64.exe
However, some 64-Bits Windows applications makes use of 32-Bits libraries. You'll need 32-Bits Wine components to be able to run it if that's the case. I'm not sure if you can do it on MacOS Monterey since 32-Bits support were discontinued on MacOS Catalina.