Okay, it ran most of the night before crashing again. It seems every time it adds a file to the qued upo list, it adds to CPU usage somehow until CPU usage spikes and holds at 100% at which point it crashes.
THe question is: Why?
The old weay, if I used explorer to access files, explorer.exe would spike CPU usage to 100% and freeze WinMx up. I'd look in Task Manager and explorer.exe would be pegged out. CPU usage at 100%. I'd use Task Manager to close explorer.exe and restart it and things would be fine.
Y'all are getting real close.