Page 1 of 1
Can't authorise DP5.1
Posted: Tue Aug 15, 2006 2:03 pm
by bsmart
Why can't I authorise DP5.1 on my machine? Just got it today, installed it and I've gone through the authorisation process several times and she don't work. The authorisation box just keeps coming back. Any suggestions?
I still have DP4.6.1 on my machine.
Re: Can't authorise DP5.1
Posted: Tue Aug 15, 2006 2:17 pm
by emulatorloo
Are you logged in as a user who can administer the computer?
Do you have your DP5 disc in your optical drive?
Are you entering your keycode for DP5 found in your manual?
Still not working?
Call MOTU then, something is screwed up. Best to call in the morning before the californians start bugging them.
---
Re: Can't authorise DP5.1
Posted: Tue Aug 15, 2006 2:19 pm
by chrispick
emulatorloo wrote:Call MOTU then, something is screwed up. Best to call in the morning before the californians start bugging them.
What? You think we don't stay up all night?
Re: Can't authorise DP5.1
Posted: Tue Aug 15, 2006 2:24 pm
by emulatorloo
chrispick wrote:What? You think we don't stay up all night?
Yeah I know that -- and then you sleep half the day and get up around 3pm!
how do I know? Because I always get thru to motu then. . .
Re: Can't authorise DP5.1
Posted: Tue Aug 15, 2006 2:42 pm
by bsmart
emulatorloo wrote:Are you logged in as a user who can administer the computer?
Do you have your DP5 disc in your optical drive?
Are you entering your keycode for DP5 found in your manual?
Still not working?
Call MOTU then, something is screwed up. Best to call in the morning before the californians start bugging them.
---
All of the above.
Posted: Tue Aug 15, 2006 2:48 pm
by bsmart
Repaired disk permissions and it works. BTW it'd be nice to get useful responses rather than monkey chirps and LCD's.
Posted: Wed Aug 16, 2006 12:51 am
by monkey man
-----------------------------------------
Monkey chirps and LCD's... deleted.
-----------------------------------------
Re: Can't authorise DP5.1
Posted: Wed Aug 16, 2006 2:43 am
by cridarco
Run Disk Utility first.
I had the same problem, solved after I repaired disk permissions.