TITAM - Technical issues that affected me

Problem:  Macroworks suddenly and inexplicably starts coming up with the "Unit ID Conflict" error / screen, claiming one or more Xkeys has a unit ID conflict that was never there before.  Happens on a previously stable system. (OK, maybe it's not exactly "Unit ID Conflict", but it's close.  I didn't write it down.) In my case, I had a bad label printer that was causing my USB hub to reboot over and over.  This confuses MW and makes "see" the same Xkeys device over and over, making it think there are multiple identical devices plugged in when there is, in fact, only one.   Removing the offending printer stopped the hub reboots, which stopped the Macroworks error.

Update August 2022:  The solution below did NOT work for me, so three more years of putting up with this nonsense. Pretty much every time I ran Macroworks, it would hog the CPU to the point where the machine became almost completely unresponsive.  It took 20-25 minutes just to start Task Manager and kill it.  However, I may have found another solution:  Set Macroworks' "Priority" in Task Manager to "Low".  This seems to let it hog the CPU without actually getting in the way of anything. This is (again) a new development and I don't know if it is going to pan out, but it's worth a shot. ------------------------------- Update Oct 2019:  Per the comments below, I updated to the latest MW (as of mid-Oct) and  it seems to be completely fixed. Oddly, PI does not mention this anywhere that I could find.  Perhaps they don't want to admit they had an issue, or perhaps the issue really was confined to a few lucky users. However, you DO need to manually...