MOTUnation.com

This happened to me twice -- both times in sessions with the clock running -- back in the early 1990's. The floppy disk "keys" somehow got hosed and would not start the software. In each case, MOTU overnighted me a new key disk (floppy). One of those had to fly from Boston to Hollywood overnight, and boy were its arms tired when it arrived. Bada-Boom! I'm outa here!

Shooshie

(really did happen, though)

What's a floppy disk?

FMiguelez wrote:.

This thing here works GREAT as a backup solution, for 2.5'' or 3.5'' drives. And it works with eSATA, FW and USB.
One can boot from a backup image with that case. Using the eSATA connection frees the FW ports for other things.

http://eshop.macsales.com/item/Newer%20 ... WU2ES2HDK/" onclick="window.open(this.href);return false;

It's worked great for me. It's like a nice toaster.

Thanks for that. I was just looking for one of these but I’ve never seen that one.

bb

I change timezones all the time with my laptop and haven’t seen that. I have had it happen when I update the OS.

I checked my Little Snitch rules and only see the MOTU download in there.

bb

I also have never had a problem changing time zones, and I've been to many different countries (Australia, Europe, India, Far East, USA etc...) and changed quite frequently.

I never use them, but can having different User Accounts have a bearing on authorisations?

Cheers

Stephen

newrigel wrote:I've had auth files go south before... in every OS. When I re-image my drives DP always ask for the CD. And CCC even copies all the invisible auth files... I still get the prompts. Could just be some corruption on the drive. He boots into windows too on that machine... anything could happen there.

It just happened to me after swapping out for a new drive. Just to see what would happen, I tried multiple ways to restore my data including Time Machine, Target Disk, Carbon Copy and SuperDuper. Every time, DP wanted to reauthorize.

I had time on my hands and another computer to get my work done so I wanted to see what happened. After each process, I checked the new drive with Disk Utility, Disk Warrior and TechTool 5. Both Apple methods worked well. CC and SD corrupted so many files in the process that I will never use them for that purpose again.

During the re-authorization, I pasted in my Key Code from a text file and accidentally included an extra space. This put me into Expired Demo mode and I couldn't get out. In other words, I corrupted my own auth file - big oops!

With help from others and a good search of this forum, I found this:
http://www.motu.com/techsupport/technot ... opard/view" onclick="window.open(this.href);return false;
Among other things, I saw multiple auth files for old versions of DP including the one I had screwed up. I was able to delete them all and do it again correctly. BTW, there was an old auth file for each hard drive swap I had ever made on this computer - four for DP 5 plus two for DP 4 and an extra for 6 as well.

Now I know and, if it ever happens again, I'll be able to fix it quickly.

mikehalloran wrote:
It just happened to me after swapping out for a new drive. Just to see what would happen, I tried multiple ways to restore my data including Time Machine, Target Disk, Carbon Copy and SuperDuper. Every time, DP wanted to reauthorize.

I had time on my hands and another computer to get my work done so I wanted to see what happened. After each process, I checked the new drive with Disk Utility, Disk Warrior and TechTool 5. Both Apple methods worked well. CC and SD corrupted so many files in the process that I will never use them for that purpose again.

During the re-authorization, I pasted in my Key Code from a text file and accidentally included an extra space. This put me into Expired Demo mode and I couldn't get out. In other words, I corrupted my own auth file - big oops!

With help from others and a good search of this forum, I found this:
http://www.motu.com/techsupport/technot ... opard/view" onclick="window.open(this.href);return false;
Among other things, I saw multiple auth files for old versions of DP including the one I had screwed up. I was able to delete them all and do it again correctly. BTW, there was an old auth file for each hard drive swap I had ever made on this computer - four for DP 5 plus two for DP 4 and an extra for 6 as well.

Now I know and, if it ever happens again, I'll be able to fix it quickly.

I sure hope CCC is working right because I use it for all my backups. Where did you here or what did you experience that told you it wasn't working right?

I never thought I'd say this, but I've grown to like the iLok. Just plug it in and go. I do wish (and think it would be only right) if they would like you make one back up copy of your iLok.

As far as DP's copy protection, it seems very stable to me. I do carry around my master disk and key code just in case.

What might be cool is an internal ilok type chip that installers could address at installation. The 'ilok' would go where the computer would go, you would need both the software codes and you machine codes to install and the f#%€head pirates could take a hike.

MIDI Life Crisis wrote:What might be cool is an internal ilok type chip that installers could address at installation. The 'ilok' would go where the computer would go, you would need both the software codes and you machine codes to install and the f#%€head pirates could take a hike.

I just don't like being tied to a machine. I've been wanting to upgrade my hardware for a while, but I don't want to have to reauthorize all my IKMultimedia, NI, and a few other packages.

RecordingArts wrote: I just don't like being tied to a machine. I've been wanting to upgrade my hardware for a while, but I don't want to have to reauthorize all my IKMultimedia, NI, and a few other packages.

If you make music on a computer, you are tied to a machine. It's not about your convenience, it's about the future of the companies making the stuff we need.

RecordingArts wrote:I never thought I'd say this, but I've grown to like the iLok. Just plug it in and go. I do wish (and think it would be only right) if they would like you make one back up copy of your iLok.

As far as DP's copy protection, it seems very stable to me. I do carry around my master disk and key code just in case.

I may be a fool for their scam, but I bought iLok's "insurance" and I keep a blank iLok in my drawer at my desk. That way, if one goes out at least I can be back up and running in a very short time. Waves plugins are the only things that aren't insured, and I'm under the impression that they have their own way of restoring your stuff in case of iLok failure. Waves tech support seems to be open 24 hours a day, or close to it, so again, you won't be down for long. Basically I'm happy with iLok, but like all things electronic, they WILL eventually fail. I'm just trying to be ready for that.

Shooshie

I really don't want DP to be Ilok'd.

I love the fact that it just works not needing any 3rd party software it's dependant on.

It saying this though I recently dusted off my old Ilok and installed the MX4 (after maybe 4 years or so ) and of course it works first time, so I thought Mmm I'll try out some URS plugins, and low and behold I bought them, which you only can use them with a Ilok, so I've got over my fear of them.

The only thing I'm unsure on how to do or for that matter if I want to, is going to another studio, could I take my iLok and use them there???

RecordingArts wrote:

mikehalloran wrote:
It just happened to me after swapping out for a new drive. Just to see what would happen, I tried multiple ways to restore my data including Time Machine, Target Disk, Carbon Copy and SuperDuper. Every time, DP wanted to reauthorize.

I had time on my hands and another computer to get my work done so I wanted to see what happened. After each process, I checked the new drive with Disk Utility, Disk Warrior and TechTool 5. Both Apple methods worked well. CC and SD corrupted so many files in the process that I will never use them for that purpose again.

During the re-authorization, I pasted in my Key Code from a text file and accidentally included an extra space. This put me into Expired Demo mode and I couldn't get out. In other words, I corrupted my own auth file - big oops!

With help from others and a good search of this forum, I found this:
http://www.motu.com/techsupport/technot ... opard/view" onclick="window.open(this.href);return false;
Among other things, I saw multiple auth files for old versions of DP including the one I had screwed up. I was able to delete them all and do it again correctly. BTW, there was an old auth file for each hard drive swap I had ever made on this computer - four for DP 5 plus two for DP 4 and an extra for 6 as well.

Now I know and, if it ever happens again, I'll be able to fix it quickly.

I sure hope CCC is working right because I use it for all my backups. Where did you here or what did you experience that told you it wasn't working right?

CCC does a compare @ the end of the backup... if it's a bad clone, it will let you know. Sometimes a sector write can get misaligned and you will get errors. Thermal expansion is a drive killer and this is why you'd get errors 99% of the time. Always use a known good drive for clones.
Oh yeah, and a nice new 12 core!

kassonica wrote:I really don't want DP to be Ilok'd.

I love the fact that it just works not needing any 3rd party software it's dependant on.

It saying this though I recently dusted off my old Ilok and installed the MX4 (after maybe 4 years or so ) and of course it works first time, so I thought Mmm I'll try out some URS plugins, and low and behold I bought them, which you only can use them with a Ilok, so I've got over my fear of them.

The only thing I'm unsure on how to do or for that matter if I want to, is going to another studio, could I take my iLok and use them there???

I agree about DP's current coy protection being good. Regarding, moving iLoks, I've only tried it on my two machines, but I would think an iLok should authorize any machine you plug it in to.