MOTUnation.com

pcm wrote:Because I be somewhere else when the need arises. How many times have I needed a download when at a friend's house, or another studio. Believe me, these situations can and do come up.

monkey man wrote:IMHO, one should at least be able to download updates to all the previous purchases and upgrades one has bought. Excluding access to non-paid-for versions' upgrades would seem fair enough too, and in most cases you'd expect that this'd pose few problems as most of us have indeed only begun projects in versions we've paid for.

I agree that MOTU should provide access to updates. Just suggesting that since they don't, and from the endless calls they get asking, they probably won't until cloud computing is standard, the safe thing to do is get them while they're hot, and carry your data with you. It won't solve all these problems, but nothing will.

monkey man wrote:... and why wouldn't you, Baysey? Rightly so, IMHO. We folks here in Jungleville have been at the forefront of world behavioural studies. OK, so we were on the receiving end as opposed to conducting the experiments, but hey, we were involved. LOL

Behavioural scientists are often confused over which species is in control.

Ha ha ha!

I agree, Baysey, that it's really up to us to keep our updates and so on. The "gotcha" for me though, at least in theory, is that one requires the original programme disks for the authorisation process, meaning that if your bought disk starts playing up as old disks tend to do, you're theoretically a goner.

One thing I'd like to know is whether or not one can circumvent this procedure by keeping copies of the original installers as well as the associated auth files, temporarily made visible, on HD/backup disks. This may well be the most foolproof solution, IMHO, should it actually prove workable.

monkey man wrote:.One thing I'd like to know is whether or not one can circumvent this procedure by keeping copies of the original installers as well as the associated auth files, temporarily made visible, on HD/backup disks. This may well be the most foolproof solution, IMHO, should it actually prove workable.

You can use unix commands to make the auth files visible and invisible. There's a tech note about it. But if your original CD gets pooched, I don't think you can install and reauthorize using the key code. I thought I'd be clever and make a backup copy of my original V5 CD so I'd never have a problem if I lost or damaged it. But my backup copy did not work for the authorization step.

That was the gotcha I was afraid of, Baysey. Obviously this means that unless MOTU retains/maintains stocks of the older products, we're doomed.

If this is indeed the case (that MOTU doesn't do this sufficiently far back), it's surely an incentive to bring the oldest projects up to date sooner rather than later, hopefully exposing any suspicious files. Of course, should there turn out to be any, one would find one's self not passing "go", not collecting any money and stuck at square one again. I sense more work coming on...

Thought: Wouldn't it be wonderful if MOTU maintained appropriate legacy systems (not a lot of work when you think about it) and offered a re-saving/updating service... for nicks? If it were my company, I'd do precicely this... or something similar. LOL

monkey man wrote:Thought: Wouldn't it be wonderful if MOTU maintained appropriate legacy systems (not a lot of work when you think about it) and offered a re-saving/updating service... for nicks? If it were my company, I'd do precicely this... or something similar. LOL

But do we know they haven't done this? Or won't? I expect they would have archives of all of their products, including source code, backups, etc. Apple can provide all versions of their OSs, and last time I looked, everything prior to 7.5.5. is free (but not supported).

I've often wondered why companies don't just move their very old versions into the public domain, and withdraw support. The value of this software as an asset to the company can't be material.

I agree again, Baysey. Whilst it is apparent that slightly-earlier versions can still be obtained from MOTU, I've not yet heard much to indicate that this support extends all the way back. You'd think it would, and I certainly hope it does, if for no other reason than that of feeling more comfortable about having placed all my bananas in one basket - MOTU all the way. Yeah!

I'm the guy who started this thread. Today I received my package from MOTU. They sent the DP6 upgrade that I ordered, which also included the DP5 disc as requested. The other day I heard from a fellow who asked for the same package, and was told it was impossible to ship DP5. So I guess it depends on who you talk to at MOTU. Go figure.

Thanks again to all of you for the advice.

All's well that ends swell. Great! Well done, ACMMD!

Then it is unlikely that you had the CD in the drive at the time. This has worked for thousands of others, and will work for you.

Hey Bayswater....hate to break this to you but I had the exact same problem when I got my shiny new DP 5. A simple permission repair fixed the problem and allowed DP to authorize properly. Apparently this must have been somewhat common as they new exactly what the problem was when I called tech support.

OK I suppose. But not being able to install an app with authorization files because you have not repaired permissions hardly constitutes a defect on the part of MOTU. Repair permissions is the most basic maintenance procedure associated with OSX. You can't go to late into the day withoit being told to do it before ans after installing anything.

I repaired permissions as it happens. Still get the same error. If that was the only problem I ever had with Performer 5 (and 6) I would still be using either one of those programmes. As it is I've put 5 and 6 (and the manuals) onto eBay. MOTU will allow me to transfer the licences which I am grateful for.