/bundles/itninjaweb/img/Breadcrumb_cap_w.png
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   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

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.
Answered 12/07/2005 by: revizor
Third Degree Blue Belt

Please log in to comment
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).
Answered 12/07/2005 by: abritton
Senior Yellow Belt

Please log in to comment
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?
Answered 05/25/2010 by: sowjanya_230
Senior Yellow Belt

Please log in to comment
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
Answered 05/25/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment