Package Printer application?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
spartacus
15 years ago
Hello,
Your post is a little short on detail, but I'm taking a guess that you are packaging a printer application that also installs some printer drivers.
If that is the case, it's really only the printer drivers part that you shouldn't really capture. So if the original installer allows an installation of the application without the drivers, then you should still be able to capture that installation and then amend the resulting package so that the desktop shortcuts and "features" you don't require are removed.
If the original installer won't let you install without the drivers, you could still go ahead and capture the whole thing and then remove the driver-related capture items afterwards, this is trickier but still acheivable.
Regarding the printer drivers themselves, there are plenty of notes in this forum that can help with this. You could either incorporate some logic in your main package to do the job, or have separate package for the drivers.
If the drivers are supplied with a .inf file then one method to install them is to call printui.dll from a custom action. Either Google, or perform a search in this forum, for printui.dll
Regards,
Spartacus
Your post is a little short on detail, but I'm taking a guess that you are packaging a printer application that also installs some printer drivers.
If that is the case, it's really only the printer drivers part that you shouldn't really capture. So if the original installer allows an installation of the application without the drivers, then you should still be able to capture that installation and then amend the resulting package so that the desktop shortcuts and "features" you don't require are removed.
If the original installer won't let you install without the drivers, you could still go ahead and capture the whole thing and then remove the driver-related capture items afterwards, this is trickier but still acheivable.
Regarding the printer drivers themselves, there are plenty of notes in this forum that can help with this. You could either incorporate some logic in your main package to do the job, or have separate package for the drivers.
If the drivers are supplied with a .inf file then one method to install them is to call printui.dll from a custom action. Either Google, or perform a search in this forum, for printui.dll
Regards,
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
