HP Computers and the New SATA ICH8M Drivers
Many of the new HP computers come equipped with the latest SATA drivers. This has caused a number of issues including Bluescreens and "Disk Drive Not Found" errors. For those of you who already have SATA set up in your Windows PE PXE image, you'll need to make adjustments to the Boot Disk Creator (BDC) in order to image this machine. We ran into this problem with the new HP 6910P laptop model, and more are sure to come.
This assumes Windows PE, and DS 6.5/8
The KB on adding the SATA drivers is still correct but you may find newer models that run the ICH8M or ICH9M driver, instead the ICH7M. Obviously you have to still support both, but they do not play well with each other when imaging with DS.
Originally, when you added SATA drivers, (ICH7M) you built the folder structure in the BDC under WinPE>I386>system32>diskdrivers>iaahci, per the KB article. Unfortunately, these older drivers do not work with the newer versions of SATA now appearing on the market (ICH8M & ICH9M), and vice versa.
Once the drivers are pulled down from the HP's website you need to adjust a few things:
The new files need to have the scsi=IaStor_ich8m line in TXTOEM file changed to scsi=IaACHI_ICH8M again just like before.
I was then able to get it to work by creating another (secondary) iaachi (iaachi1) folder under 'disk drivers' and by dropping the same 9 newer files from the HP website there. This process seems to allow for both kinds to be recognized when a machine boots into automation and is sent an imaging job.
Please note: You will have to make a folder for EACH instance of SATA. (i.e. diskdrivers1, diskdrivers2, diskdrivers3, etc)
Once you make these two changes, and recreate the PXE boot file, it works on both types of SATA drivers. The structure should look like this: (although I don't think the bottom level folder names matter)
WinPE Additional Files> I386> system32 >diskdrivers >iaahci >iaahci1
As far as this HP model(s) goes, you do need to disable the Native SATA mode when building the image, but make sure you re-enable it when you test push the new image to ensure it works. I found that the system will blue screen on startup if disabled and the drivers are loaded.