On Tue, 6 Apr 1999, Bob Ebert wrote:
> At 11:51 AM -0800 4/5/99, Richard Bram wrote:
> >(It seems like they should all be unlocked, of course, but I notice that the
> >"busy" bit of records do not automatically get cleared after a crash, as I
> >suspect they should be)
>
> While it's true that the busy bit isn't cleared on reset, it should be
> cleaned up the next time you open a database.
>
> There's a check in DmOpenDatabase to see if the database was still marked
> as open from a previous life. If it is, it's assumed that it didn't close
> because of a reset, and DmResetRecordStates is called, which clears the
> busy bits.
And DmResetRecordStates() doesn't crash in this context? (It's fairly
obvious it doesn't as devices don't usually crash right about then. But
I'm curious how it actually manages to works, for once.)
--
Kenneth Albanowski ([EMAIL PROTECTED], CIS: 70705,126)
