That's correct, SACDExtractGUI itself is universal to Windows, Mac, or Linux. It will run the same on any of the 3 so long as you have the Java Runtime Environment installed, and the correct platform version of sacd_extract 3.9 (i.e. Windows, Mac, or Linux).This looks like a quantum leap forward!
I would like to try on both Mac & PC. Mindset notes indicate GUI runs on Mac/Win/Linux, presumably with different versions of the newest sacd_extract. Looking forward to ripping ISO/multi simultaneously.
So the new GUI itself is not itself platform specific, but the JRE is, and as well sacd_extract 3.9 is too.
To do this on a Windows machine you will first need to solve whatever problem is causing the sacd_extract 3.9 .exe file to get instantly zapped/deleted from your computer. I'm thinking for sure it is Windows Defender doing that, but it could also be some other security software. You can't use the new GUI in Windows until you get that issue resolved on your Windows machine.
As stated above in Post #176, I am not having that same issue with the respective security scans done by Vipre in Windows, and by Sophos on Mac, so I'm not sure why that's happening on your Windows machine except to say Windows Defender is notorious for exactly that behavior.
On a Mac, you need to compile sacd_extract 3.9 using Terminal. While not exactly for the faint of heart, it's also not super difficult either. The actual command line entry only takes a few minutes, then you sit back while the developer tool compiles a Unix executable, pretty fast depending on variables such as your download speed, CPU speed, and how much RAM you have. Don't multi-task with that machine while it is compiling, shut down all other programs and let the compile take full thread priority and then it goes by very quickly.
When invoking the build commands in Terminal you will be asked to install Apple's XDA Developer Tools package, you do that right there in Terminal simply by answering y to the y/n question when prompted.
If the above sounds crazy, then maybe it's not for you. Trust me it is not crazy, actually it's very straightforward and easy, so long as you carefully/methodically follow the instructions and pay very strict attention to spelling/spaces/capitalization as indicated. There can be no exceptions to that, enter the build commands correctly in Terminal and it just works with the above mentioned developer tool doing the actual compiling for you. Syntax is critical there.
The only real point of confusion for many people comes when Terminal asks you to enter your password, typing it in yields no visual indicator, not only do you not see your password, nor any series of **** characters representing your password, you don't even see the cursor move. This is normal behavior in Terminal, but it blows some people's minds. Don't sweat it, just carefully enter your password.
Are you up for that? If so, open a Terminal session on your Mac and slowly carefully enter the following (note: you very well might need to enter this by hand as copy/paste won't always work and that's an involved explanation best summed as "when a space is not a space" in certain circumstances depending on the various GUI, web/platforms involved). So don't be surprised if you can't just copy/paste the following commands, you might need to type them in by hand, however I have tested the commands as formatted directly below in copy/paste fashion (one line at a time) to the Terminal and it worked just fine for me:
xcode-select --install /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" brew install cmake git clone https://github.com/setmind/sacd-ripper.git cd sacd-ripper/tools/sacd_extract cmake . make
Please keep us posted/let us know how you do.