Software Deployment

Are you sure that ghostscript.exe is installing required printer drivers ?

if I remember correctly ghostscript.exe was another requirement but not the driver itself.

Thanks a lot for your responses.
Yes you are right... Ghost-script is for another function of converting a file to PDF, it's not responsible for driver installation.
Finally we were able to segregate the driver components properly.

There were 3 to 4 files which were to be installed locally along with a bunch of registries.

Hi Karshi,

It would be nice if you could share the name of the files that you installed locally.

Ideally I would appreciate if you can share the detailed steps followed to create a working sequence for this application.

Install the driver manually on the machine and sequencing the remaining part of application should work

Thanks for ur reply.
However, i need a little help here...I tried to distinguish driver files. i copied files going to spool directory and system32 prior to sequencing. However, there are other driver related files that are installing to Installdir.do we need to seperate them as well?

we have followed the following process:
1. sequenced the application normally.
2. Compared with a picture of source and installed the left out files on the machine prior to publishing it.
3. Also. exported all the printer related registries on the machine manually.
4. Published my package.
5. Started and stopped the spooler service.

PDFPrinter appears in control panel. However if we try to print a file it does not convert it to PDF.
It shows a progress bar and queues up n task bar as pending job.

Please suggest.

Keeping the files, exporting printer registries and importing them prior to publishing the sequenced app will not work.
There will an EXE which will perform the driver installation. You need to run it prior to the publishing of your sequenced app.
Once you launch check the functionality, it should work as expected

Thanks for pointing this.
I located the component responsible for driver installation i.e ghostscript.exe.
so as suggested i finished the above tasks before sequencing the app and then published it in the similar manner.
Still it's the same behavior. i was really hoping it would work this time.