Application hangs when calling StartDoc on AMD64

The Amyuni PDF Converter is our Printer Driver that enables you to convert any documents to PDF format. If you have any questions about installing and using the Amyuni PDF Converter please post them here.
Post Reply
sir_hel
Posts: 20
Joined: Tue Mar 13 2007

Application hangs when calling StartDoc on AMD64

Post by sir_hel »

Hello,
we are using "Amyuni PDF Converter Version 3.01a". I have downloaded the latest available version of PDF Document Converter today!

On 32bit-Systems (Windows XP) everything works fine.

On a 64bit AMD-System (Windows 2003 Server) we have serious problems:
+ Printer is installed successfully with "install -s printername"
+ Printer ist configured to print to LPT1: (tried also COM1: as mentioned in a previous thread - same result!)
+ We are using the 64bit-dlls as follows:
acfpdfuamd64.dll
version 0.3.0.301 / 3.01a
renamed to acpdf300.dll
acfpdfuiamd64.dll
version 0.3.0.301 / 3.01a
renamed to acpdfui300.dll
cdintf.dll
version 3.0.1.1 / 3.01a
renamed to cdintf300.dll
+ When printing the application hangs after calling StartDoc
+ Here is a short snippet of the code
DriverInit
...
hdc = CreateDC
EnablePrinter
(SetMapMode)
(SetTextAlign)
StartDoc
-> App. never returns from calling StartDoc!!

Only cancelling the print-job in the print queue (displays "printing" and "error") generates a printing error and returns to the application!

Any suggestions how to solve the problem?

Best Regards,
Helmut Schierer
Jose
Amyuni Team
Posts: 553
Joined: Tue Oct 01 2002
Contact:

Post by Jose »

Hello,

Can you try setting the PDF document filename in the PDF Converter's SetDefaultFileName() function and not in the DOCINFO structure?

I believe that this will eliminate your issue?


(*SetDefaultFileName)(pdfPrinter, "c:\\temp\\test_64bit.pdf");

// di.lpszOutput = _T("c:\\temp\\test_64bit.pdf");

Hope this helps?
sir_hel
Posts: 20
Joined: Tue Mar 13 2007

Application hangs when calling StartDoc on AMD64

Post by sir_hel »

Hello,
after additionally using "SetFileNameOptions" it seems to work now:

DriverInit
...
hdc = CreateDC
EnablePrinter
...
SetFileNameOptions(NoPrompt + UseFileName)
SetDefaultFileName
StartDoc
...

Thank you for the quick reply.

Question: Will that workaround have to be used forever or will that bug be eliminated in future versions?

Best Regards,
Helmut Schierer
Jose
Amyuni Team
Posts: 553
Joined: Tue Oct 01 2002
Contact:

Post by Jose »

Hello,

We have debugged this thoroughly and believe it is a limitation in 64bit Windows. Since this is out of our control, we suggest you use our work around.

Hope this helps?
sir_hel
Posts: 20
Joined: Tue Mar 13 2007

Post by sir_hel »

Yes, it does!

Thank you.
Helmut
Post Reply