spmm Lv 1
'SmilingOne and a few others report that they are getting çorrupt database error messages and can't load the client after accepting the latest upgrade.
Error sounds similar to last database one.
Tears, lost work, gnashed teeth etc
'SmilingOne and a few others report that they are getting çorrupt database error messages and can't load the client after accepting the latest upgrade.
Error sounds similar to last database one.
Tears, lost work, gnashed teeth etc
I managed to provide the normal fix for these database failures to Smiling by having her copy over the contents of affected folder with contents from an un-affected folder, however she did lose a rather high solo score in the process.
However as a result of her warning, I have not updated any of my clients and won't be until I hear something GOOD in this feedback thread, not a different thread…
affected too. had to switch to main.
assigning…
It is also occurring in MAC OS running Beta.
I was going to run a third instance of the ap and it updated and couldnt find the database.
The two I am running I wont quit and havent been effected.
Let's hope they didn't just release a new beta/dev version, and then run away for the holidays.
Ditto for my two MAC OS machines. Getting corrupt database error messages and can't load the client after accepting the latest upgrade. Preferences, recipes list and tracks with scores are all gone. Same message when I run the backup copy.
I'm usually very complimentary about Fold.it program and its been fun but this is really amateurish. Reminds me of the '90's when I saw these kinds of messages frequently. Let me get this straight. Fold.it has code that will crash if the database is corrupt? And, the Fold.it error message/advice then is to download a new copy of the software causing all resources to be lost? Haven't we made any progress in the last decade? Oh, I forgot. This is just beta software. User beware. How about testing procedures? How about code that will work even when the data is garbage? How about code that will repair itself or warn the user ahead of a fatal crash. How about quality control? Come on guys.
we get holidays?
Well tsk tsk - you know you should make proper and more than regular backups - especially if you are running beta - but it is a bit tricky when you don't get any warning, and a total pain. Some protocol of just telling people when an update is being done and to backup may help.
Still we may get Lua V2 in main for Christmas.
Updates now working, or at least seem to be. There may be features I have not checked tho.