Add 82801EB Ultra ATA to WinXP RTM Sysprepped image

[Paul]

Hi,

I have a client, for whom I have created a Windows XP RTM Sysprepped
image for all their hardware. They ordered a new PC with Serial ATA
drives that connect to a Intel(R) 82801EB Ultra ATA Storage Controller
which isn't natively supported. I have added the line in the
sysprep.inf to locate the drivers but I still get a Stop 7B error.
Following is what I've put in the sysprep.inf:

[SysprepMassStorage]
PCI\VEN_8086&DEV_24D1=c:\sysprep\pnpdrvrs\intel\ich5ide.inf
PCI\VEN_8086&DEV_24DB=c:\sysprep\pnpdrvrs\intel\ich5ide.inf

Note: Installing SP1 or SP2 is not an option for this client.

What am I doing wrong here?

Rgds

Paul

 

[Carey Frisch [MVP]]

Install SP2 for Windows XP. Why is "installing SP1 or SP2 is not an
option for this client"?

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Get Windows XP Service Pack 2 with Advanced Security Technologies:
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

-------------------------------------------------------------------------------------------

:

| Hi,
|
| I have a client, for whom I have created a Windows XP RTM Sysprepped
| image for all their hardware. They ordered a new PC with Serial ATA
| drives that connect to a Intel(R) 82801EB Ultra ATA Storage Controller
| which isn't natively supported. I have added the line in the
| sysprep.inf to locate the drivers but I still get a Stop 7B error.
| Following is what I've put in the sysprep.inf:
|
| [SysprepMassStorage]
| PCI\VEN_8086&DEV_24D1=c:\sysprep\pnpdrvrs\intel\ich5ide.inf
| PCI\VEN_8086&DEV_24DB=c:\sysprep\pnpdrvrs\intel\ich5ide.inf
|
| Note: Installing SP1 or SP2 is not an option for this client.
|
| What am I doing wrong here?
|
| Rgds
|
| Paul

 

[Paul]

I knew I'd get that They have some in house mission critical
applications that will not work in that environment. They are working
on upgrading the applications. And yes we've tried the Application
Compatability suite with no luck. You don't want to know what we have
tried to get this thing working under SP1 or SP2.

Can I get the 82801EB controller to be recognised by Sysprep as a
MassStorageDevice for Windows XP RTN?

 

[Rafael]

I ran into a similar situation with at Dell Precision 370 and I was able to
use the image by switching the BIOS controller setup section to
"Combination". At that point Windows XP SP2 was able to boot up normally.

Rafael

I knew I'd get that They have some in house mission critical
applications that will not work in that environment. They are working
on upgrading the applications. And yes we've tried the Application
Compatability suite with no luck. You don't want to know what we have
tried to get this thing working under SP1 or SP2.

Can I get the 82801EB controller to be recognised by Sysprep as a
MassStorageDevice for Windows XP RTN?

Install SP2 for Windows XP. Why is "installing SP1 or SP2 is not an
option for this client"?

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User
Microsoft Newsgroups

Get Windows XP Service Pack 2 with Advanced Security Technologies:
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

-------------------------------------------------------------------------------------------

:

| Hi,
|
| I have a client, for whom I have created a Windows XP RTM Sysprepped
| image for all their hardware. They ordered a new PC with Serial ATA
| drives that connect to a Intel(R) 82801EB Ultra ATA Storage Controller
| which isn't natively supported. I have added the line in the
| sysprep.inf to locate the drivers but I still get a Stop 7B error.
| Following is what I've put in the sysprep.inf:
|
| [SysprepMassStorage]
| PCI\VEN_8086&DEV_24D1=c:\sysprep\pnpdrvrs\intel\ich5ide.inf
| PCI\VEN_8086&DEV_24DB=c:\sysprep\pnpdrvrs\intel\ich5ide.inf
|
| Note: Installing SP1 or SP2 is not an option for this client.
|
| What am I doing wrong here?
|
| Rgds
|
| Paul

 

[Renee]

Paul here is a good example of what needs to be done...

http://greenmachine.msfnhosting.com/READING/addraid.htm

 

[p.langton]

Hi Renee,

Thats is for an unattended installation, I'm doing sysprepped
installations...

 

[Paul]

Hi Rafael,

I have no problems getting my image to work with SP1 or SP2, I don't
have to change the BIOS settings at all. My issue is that this isn't
recognised as a masstoragedevice with Windows XP RTM (i.e. no service
pack). I tried adding what I posted above to the sysprep.inf with no
luck. As soon as I upgrade to SP1 or SP2 it works without me having to
do anything at all, but sadly thats not that much use to me.

Rgds

Paul

 

[Renee]

Hi Paul,

I'm still up to my derierre with this myself and I've been thinking about your problem today. Believe I have been.

I had some realizations. I found myself wondering if your problem can be fixed in an image for several reasons.

PNP is one thing in an image. Adding support for new PNP devices is quite another. Often existing drivers are OK and sometimes they aren't. But I was thinking about the phase of system generation in which all of this occurs and what it's all for.

Non-specifically this is all for system configuration, becoming more specifiic it's for:

1.) Recognizing a piece of hardware and if needed loading a driver
2.) If further required, altering the registry for necessary datastructures for additional support, an example might be a miniport.

These things are managed by the inf files and what the support they supply. I doubt your image has that support. Right now, I'm trying to get install support for a plextor 712-SA and the codes are not in the inf files.

It's not as simple as adding a code to an inf file in your image I don't believe. I believe that would become incompatible with their pnf files, the pre-compliled images.

All this lead me to wonder, since there isn't any support in your image, whether or not your going to be able to do this in an image.

I did run across a method to do this on two running systems. You have to take the new systems hard drive to a system that does not have that hardware (or disable the specific piece of hardware on the new system).

Then you a apply a rather massive path to the registry and it also looked as if they also applied pathes to the drivers too... in the same .reg file.

At any rate, the knowledge base related to an F8 stop in the HAL (Hardware abstraction layer)... all of this stuff is interelated I know that's not the exact error that you are seeing but the underlying problems are the same.

At any rate, after thinking it over, I found myself wondering if it was going to be possible for you to alter that image to get what you need. I fear you may have to regenerate that image.

That Knowledgebase article is located at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314082




Renee