Quote:
Originally Posted by davidfor
No, that statement should be:
If someone wants to run something other then the latest firmware released, they can if they want to. But, 4.31 would be a bad choice.
@Desertway: As @retro said, there were problems with firmware 4.31. Your description matches what was happening. The prompt to scan when plugging the device in has always been an occasional issue, and a corrupt database as well. Some people never see them, others seem to see them frequently. This got worse with firmware 4.31 to the point were some people hit it each time they connected. Your "a few weeks ago", suggests that you might have been running 4.31 and hence the likelihood of seeing this problem was higher.
These problems have been fixed in firmware 4.32. From my experience, the number of prompts to scan the drive when connecting has gone back to pre-4.31 numbers. As have the corrupt databases. Unfortunately, both can still happen, the reasons (other than a bad disconnect from the PC) are unknown.
|
Thanks very much for the thorough explanation. I definitely had those errors in abundance before the firmware update, and only the once since the update. But this was the first corrupted database I've had. Thanks to your plugin, it wasn't nearly the setback that it could have been.
I'll be very mindful of disconnects going forward.