Prev: INF for Ports class CDC USB device using usbser.sys fails DTM
Next: Access permission for registry in Windows 7
From: mpv on 29 Apr 2010 10:19
Hi,

"JoeB" <JoeB(a)discussions.microsoft.com> schreef in bericht
news:6E27876C-E555-4795-8DB7-5ACDA8903CE6(a)microsoft.com...
>
> you mentioned using a WISE script, is there any
> way you could share that or how it works?
>
Wise InstallBuilder is (or was) a tool for software distribution that allows
you to write setup programs for Windows applications.
It was bought by Altiris, and then by Symantec, and is now called Wise
Package Studio.
I have never upgraded from the 1998 version, as the Wise scripts are now
deprecated in favor of Windows installation script. The latest version only
adds stuff like a 64 bit test to the Wise scripts, which was not very hard
to write myself as a straight DLL function.
To install drivers (before plugging in the device), you should look into
Microsoft's DPInst, which does most of the work. Your script just copies the
necessary files and starts DPinst, that's basically it.

The issue with WinUSB is that it is an exception in the device driver field.
Being a ready made driver, it should not be that hard to use it, but there
are many pitfalls in the process, with lots of imperfect documentation.
I can understand that the hardcore driver people in this forum think it is
somewhat uninteresting compared to writing your own driver, and the signing
business is a lot of red tape.
If have, however, some difficulty reading in this forum that you need WHQL
when using WinUSB on 64 bit Windows, that is all. In my experience, you can
easily do without.

Regards, Matt


From: Tim Roberts on 30 Apr 2010 23:11
"mpv" <nospam(a)forget.it> wrote:
>
>To install drivers (before plugging in the device), you should look into
>Microsoft's DPInst, which does most of the work. Your script just copies the
>necessary files and starts DPinst, that's basically it.

Right. I have an NSIS installer that does that: I copy all of the files
(including dpinst) to a folder under Program Files, then launch dpinst.
Pretty painless, actually, and I even get an uninstall ability.

>The issue with WinUSB is that it is an exception in the device driver field.
>Being a ready made driver, it should not be that hard to use it, but there
>are many pitfalls in the process, with lots of imperfect documentation.
>I can understand that the hardcore driver people in this forum think it is
>somewhat uninteresting compared to writing your own driver, and the signing
>business is a lot of red tape.
>If have, however, some difficulty reading in this forum that you need WHQL
>when using WinUSB on 64 bit Windows, that is all. In my experience, you can
>easily do without.

That's true. The driver file itself has already been signed by Microsoft,
so there are no KMCS issues. The extent to which you go depends on your
needs. If you do not sign the CAT at all, you get the dreaded "CAUTION!
This driver is unsigned, the world's about to end" dialog. For some
people, that's just fine. If you sign the CAT with your own certificate,
you get the "Do you trust this publisher?" warning, which is not so bad. If
you submit for the WHQL signature, there's no dialog at all.

It depends on what your marketing department wants.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
First  |  Prev  | 
Pages: 1 2 3
Prev: INF for Ports class CDC USB device using usbser.sys fails DTM
Next: Access permission for registry in Windows 7