[SOLVED] PDF converter in Vista x64

[raimon]

Hello Joan,

Any news about 3.02 release version or patch to handle create port issue in vista x64 systems?

Thanks in advance
Raimon

[Joan]

Hello,

The patch to overcome the 64-bits port issue is not ready yet. Our developers are working on it.

For the moment please create a new port manually or using a script and attach the PDF Printer to it.

[raimon]

Thanks Joan,

I'll ask for it again in a couple of weeks

Regards

[Maestro]

Hello Joan,

Any news about the issue in vista x64 systems (create new port, give administrtor right)?

Thanks in advance
Benoit

[raimon]

Hello Joan too!

One month later... any news/patch about this issue with x64 systems?

Looks like it happen in any x64 system... at least tried with Vista and 2003, don't have any Windows XP x64 to report...

Thanks in advance
raimon

[Joan]

Hello Everybody,

The only current workaround you need to do is to change the printer port from LPT1: to any other port that you create yourself on the machine.

You will definitely need to install the printer and create the new port while being an administrator on the system. Once you do this, you can login to the system using a user password and use the installed printer.

I tried this issue myself under Vista-64 bits and I was able to print to the PDF Converter while logging in as a standard user.

A resolution for this issue is not available yet but our developers are working on it.

Hope this helps.

[Rosewood]

When I go to create a local port in Vista x64, whatever I put for the port name comes back as an invalid name.

Can I just switch it to LPT2 or COM12 or something? What about a TCP/IP port that I created?

[Joan]

If you are logging in as Administrator in Vista x64 you should be able to create a new port using any name.

You can use 'NewPort', 'MyPort' or anything.

Please try turning UAC off.

You can try using COM1 port LPT2 but in my case i usually create a new port.

[raimon]

Hello Joan again!

ANOTHER One month later... any news/patch about port creation issue with x64 systems?

I know this is not a HIGH PRIORITY issue but think that should be solved.

*** MODIFIED BEGIN ***

This thread has obtained the second position in forum views after w98 issues thread so I think it must be important for people...

**** MODIFIED END ****

Thanks in advance and looking for your news!
raimon

[italital]

hello everybody,

I'm also waiting for a patch to resolve our problems with x64 systems.
How long should we wait?
x64 systems are not a new entry, I don't understand why Amyuni Converter don't work here...

[Joan]

Hello,

No doubt this thread this among the highest viewed threads in this forum.
yes it obtained the highest viewes after Windows 98 the weired thing is that Windows 98 and 64-bits are separated by 10 years of technology. I was personally surprised to know that people are still using Windows 98.

This issue is not of high priority as it has a very simple and efficient workaround. However definitely it is on our developers' to do list and is going to be solved shortly.

But when things of highest importance arise, things of average importance will have to wait a while.

Hopefully the solution will not be long to arrive.

[GMCfourX4]

We're still anxiously awaiting a resolution to the x64 issue for both Vista and Server 2003... Any news?

[Joan]

Hello,

Unfortunately, there is no news at the moment but our developers are still working on this. Whenever a solution is ready I will information all the participants of this thread.

Best Regards,

[raimon]

Hello Joan one month later "again"

I've seen you talking about 3.10 release in this forum, could you confirm if this release have any workaround for x64 systems port issue or perhaps some standalone fix to apply?

Thanks in advance.
raimon

[Ger van der Kamp]

Just spend three days trying to figure out why our 32-bit code does not work on Vista-x64

We are generating a lot of RTF which we convert to PDFs using Word (or Wordviewer if the customer has no Word installed). Debugging showed that the DOCUMENTEVENT_STARTDOCPRE is received by the Event-Handler-Window. But then the Application (Word) hangs and we receive no DOCUMENTEVENT_STARTDOCPOST. An Pdf-file has been created but this file is locked by the splwow64 process.

After seeing this thread and changing the Port to COM1 or a dummy local port, the PDF converter works. Is it so hard to modify the install.exe to create a dummy port on x64? You could even release this install.exe for the existing 3.02 Converter as a beta for customers to test on their x86 systems. This would have saved us a lot of time. This would give your developers time to build a solid generic solution in the driver.