Afraid I tried that fix and it didn't work. The error occurs "before" the program shell actually runs. The program appears to scan for drives first, then starts the actual program window. The error is immediate and always the same, "Error (5)" and "Error (35)" for each drive installed. The Error (5) is attached as a GIF. Quite a mystery. Appreciate the effort. I think it's time to hear from the owners who've made the money on this doncha think?
