PNP Driver overwrites oem0.inf
I am working on an XP SP2 image, and trying to install some hardware drivers. Whenever I use the PNP Driver method from the sticky, or use the DIFxAPP method, everytime the device installs, it installs as c:\windows\inf\oem0.inf and oem0.pnf instead of using the next number available. So if I install more device drivers, it just overwrites oem0 again, causing it not to detect the devices when they are plugged in. If I make all of the existing oem* files read-only, then it will go to the next available number in the list.
This actually is also happening without my package, if I just use the Add Printer wizard, and point to the driver files, it will again make it oem0, so I don't think it is a problem with my packaging, but possibly with XP or our Image.
Has anyone seen this before?
Also with the PNP Driver method, it looks like one of the parameters of SetupCopyOEMInf is to set the destination inf filename, but I have been unsuccessful in getting that to work. That would work for me, since I could control the name. There is info on the parameters here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/setup/setupcopyoeminf.asp
Anyone ever seen or used this before?
Thanks!
This actually is also happening without my package, if I just use the Add Printer wizard, and point to the driver files, it will again make it oem0, so I don't think it is a problem with my packaging, but possibly with XP or our Image.
Has anyone seen this before?
Also with the PNP Driver method, it looks like one of the parameters of SetupCopyOEMInf is to set the destination inf filename, but I have been unsuccessful in getting that to work. That would work for me, since I could control the name. There is info on the parameters here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/setup/setupcopyoeminf.asp
Anyone ever seen or used this before?
Thanks!
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
kkaminsk
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.