Vista: Install.exe -s followed by the listener app generates

Mike.B · Post by **Mike.B** » Sun Mar 25 2007

We are launching a listener application after installation of the Amyuni driver. . The call to install.exe -s is in the Install portion of the deployment project and the listener app is launched in the commit phase (which happens after the install is completed successfully).

Both the DriverInit and EnablePrinter return true, but on Vista when printed from notepad to our printer right after the installation we get Printer not Activated error -30. Followed by a message box "Device not ready"

What's interesting is that exiting the listener application and starting it again completely solves the problem.

Adding a timeout in the custom action that spawns the printer doesn't help either, even if the timeout is 30 seconds.

Has anyone had a similar problem?

Joan · Post by **Joan** » Mon Mar 26 2007

Hello,

Which version of the PDF Converter you are installing? the End User or the Developer version?

If you are using an evaluation version please provide the licensee and activation code to check them.

Mike.B · Post by **Mike.B** » Mon Mar 26 2007

We are installing a licensed 2.51b. The same build from the same build server works on XP SP2 and doesn't on Vista.

Here is some other information you might need. I will pro actively answer these common questions:
1) Vista is a fresh install with all the default settings.
2) UAC does not pop up and the install is done with a live tester so if there was a UAC dialog it would be accepted right away.
3) Test machines are all x86 (no AMD64 or IA64 is used)

Joan · Post by **Joan** » Tue Mar 27 2007

Hello Mike,

Is your licensed version a Developer or and End User Edition?

If it is a Developer edition it is normal to get a printer not activated error message when trying to print from Notepad directly or if you are adding a timeout between the activation and printing statements programatically.

The Developer version is activated only for 20 seconds and adding any timeout between the activation and the priting will definitely generate and activation error message.

From what I see this is an activation issue but it is weired that the same process was working on XP.

I suggest that you try 2 issues:
1 - Please try calling EnablePrinter right before printing and replace PDFDriverInint by DriverInit in your application
2 - If one didn't work please downloading our newer version 2.51-d or 3.00 and try it.

Mike.B · Post by **Mike.B** » Tue Mar 27 2007

We do have a fully licensed version and we have been calling DriverInit instead of PDFDriverInit to avoid the "copying down files" message.

In the download page for our product I see download the latest version 2.51b. Are we not licensed for 2.51d if we have a license for 2.51b?

Are there some debug hooks that can be enabled for your driver? It is my expectation that if

CDIntfControl.DriverInit returns true and
CDIntfControl.EnablePrinter returns true

that we are good to go.

Joan wrote:Hello Mike,

Is your licensed version a Developer or and End User Edition?

From what I see this is an activation issue but it is weired that the same process was working on XP.

I suggest that you try 2 issues:
1 - Please try calling EnablePrinter right before printing and replace PDFDriverInint by DriverInit in your application
2 - If one didn't work please downloading our newer version 2.51-d or 3.00 and try it.

Post by **Jose** » Thu Apr 05 2007

Hello Mike,

The developer license does not allow you to install the PDF Converter as general printer driver. Can you contact support@amyuni.com regarding your issue?

Mike.B · Post by **Mike.B** » Thu Apr 05 2007

We have a full license