cncbasher: I decided not to use the old operating system and use the PathPilot restore disk for none machine owners instead as a guide. I will keep the link you provided in case I need it in the future.
I'm encouraged that it looks like this is going to be doable but its not a simple thing to do. I'm happy with the progress I have made to get the PathPilot gui working to "some" degree in a updated version of linuxcnc. Initially halshow did not show any of the PathPilot "signals" in its tree list but that appeared to get fixed by eliminating incompatibility issues with redis versions. Likely a conflict 32 bit version and my 64 bit version.
Issues that I had to be bypass for now and thus not worry about to much are related 4th axis homing, jog speeds, liststore, netbios and usb, with others likely lurking in the background. More code will likely need to be added to the build recipe of linuxcnc to fix these problems. So the use of the gui outside of PathPilot with all its functionality will require the build structure of linuxcnc to be modified before linuxcnc is compiled.
There are likely different ways to incorporate this gui into linuxcnc. The way I choose was to copy all required files into appropriate locations my linuxcnc-dev folder since this would likely be the way used if the PathPilot gui was ever distributed with linuxcnc. There are a few folders that are in the "home" folder for convenience. Right now these are folders, gcode, lathe_data, mil_data, tmc and updates. In the end some of these may not be needed or can be moved as desired.
To make the modifications required to a linuxcnc build when the PathPilot gui "is desired to be used" a script file will likely need to be generated to modify linuxcnc "configure" in the /linuxcnc/src folder and also move the gui files files to their desired locations automatically within the linuxcnc-dev folder. This will need a knowledgeable script writer volunteer.
