How to interpret setupapi.log ?
If I get the messages below in the log file.
1. Will I be sure that the driver is installed properly allthough it isn't digitally signed .
2. When a normal users logs in after installation, will he be able to use the driver without being receiving any prompts.
Command line processed: "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\PreInstaller.exe"
#E361 An unsigned or incorrectly signed file "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\deifbus.inf" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
[2010/04/14 16:28:40 3156.3]
#-198 Command line processed: "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\PreInstaller.exe"
#E361 An unsigned or incorrectly signed file "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\deifw2k.inf" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
1. Will I be sure that the driver is installed properly allthough it isn't digitally signed .
2. When a normal users logs in after installation, will he be able to use the driver without being receiving any prompts.
Command line processed: "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\PreInstaller.exe"
#E361 An unsigned or incorrectly signed file "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\deifbus.inf" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
[2010/04/14 16:28:40 3156.3]
#-198 Command line processed: "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\PreInstaller.exe"
#E361 An unsigned or incorrectly signed file "C:\Program Files\DEIF\multi-line 2 Utility Software\usb_driver\temp\deifw2k.inf" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
pjgeutjens
14 years ago
Have you seen this?
From what I read there I think you're good. However, when in doubt, test test and test some more [;)]
PJ
From what I read there I think you're good. However, when in doubt, test test and test some more [;)]
PJ
Posted by:
ikke
14 years ago
Testing is vital I know.
Thats the problem.
We don't have the hardware at our disposal. I fear that we will create a package and during pilot tests we will notice that a normal user cannot use the device immediatelly we plugin in the device.
Thats the problem.
We don't have the hardware at our disposal. I fear that we will create a package and during pilot tests we will notice that a normal user cannot use the device immediatelly we plugin in the device.
Posted by:
pjgeutjens
14 years ago
We don't have the hardware at our disposal. I fear that we will create a package and during pilot tests we will notice that a normal user cannot use the device immediatelly we plugin in the device.
That's what pilot tests are for [:D]. anyway, doesn't seem like you have much choice. Maybe you can suggest a field test to your client in light of validation.
Posted by:
anonymous_9363
14 years ago
If the package is for internal consumption, i.e. within your organisation, why not sign the driver yourself? There's a ton of stuff in the archives about driver-signing.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.