Once you have paid you will receive your registration information via email. Messages are sent by a fully-automated system so you should receive the message within seconds or minutes of completing your payment depending on network conditions. Note that if you have used a PayPal eCheck it will take at least 4 days though. Please read below to get more information on PayPal eChecks.

PayPal eChecks: If you paid using a PayPal "eCheck" then the transaction will not be completed until the payment has cleared. Just as it would for a real-world check, PayPal imposes a clearance delay of several days (typically about four business days) before allowing the funds to clear and the transaction to be completed. Immediately upon clearance PayPal's automated systems will cause your registration information to be sent to you via email. There is no human intervention required so there should be no additional delays.

Your registration information is automatically sent after automatic checking of the payment, by e-mail to the email address that you provided during your payment. If you provided a wrong return email address you won't be able to receive your registration information. Messages are sent by a fully-automated system so you should receive the message within seconds or minutes of completing your payment depending on network conditions. If after waiting a couple of hours you still have not received your license notice check the following:

Check that our message containing the registration information did not get falsely identified as spam and diverted to your junk mail folder. If your email client, or your email server, or your ISP has a misconfigured anti-spam filter you might not be able to receive your registration information. If your email box is full you won't be able to receive your registration information either. If you have a challenge-response system in place it may have bounced the message containing the registration information and prevented it from being delivered. Given that such messages are sent by an automated system there is no human that could respond to such a challenge; you'll therefore need to check your quarantined messages or add the appropriate maxprog.com address to your "whitelist". If you don't receive an answer from us after a couple of days, please open a support ticket and request that your registration information be sent to a newer address (please supply your full name, old email address, new email address, product purchased, purchase date, and receipt or transaction number).

Note that you can have your license code resent to you at any time by using the Serial Number Recovery form (this is an automated system).

Your internet connection might not be stable or your internet browser probably did not download correctly the file from our website. Check that your internet connection works correctly, empty the cache of your internet browser, and redownload the file from scratch. When your file is correctly downloaded, you don't have any error message when it uncompresses. Once the file is uncompressed, just launch the application located inside the folder.

All the registration codes we send work perfectly. If you can't make them work it's often a problem on your side, in the way you use them. Read again carefully the registration email you received. Everything is explained in it. Make sure that the registration code you use is for the right application but also for the right version. Make sure that you enter correctly your registration code (exactly as it is given in the email) in the registration window, then click on the "Register" button. If a failure message appears, check again the registration information you entered. If you really can't manage, please open a support ticket here accompanied with the registration email you received.

We always answer your requests. If you send us an email with a wrong return email address you won't be able to receive an answer from us. If your email client, or your email server, or your ISP has a misconfigured anti-spam filter you might not be able to receive an answer from us. If your email box is full you won't be able to receive an answer from us either. If you don't receive an answer from us after a couple of days, please open a support ticket.

The aim of a bug report is to enable us (the programmers) to see the program failing in front of us as it does in front of you. Therefor you should give careful and detailed instructions on how to make it fail. If we can make it fail, we will try to gather extra information until we know the cause. If we can't make it fail, we will have to ask you to gather that information for us.

Please avoid reports that say nothing, like "It doesn't work!", reports that make no sense to you, reports that don't give any information at all, reports that give speculative information. Be aware that a problem can come from your operating system, somebody else's program or a network failure. Try to make very clear what are actual facts ("I was at the computer and this happened") and what are speculations ("I think the problem might be this"). Leave out speculations if you want to, but don't leave out facts. Describe what happened. Tell us exactly what you saw. Tell us why you think what you saw is wrong; better still, tell us exactly what you expected to see.

When you report a bug, you are doing so because you want the bug fixed. There is no point in swearing at the programmer or being deliberately unhelpful: it may be our fault and your problem, and you might be right to be angry with us, but the bug will get fixed faster if you help us by supplying all the information we need.

Give us some credit for basic intelligence: if the program really didn't work at all, we would probably have noticed. Since we haven't noticed, it must be working for us. Therefore, either you are doing something differently from us, or your environment is different from ours. We need information; providing this information is the purpose of a bug report. More information is almost always better than less.

If you are not reporting a bug but just asking for help using the program, you should state where you have already looked for the answer to your question. ("I looked in chapter 4 and section 5.2 but couldn't find anything that told me if this is possible.") This will let us know where people will expect to find the answer, so they can make the documentation easier to use.