The main problems revolve around the detection of nested islands and the
ability to control the direction of the cut, (CW vs. CCW), and the order
of operation.  Also, every once in a while DesKAM will generate a tool
path that will blow through material that is intended as part of the
part on its way to cut a pocket.  At first I suspected that it was my
error, but I have always re-checked everything and can never find an
error.  I work alone most of the time so there is no one else to double
check me.

I did a quick search for MACH and NC on Google and I did not see
anything relevant in the first few entries.  Since I get these emails at
my office, I do not have a lot of time to spend cruising the web to look
things up.

Bst rgds,
Scott Carroll

Could be windows went off and did something else. No telling
what Windows is doing and when it does it as no one has the source code.
That makes it nearly impossible to track down program verses
operating system bugs. Windows has been out 20 years
now and it is still buggy.

Not recommended for NC tools. The FAA won't allow it in certified
avionics for certified airplanes either.

Paul Lamar

It was probably windows going off on a networking nut !  Unfortunately,
networking was an after thought for Windows. Uncle Bill was very slow to
see the networking light and as a result, it is a kludge at best now.
Windows can not handle networking issues without pausing and belching
with no discernible process in the task manager.

I strongly recommend that if MUST use WinDoze to cut material, REMOVE the
network card and all the networking software, most important, the Windows
Networking clients. This will greatly increase your reliability of the 7
million lines of code that no one person has a full picture on. Also
remove all extra processes from your startup configs.  You will
then have to use media ( CD, USB drive, etc ) to get your files to this
machine and it will be more vulnerable to viruses and such because you
can't patch it easily, but it will be "more" reliable....

-dave

PS - I have been to Redmond and spoken to the actual programmers of the
network stack as well as their top security people...  Don't look for
Longhorn to be much better in this respect as they are not using a clean
sheet of programing paper...