On 07/06/2007 02:56 PM, Mathias Bauer wrote: > Alister Lownie schrieb: > >> Thanks for the advice so far: >> >> 1) changing the OOo Temp directory doesn't help >> 2) the problem only seems to happen with saved files -- a new file that >> hasn't been saved doesn't seem to suffer from it (although perhaps I >> just haven't encountered that yet). >> 3) I now have the problem on another computer: this one is running OOo >> 2.2.0 on XPSP2. That seems to rule out a memory error on my computer only. >> >> The only thing that I can think of that would link the behaviour on both >> PCs is that they have the CA Security Suite running on them. Might >> there be a conflict with that? (Although they've had that running with >> OOo for a long time and no problems.) > > Can you switch it off? That would be the easiest way to check if your > problem is related to that. > > Another idea would be to use a diagnosis tool that is able to detect > file system access errors. "filemon" is a great tool for that. It can be > downloaded from > > http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx. > > I admit that it's a little bit "techy" but creating a filemon log from a > failed try to save a document surely would help to find the root cause. >
I wonder... ==== 2) the problem only seems to happen with saved files -- a new file that hasn't been saved doesn't seem to suffer from it ==== if perhaps a read-only type lock is being set? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
