Seems to be an issue on the GUI. The command line part works fine, I've tested it on Peter's project some time ago.
The tool works and is open source. If someone has time to track and fix the defect then it would be a good way to iron out any wrinkles. On my case I'm working in other tools right now.
Look, I don't want to seem grumpier than usual , but you are downright recommending a tool that another (highly experienced) member has reported as being buggy and you are saying that you aren't going to fix it, because you have better (or more important) things to do.
This is not about "wrinkles", the tool has been reported as NOT WORKING completely for it's MAIN scope.
If you cannot get the amount of foolishness involved in this, I am here exactly to highlight it.
It is logical to recommend tools that work (even with minor "wrinkles").
It is illogical (and foolish) to recommend tools that DO NOT WORK.
Or - alternatively - you are indirectly saying that a bug report by pscEx is NOT to be taken into consideration and it is void of any validity/truthfulness.
So, we have a command line/GUI app that doesn't work in GUI, what remains is just command line.
Maybe mentioning this on the release thread would lessen the amount of frustration of the people attempting to use it.