Hi narin,
Petr's response is completely reasonable, if perhaps a bit vague. Unlike many other vendors, we release a new version of ATK/VNL every year with many new features, which means we spend a lot of resources developing the code. At the same time, this means we cannot afford to support older versions, and thus if there are issues, people are encouraged to upgrade to the latest version. This is not so much a matter of being friendly or not, it's rather an economical reality - we reserve the right to limit the amount of support we can offer to customer who are not actively paying the maintenance fee. In fact, we often answer scientific or technical questions without checking if the user has an active maintenance contract, but when the question is related to a specific old version of the code, or indeed is particular to one user (I haven't seen any other user with this problem, so it might only appear with your graphics card/driver combination) then yes, you do in fact have to pay every year to get support. Actually, why would you expect to get it for free in the first place?
Btw, was this an issue also in 2014, or only when using the latest drivers today? If it was a problem in 2014, we could have fixed it then if it was reported, but if it only appears now then as Petr indicates it may be that the old code is not compatible with newer drivers (or hardware) - this happens to a lot of software, and is why one sometimes needs to upgrade.
You might want to try ATK/VNL 2017 using a trial license - the upgrades since 2014 involve way more than just a few new pseudopotentials!
With regards,
Anders Blom