Sorry, I see I missed quite a bit. For some reason I am no longer getting notifications about new posts in this thread. Thank you all for kind words. Looks like Rob already sorted out most of the issues, but I will make a few remarks:
1. By this moment I am sure that if PI does not list StarNet as a new module in the search window, that means your CPU is not supported and the code will not work anyway.
2. If you installed module, but still getting checkpoint error, try restarting PI. If that still does not help, try opening Process Console and run 'pwd' command. Ideally, that should output PI's bin directory address, in my case its
C:/Program Files/PixInsight/bin
If it outputs something different, then try typing:
cd "C:/Program Files/PixInsight/bin"
Or other path depending on your PI's installation location. And don't forget double quotes here! That should solve the problem, I think. I will try to address this issue in the next version.
3. PI plugin for MacOS is on the way. I am a bit busy right now, but still working on it.
4. I do not recommend changing stride value anymore. Just live it at 128. It is much simpler to correct remaining artifacts in PS. The reason for that is that as you decrease the stride value, artifacts get less notable, yes, but on the other hand you start getting more of them since image is processed in smaller tiles.