Topic: intelide vs pciide
I see that this is a "many-headed hydra" kind of thing, yet it must have a haircut!
------------------------------------------------------------------------------------------------------
Primarily, i would like confirmation on how this should work on NT5, with an eye towards NT6.x. This discussion doesn't yet take AHCI (msahci.inf) into consideration.
I see that intelide, a native driver, is used for Intel controllers ICH0 through ICH5 (w2k) & ICH6 (xp,2k3) by NT5. All other "unknown" pci controllers tend to use pciide, another native driver. This is accomplished via the driver mshdc.inf. Note that any Intel PCI IDE controller newer than ICH6 should natively install the pciide driver.
Add Intel's Chipset package into the mix with it's own drivers. Now we have a choice between intelide and pciide. There are drivers named ibexide.inf for instance, which generally support pciide (mask of ????ide.inf). There is also drivers named ibexid2.inf for instance, which generally support intelide (mask of ????id2.inf).
On XP sp3, intelide is "5.1.2600.5512 (xpsp.080413-2108)", 5504 bytes, and references ntoskrnl.exe {KeBugCheckEx, KeTickCount} & PCIIDEX.sys (PCI IDE Bus Driver Extension).
Pciide is "5.1.2600.0 (XPClient.010817-1148)", 3228 bytes, and references only PCIIDEX.sys.
Pciidex.sys is "5.1.2600.5512 (xpsp.080413-2108)", 24960 bytes, and references HAL.dll & ntoskrnl.exe including {KeBugCheckEx, KeTickCount}.
Both types of driver have been included in DriverPacks, since at least 2007. This has not been without issue.
I do recall that the intelide driver did cause issue for some with ICH7 controllers (changed in MS v11.07). see: http://forum.driverpacks.net/viewtopic. … 885#p37885
There have also been issues with Sysprep, and some Dell GX600 series systems, if i have read those topics correctly.
Conclusion: For NT5, i tend to think that these drivers should be archived as "intelide" and "pciide". It should be up to the individual whether or not they are installed. This would avoid any possible pitfall of their usage. It also offers an obvious bugfix should native drivers fail.
What are your thoughts?
Last edited by TechDud (2013-10-13 16:35:14)
MemTest86+ Video Memory Stress Test D-P-C Driver Latency Tester (Win7-max)