Save disabled makes a lot of sense for the first beta release IMHO. Dunno if this is the reason, but by doing so they can freely address any and all problems associated with the file formats WITHOUT having to worry about backward compatability of those formats for work saved by users of the first release. (Yes, they could just say that saved files may not be readable by B2, but they would probably get lynched here when B2 came out, no? ;-) So a pain for B1 testers? Yes. An advantage in the long run? Absolutely. And if save-disabled is too much to stomach - then just don't download B1 and let others do the initial testing on your behalf. How does a limitation in B1 get to be Daz's problem? It's not as if they will be short of B1 volunteers... (In fact the rational may be as simple as ELIMINATING a significant number of testers from B1!) BTW, standard procedure in software testing: Don't rely on the product under test as the mechanism for recreating the problem scenario, esp. for the first few test releases. Else you can't isolate the initial bug from potential bugs related to the (untested) save/re-read process.