Hi everybody.
We have a problems with some end-users of our partners. They work with ours software where we integrated the PDF CONVERTER (last release used 2.10E).
Problems are under s. o. like NT/2000/XP/SERVER 2003 with users with "ordinary users" rights. Nothing seems is to us with "Power Users" (and obviously with "Administrator"). Using the PDF CONVERTER they appear a series of error messages like:
------------------------------------------------------------------------------------
Lic. Error.
Loc. EP.
Licensing Error.
------------------------------------------------------------------------------------
We think that the problem is about the registry's key "HKEY_CURRENT_CONFIG" -> "Software", where we place the license and where probably "Ordinary Users" cannot access for one issue of rights.
Ours partners cannot force their final-users to change access rights over the machines for obvious and logics reasons.
In consideration of the fact that we use "PDFDriverInit" and not "DriverInit" (PDF Printer it comes then created and then "destroyed" every time)...how can we solve this very important problem?
We hope in some help...
Thanks in advance!!
Federico
PDF CONVERTER and user without administrative rights
Hello,
To solve this issue it is better to use DriverInit and not PDFDriverInit.
If users don't have administrative rights under Windows NT/ 2000/ XP they will not be able to install a printer on the system, wether this is our PDF printer or any other physical printer. This is why in similar cases we advise our customers to install the printer on the system using Install.exe and to replace PDFDriverInit by DriverInit.
Hope this helps.
To solve this issue it is better to use DriverInit and not PDFDriverInit.
If users don't have administrative rights under Windows NT/ 2000/ XP they will not be able to install a printer on the system, wether this is our PDF printer or any other physical printer. This is why in similar cases we advise our customers to install the printer on the system using Install.exe and to replace PDFDriverInit by DriverInit.
Hope this helps.
Hello!
First, thank for the answer.
Problem is that our license is for DEVELOPER: that means that printer must be delete at the moment we close the application.
If we use DriverInit in place of PDFDriverInit, moreover, we must give to our customer our license. We think that isn't possible, for a question of contract and 'cause we don't want that the user must insert the code.
I'm waiting for another answer...
Thanks in advance!
First, thank for the answer.
Problem is that our license is for DEVELOPER: that means that printer must be delete at the moment we close the application.
If we use DriverInit in place of PDFDriverInit, moreover, we must give to our customer our license. We think that isn't possible, for a question of contract and 'cause we don't want that the user must insert the code.
I'm waiting for another answer...
Thanks in advance!
Federico
Hello,
The Activation Code and license To information should be set in your code. When delivering your application you will deliver the exe and not the code itself, so your users will not know the activation code and license to values.
If you have the Developer version of the driver you can install the printer and keep it on the system using version 2.10 but you can not give your "activation code" and "license to" to your customers.
Hope this helps.
The Activation Code and license To information should be set in your code. When delivering your application you will deliver the exe and not the code itself, so your users will not know the activation code and license to values.
If you have the Developer version of the driver you can install the printer and keep it on the system using version 2.10 but you can not give your "activation code" and "license to" to your customers.
Hope this helps.
Would this work also in version 2.09?
We haven't yet moved to using your 2.1 series because of some bugs that weren't yet resolved (even through we did buy that update). So our software still uses 2.09 instead. But we also get the complaint from users that they don't want certain machines to run with Adminstrative rights, which means then they can't really use our software because the PDF driver needs to load/unload as the program opens and closes.
We haven't yet moved to using your 2.1 series because of some bugs that weren't yet resolved (even through we did buy that update). So our software still uses 2.09 instead. But we also get the complaint from users that they don't want certain machines to run with Adminstrative rights, which means then they can't really use our software because the PDF driver needs to load/unload as the program opens and closes.
Yes, you can install the printer on the system and use DriverInit even if you have version 2.09 but this will be a momentary solution until you implement version 2.10. Please note that our latest release is 2.10h, you may get an update to that version from our Updates page.
Please not that if you wish to install version 2.09 on your customer system you don't need to provide him / her with your serial number. All what you need to do is saving the files of the PDF Converter in your application folder and run Install.exe on your customer machine.
You can run Install "My Printer" to install a printer with a specific name.
Please not that this solution is applicable only until you implement version 2.10.
Hope this helps.
Please not that if you wish to install version 2.09 on your customer system you don't need to provide him / her with your serial number. All what you need to do is saving the files of the PDF Converter in your application folder and run Install.exe on your customer machine.
You can run Install "My Printer" to install a printer with a specific name.
Please not that this solution is applicable only until you implement version 2.10.
Hope this helps.