correction: BA != BAA
An ongoing disaster for users. Surely Microsoft and T-Mobile must be singing the blues.Why there weren't any backups -- even older ones -- that could've been used as a restore point is totally unclear, so we're hoping Microsoft has the stones to come clean for the benefit of an entire industry that wants to understand how to make sure this never happens again.Saidi<tongue_in_cheek>With BA's giant software migration (mentioned in another skunks-ke post), would you feel safe flying BA?</tongue_in_cheek>