Print hangs on Win7 - Server2008R2 64bit - Amyuni 4.0.10

[albgio]

Hello,
we experience an issue on Windows 7 /Server 2008 R2 64bit.
We have a 32bit application running on these OS, which use Pdf converter 4.0.10. When we print "directly" from our application everything's fine...
However sometimes we create a document (a report) from our main application, and we use a satellite application (also made by us) to print it. Both applications uses right activation codes for printer... On 32bit machines this process works, but on 64bit when we lauch printing, it waits forever. Once we close the main process, print goes on from secondary application as it should.
If we force cdintf.dll unload form main process just after creating datas to print, it looks to work... sometimes.
Does anyone has the same problem?
Thanks in advance
Gio

[Theta]

Gio,
32bit application 1 --> print (64bit print spooler) --> 32bit printer
To allow windows to print from a 32bit application to the 64bit spooler windows creates a process 'splwow64' this translates or 'thunks' (official term) the 32bit call to a 64bit call so that the print spooler can do it's thing. the problem here is that your main application has an exclusive lock on the splwow64 process, thus your second app waits indefinitely, whether this is due to your usage of the pdf converter api, amyuni's printing logic or within windows itself.

[sprezzatura]

your main application has an exclusive lock on the splwow64 process

Would this be true if the customer has another application that uses Amyuni, such as Quicken or PDF Creator?
Even if Quicken is not running, is there some background service that could be interacting with splwow64?

We have a couple of customers who report our app locking up, and they both have Quicken.

Oy vey, are we all going to have to convert our apps to 64-bit?