Well, it is a good solution, but I think there is a problem. It doesn’t appear to be Fritzing that is issuing the message, I think it is internal to Windows when it can’t find the dll and thus Fritzing doesn’t have control of the contents of the error message. I’ll have to unistall the C runtimes on one of my Windows boxes and see if I can reproduce the problem (ugh! then I’ll have to set up a QT and build environment on Windows too …). Some good news though, I think I have managed to fix the issue when a part is corrupted by swiping some code from elsewhere and patching it in to the area where the seg fault occurs on head. It appears to work on Linux so I’ll try a push and see if saner (and more experienced) heads agree it is a valid fix. On to the parts manager / export bug where it doesn’t delete the files it said it did.
Peter