Hi,
that sounds like a 'run out of data' issue.
Mach is the trajectory planner and it sends blocks of numeric P(osition) V(elocity) over T(ime) data to the motion controller, in your circumstance the parallel port
driver. These blocks of data are stored in a buffer and the motion controller consumes one time slice, or data packet, every 1 millisecond.
Hopefully Mach can keep up and send enough data packets to keep the buffer full. If however Mach gets bogged down or some other software prevents Mach from running
at timely intervals then the buffer will empty and the motion controller wont have any data and will not know what to do and stop. This is called a 'run out of data fault'.
One simple expedient is to increase the length of the buffer. Machs parallel port has, if memory serves, a 500 millisecond buffer. You might try increasing that to 750 ms
and see whether that helps.
I use an Ethernet SmoothStepper as a motion controller, and it relieves the PC of having to generate pulse streams, for which PCs are notoriously poor, and so can run
the buffer at well under 500ms, in fact I have it set to 180ms, but I have reduced it further on a trial basis down to 100ms, all without encountering the dreaded
'run out of data' fault.
A good external motion controller will markedly improve the smoothness of operation, increase the reliability in face of competing software while additionally allowing the use
of 64bit OS's like Windows 10. Do yourself a favor.
Craig