There is no printed reference book with what you're looking for. I have used hlp2rtf in the past to get a readable/editable (.RTF) file from the help system. Usually comes in at about 2200 pages though since each topic becomes a page. Pictures come through though. You can remove the manual page breaks with MS Word and then reformat for the size page you're printing to. Then print it yourself. Takes ALOT of work, but if you must have a hard copy, it'll do.

Had to confirm spelling in the .pdf's

Toolplanes are indexing because your work offset is -1. Change them all to 0 and you'll just get G54. If you add a prv_cout = -9999 or some such to the beginning of psof, you should get the first A0

Should be n_tap_thds.

I just looked at this, and the last chain seems to be the only one with the problem. The pocket is too small for the whole lead-in to be created, so it gets trimmed off when it intersects the rest of the path leaving just the arc motion. I'd create a seperate toolpath for this pocket and adjust lead-in accordingly (maybe even do the whole thing as a ramp contour instead.

This would be a Windows registry issue. I don't think there's any way to add a parameter to the application call, so if you have a NetHASP, and you're checking out specific licenses, I think you're out of luck.

Having worked with spindle transfer and such with Mastercam, I've learned that it's much easier to trigger a series of pertinent questions in the post an then build the transfer and part-off (if required) completely within the post. The misc ops (transfer, flip, move chuck, etc.) are VERY picky as far as the parameters are concerned and they CANNOT be saved to a library or imported, so you have to do them from scratch for each part. I set up a post so that when a misc ops transfer is called I ask for the gripping distance and retract position and then all of the info for a partoff (which is triggered by a misc value). The misc ops can be used correctly, but they still have to be implemented into the post, and that can be a real pain because of how the info shows up in the .NCI file. In your LatheSamplesNew V9 directory is a file called "MAIN TO SUB SPINDLE T'FER.MC9" which shows a sub spindle part (without part off).