The "Unlock Save" is a feature suggested to me by @butnut It fills the ACCOUNT_ID of the PARAM.SFO with 16 null chars (0x00) and fields npaccountid, psid and userid2 in the PARAMS field are also nullfied. According to butnut, in his tests this makes the save universal and can be used in any account id. He tested 3.3.2 and reported it working fine... however, he just PM'd me telling that there are still issues with the patch. IMO, only the ACCOUNT_ID and PARAMS:AccountID should be nullfied. The psid should contain the PSID from a template.sfo created on your PS3 and the userid2 should not be not touched. But I need some help testing this feature The current version 3.3.3 works as butnut suggested initially. EDITED: @gingerbread the issue is due the resolution that you're using (probably 125%). I switched to 125% font size and adjusted the window. It should be fine in the next update.
