Jump to content

Recommended Posts

Posted

Hello

I've noticed that INF update for intel chipset contains subdirectory SP (with small remark in readme.txt - "The sub directories (e.g. SP) contains special INFs."). When I ran diff over, for example, esb2ide.inf and esb2id2.inf, the files turn out to be almost identical (referencing different cats and intelide.sys in case of SP).

How, if at all, should this directory be approached from perspective of sysprep or cd integration ?

Is it safe to ignore SP subdir, and just supply the path to main directory (xp for instance) in OemPnPDriversPath ? Or maybe should I move "special" cats and infs for the main directory ?


Posted

check the exact device id in inf with us system spec

then u can add them or not

however it desnt cause any conflict with windows setup

as it select the most appropriate inf containg the device in u r system

Posted

IDs are the same. This is just a separate directory with a few inf/cat files. From what I understand, they are chosen by intel's installer, depending on the situation (what already is installed). Manually, it seems to be up to me. The only differences in all the files are:

-CatalogFile=ich6ide.cat

+CatalogFile=ich6id2.cat (depends on inf)

-IfInstalledDriverFile=pciide.sys

+IfInstalledDriverFile=intelide.sys

-Needs=pciide_Inst

+Needs=intelide_Inst

-Needs=pciide_Inst.Services

+Needs=intelide_Inst.Services

Either way, I'll try with both and see how it goes.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...