Difference between revisions of "HP drivers"
From WPKG | Open Source Software Deployment and Distribution
m |
m |
||
| Line 1: | Line 1: | ||
| − | Most HP drivers come as InstallShield packages. The installer usually have name like <code>sp<number>.exe</code>, for example, <code>sp32556.exe</code> is the name for Broadcom network drivers. | + | Most HP drivers (audio, graphics, keyboard, network, input devices etc.) come as InstallShield packages. The installer usually have name like <code>sp<number>.exe</code>, for example, <code>sp32556.exe</code> is the name for Broadcom network drivers. |
| − | + | Sometimes, it will install silently with a /s switch, i.e.: | |
sp32566.exe /s | sp32566.exe /s | ||
| − | Unfortunately, | + | Unfortunately, in most cases manual intervention is needed (i.e., using other InstallShield switches, recording the installation etc.), so there is no golden rule here. |
| + | |||
| + | Sometimes, after starting the installer, you will find an extracted MSI package in <code>%TEMP%</code>. | ||
| + | |||
[[Category:Silent_Installers]] | [[Category:Silent_Installers]] | ||
Revision as of 14:52, 3 April 2008
Most HP drivers (audio, graphics, keyboard, network, input devices etc.) come as InstallShield packages. The installer usually have name like sp<number>.exe, for example, sp32556.exe is the name for Broadcom network drivers.
Sometimes, it will install silently with a /s switch, i.e.:
sp32566.exe /s
Unfortunately, in most cases manual intervention is needed (i.e., using other InstallShield switches, recording the installation etc.), so there is no golden rule here.
Sometimes, after starting the installer, you will find an extracted MSI package in %TEMP%.