Repair Table gave me a File-Open prompt... I guessed and picked Entries.DAT, told it to back up, and ran it. And then it locked up again. I don't know if it locked during the repair or after.
Fortunately, I did backup last week as well, unfortunately AFTER this came up. Would have been nice if I'd done a backup just a few days prior and could just revert to that...
Oh, and the next time I bring up Blog, I get an error message that may or may not be related:
"DBISAM Engine Error #11013: Access denied to table C:\DOCUME~1\JLIACE\LOCALS~1\Temp\blogtmp\32682.DAT"
I've run repair on each of the DATs in the Blog directory but did not create a new post before publishing to see if I was fixed. I locked up in Publish as well, it uploaded archive, uploaded index.php and pinged both Weblogs.com and blo.gs, but didn't continue on from there.
Edit: Created a new post, saved, published. First time I got time-out error, republished and it wentthrough the full process fine. The gremlin is still there, and I'm afraid to click on the 10/18 calendar date in Blog to see if I can actually view entry(ies), cause that's been the action that has caused it to lock up on me for the past few days.
Edit again: Woot! I can get into 10/18 now! (yeah, I have nothing better to do today at work than play with Blog LOL). Now I can see the weirded out entry, although I still have no idea what made it go wacky. I've successfully deleted it and re-published with no problems.
Who knows, maybe it's been a full moon or something.... or maybe it really was Halloween gremlins... Whatever it was, we seem to be gold again! Thanks!