There is also Mach4GUIR.exe. This is the remote GUI that is meant for controlling a Mach instance remotely. But in this instance, you would just run it on the same machine and point it to 127.0.0.1 (local host IP address).
First, design a screen that you want to use on the other monitor. In this example, I'll name this screen "myAlternateScreen". Do this with your current profile (you will switch back to your current screen later). The screen that is to run on the remote GUI cannot have a tool path and you can't load G code files from it. I think those are the only two restrictions at the moment. Once you have the remote screen designed (and Mach4GUI.exe running with your current scree and profile), you can launch the Mach4GUIR.exe program like this:
Mach4GUIR -r 127.0.0.1 -s myAlternateScreen
As I said, Mach has to be running already before you launch the remote screen. This could be automated in the screen load script of the primary MachGUI.exe.
os.execut("Mach4GUIR -r 127.0.0.1 -s myAlternateScreen")
To terminate the remote GUI along with the primary GUI, you will have to do some register based communications between the GUI.
On the remote GUI (pseudocode) :
if (some register equals 1) then
scr.Exit(true)
end
Steve