Prev: Parsing devices from setup classes
Next: size of device context limit ?
From: G�nter Prossliner on 16 Apr 2010 04:12
Hello Mike!

> The first question is whether you know that the XP driver will work
> on Win 7?

I don't. But as I read various times here and in ntdev, Windows tries to be
as upward compatible as possible - even in Kernel Space. And the XP Driver
is x64, so I think that may be possible.

Please correct me if I'm wrong, but should the driver just work, as long as
it doesn't do something which is illegal now (PatchGuard).

> If you are an admin on the machine you can force install any driver
> you want, even if it will bluescreen the machine. Just point at the
> driver using the Update Driver wizard in Device Manager.

Ok.

> Generally it should just be able to be installed on Win 7 without
> being modified unless Windows or the driver vendor specifically tried
> to prevent that.

OK, that's good.

> Have you tried installing the driver somehow and been unable to? How
> did you try and what error are you seeing?

Not for myself, but I'll do so!


GP


From: G�nter Prossliner on 16 Apr 2010 04:24
Hello Tim!

>> ... So if there is a working driver for Windows XP 64 Bit
>> Edition, is it somehow possible to get it installed on Win7 (with
>> test-signing)
>
> No. You have to suppress the KMCS signing requirement at every boot,
> or by hooking up the kernel debugger.

I always thought that Test-Signing is a way to avoid "to do something an
every boot" (if Test-Signing is enabled on the machine).

> However, you don't need source code. You can sign the binary
> yourself, if you have a qualifying code-signing certificate.

But even if I buy one, will I be able to trust my certificate? I thought
that I would need an organisation, because Code-Signing Certificates which
can be used for Driver-Signing are only issued to organisations, not
individuals (even if it's me, and it's my computer). Also wrong?


GP


From: Maxim S. Shatskih on 16 Apr 2010 04:57
> btw, we're talking about the Yamaha M-LAN Driver, used for musical equipment
> (01X in my case). And yamaha it not willing to roll-out drivers for Vista

I think this is a way to require people to buy newer hardware. I don't think MIDI controller can be too expensive.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Maxim S. Shatskih on 16 Apr 2010 05:04
>> However, you don't need source code. You can sign the binary
>> yourself, if you have a qualifying code-signing certificate.
>
> But even if I buy one, will I be able to trust my certificate?

The PnP signature checks (executed in SetupCopyOEMInf during driver package install) are suppressed by creating a test cert ("makecert"), signing the .CAT with it and properly installing it on the machine - i.e. the "Root Agency" of the test cert to Machine/Trusted Root Certification Authorities, the cert itself to Machine/Trusted Publishers. The documentation on this is poor, and I know people who were unable to test-sign the PnP package on 2003 when following the docs. A bit of tricks described above solves the issue on 2003.

The only difference between pre-Vista and Vista+ in terms of .CAT signing is that Vista+ really only checks the signature in SetupCopyOEMInf to Driver Store, after which any devnode setup using this package is silent. 2003 and XP, on the other side, will show you UI on each devnode setup if the signature is not correct and trusted.

As about KMCS checks (executed on .sys file load on all Vista+ x64 OSes) - they are suppressed by signing with a test cert, and then "set testsigning on".

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

From: G�nter Prossliner on 16 Apr 2010 05:20
Hello Maxim!

>> And yamaha it not willing to roll-out
>> drivers for Vista
>
> I think this is a way to require people to buy newer hardware.

Of cause it seems to be like that.

> I don't think MIDI controller can be too expensive.

If the 01-X would just be a MIDI controller I would not be worth the time.
I'd buy a new one for 20-30 EUR, but the device I'm talking about is a
Digital Mixer, Audio-Interface, Midi-Interface and a Remote-Controller for
popular Production Programs (like Cubase, Logic, ...). And even the new
products from the same manufacturer (e.g. the N-Series) don't cover 20% of
the functionality of the 01-X. The 01-X integrates totally with the Software
(e.g. Moto-Faders). For me the 01-X is just great for recording rehersals or
making pre-productions. So it would be really urly to eigher keep an
otherdated OS "forever", or to drop out the 01-X.


GP


First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Parsing devices from setup classes
Next: size of device context limit ?