Amyuni filling up registry
Amyuni filling up registry
I have used amyuni for several years within a legacy ASP 3.0/VB 6.0 application. I've been very pleased with the product, but I am noticing that the registry is getting filled with entries under HKEY_CURRENT_CONFIG/Software/Amyuni PDF Converter/Jobs and HKEY_CURRENT_CONFIG/Software/Amyuni PDF Converter/Locks. This actually killed our Win2000 server b/c the registry got too large. Is there any way to stop this from happening?
Hello,
This is very similar to an old issue that was solved some time ago.
Please tell me which version of the PDF Converter you are using.
Als please try the newest version from our siste www.amyuni.com
Hope this helps.
This is very similar to an old issue that was solved some time ago.
Please tell me which version of the PDF Converter you are using.
Als please try the newest version from our siste www.amyuni.com
Hope this helps.
Custom Brand the Amyuni PDF Printer Driver http://www.amyuni.com/en/developer/branding/index.html
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
Sorry for the delayed response. I was working on a completely different issue the last few weeks. I'm using version 2.10i_7. I tried using 2.5 but it wouldn't do anything. Anytime I tried printing to it, it wouldn't work. I've tried using that version on multiple machines with multiple OS types (win2000 server, win xp, win 2003 server, win vista). For example, as a test, I went into excel and got an error that said "Your file could not be printed due to an error on Amyni PDF Converter on LPT1:".
Hello,
What you are getting is normal.
Version 2.51 needs a different activation code than version 2.10, If you downlaoded and installed the Developer version 2.51 please check the file install.ini that you get in the folder where the PDF Converter files and dlls where deployed to get the new activation code and licensee name and replace them in your application.
If you are using the DLL interface of CDIntf you will also need to change the dll name in the functions declaratino and replace cdintf210 by cdintf250 or cdintf251 depending on which version you have.
Finally please not that the PDF Converter Developer edition doesn't allow you to print to the PDF Printer from desktop applicaitons like Word and Excel directly.
What you are getting is normal.
Version 2.51 needs a different activation code than version 2.10, If you downlaoded and installed the Developer version 2.51 please check the file install.ini that you get in the folder where the PDF Converter files and dlls where deployed to get the new activation code and licensee name and replace them in your application.
If you are using the DLL interface of CDIntf you will also need to change the dll name in the functions declaratino and replace cdintf210 by cdintf250 or cdintf251 depending on which version you have.
Finally please not that the PDF Converter Developer edition doesn't allow you to print to the PDF Printer from desktop applicaitons like Word and Excel directly.
Custom Brand the Amyuni PDF Printer Driver http://www.amyuni.com/en/developer/branding/index.html
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
Hello,
This issue is resolved in 2.50 and 2.51 I advise you to use 2.51-b if you have it .
This issue is resolved in 2.50 and 2.51 I advise you to use 2.51-b if you have it .
Custom Brand the Amyuni PDF Printer Driver http://www.amyuni.com/en/developer/branding/index.html
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark
Amyuni PDF Converter tested for true PDF performance. View results - http://www.amyuni.com/benchmark