Yikes… thanks for the heads up Hawk. Sorry to hear you’re one of the ones dealing with the bug :(

Not that it will help the immediate problem but… if you’re willing to do a little additional work…

I have had a number of other applications that experienced a similar issue back with the original 10.4.6 issue. Since then, I adopted a method that appears to have worked for me…

I’ve started to use SVN as a method of storing over the network on a network device. Given… this requires a bit of what would be a complex service (I have a server that then connects to my NAS and stores all my SVN data as well as backups), I haven’t had any corruptions. It added a extra step to most of my work, but I use SVN so much at the office for scripts and the majority of what I do it was a small change that wasn’t too inconvenient. The ability to roll back and recover so easily has also saved me on more than one occasion!

network shares are always hazardous. You have to also save locally. backup in the network later or use versioning software / time machine stuff.

I could told you many stories about disastrous NFS side-effect, or SAMBA/CIFS/Windows share sides effects or , of course, AFP share.

as a rule of thumb, in my enterprise, I explain to people to work their important stuff onto the local folders on their own computer (on the desktop for example) and put a copy on the corporate sharing networks. as a backup and way to share.

the servers is also double-backuped

-
wifi is a lot of more dangerous. it’s easy to add so many faults than the computers cannot know it fails. you could of course add a check of the contents everytime, it would destroy the speed of wifi networks.

dang, I just upgraded a few hours ago. Seems like updates are always a mixed blessing. On the one hand I can’t save to a network share with CS3 and on the other hand Pro Tools 7.4.2 now works on Leopard!