WinUSB on Vista 64

Hi,

I am trying to install the winusb driver to use a device on Vista 64.
I have followed the Microsoft publications:
"How to use WinUSB to Communicate with a USB Device" and
"Kernel-Mode Code Signing Walkthrough"

I have adapted the .inf file from the one described in the HowTo. I have the
amd64 and i386
subdirectories with their respective coinstallers in place.
This all works fine on 32 bit XP and 32 bit Vista.

On 64 bit XP, it works after specifying the path to WinUSBCoInstaller.dll in
a dialog that
appears after starting the wizard from the device manager.

For 64 bit Vista, I have generated a .cat file from the .inf, and
test-signed it
in the described way, following the Contoso example from the Walkthough. I
have put the
filename of the .cat file in the .inf file.

Next, when installing in Test Mode, with the wizard from the device manager,
I keep getting a
file not found error.
If I check the error in \windows\inf\setupapi.dev.log the error reads:

"The driver package has a reference to a missing file. File name =
WinUSBCoInstaller.dll,
Error = 80070002"

This message is obviously incorrect, as the file really is present in the
amd64 subdirectory.

Since these paths work fine with XP-32 and Vista-32, and so-so in XP-64, I
am starting to
believe something else is wrong with the .inf file from the HowTo.

I do not know whether this might be caused by the (incorrect) code signing
in testmode.
The \windows\inf\setupapi.app.log file lists many signing errors, but maybe
these are generated
anyway, in spite of being in Test Mode.

Very confusing !

Is there anyone with experience installing WinUSB on Vista 64 that can point
me in the right way?

Regards, Matt

"mpv" <> wrote:

>Hi,
>
>I am trying to install the winusb driver to use a device on Vista 64.
>I have followed the Microsoft publications:
>"How to use WinUSB to Communicate with a USB Device" and
>"Kernel-Mode Code Signing Walkthrough"
>
>I have adapted the .inf file from the one described in the HowTo. I have the
>amd64 and i386
>subdirectories with their respective coinstallers in place.
>This all works fine on 32 bit XP and 32 bit Vista.
>
>On 64 bit XP, it works after specifying the path to WinUSBCoInstaller.dll in
>a dialog that
>appears after starting the wizard from the device manager.
>
>For 64 bit Vista, I have generated a .cat file from the .inf, and
>test-signed it
>in the described way, following the Contoso example from the Walkthough. I
>have put the
>filename of the .cat file in the .inf file.
>
>Next, when installing in Test Mode, with the wizard from the device manager,
>I keep getting a
>file not found error.
>If I check the error in \windows\inf\setupapi.dev.log the error reads:
>
>"The driver package has a reference to a missing file. File name =
>WinUSBCoInstaller.dll,
>Error = 80070002"
>
>This message is obviously incorrect, as the file really is present in the
>amd64 subdirectory.

Yes, but does your INF file include the amd64 directory name when referring
to the file?
--
Tim Roberts,
Providenza & Boekelheide, Inc.

"Tim Roberts" <> schreef in bericht
news:...
> "mpv" <> wrote:
>
>>
>>This message is obviously incorrect, as the file really is present in the
>>amd64 subdirectory.
>
> Yes, but does your INF file include the amd64 directory name when
> referring
> to the file?
> --
> Tim Roberts,
> Providenza & Boekelheide, Inc.

Hi Tim,

Thank you for your answer. In the mean time, I have succeeded by trial and
error to get the driver to install, and my test program even works now
(although only for 32bit at present, the 64bit version still has some
problems).
I had to copy the coinstallers from the amd64 subdirectory up to the
subdirectory that the .inf file itself is in, which is one level up. The
..inf file really refers to these subdirectories, the same way for amd64 as
it does for i386. This is all straight from the example in the HowTo.

So there really is a problem in both 64 bit windows versions with handling
this .inf file. Either they do not support these subdirectories at all, or
they look in the wrong place.

This is probably because all this is rather new ground. I have seen more
glitches:
- My 64 bit test program did not startup at all after linking without
errors, but gave an error claiming the executable was incorrect: "Error
executing program". Installing VS2008 SP1 miraculously fixed this, which is
the first time I actually see a program of my own dramatically be fixed by a
fixpack.
- The 'Test Mode' message in the four corners of the screen that you see
when installing testsigned device drivers in Vista 64 did not appear in the
Windows Classic theme, only in the Windows Vista theme, which made me miss
it at first.
- the vcvarsam64.bat script generated some double backslashes in the path,
this is also fixed in SP1.

Regards, and thanks again.

Matt

> - My 64 bit test program did not startup at all after linking without
> errors, but gave an error claiming the executable was incorrect: "Error
> executing program". Installing VS2008 SP1 miraculously fixed this, which is
> the first time I actually see a program of my own dramatically be fixed by a
> fixpack.

Try using WDK to build user-mode 64bit app. It has limited MFC library, but for simple UI and UI-less user mode code it is great.

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com