You are not logged in. Please login or register.
Active topics Unanswered topics
Search options
Hey there Bâshrat the Sneaky. I work for a financial company in new york. Pretty much every laptop we buy these days has HDD protection built in. The drivers are for the accelerometer and then there are control panel applets to control when it kicks off protection (i.e. parks the HD read head). Biometrics are less common but still making major inroads in business here.
The specific laptop I was building was an HP nc6400 series. All the drivers are available off HPs website. I'd like to thank you though for all your hard work with the driverpacks. It makes my build system very clean (single PXE/RIS image across all my desktops and notebooks) and can build on everything I can put my hands on. If you're thinking of integrating extra drivers into the mass storage pack, feel free to e-mail me and I can run tests against my systems.
- Rickie
Thanks for the reply. I wound up just putting the additional driver subdirectories under $1\D in order to have devpath automatically add them. 
Easier to work with when you're debugging drivers since nLite each time would be a pain.
- Rickie
Hi. I'm running a RIS based install and integrated Bâshrat the Sneaky using Method 2. This uses the DevicePath registry key to find all the drivers during the setup phase. Since I have additional drivers (i.e. biomethic, hdd shock protection, etc) that had worked previously using the OemPnPDriversPath= sif entry, I was wondering if there was a clean way to append these paths to the DevicePath folder during the installation phase so that it locates these drivers (it seems to ignore the OemPnPDriversPath sif field when method 2 is used). Any help would be greatly appreciated.
- Rickie
Posts found [ 3 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.009 seconds, 5 queries executed ]