OW 5.1 Final Released

[DV Henkel-Wallace]

On 06 Jan 2005, at 08:22, Ken Case wrote:
> On Jan 6, 2005, at 6:21 AM, Jake Robb wrote:
>> So am I correct to assume that the problem where OW "forgets" about 
>> all of your workspaces still exists?
> Apparently it does:[...]
>
> What I most need to know is when the workspace information is lost:  
> in particular, is it lost when writing the file, or when reading it?  
> (On quit, or on launch?)  In an ideal world, I'd like a look at the 
> workspace file just before it gets corrupt and just after, and exactly 
> what happened between those states.

How can I tell which?

My observation is like Jake's: by the time it happens it's too late.  I 
just reflectively cmd-ctl-t all the time and have just added a cron job 
to copy my workspace every hour to /tmp.  It only happens once in a 
while, but when it does, it's a real disaster!

Crashes don't seem to have triggered it, though I only have been paying 
attention to this lately.

By the way I haven't lost all my workspaces, only the currently active 
one.

FWIW my machine has no "haxies" and in fact very few non-bundled 
applications installed, and only one (as far as I know) non-apple kext 
(for missing Sync).  Extremely generic.

-d