I just have to say that I love the new verify. The old verify was useless for me it took forever to processes and I did not usually have the time to run it and change something and run it again. the new verify actually runs so fast that I can use it on every part.

Terry did you start out using the start point? If you added it to the toolpath later it dose not always work. Try recreating the toolpath from scratch and make sure you turn on the start point from the very beginning.

Terry I usually copy the surfaces from around the hole to a different level. Then create curves all edges, then untrim and recreate boundries to leave the surfaces just over the hole then retrim. Sometimes you have to fill in the center area but you will have tangent surfaces where it meets your good surfaces.

No spoon for me I just dive right in. If you can use the old ones you can figure out the new ones.

I use only the new toolpaths for finishing, never the old finish paths. Occasionally I will need surface rough pocket, but other then that I only use the new ones for roughing also. On some of the high speed finish toolpaths there is a rest material tab that turns that toolpath into a leftover toolpath.

Also if files are sent zipped thay are ok.

Not the problem we can get the files off the network and they are fine only when we send them as email attachments do we have a problem.

Nope tried no joy.

Neither worked Gcode. I have our designer talking to our service provider to see if they changed thier av settings in the last 5 months.

I turned my antivirus off to stop the crash on post problem I was haveing. A whole month now with no crashes on post.

We can pass them through the network and have no problems. Only when we send them through email do we have a problem. Within the company it is not a problem we just save on the network and send the location through email. But outside we had to go to step files. Also this is happening with both MCX x_t files and Solidworks x_t files.

Saving to computer first. Works both ways, we send x_t and reciever can not open. We recieve x_t and we can not open.

Has anyone had this problem? If we email an x_t file it cannot be opened.

As far as I can tell this MSE is what was causing my computer to crash on post. Have a new computer running MCX6 W7x64 I7 processor With 12G of ram, and I was crashing on post. Not every time but once it started I had to reboot. I turned this off and have not had a problem since. It has been a month now. It was crashing about 8 times a day every day untill I turned it off, it is no fun rebooting 8 times a day.

Rob thanks for the info.