So I've tested the Tosa/Opie OZ-3.5.4-RC and here's what I think of it
after a little more than one day of use, but first I should outline
what I most use my Z for lately, that is to say basically reading e-books with
opie-reader and from time to time play some games, not really anything
else.
So here it is :
- The good :
* It's even more beautiful, a lot of icons and the themes has been
reworked to match the 480x640 resolution and it's just beautiful,
looking sharp and all.
- The bad & ugly :
* OZ just told the partitions of my ext3 formatted 2G microdrive to
go to hell, all, disappeared but to beginning of the e-book I was
presently reading. I noticed it when I got to the next page and was
presented with what looked like a dump of some part of the RAM
instead of the next chapter of 'A song of stone' by Iain Banks... I
launched opie-advancedFM to take a look at the file with the text
editor and before my eyes I could see all the content of the drive
was gone

I ejected the HD, plugged it in my laptop to reformat
it and fill it with my backup, so no big deal for the datas but well
it's not something I like to see happen.
As for the why, I can only make some guesses from how the OS was
configured. Unlike what've done before I had activated the
'DocTab'. Second thing I think of is the new behaviour of the OS
that asks what to do with the drive when inserted first time, it was
set to suspend it when inserted and when the OS resume from sleep.
Now I've refilled the drive with the datas and plugged it back in
the Z so at least I can continue to read the book. I changed the
setting of the OS to activate the drive when inserted and when the
OS resume from sleep. I'll see if it continue to think of my datas
as crap and if it trash it again. I'll let you know if it happen
again.
Come to think of it I think the 'suspend drive' stuff that
might be guilty. I've not investigated by I wonder if it unmount the
drive before suspending it... So let's suppose the drive was
suspended, not unmounted ; then opie-reader, when I go to the next
page realize it's not in RAM, tries to read it from the drive and
then *BOOM*, trying to read from the drive while it's suspended make
a mess of it. I think about that because I saw this with my laptop
and its external HD : once I suspended it with the external HD
mounted and on and when I woke it up the external HD was unreadable,
a 'ls' would print crap. No data loss but I had to unmount then
mount the drive to get access to it...
EDIT : I've forgot to say thanks for the "kinda" release