Ok, got this to work just fine on a E-6500
 
BUT, I noticed that if I take the hard drive out of a 6500, and put it
in a 6400, it will still BSOD.  With all the D-Series of Dell, or
ATA/Non AHCI Dells I guess, I could move hard drives to all different
types of hardware, no problem.  Great if a user's D630 dies, and you
need to give them a D830 spare, etc...  Plop it in, and good to go.
 
Any way around this?  Or does AHCI complicated things so much that I am
asking too much...   Perhaps I could dump down the spare machines to ATA
to get things rolling....
 
tia,
 
Sam
 

________________________________

From: johonn2 _ [mailto:[email protected]] 
Sent: Wednesday, December 31, 2008 6:19 AM
To: NT System Admin Issues
Subject: Re: AHCI Sata and sysprep



Alright,

I was wrong i do have "&CC_0106" included but looking at the sysprep
def. turned a light bulb on.  The drivers dell has for downloads do NOT
work.  You have to get them from Intel.  Yes i was stuck on that too
which is why i commented it in the sysprep file..   

I am using this version for the E6400

; **    Filename:  iaStor.INF
; **    Revision:  Version 8.6.0.1007
; **    Date:      09/12/2008
; **    Abstract:  Windows* INF File for Intel(R) Matrix Storage Manager
Driver
------------------------------------------------------------------------
--------------------------------------------
; **    Filename:  iaAHCI.INF
; **    Revision:  Version 8.6.0.1007
; **    Date:      09/12/2008
; **    Abstract:  Windows* INF File for Intel(R) Matrix Storage Manager
Driver
------------------------------------------------------------------------
---------------------------------------------

Sysprep file

;Dell E6400
;Get drivers from Intel not Dell
*PNP0600.DeviceDesc=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_2681&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_27C1&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_27C5&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_2821&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_2829&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_2922&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_2929&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_3A02&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_3A22&CC_0106=C:\Drivers\storage\E6400\iaAHCI.inf
PCI\VEN_8086&DEV_2682&CC_0104=C:\Drivers\storage\E6400\iaStor.inf
PCI\VEN_8086&DEV_27C3&CC_0104=C:\Drivers\storage\E6400\iaStor.inf
PCI\VEN_8086&DEV_27C6&CC_0104=C:\Drivers\storage\E6400\iaStor.inf
PCI\VEN_8086&DEV_2822&CC_0104=C:\Drivers\storage\E6400\iaStor.inf
PCI\VEN_8086&DEV_282A&CC_0104=C:\Drivers\storage\E6400\iaStor.inf
;END Dell E6400


FYI...

XP SP3 changes the way it handles the account being sysprep under.  If
you are like us and use the admin account and expect that to be copyied
over to your default profile during sysprep then you have to add
"UpdateServerProfiledirectory=1" into the [Unattended] section.



Bob
------------------------------------------------------------------------
------------------------------------------------


On Tue, Dec 30, 2008 at 4:29 PM, Phil Brutsche <[email protected]>
wrote:


        On my machines the non-AHCI SATA would not work if I didn't put
in the
        &CC_0106 at the end of the PCI ID.
        
        To be on the safe side I ALWAYS put the device IDs in
sysprep.inf
        EXACTLY the way they were in the driver .inf.
        
        I see I'm not the only one to suspect that putting
        "BuildMassStorageSection = YES" in there will override your
custom
        SysprepMassStorage section ;)
        

        Johonn2 wrote:
        > I finished my sysprep for both the E6400 AHCI and IRRT and the
Dell
        > OP760 series late last month.  I believe you need to drop the
"&CC_0106"
        > on it but I would have to look at mine to know for sure.  I am
not in
        > the office today so if someone else does not help out by then,
then I
        > will post it tomorrow.  Also I may be wrong again but
        > "BuildMassStorageSection = YES" I believe will overwrite your
custom
        > [SysprepMassStorage].
        
        
        --
        
        Phil Brutsche
        [email protected]
        
        
        ~ Finally, powerful endpoint security that ISN'T a resource hog!
~
        ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
        


 

 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to