can't authorize Max 7, stuck!
I work on a few machines (desktop and laptop), which run both windows and mac, so my authorization places run out quite fast. An other reason why an authorization place gets used with me is when I do a clean install, replace a hard disk, etc. There is no way to revoke authorizations myself as I know. The ilok was perfect for handling these situations.
Normally I can log into my account from Max and authorize the copy (each time I start it up...). But now I upgraded from Windows 7 to 8.1 and Max 7 starts with "Not yet authorized". But when I log in it says "authorization file has expired." Then the dialog box appears again "sign into your account or create a new account". I contacted support but haven't heard back yet. Tomorrow I have a live performance so time is getting crucial for me now!
Actually I don't see your email in support - could you please try emailing support@ again?
We'll get this sorted out straight away
-A
thanks Andrew. Yesterday I send three emails (two only referring to MAX/MSP then I saw the authorization check box). Now Max 7 is authorized again! But does this mean, I authorized it too many times before? I had to keep doing that... I thought this was the 'gentleman's agreement. Otherwise the new system is now really a substitute for the ilok...
Being able to deauthorize Max(es) would then be a better option?
The support form seems to (still) have problems. I (re) encountered that problem recently. Today I informed @GINGER about it.
Re: JAN I see, that's not handy, thanks for informing
Usually you'll receive an auto-response mail after using the support form. If it doesn't arrive something went wrong and in urgent cases you can contact support directly (they are very!!! supportive).
@Jan: ah yeah that makes sense, thanks for the tips!
They did respond today, so somehow the form came through with a delay.
Somehow it is strange that the authorization couldn't happen, normally I should be able to authorize ad hoc (so non permanently) after the max authorizations have happened, no?
Hi Folks,
This has been resolved in support
Cheers