UltraVNC Mirror Driver 1.00.22: Signed or Unsigned?
Hi everyone,
I am trying to repackage the UltraVNC Mirror Driver 1.00.22 with Wise Package Studio 7.0 SP3. I am following the guidance from these URLs:
However, if I try to install the driver manually using devcon.exe for testing:
[blockquote][font="courier new"]devcon.exe install mv2.inf mv_hook_display_driver2
[/blockquote]... I get this warning message, which suggests that the driver is unsigned:
Can anyone explain what is happening here? Is it because it's not signed by Microsoft themselves (i.e., when I inspect .cat files on my own computer, they all seemed to be signed by Microsoft Windows Hardware Compatibility Publisher)? If so:
I am trying to repackage the UltraVNC Mirror Driver 1.00.22 with Wise Package Studio 7.0 SP3. I am following the guidance from these URLs:
- http://www.symantec.com/connect/articles/how-package-signed-device-driver-using-wise-package-studio
- http://itninja.com/question/how-do-you-roll-out-new-machines?0873
- mv2.cat
- mv2.dll
- mv2.inf
- mv2.sys
However, if I try to install the driver manually using devcon.exe for testing:
[blockquote]
[/blockquote]... I get this warning message, which suggests that the driver is unsigned:
Can anyone explain what is happening here? Is it because it's not signed by Microsoft themselves (i.e., when I inspect .cat files on my own computer, they all seemed to be signed by Microsoft Windows Hardware Compatibility Publisher)? If so:
- Does this mean that the vendor provided .cat file is essentially useless?
- How does creating and self signing your own your own .cat file (as suggested in http://itninja.com/question/how-do-you-roll-out-new-machines?0873) get around this?
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
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.