Difference between revisions of "HP drivers"
From WPKG | Open Source Software Deployment and Distribution
m |
m |
||
Line 7: | Line 7: | ||
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. | 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. | ||
+ | |||
+ | Most HP installers save its data into C:\SWSetup. | ||
Sometimes, after starting the installer, you will find an extracted MSI package in <code>%TEMP%</code>. | Sometimes, after starting the installer, you will find an extracted MSI package in <code>%TEMP%</code>. |
Revision as of 15:00, 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.
Most HP installers save its data into C:\SWSetup.
Sometimes, after starting the installer, you will find an extracted MSI package in %TEMP%
.