Similar crashes arose during the
CAESAR II seminar at Qatar last week. It happened during the prior-class preparatory runs.
On the earthquake module, the input field suddenly froze with 6 significant zero numbers. That is, it would not accept any value no matter how I tried to type, delete or curse david little (
) about it. I reloaded
CAESAR II, deactivated the anti-virus, anti-spyware programs, and somehow it worked.
Then next day, the time-history module began to cough up. Its "entry/edit" dialog persistently showed "Hz" instead of "ms" in the head column. The TH program wouldn't run at all. After reloading
CAESAR II three times with different program names, it still failed. But in the class it miracuously worked again.
Observe that none of my students bore any of the agony. Their computers saw only one latest
CAESAR II build--unlike mine, which has been upgraded by myriad builds and versions. I suspect that lies in the culprit.
Anyway, hopefully v5.0 will arrive without these legacies.