I have located the piece of info I was interested at:
http://msdn.microsoft.com/en-us/library/ms791096.aspx
If the link is broken, then search for "How setup selects drivers".
"
(Windows XP SP1 and later) For drivers with equal rank, date, and version,
Setup can select any driver.
"
Combine this information with
http://msdn.microsoft.com/en-us/library/aa477011.aspx
and
http://support.microsoft.com/kb/254078
makes me think that the setup looked into Windows\inf folder, took the oem
file from there and installed it instead of having the new one installed.
"Calin Iaru" <> wrote in message
news:22DA2FF3-CB8A-48FA-8517-...
> We have inappropriately modified some driver parameters and reflected
> those in the inf file. The problem - I think - was that the version was
> not updated and the old inf was taken from the driver store. I remember
> something about this in the wdk; will come back later with the exact
> reference if found.
>
> "Calin Iaru" <> wrote in message
> news:E500CDAB-A454-46EB-816A-...
>> It appears that CreateServiceW fails with code 0x436. I cannot see the
>> display name by using the "sc query" command. Is there any other tool
>> that can enumerate the installed drivers together with the displayed
>> names?
>>
>> "Calin Iaru" <> wrote in message
>> news:8018163A-706A-4EA5-BCFD-...
>>> I went as far as debugging netcfgx functions, but there still some code
>>> paths that need to be investigated. A strange thing happens with the
>>> dpinst wizard - the ndis driver is not signed and there are 2 warnings
>>> about this problem - first during DriverPackagePreinstallW and the
>>> second appears during UpdateDriversForPlugAndPlayDevices. Maybe I will
>>> revert the changes today - it already took a lot of time to figure out
>>> this much.
>>>
>>>
>>> "Calin Iaru" <> wrote in message
>>> news:728D4EF8-FA33-4897-9D6F-...
>>>> Here's an issue that occurred recently:
>>>> - we renamed the inf files, together with images and service names
>>>> inside those infs
>>>> - we uninstalled the previous drivers
>>>> - when installing a new one, the following error is logged:
>>>> "
>>>> #-035 Processing service Add/Delete section [MDP_NDIS.ndi.NT.Services].
>>>> #E279 Add Service: Failed to create service "mdp_ndis". Error 1078: The
>>>> name is already in use as either a service name
>>>> or a service display name.
>>>> #E033 Error 1078: The name is already in use as either a service name
>>>> or a service display name.
>>>> #E275 Error while installing services. Error 1078: The name is already
>>>> in use as either a service name or a service disp
>>>> lay name.
>>>> #E122 Device install failed. Error 1078: The name is already in use as
>>>> either a service name or a service display name.
>>>> #E154 Class installer failed. Error 1078: The name is already in use as
>>>> either a service name or a service display name.
>>>>
>>>> #I060 Set selected driver.
>>>> #I125 Installing NULL driver for "MDP\NDIS\0000FF00".
>>>> #I121 Device install of "MDP\NDIS\0000FF00" finished successfully.
>>>> "
>>>> The ndis driver is enumerated by a multifunction driver which is
>>>> enumerated by the pci bus driver. The multifunction driver had the same
>>>> errors, but due to persistence (undocumented, which is the worst kind),
>>>> the registry keys for the old driver were removed and the renamed
>>>> driver installed. I would like to take a documented approach to this
>>>> issue:
>>>> - how can I find out which display name collides and where is it
>>>> traked? if it is in the registry, then which registry key is compared?
>>>> - what is the cause of the problem and how can I prevent it in the
>>>> future? is it because the driver uninstall process left traces?
>>>> - consequently, is there an automated way to clean up these errors?
>>>>
>>>> Nothing relevant showed up in ProcMon. I used both dpinst and guided
>>>> installation with "New Hardware Wizard". ChkInf does not show any
>>>> relevant errors. Both drivers installed without problems before
>>>> renaming.
>>>>
>>>> The system is XP SP2.
>>>
Similar Threads
Linear Mode
