Search found 19 matches

by Robert
Tue Jul 11 2006
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Amyuni and Windows Vista
Replies: 14
Views: 41608

Amyuni and Windows Vista

Hi Joan, I've finally got the 2.50b version of PDF Converter and tested it on Vista. I have one question though. I deploy my apps that use PDF Converter on all flavors of Windows except Win95 and I was looking at the deployment requirements in the Introduction section of the Common driver Interface ...
by Robert
Wed Jun 21 2006
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Amyuni and Windows Vista
Replies: 14
Views: 41608

Amyuni and Windows Vista

Hello, Here's the message that Vista displays when I execute Install.exe on Vista. "Windows can't install the Amyuni PDF converter 2.10 kernel-mode print driver. To obtain a driver that is compatible with the version of Windows you are running, contact the manufacturer." <Ok> I took a look...
by Robert
Tue Jun 20 2006
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Amyuni and Windows Vista
Replies: 14
Views: 41608

Amyuni and Windows Vista

Hello, Has anybody looked into Amyuni PDF converter and Windows Vista yet ? I've installed the Beta 2 version of Vista and tried to install Amyuni PDF converter 2.10i and was unable to. I know this is early on for tests on Vista but it would be nice to know when a Vista compatible version of Amyuni ...
by Robert
Thu Feb 24 2005
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Conflict between PDF Converter 2.10i and HP laserjet 3150
Replies: 1
Views: 4065

Conflict between PDF Converter 2.10i and HP laserjet 3150

Hello, We've been experiencing conflict problems when we install AmyUni PDF Converter 2.10i on machines that have an HP LaserJet 3150 printer. We use the install.exe supplied with AmyUni PDF Converter to define a printer named "IAG PDF Printer". The install works fine and defines the print...
by Robert
Wed Sep 15 2004
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: cdintf210.dll replaced by a one of a previous version
Replies: 1
Views: 3949

cdintf210.dll replaced by a one of a previous version

Hello, I've had a problem recently that seem unusual the I want to draw attention to. I have 2 software kits that install AmyUni PDF Converter 2.10 but one is 2.10i and the other 2.10d. 1) If I install the 2.10i kit after installing the 2.10d kit, the cdintf210.dll in system32 directory is for the 2...
by Robert
Thu Aug 26 2004
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error Code 126 on Windows XP Embedded
Replies: 11
Views: 14726

Did you check the type of the path variable. It should be Reg_Epand_SZ. If is not, any reference to %systemroot% or other tags will not be replaced and install.exe will give you a error code 126.
by Robert
Thu Aug 26 2004
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error Code 126 on Windows XP Embedded
Replies: 11
Views: 14726

Check the post by cluzhoxsie concerning the Path environment variable.
by Robert
Wed Aug 25 2004
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error Code 126 on Windows XP Embedded
Replies: 11
Views: 14726

Hi ZakZak,

Check the following posting. This solved our problem with Error Code 126.

http://www.amyuni.com/forum/viewtopic.p ... 6&start=20
by Robert
Fri May 07 2004
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error 126 when installing printer on Windows XP
Replies: 22
Views: 83126

Thanks for the tip,

This bug has been eluding us for almost a year now. How did you figure it out ?

Regards

Robert
by Robert
Wed Jan 21 2004
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: AmyUni and FaxTalk
Replies: 1
Views: 3928

AmyUni and FaxTalk

Hello,

In the following newsletter concerning conflicts between FaxTalk 4.5 and AmyUni PDF Converter

http://www.amyuni.com/forum/viewtopic.php?t=426

one of the workarounds is to Disable FaxTalk. How is this done ?

Thanks
by Robert
Thu Sep 25 2003
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error 126 when installing printer on Windows XP
Replies: 22
Views: 83126

Hello Jose, Since I install all the files you mentioned in the directory (c:\Program Files\AmyUni) with the Install.exe the acfpdfu.dll or acfpdf.dll file should be found. When I call Install.exe from my InstallShield script I change the current directory the one containing the Install.exe to make s...
by Robert
Tue Sep 23 2003
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error 126 when installing printer on Windows XP
Replies: 22
Views: 83126

Hello Jose, Thanks for the reply. I need to have something clarified though. I install the following PDF Converter files in C:\Program Files\AmyUni and execute the Install.exe in silent mode after these files have been copied to the directory : acfpdf.dll acfpdf.drv acfpdf.inf acfpdf.txt acfpdf16.dr...
by Robert
Tue Sep 23 2003
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error 126 when installing printer on Windows XP
Replies: 22
Views: 83126

Hi Joan, This is a follow up to the installation saga on WinXP. We tried using the oemsetup.inf and on several machines with no success. When we use the install.exe we have an error code 2 followed by error code 1797. We've noticed that this happens on WinXP machine were another software installatio...
by Robert
Mon Sep 15 2003
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Error 126 when installing printer on Windows XP
Replies: 22
Views: 83126

Hi everybody, I've been doing some tests concerning this problem and I've found that this error appears on WinXP machines because XP detects that the AmyUni driver is unsigned. In the case of all drivers that are not "WinXP compatible" according to Microsoft, that is they are not digitally...
by Robert
Mon Sep 15 2003
Forum: Amyuni PDF Converter (PDF Printer Driver)
Topic: Installing Error on XP-Machine
Replies: 4
Views: 9031

Hi everybody, I've been doing some tests concerning this problem and I've found that this error appears on WinXP machines because XP detects that the AmyUni driver is unsigned. In the case of all drivers that are not "WinXP compatible" according to Microsoft, that is they are not digitally...