Yasu Public Beta v2.5.3b3 Released
A new beta release of Yasu has been made available. For those who are curious, the following changes have been made in the beta releases since v2.5.2:
- v2.5.3b1 (276)
- update reset launch services for Leopard
- changed/updated many paths that were shared, Tiger only, and/or Leopard only
- locks all keychains before restart, shut down and log out to hopefully prevent corruption
- v2.5.3b2 (277)
- added cache & temp file removal to system domain for /private/var/folders/ specific to Leopard
- v2.5.3b3 (278)
- added DNS cache flush to browser history
You can view the full Yasu release history at this link.
Yasu Public Beta v2.5.3b2 Released
A new version (2.5.3b2) of Yasu was released today that adds extra Leopard specific cache cleaning paths, and is available for download on the Yasu page.
I’ve had no reports of trouble from the b1 version — so unless what I’ve added to this version somehow causes the magnetic poles of the planet to switch polarity, the final version should be ready to publicly release by late next week sometime.
So Much For a Private Beta
Okay, so maybe I’m behind the times and private beta testing is just considered passé these days. I only received one response to my call for Yasu testers — and that was from someone I knew was going to respond. So…
We’re going to try a public beta release instead. No free license codes for testing this one though. If you like to live on the edge and want to give the latest beta a spin, you can download it from this link:
http://jimmitchelldesign.com/files/Yasu_PublicBeta.zip
Here’s what’s addressed:
- Some Apple specific user cache paths are substantially different between 10.4 & 10.5. This beta fixes that.
- Yasu no longer removes font caches for Adobe or MS products. It only clears Apple font caches now.
- Updates the “Reset launch services” task for better Leopard compatibility.
- Locks all Keychains before logout, restart & shutdown to hopefully address spurious reports of keychain corruption after running Yasu.
The testing period will run for roughly the next two weeks, maybe longer if reports are still rolling in by that time. Or, it could be shorter if no problems are reported. Please, be sure to leave some feedback on this post regarding positive or negative experiences with this beta.
