Problems with AHCI mode and IDE mode when deploying images

I have been working on a project to get MDT 2010 deployed and working in production for a couple of months now.  All was going great until the new HP Elitebook 8440p came along.  We had been changing all of our laptops to IDE Emulation rather than AHCI (or "SATA Native") because XP would not install and that was the instructions given by the HP support staff at the time.  It was working fine for us like that until we got the 8440p model.  No matter what I did, I could not install the audio driver.  The driver provided by HP, the IDT High Defintion Audio Codec driver refused to install saying that the software did not match the hardware.  Even when HP sent me their CDs for both the OS and the drivers, they didn't work.  That's when I decided to slipstream SATA drivers into the WIndows installation and change it to AHCI and give it a go.  Lo and behold, the audio worked!  So now I changed my 6930p and 6710b test machines to AHCI and deployed the image - now the problem that the 8440p had is gone, the 6930 and the 6710 have picked it up!  Now they sound wont work for them either, and same as with the 8440, you cant install it either, no matter what you do.  So I thought to self "Self, perhaps you could switch the 6930p and the 6710b back to IDE emulation and deploy the image, and since its not in AHCI mode, the SATA drivers on XP install surely isn't causing the problem - and everything will be great!"  Wrong.  I switched them back to IDE emulation, and again, same thing - no sound, nothing.  So the computer I spent a week on trying to get working properly is working, now the ones I had working AREN'T.  If I use the other image that doesn't work for the 8440p, it still works fine for the other 2 if they are switched back to IDE.

What in the world am I supposed to do?  Any ideas?
Archie314Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

FayazCommented:
Download the latest BIOS update for relevant models and upgrade it.  Then install windows, that should resolve the issue.
0
Archie314Author Commented:
The problem with that is 1. the drivers were downloaded very recently (in the past couple of months) for the 6930p and the 6710b, so that is fairly new.  And 2, we are hoping to deploy these images over the network on computers that won't have an OS on them and will be drop shipped from our vendor, so no way to get a BIOS update on it before hand.
0
Archie314Author Commented:
Now my HP engineer is saying I need to slip stream the drivers for the SATA drive AND the chipset into the CD.  This will get pretty annoying around the third or fourth computer I do, and the size of the install CD is going to get huge.  I can't believe there isnt a better way to do this.
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

FayazCommented:
I did personally worked and resolved similar issue with the above mentioned models;
You need to upgrade the BIOS and include relevant drivers in your instellation media.  You can find required BIOS and Audi drivers from HP's site.  Chnaging the SATA mode to Native is only a work-arround and that skipps the SATA features.  
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FayazCommented:
I expect the user to accept the input here as that was the solution.
0
Archie314Author Commented:
I am satified with Fayez's response, as this fixed my issue.  I put the BIOS drivers in to MDT and it worked great.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.