HT201691: About QuickTime 7 Pro registration keys
Learn about About QuickTime 7 Pro registration keys
-
All replies
-
Helpful answers
-
Dec 4, 2013 6:33 PM in response to AppleJoeby Jon Walker,I have a receipt from 2007 where I purchased QuickTime 7 PRO. It has the reg. Code on it.
I remember using it a few times in the past, now all of a sudden it claims to be an invalid code.
Can anyone help me with this issue?
Did you enter both the name and the code as included on your receipt? Both are required and the name must include any salutation or suffix used as part of the purchase account name.
-
Dec 5, 2013 1:25 AM in response to Jon Walkerby AppleJoe,Hi Jon,
Thanks very much but I had no luck.
I am entering it exactly as it appears.
I think they retired my code somehow.
If you happen to know of a resourse I could direct this to,
that would be really helpful.
Thanks Again,
Joe
-
Dec 5, 2013 4:54 AM in response to AppleJoeby Jon Walker,I think they retired my code somehow.
As far as I know, the QT 7 app/structure has no built-in mechanism for retiring or invalidating a correctly generated QT 7 registration code based on your account purchase name and platform.
I am entering it exactly as it appears.
You keep saying "it" as in the singular when you should be referring to them—both the generated registration code key and the account name used to generate the registration code key. I don't know here if you are just referring to the key or not. Both are required and both must be exact.
If you happen to know of a resourse I could direct this to,
that would be really helpful.
I only know of three or four resources:
1) Customer services. This is where you should go if a just purchased key doesn't work. I.e., in some cases the key may not have been properly generated by the auto-software routines and Apple will refund your purchase allowing you to re-order a key or not as you may choose. Unfortunately, you have already indicated that the keying process had worked in the past and that this key was purchased some time ago which would seem to void this approach.
2) You could send QT feedback to Apple via the product feedback form. However, once again it is unlikely this will get any help owing to elapsed time, the fact that the key previously worked, and the probability that this is not a general problem affecting users other than you.
3) The third resource would be an official bug report through the Developer area which will require exacting information as to what you are doing, how you are doing it, along with specific details regarding results. Unfortunately, I'm not sure this resource can be used for what appears to not actually be a bug or be used by the general, non-developer public.
4) Seek assistance from your local user group. This would like only help if the problem is in your work flow or software installation which you seem to be indicatiog is not the case here.

