Hello everyone. I'm running Parallels 20 on an M4 Pro, with MacOS 15.2. My virtual machine is Windows 11 (for ARM architecture), updated to 24H2. I'm trying to find a way to launch a Mac executable by command line, while on Windows. I'm pretty sure that on my old computer (with a similar setup, but somewhat older versions of everything) I had a script file that was associated to the Terminal app, which in turn launched the executable with some options I had set in the script code; I could just launch the script from the virtual machine, and the executable would start on the "Mac side". Sadly that computer is lost and somehow I can't replicate that behavior - I honestly don't remember how I did set it all up, but if I did it all on my own last time and I can't now, there must be something different going on. Could you kindly guide me through the process that would get me there? Or suggest some other (similarly convenient) options if new versions of stuff made my solution not feasible anymore? Thank you a lot.
I have mostly done it, even if it works differently than last time, and I would still use some help in making it more similar to how it used to be - or in clearing the fact that it's indeed impossible. I used a .terminal file this time around - I'm sure I used something different, probably .sh, but it seems like it's become impossible to make Windows accept that such extension should be executed with Terminal. Anyway, this is a little change that isn't important. The real block was that I wanted to keep both the script and the thing I'm trying to launch in a folder on my Windows drive. While the launching script ultimately worked when executed directly from Terminal, executing it from Windows' Explorer triggered an error with the MacOS saying that I didn't have permission to execute that file. I strongly suspect that it's because I'm not using the user folders this time (I really don't like how version 20 changed how file deletion is handled when that option is active), and the files are somewhere under Desktop, so logically on Windows drive. This was solved by moving everything under my MacOS' Desktop folder instead, but I don't like it very much; so, as I said above, I'm still looking for advice. Thank you.