[argyllcms] Re: Colormunki Windows Driver
- From: "Bruce Houston" <bhouston1@xxxxxxxxxxx>
- To: <argyllcms@xxxxxxxxxxxxx>
- Date: Mon, 11 Jan 2010 02:03:33 -0600
Hi Graeme,
Thank you again for your help with the Munki driver for Win 7 x64; and
please forgive my being a pest by asking for additional assistance. I
really, really look forward to using ArgyllCMS with the Munki.
I believe that the ColorMunki.inf file needs a tweak or two. First, the
Signature line of the Version section reads "$Chicago$" and causes the
driver installation to fail in Win7 x64 with the message "this driver is for
a different platform" (or the like). Changing this parameter to "$Windows
NT$" gets rid of this error and allows the driver to install.
After installation, however, the following three driver components show up
in Device Manager under "LibUSB-Win32 Devices"-->"ColorMunki (Argyll)":
c:\Windows\system32\drivers\libusb0.sys
c:\Windows\system32\libusb0.dll
c:\Windows\syswow64\libusb0.dll
Neither libusb0_x64.dll nor libusb0_x64.sys is to be found. I believe that
this may be due to other problems in ColorMunki.inf. Problem is, with my
level of familiarity with .inf files, I would really be mucking around by
attempting to further mod ColorMunki.inf.
Also, Plug-N-Play re-installs the X-rite ColorMunki driver ever time that
the device is plugged into USB, notwithstanding that I specify "delete
driver files" when uninstalling the X-rite driver. Perhaps that behaviour
would stop if I can get the Argyll x64 driver correctly installed. I am not
sure about that, though, because the Argyll driver shows up under a
different category of devices in Device Manager ("LibUSB" vs. "X-rite").
Thus, I am not sure whether Windows can recognize that it is installing and
making active a second driver for the same device.
Any further thoughts would be much appreciated.
Best regards,
Bruce
-----Original Message-----
From: argyllcms-bounce@xxxxxxxxxxxxx [mailto:argyllcms-bounce@xxxxxxxxxxxxx]
On Behalf Of Graeme Gill
Sent: Saturday, January 09, 2010 6:21 PM
To: argyllcms@xxxxxxxxxxxxx
Subject: [argyllcms] Re: Colormunki Windows Driver
darkbasic wrote:
> I tried booting with signing checking disabled but I got a BSOD, so I
> downloaded "Driver Signature Enforcement Overrider".
> I disabled UAC, I owerwrote libusb0* and I enabled test mode, then I
rebooted.
> Finally I self-signed colormunki* and libusb* and I rebooted again.
> I still cannot install the drivers (they seem to be still not signed).
> How can I solve?
Hmm. I'm not sure.
I tried self signing manually, and it worked without a hitch.
(This is from
<http://nil-techno.blogspot.com/2008/08/installing-unsigned-drivers-on-vista
-64.html>)
Here's what I did:
Grab the necessary tools. They should be in the MSWindows Platform SDK
(makecert.exe, certmgr.exe, signtool.exe), but it's about 1.5 GB.
(Googling for "SignTools_Vista.zip" might be easier, but I didn't tell you
that!).
Uninstall & delete any unsigned drivers installed using F8. You probably
have to plug the instrument in for them to show up under hardware, to
be able to then delete them and remove the driver. (You don't have
to boot under F8 for this). You might be able to update the driver
instead of this, but I didn't try it.
I opened a shell as Administrator and turned on test mode:
bcdedit.exe /store C:\Boot\BCD /set testsigning yes
(The "/store C:\Boot\BCD" is to cope with multi-boot setups, and assumed
your system boots up to C:)
Then I rebooted Vista. It should come up in test mode, with "TestMode" at
the
four corners of the desktop bitmap.
Then (with the Administrator shell again) I created a certificate:
makecert -$ individual -r -pe -ss "ArgyllSS" -n CN="ArgyllSS"
argyllss.cer
Then I installed the certificate:
certmgr /add argyllss.cer /s /r localMachine root
then I signed the driver (from <http://www.argyllcms.com/win64libusb.zip>)
in the libusbw directory:
signtool sign /v /s "ArygllSS" /n "ArgyllSS" libusb0_x64.sys
Then I plugged the instrument in, and followed the usual tortuous path
of selecting the libusbw directory with the .inf files in it,
and installing the driver (even though Microsoft doesn't recognize
the software vendor!).
The driver installed OK, and then the Argyll tools could access it.
Note that I did NOT have to disable UAC.
Perhaps "Driver Signature Enforcement Overrider" can't cope with
a multi-boot setup, or perhaps it got confused by something else,
or perhaps it simply doesn't work, I don't know since I haven't tried it.
Perhaps you could try removing the drivers and trying it again ?
Graeme Gill.
Other related posts:
