Hello !
We have a developper version of amyuni PDF Converter (2.10i). We made a program last year in Microsoft Visual C++ 6.0 using this dll under Win NT and it works very well.
Today, users change from Win NT to Win 2000 and the program did'nt create pdf file anymore. A message "could not start print job" appear on screen for each file to print. (FYI, the message appear when StartDoc is called)
I've spend a lot of time to understand what happened but ... everything seems to be Ok. LoadLibrary, PDFDriverInit, EnablePrinter, SetDefaultPrinter, etc all seem to work before it passed StartDoc.
The only difference we found, between NT and 2000, is the Security pane of the printer (Once installed under 2000, there's no information available in the Security pane in the printer properties)
Could you help us to resolve our problem ?
Thanks.
could not start print job under Windows 2000
Thank you for your answer.
In fact the dll version is 2.1.0.9
We cannot download updated version since our updating period is finished. Also, we've try this morning with Evaluation version 2.50. The first test seems to work.
What's the difference between this 2 versions with Windows 2000 ?
Is there any solution enabling us to continue using our 2.10 version under W2000 until we don't buy v2.50 ?
In fact the dll version is 2.1.0.9
We cannot download updated version since our updating period is finished. Also, we've try this morning with Evaluation version 2.50. The first test seems to work.
What's the difference between this 2 versions with Windows 2000 ?
Is there any solution enabling us to continue using our 2.10 version under W2000 until we don't buy v2.50 ?
Ok. In fact, it's not a version's problem. It works as well with 2.10 and 2.50.
We didn't understand why all clients works on Windows NT and why in Windows 2000, it works sometimes and sometimes not...
Today, we found the cause of the problem. Some clients have an Environment variable (required by one module of our application).
TZ=MET-2
So, it's very simple : if we delete this environment variable (even if we change its value) it works very well and if we add it again it's impossible to print pdf files (with the same message "could not start print job").
Do you know this problem ?
Thank you for your help.[/quote]
We didn't understand why all clients works on Windows NT and why in Windows 2000, it works sometimes and sometimes not...
Today, we found the cause of the problem. Some clients have an Environment variable (required by one module of our application).
TZ=MET-2
So, it's very simple : if we delete this environment variable (even if we change its value) it works very well and if we add it again it's impossible to print pdf files (with the same message "could not start print job").
Do you know this problem ?
Thank you for your help.[/quote]
Hello Xavier,
We knew that some environment variables will prevent installation of the PDF Converter under XP. There is a post in the forum about this:
Thanks for the information, I am sure if others here are facing the same problem it will be helpful for them to look at your post.
We knew that some environment variables will prevent installation of the PDF Converter under XP. There is a post in the forum about this:
But we didn't know that an environment variable will interact with printing.uninstalling certain programs in Windows XP changes the Path environment variable in the registry from a Reg_Epand_SZ to a Reg_SZ. This variable is located in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment.
Correcting this variable type and rebooting allowed the Windows XP workstations to install the Amyuni driver.
Thanks for the information, I am sure if others here are facing the same problem it will be helpful for them to look at your post.