Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SATA ICH9 Drivers: Windows XP Driver Injection Script

Updated: 19 Mar 2008 | 13 comments
andyolly's picture
+2 2 Votes
Login to vote

I have taken the basis of a Microsoft workaround to take the out-of-the-box shipped XP IDE drivers and inject them into an image format to prevent the well recognized BSOD on boot-up.

This simple script/package will copy the required drivers into the correct area for XP to detect them and inject the required registry keys for the O/S to boot trouble free with SATA native mode enabled on the current generation of HP laptops.

Since posting the SATA script for the HP range of laptops there have been requests for the Dell ICH9 series of drivers, This is them.

I have been unable to test them as I have no ICH9 hardware so please ensure you run this on test hardware first and provide feeback on this thread, or message me directly.

As later generations of the drivers are released I will try and keep this updated to include the new drivers.

For history and how I got to this please see my ICH8 thread: http://www.symantec.com/connect/download/2834/sata...

License: AJSL
By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License
Support: User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab.
download Filed Under:
Group Ownership:

Comments

that2bad's picture
09
Jun
2008
0 Votes 0
Login to vote

Yes, thank you for

Yes, thank you for this.
Worked fine.

rakesh's picture
26
Jul
2008
0 Votes 0
Login to vote

Will this solution will work for Dell Models

Just curious, is this package is going to work for Models like Dell Latitude 630 and Optiplex 755.

Please let us know. I will also try and keep you guys posted.

rakesh's picture
28
Jul
2008
1 Vote +1
Login to vote

Lattitude D630 - all well

Great one man, i was able to successfully boot Dell Lattitude D630, not sure about the Optiplex 755 as the model is not available.

If anybody get chance please let me know.

tpham's picture
01
Aug
2008
1 Vote +1
Login to vote

D630 WinPE Boot

I still not able to see the hard drive on the D630. Can you show me how to add these into Altiris BootWizard? Much appreciated.

John Atkins's picture
01
Aug
2008
1 Vote +1
Login to vote

Hopefully this will help

Adding mass storage drivers for Windows PE article 20566
https://kb.altiris.com/display/1/index.asp?c=&cpc=...

How do I add mass storage drivers to the WinPE pre-boot OS files for use in Boot Disk Creator? article 19067
https://kb.altiris.com/display/1/kb/article.asp?ai...

John Atkins
Advanced Client Services Engineer
LifeWay Christian Resources
http://www.lifeway.com

TN User Group Membership Director
 

tpham's picture
01
Aug
2008
0 Votes 0
Login to vote

It worked

Thank you for your replied, That solved my problems.

Gamer1971's picture
28
Jul
2008
1 Vote +1
Login to vote

Awesome!!!

Very much appreciated. I've got a 6535b early eval and was encountering that darn bsod. I found the ICH9 drivers but must not have been applying them correctly. This is great. Thank you.

scsummers's picture
28
Aug
2008
1 Vote +1
Login to vote

Optiplex 755 Registry Settings

We recently switched to Dells and I had the BSOD issues with the 755 trying to integrate it with our current image. I used the posted .zip file in this thread but it did not work for me. I had the factory image so I trolled through the registry and this is what ended up working for me.

I also had to run the install for the Chipset utility afterwards to get the proper USB, etc. drivers installed:

http://support.dell.com/support/downloads/format.a...

Hope this helps.

==Begin Registry entries:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2653&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2681&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2682&cc_0104]
"Service"="iaStor"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c1&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c3&cc_0104]
"Service"="iaStor"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c5&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c6&cc_0104]
"Service"="iaStor"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2821&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2822&cc_0104]
"Service"="iaStor"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2829&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_282a&cc_0104]
"Service"="iaStor"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2922&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_5029&cc_0106]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

negal's picture
28
Aug
2008
0 Votes 0
Login to vote

Forgive me if I am off the

Forgive me if I am off the mark on this, but surely it is easier to script the sata driver injection within the imaging job using Firm Copy after image has been downloaded to target pc, i.e.
firm.exe -recurse copy .\drivers\Sataxxx PROD:\Drivers\SATAxxx

And then make sure the Sysprep OEMPnPPath contains this c:\driver\Sataxxx path

That should take care of it, surely.

brinedoller's picture
27
Oct
2008
0 Votes 0
Login to vote

ICH9M drivers

Ok, I'm new to this, and maybe I'm doing it a bit different, but...

I created my boot disk with the new drivers and went to image my Lenovo T500. The imaging IMMEDIATELY fails with the message below:

Error description:
The disk read or write operation referenced an invalid location.
(Note: Current volume is NTFS from source slot 1.)

==================== Technical details ====================

Logfile = created Mon Oct 27 22:49:45 2008
Build = RDEPLOY.EXE 6.5 (6844)
Cmdline = F:\RDEPLOY.EXE

Status = 30 (0x1e)
Source file = imglib\disk\disk.h
Line number = 239 (0xef)
Stack trace = 0x78093e 0x85e97a 0x89e401 0x89d60c 0x85c1ad 0x77d377 0x717067 0x7190a1 0x6b505d 0x6f8b9a 0x7ba95b 0x6f6f53 0x6b2fff 0x6e07c9 &Known=0x713980
Logical block address = 312600440 (0x12a1e778)
Sector count = 112 (0x70)
Note = Current volume is NTFS from source slot 1.
Imaging library revision = 6844 (dos-x86-release build, Fri Apr 14 14:04:10 2006)

The drive is then inaccessible. What is being done to the drive at that point?

Is this the image or is there something wrong with the drivers on the boot disk? The only way I can get it to work is to reinstall Windows, apply the drivers thru the F6 install and then the image will come down. I'm so confused . . .

Thanks for any help!

Stevo77's picture
03
Feb
2009
0 Votes 0
Login to vote

Where do I

Hi

Could someone please tell me where I run this scrip? Do I add it to the deployment job I have on DS after it has copied the image but befor it reboots?

mike_plichta's picture
23
Feb
2009
0 Votes 0
Login to vote

where to run the script

when you setup the imaging job, there is an option to do additional tasks after the imaging task. I believe you'd want to do a file copy job, and the kick off the copy.bat included in the zip file.

If it all works right, it should image the computer and immediatly run the scripts before the computer reboots or the agent exits.

Juliano Costa's picture
20
Apr
2011
0 Votes 0
Login to vote

thanks, problem solved. 

thanks, problem solved.