Crashing and BNP corruption
Posted: Wed Mar 09, 2005 8:57 pm
While running past Pyr today, near the Pagans camp, I suddenly crashed out with a very odd error, "application asked Runtime to terminate it in an unusual way", or thereabouts.
So I restarted, selected "Crash without neL window", and logged in again, waited to be disconnected, and selected my character. And crashed again while the loading screen was still up.
I've had this happen once before, so I ran the data check and sure enough, the newbie zone object file and sound.bnp file were corrupted. Thus begins the very, very slow download and repair.
My questions are: Did I initially crash because those files became corrupted, or did those files become corrupted because of the initial crash? The data integrity on the rest of the drive seems fine. It's only Ryzom this seems be happening to, and sound.bnp twice.
Will Ryzom run okay if I set those files to read-only? I'm hoping the Ryzom client doesn't do something like opening those files read/write when it isn't patching.
So I restarted, selected "Crash without neL window", and logged in again, waited to be disconnected, and selected my character. And crashed again while the loading screen was still up.
I've had this happen once before, so I ran the data check and sure enough, the newbie zone object file and sound.bnp file were corrupted. Thus begins the very, very slow download and repair.
My questions are: Did I initially crash because those files became corrupted, or did those files become corrupted because of the initial crash? The data integrity on the rest of the drive seems fine. It's only Ryzom this seems be happening to, and sound.bnp twice.
Will Ryzom run okay if I set those files to read-only? I'm hoping the Ryzom client doesn't do something like opening those files read/write when it isn't patching.