Richard A. Smith wrote: > Sorry for the noise. > > This seems to be already fixed in 1.0.6pre1. (Although the web page > calls this 1.0.5b?) Nope. The file just wasn't really locked. 1.0.6pre1 still chokes on locked files. So is this bug or feature? -- Richard A. Smith Bitworks, Inc