SetupCopyOEMInf

SetupCopyOEMInf does not recopy the file if it finds that a binary image of
the specified INF file already exists in the INF directory with the same
name or a name of the form OEM*.INF.

My question is:
If I wanted to replace the INF file and OEM file every time installing the
driver, what method or function call I need to use in order to make this
happen?
I used CopyFile() to copy the INF file while installing but it pop up the
window asking for the DLL file and I don't want the pop up either, it
suppose to be silent install.
I also tried SetupCopyOEMInf(szInfFullPath2, NULL, SPOST_PATH,
SP_COPY_REPLACEONLY, szInfNameAfterCopy, MAX_PATH, NULL, NULL)
to replace the INF file and I got error code 0x80070002

Any help are apreciated,
Thanks,
Hannah.

Chris
Wed Oct 13 08:30:48 CDT 2004

"hdang" <hannah.dang@honeywell.com> wrote:
> SetupCopyOEMInf does not recopy the file if it finds that a binary image
> of
> the specified INF file already exists in the INF directory with the same
> name or a name of the form OEM*.INF.

When the documentation says "...if it finds a binary image...", it means
"...if it finds a file with the same content (a binary compared match)...".
That being said, the file should copy just fine if it changed. Why do you
need to always copy your file, even if it's exactly the same?

Chris

hdang
Wed Oct 13 12:00:17 CDT 2004

The reason I need to always copy my file is because I make changes to the
inf file. for example: I have the registry below in my original install inf
file
HKR, Parameters, MyNodeId, %REG_DWORD%, 0
replace the value above with
HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
Now I have an update inf file. So, when I use SetupCopyOEMInf to install
driver, it look in the inf file and find that oemxxx.PNF is existing and it
never replace with the new file, instead it keep using the old value to
install the driver and the update inf file never get to install.

Thanks for your reply,
Hannah

"Chris" <cdore.connecttech.com> wrote in message
news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
> "hdang" <hannah.dang@honeywell.com> wrote:
> > SetupCopyOEMInf does not recopy the file if it finds that a binary image
> > of
> > the specified INF file already exists in the INF directory with the same
> > name or a name of the form OEM*.INF.
>
> When the documentation says "...if it finds a binary image...", it means
> "...if it finds a file with the same content (a binary compared
match)...".
> That being said, the file should copy just fine if it changed. Why do you
> need to always copy your file, even if it's exactly the same?
>
> Chris
>
>

Chris
Wed Oct 13 13:30:47 CDT 2004

Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so should
give you the desired result.

Chris

"hdang" <hannah.dang@honeywell.com> wrote in message
news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
> The reason I need to always copy my file is because I make changes to the
> inf file. for example: I have the registry below in my original install
> inf
> file
> HKR, Parameters, MyNodeId, %REG_DWORD%, 0
> replace the value above with
> HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
> Now I have an update inf file. So, when I use SetupCopyOEMInf to install
> driver, it look in the inf file and find that oemxxx.PNF is existing and
> it
> never replace with the new file, instead it keep using the old value to
> install the driver and the update inf file never get to install.
>
> Thanks for your reply,
> Hannah
>
> "Chris" <cdore.connecttech.com> wrote in message
> news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
>> "hdang" <hannah.dang@honeywell.com> wrote:
>> > SetupCopyOEMInf does not recopy the file if it finds that a binary
>> > image
>> > of
>> > the specified INF file already exists in the INF directory with the
>> > same
>> > name or a name of the form OEM*.INF.
>>
>> When the documentation says "...if it finds a binary image...", it means
>> "...if it finds a file with the same content (a binary compared
> match)...".
>> That being said, the file should copy just fine if it changed. Why do
>> you
>> need to always copy your file, even if it's exactly the same?
>>
>> Chris
>>
>>
>
>

hdang
Wed Oct 13 16:01:56 CDT 2004

Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't give
me the rusult. It's always install the original inf file with the default
value not the updated inf file...

Hannah,

"Chris" <cdore.connecttech.com> wrote in message
news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
> Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so should
> give you the desired result.
>
> Chris
>
> "hdang" <hannah.dang@honeywell.com> wrote in message
> news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
> > The reason I need to always copy my file is because I make changes to
the
> > inf file. for example: I have the registry below in my original install
> > inf
> > file
> > HKR, Parameters, MyNodeId, %REG_DWORD%, 0
> > replace the value above with
> > HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
> > Now I have an update inf file. So, when I use SetupCopyOEMInf to
install
> > driver, it look in the inf file and find that oemxxx.PNF is existing and
> > it
> > never replace with the new file, instead it keep using the old value to
> > install the driver and the update inf file never get to install.
> >
> > Thanks for your reply,
> > Hannah
> >
> > "Chris" <cdore.connecttech.com> wrote in message
> > news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
> >> "hdang" <hannah.dang@honeywell.com> wrote:
> >> > SetupCopyOEMInf does not recopy the file if it finds that a binary
> >> > image
> >> > of
> >> > the specified INF file already exists in the INF directory with the
> >> > same
> >> > name or a name of the form OEM*.INF.
> >>
> >> When the documentation says "...if it finds a binary image...", it
means
> >> "...if it finds a file with the same content (a binary compared
> > match)...".
> >> That being said, the file should copy just fine if it changed. Why do
> >> you
> >> need to always copy your file, even if it's exactly the same?
> >>
> >> Chris
> >>
> >>
> >
> >
>
>

Ray
Wed Oct 13 18:13:03 CDT 2004

Are both drivers signed? Do they both assign the same compatibility
profile in terms of PnP ids?

hdang wrote:
> Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't give
> me the rusult. It's always install the original inf file with the default
> value not the updated inf file...
>
> Hannah,
>
> "Chris" <cdore.connecttech.com> wrote in message
> news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
>
>>Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so should
>>give you the desired result.
>>
>>Chris
>>
>>"hdang" <hannah.dang@honeywell.com> wrote in message
>>news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
>>
>>>The reason I need to always copy my file is because I make changes to
>
> the
>
>>>inf file. for example: I have the registry below in my original install
>>>inf
>>>file
>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0
>>>replace the value above with
>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
>>>Now I have an update inf file. So, when I use SetupCopyOEMInf to
>
> install
>
>>>driver, it look in the inf file and find that oemxxx.PNF is existing and
>>>it
>>>never replace with the new file, instead it keep using the old value to
>>>install the driver and the update inf file never get to install.
>>>
>>>Thanks for your reply,
>>>Hannah
>>>
>>>"Chris" <cdore.connecttech.com> wrote in message
>>>news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
>>>
>>>>"hdang" <hannah.dang@honeywell.com> wrote:
>>>>
>>>>>SetupCopyOEMInf does not recopy the file if it finds that a binary
>>>>>image
>>>>>of
>>>>>the specified INF file already exists in the INF directory with the
>>>>>same
>>>>>name or a name of the form OEM*.INF.
>>>>
>>>>When the documentation says "...if it finds a binary image...", it
>
> means
>
>>>>"...if it finds a file with the same content (a binary compared
>>>
>>>match)...".
>>>
>>>>That being said, the file should copy just fine if it changed. Why do
>>>>you
>>>>need to always copy your file, even if it's exactly the same?
>>>>
>>>>Chris
>>>>
>>>>
>>>
>>>
>>
>
>

--
../ray\..

Please remove ".spamblock" from my email address if you need to contact
me outside the newsgroup.

hdang
Thu Oct 14 11:51:57 CDT 2004

No, the drivers are not sign, yes they both assign the same compatibility
profile.
I also try :
if(SetupUninstallOEMInf (L"C:\\windows\\inf\\fteimdrv.inf",
SUOI_FORCEDELETE, NULL))
{
ShowMessage(L".......Fail uninstall fteimdrv.inf");
}
else
{
ShowMessage(L".......Fail uninstall fteimdrv.inf");
}

It always give me the fail message. What did I do wrong? Please advice...

Hannah,



"Ray Trent" <rat@synaptics.spamblock.com> wrote in message
news:uKIyxoXsEHA.3604@TK2MSFTNGP15.phx.gbl...
> Are both drivers signed? Do they both assign the same compatibility
> profile in terms of PnP ids?
>
> hdang wrote:
> > Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't
give
> > me the rusult. It's always install the original inf file with the
default
> > value not the updated inf file...
> >
> > Hannah,
> >
> > "Chris" <cdore.connecttech.com> wrote in message
> > news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
> >
> >>Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so
should
> >>give you the desired result.
> >>
> >>Chris
> >>
> >>"hdang" <hannah.dang@honeywell.com> wrote in message
> >>news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
> >>
> >>>The reason I need to always copy my file is because I make changes to
> >
> > the
> >
> >>>inf file. for example: I have the registry below in my original install
> >>>inf
> >>>file
> >>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0
> >>>replace the value above with
> >>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
> >>>Now I have an update inf file. So, when I use SetupCopyOEMInf to
> >
> > install
> >
> >>>driver, it look in the inf file and find that oemxxx.PNF is existing
and
> >>>it
> >>>never replace with the new file, instead it keep using the old value to
> >>>install the driver and the update inf file never get to install.
> >>>
> >>>Thanks for your reply,
> >>>Hannah
> >>>
> >>>"Chris" <cdore.connecttech.com> wrote in message
> >>>news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
> >>>
> >>>>"hdang" <hannah.dang@honeywell.com> wrote:
> >>>>
> >>>>>SetupCopyOEMInf does not recopy the file if it finds that a binary
> >>>>>image
> >>>>>of
> >>>>>the specified INF file already exists in the INF directory with the
> >>>>>same
> >>>>>name or a name of the form OEM*.INF.
> >>>>
> >>>>When the documentation says "...if it finds a binary image...", it
> >
> > means
> >
> >>>>"...if it finds a file with the same content (a binary compared
> >>>
> >>>match)...".
> >>>
> >>>>That being said, the file should copy just fine if it changed. Why do
> >>>>you
> >>>>need to always copy your file, even if it's exactly the same?
> >>>>
> >>>>Chris
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
>
> --
> ../ray\..
>
> Please remove ".spamblock" from my email address if you need to contact
> me outside the newsgroup.

hdang
Thu Oct 14 12:31:58 CDT 2004



No, the drivers are not sign, yes they both assign the same compatibility
profile.
I also try :
if(SetupUninstallOEMInf (L"C:\\windows\\inf\\fteimdrv.inf",
SUOI_FORCEDELETE, NULL))
{
ShowMessage(L".......uninstall fteimdrv.inf successed!!");
}
else
{
ShowMessage(L".......Fail uninstall fteimdrv.inf");
}

It always give me the fail message. What did I do wrong? Please advice...


Hannah,


> "Ray Trent" <rat@synaptics.spamblock.com> wrote in message
> news:uKIyxoXsEHA.3604@TK2MSFTNGP15.phx.gbl...
> > Are both drivers signed? Do they both assign the same compatibility
> > profile in terms of PnP ids?
> >
> > hdang wrote:
> > > Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't
> give
> > > me the rusult. It's always install the original inf file with the
> default
> > > value not the updated inf file...
> > >
> > > Hannah,
> > >
> > > "Chris" <cdore.connecttech.com> wrote in message
> > > news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
> > >
> > >>Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so
> should
> > >>give you the desired result.
> > >>
> > >>Chris
> > >>
> > >>"hdang" <hannah.dang@honeywell.com> wrote in message
> > >>news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
> > >>
> > >>>The reason I need to always copy my file is because I make changes to
> > >
> > > the
> > >
> > >>>inf file. for example: I have the registry below in my original
install
> > >>>inf
> > >>>file
> > >>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0
> > >>>replace the value above with
> > >>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
> > >>>Now I have an update inf file. So, when I use SetupCopyOEMInf to
> > >
> > > install
> > >
> > >>>driver, it look in the inf file and find that oemxxx.PNF is existing
> and
> > >>>it
> > >>>never replace with the new file, instead it keep using the old value
to
> > >>>install the driver and the update inf file never get to install.
> > >>>
> > >>>Thanks for your reply,
> > >>>Hannah
> > >>>
> > >>>"Chris" <cdore.connecttech.com> wrote in message
> > >>>news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
> > >>>
> > >>>>"hdang" <hannah.dang@honeywell.com> wrote:
> > >>>>
> > >>>>>SetupCopyOEMInf does not recopy the file if it finds that a binary
> > >>>>>image
> > >>>>>of
> > >>>>>the specified INF file already exists in the INF directory with the
> > >>>>>same
> > >>>>>name or a name of the form OEM*.INF.
> > >>>>
> > >>>>When the documentation says "...if it finds a binary image...", it
> > >
> > > means
> > >
> > >>>>"...if it finds a file with the same content (a binary compared
> > >>>
> > >>>match)...".
> > >>>
> > >>>>That being said, the file should copy just fine if it changed. Why
do
> > >>>>you
> > >>>>need to always copy your file, even if it's exactly the same?
> > >>>>
> > >>>>Chris
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >
> > >
> >
> > --
> > ../ray\..
> >
> > Please remove ".spamblock" from my email address if you need to contact
> > me outside the newsgroup.
>
>

Ray
Thu Oct 14 16:50:20 CDT 2004

What does GetLastError return in this case and the SetupCopyOEMInf file
case?

hdang wrote:
> No, the drivers are not sign, yes they both assign the same compatibility
> profile.
> I also try :
> if(SetupUninstallOEMInf (L"C:\\windows\\inf\\fteimdrv.inf",
> SUOI_FORCEDELETE, NULL))
> {
> ShowMessage(L".......uninstall fteimdrv.inf successed!!");
> }
> else
> {
> ShowMessage(L".......Fail uninstall fteimdrv.inf");
> }
>
> It always give me the fail message. What did I do wrong? Please advice...
>
>
> Hannah,
>
>
>
>>"Ray Trent" <rat@synaptics.spamblock.com> wrote in message
>>news:uKIyxoXsEHA.3604@TK2MSFTNGP15.phx.gbl...
>>
>>>Are both drivers signed? Do they both assign the same compatibility
>>>profile in terms of PnP ids?
>>>
>>>hdang wrote:
>>>
>>>>Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't
>>
>>give
>>
>>>>me the rusult. It's always install the original inf file with the
>>
>>default
>>
>>>>value not the updated inf file...
>>>>
>>>>Hannah,
>>>>
>>>>"Chris" <cdore.connecttech.com> wrote in message
>>>>news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
>>>>
>>>>
>>>>>Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so
>>
>>should
>>
>>>>>give you the desired result.
>>>>>
>>>>>Chris
>>>>>
>>>>>"hdang" <hannah.dang@honeywell.com> wrote in message
>>>>>news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
>>>>>
>>>>>
>>>>>>The reason I need to always copy my file is because I make changes to
>>>>
>>>>the
>>>>
>>>>
>>>>>>inf file. for example: I have the registry below in my original
>
> install
>
>>>>>>inf
>>>>>>file
>>>>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0
>>>>>>replace the value above with
>>>>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
>>>>>>Now I have an update inf file. So, when I use SetupCopyOEMInf to
>>>>
>>>>install
>>>>
>>>>
>>>>>>driver, it look in the inf file and find that oemxxx.PNF is existing
>>
>>and
>>
>>>>>>it
>>>>>>never replace with the new file, instead it keep using the old value
>
> to
>
>>>>>>install the driver and the update inf file never get to install.
>>>>>>
>>>>>>Thanks for your reply,
>>>>>>Hannah
>>>>>>
>>>>>>"Chris" <cdore.connecttech.com> wrote in message
>>>>>>news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
>>>>>>
>>>>>>
>>>>>>>"hdang" <hannah.dang@honeywell.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>SetupCopyOEMInf does not recopy the file if it finds that a binary
>>>>>>>>image
>>>>>>>>of
>>>>>>>>the specified INF file already exists in the INF directory with the
>>>>>>>>same
>>>>>>>>name or a name of the form OEM*.INF.
>>>>>>>
>>>>>>>When the documentation says "...if it finds a binary image...", it
>>>>
>>>>means
>>>>
>>>>
>>>>>>>"...if it finds a file with the same content (a binary compared
>>>>>>
>>>>>>match)...".
>>>>>>
>>>>>>
>>>>>>>That being said, the file should copy just fine if it changed. Why
>
> do
>
>>>>>>>you
>>>>>>>need to always copy your file, even if it's exactly the same?
>>>>>>>
>>>>>>>Chris
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>--
>>>../ray\..
>>>
>>>Please remove ".spamblock" from my email address if you need to contact
>>>me outside the newsgroup.
>>
>>
>
>

--
../ray\..

Please remove ".spamblock" from my email address if you need to contact
me outside the newsgroup.

hdang
Mon Oct 18 13:11:17 CDT 2004

For SetupUninstallOEMInf GetLastError return error code 0x80070057 (I
believed this is passing wrong parameter, but don't know how to fix it).

For SetupCopyOEMInf GetLastError return SUCCEEDED

Hannah,

"Ray Trent" <rat@synaptics.spamblock.com> wrote in message
news:unBPOfjsEHA.3152@TK2MSFTNGP14.phx.gbl...
> What does GetLastError return in this case and the SetupCopyOEMInf file
> case?
>
> hdang wrote:
> > No, the drivers are not sign, yes they both assign the same
compatibility
> > profile.
> > I also try :
> > if(SetupUninstallOEMInf (L"C:\\windows\\inf\\fteimdrv.inf",
> > SUOI_FORCEDELETE, NULL))
> > {
> > ShowMessage(L".......uninstall fteimdrv.inf successed!!");
> > }
> > else
> > {
> > ShowMessage(L".......Fail uninstall fteimdrv.inf");
> > }
> >
> > It always give me the fail message. What did I do wrong? Please
advice...
> >
> >
> > Hannah,
> >
> >
> >
> >>"Ray Trent" <rat@synaptics.spamblock.com> wrote in message
> >>news:uKIyxoXsEHA.3604@TK2MSFTNGP15.phx.gbl...
> >>
> >>>Are both drivers signed? Do they both assign the same compatibility
> >>>profile in terms of PnP ids?
> >>>
> >>>hdang wrote:
> >>>
> >>>>Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't
> >>
> >>give
> >>
> >>>>me the rusult. It's always install the original inf file with the
> >>
> >>default
> >>
> >>>>value not the updated inf file...
> >>>>
> >>>>Hannah,
> >>>>
> >>>>"Chris" <cdore.connecttech.com> wrote in message
> >>>>news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
> >>>>
> >>>>
> >>>>>Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so
> >>
> >>should
> >>
> >>>>>give you the desired result.
> >>>>>
> >>>>>Chris
> >>>>>
> >>>>>"hdang" <hannah.dang@honeywell.com> wrote in message
> >>>>>news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
> >>>>>
> >>>>>
> >>>>>>The reason I need to always copy my file is because I make changes
to
> >>>>
> >>>>the
> >>>>
> >>>>
> >>>>>>inf file. for example: I have the registry below in my original
> >
> > install
> >
> >>>>>>inf
> >>>>>>file
> >>>>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0
> >>>>>>replace the value above with
> >>>>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
> >>>>>>Now I have an update inf file. So, when I use SetupCopyOEMInf to
> >>>>
> >>>>install
> >>>>
> >>>>
> >>>>>>driver, it look in the inf file and find that oemxxx.PNF is existing
> >>
> >>and
> >>
> >>>>>>it
> >>>>>>never replace with the new file, instead it keep using the old value
> >
> > to
> >
> >>>>>>install the driver and the update inf file never get to install.
> >>>>>>
> >>>>>>Thanks for your reply,
> >>>>>>Hannah
> >>>>>>
> >>>>>>"Chris" <cdore.connecttech.com> wrote in message
> >>>>>>news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
> >>>>>>
> >>>>>>
> >>>>>>>"hdang" <hannah.dang@honeywell.com> wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>>SetupCopyOEMInf does not recopy the file if it finds that a binary
> >>>>>>>>image
> >>>>>>>>of
> >>>>>>>>the specified INF file already exists in the INF directory with
the
> >>>>>>>>same
> >>>>>>>>name or a name of the form OEM*.INF.
> >>>>>>>
> >>>>>>>When the documentation says "...if it finds a binary image...", it
> >>>>
> >>>>means
> >>>>
> >>>>
> >>>>>>>"...if it finds a file with the same content (a binary compared
> >>>>>>
> >>>>>>match)...".
> >>>>>>
> >>>>>>
> >>>>>>>That being said, the file should copy just fine if it changed. Why
> >
> > do
> >
> >>>>>>>you
> >>>>>>>need to always copy your file, even if it's exactly the same?
> >>>>>>>
> >>>>>>>Chris
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>--
> >>>../ray\..
> >>>
> >>>Please remove ".spamblock" from my email address if you need to contact
> >>>me outside the newsgroup.
> >>
> >>
> >
> >
>
> --
> ../ray\..
>
> Please remove ".spamblock" from my email address if you need to contact
> me outside the newsgroup.

Ray
Mon Oct 18 14:42:29 CDT 2004

Hmmm. Nothing obvious there. I assume the file actually exists and is in
that location...

I don't remember whether the setupapi log shows details for
SetupCopyOEMInf... anyone know? Anyway, cranking up the level on that
might possibly be a route to take.

hdang wrote:
> For SetupUninstallOEMInf GetLastError return error code 0x80070057 (I
> believed this is passing wrong parameter, but don't know how to fix it).
>
> For SetupCopyOEMInf GetLastError return SUCCEEDED
>
> Hannah,
>
> "Ray Trent" <rat@synaptics.spamblock.com> wrote in message
> news:unBPOfjsEHA.3152@TK2MSFTNGP14.phx.gbl...
>
>>What does GetLastError return in this case and the SetupCopyOEMInf file
>>case?
>>
>>hdang wrote:
>>
>>>No, the drivers are not sign, yes they both assign the same
>
> compatibility
>
>>>profile.
>>> I also try :
>>>if(SetupUninstallOEMInf (L"C:\\windows\\inf\\fteimdrv.inf",
>>>SUOI_FORCEDELETE, NULL))
>>>{
>>> ShowMessage(L".......uninstall fteimdrv.inf successed!!");
>>>}
>>>else
>>>{
>>> ShowMessage(L".......Fail uninstall fteimdrv.inf");
>>>}
>>>
>>>It always give me the fail message. What did I do wrong? Please
>
> advice...
>
>>>
>>>Hannah,
>>>
>>>
>>>
>>>
>>>>"Ray Trent" <rat@synaptics.spamblock.com> wrote in message
>>>>news:uKIyxoXsEHA.3604@TK2MSFTNGP15.phx.gbl...
>>>>
>>>>
>>>>>Are both drivers signed? Do they both assign the same compatibility
>>>>>profile in terms of PnP ids?
>>>>>
>>>>>hdang wrote:
>>>>>
>>>>>
>>>>>>Yes, I did try SetupCopyOEMInf with CopyStyle = 0 and it still didn't
>>>>
>>>>give
>>>>
>>>>
>>>>>>me the rusult. It's always install the original inf file with the
>>>>
>>>>default
>>>>
>>>>
>>>>>>value not the updated inf file...
>>>>>>
>>>>>>Hannah,
>>>>>>
>>>>>>"Chris" <cdore.connecttech.com> wrote in message
>>>>>>news:e6oSCLVsEHA.2692@TK2MSFTNGP10.phx.gbl...
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Have you tried calling SetupCopyOEMInf with CopyStyle=0. Doing so
>>>>
>>>>should
>>>>
>>>>
>>>>>>>give you the desired result.
>>>>>>>
>>>>>>>Chris
>>>>>>>
>>>>>>>"hdang" <hannah.dang@honeywell.com> wrote in message
>>>>>>>news:%23%23argYUsEHA.2316@TK2MSFTNGP12.phx.gbl...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>The reason I need to always copy my file is because I make changes
>
> to
>
>>>>>>the
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>inf file. for example: I have the registry below in my original
>>>
>>>install
>>>
>>>
>>>>>>>>inf
>>>>>>>>file
>>>>>>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0
>>>>>>>>replace the value above with
>>>>>>>>HKR, Parameters, MyNodeId, %REG_DWORD%, 0x00000007
>>>>>>>>Now I have an update inf file. So, when I use SetupCopyOEMInf to
>>>>>>
>>>>>>install
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>driver, it look in the inf file and find that oemxxx.PNF is existing
>>>>
>>>>and
>>>>
>>>>
>>>>>>>>it
>>>>>>>>never replace with the new file, instead it keep using the old value
>>>
>>>to
>>>
>>>
>>>>>>>>install the driver and the update inf file never get to install.
>>>>>>>>
>>>>>>>>Thanks for your reply,
>>>>>>>>Hannah
>>>>>>>>
>>>>>>>>"Chris" <cdore.connecttech.com> wrote in message
>>>>>>>>news:%23VDMajSsEHA.2252@TK2MSFTNGP11.phx.gbl...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>"hdang" <hannah.dang@honeywell.com> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>SetupCopyOEMInf does not recopy the file if it finds that a binary
>>>>>>>>>>image
>>>>>>>>>>of
>>>>>>>>>>the specified INF file already exists in the INF directory with
>
> the
>
>>>>>>>>>>same
>>>>>>>>>>name or a name of the form OEM*.INF.
>>>>>>>>>
>>>>>>>>>When the documentation says "...if it finds a binary image...", it
>>>>>>
>>>>>>means
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>>"...if it finds a file with the same content (a binary compared
>>>>>>>>
>>>>>>>>match)...".
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>That being said, the file should copy just fine if it changed. Why
>>>
>>>do
>>>
>>>
>>>>>>>>>you
>>>>>>>>>need to always copy your file, even if it's exactly the same?
>>>>>>>>>
>>>>>>>>>Chris
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>--
>>>>>../ray\..
>>>>>
>>>>>Please remove ".spamblock" from my email address if you need to contact
>>>>>me outside the newsgroup.
>>>>
>>>>
>>>
>>--
>>../ray\..
>>
>>Please remove ".spamblock" from my email address if you need to contact
>>me outside the newsgroup.
>
>
>

--
../ray\..

Please remove ".spamblock" from my email address if you need to contact
me outside the newsgroup.