I think many other developers have procedures that aren't so different. I don't keep the old installers available for very long, since I've found that people may still purchase something I no longer support and I don't want them to have unrealistic expectations. In all cases, I try to make that last build as solid as I can. The end of 2017 will mark the end of support for 32-bit AAX (Windows 10).

I dropped Windows XP three years ago, RTAS a couple of years back, and then dropped 32-bit AU, VST and VST3 at the start of this year. Support engineers don't want to stay too far behind the technology curve, since it dims their future employment prospects.

The sales pool for those systems has dried up and-even if the original pricing has accounted for a certain period of support-you just can't afford to pay somebody to keep up with the old stuff. And if you don't have an image backup or every single installer, then you'll be faced with updating your whole studio.Ī developer of any size has limited resources and it simply makes no sense to try to maintain (and validate) software for obsolete systems. Sooner or later you'll hit the update that breaks the system-either the thing you updated or something else. If you're running a legacy system (and Snow Leopard really fits that description), then keep it legacy and don't update anything. That sums it up pretty well (and Mike Thornton has a nice take on this same subject a couple of weeks ago on PTE).

Ilok license manager installer