/build/static/layout/Breadcrumb_cap_w.png

.inf and .pnf files in capture

hi all,
my app is a label creator that uses a usb connected printer. basically in my setup capture i have oem0.inf and oem0.pnf in the windows\inf directory. i think that these are not needed. am i correct? can anyone give me a clear reason why these are needed, not needed.
thanks in advance

0 Comments   [ + ] Show comments

Answers (4)

Posted by: revizor 18 years ago
Third Degree Blue Belt
0
I might be totally off the base, but in my experience, .pnf files are generated by the system. I do normally keep .inf files whenever those are captured - there's sometimes useful info inside those.
Posted by: abritton 18 years ago
Senior Yellow Belt
0
Usually when you see OEM*.INF files popping up in %SYSTEMROOT%\INF, it means that Windows has installed a driver. When Windows installs a driver (always from an INF file somewhere), it copies the file to %SYSTEMROOT%\INF and gives it a new OEM based name. The PNF files are generated automatically and are basically precompiled versions of the INF files (I think).

I would say that the driver should either be separated from the software installation, or dealt with in the correct way for drivers (use the DIFX driver installation framework).
Posted by: sowjanya_230 14 years ago
Senior Yellow Belt
0
Does oemxx.inf and oemxx.pnf pairs gets created for only signed drivers while installing the driver using dpinst.exe at runtime or for un-signed drivers also they get created?

can anyone provide some info on this?
Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
have a look at this very good info from v jay READ

you can also do a search for dpinst / difxapp

lots of info on this forum
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ