[argyllcms] Re: Colormunki Windows Driver

  • From: Graeme Gill <graeme@xxxxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Thu, 11 Feb 2010 13:41:10 +1100

Davide wrote:
Only by following the procedure I outlined. What do the properties of
the .sys files show under "Digital Signatures" ? What are the details ?

I see this:
http://i46.tinypic.com/2eprk9h.png
http://i45.tinypic.com/sm3ia0.png

Sorry, it's hard for me to decipher that, but I get the impression
they seem to be signed.

Exactly how do you know that it's not worked though ? Do you get:

   a) A popup window when you install or plug the device in saying that
      the driver install has failed ?

   b) Device manager status on the ColorMunki-libusb driver saying
      it isn't installed properly ?

   c) Argyll's tools not seeing the ColorMunki ?

If it's just a), then I've certainly seen MSWindows put such
notices up, even when the install has succeeded, or even before/during
an install. You need to have verified whether it works or not using spotread.

If it has definitely not installed properly, then all I
can suggest is looking over the situation carefully,
and carefully check (and double check) each step, and
that each step has worked.
It's possible for it to work as several people have reported
success, so there are a limited number of possibilities:

1) Something about your Windows 7 is different. It could be:

    a) A different version of Windows. I used "Win Pro 7 64-bit English"
       Perhaps you've got a different version or service pack ?
    b) It's installed differently.
    c) It's configured differently.
    d) It's in a different state.

2) Something about the procedure you used is different.

I'm not sure how to help if it's 1a) or 1b).
1c) would be something like it's not in test mode.

From what people have reported, 2) can cause 1d) :- if you first
install unsigned drivers and then try to install signed drivers,
then it won't overwrite the unsigned drivers on a re-install.

If this is what's happened, you need to uninstall the ColorMunki/libusb
drivers (remembering to tick the "remove files" tick box in the process),
then manually delete all traces of the libusb .sys, .dll and .inf files
from under windows. To recap, there are likely to be the following files
that need manually deleting:

   Windows\System32\libusb0.dll
   Windows\SysWOW64\libusb0.dll
   Windows\System32\Drivers\libusb0.sys

To make absolutely sure, search the drive that Windows lives
on for libusb (making sure that hidden and system files are searched),
and make sure there is no trace under the Windows directory.
You may also want to search for any Argyll ColorMunki.inf files
(you don't want to delete any X-Rite ColorMunki.inf files though.)

Make sure the .sys files in the Argyll distribution are signed,
and double check the properties to make sure that they are signed.

If you have X-Rite drivers, remember that you need to "Let me pick
from a list of devices drivers on my computer" rather than the normal
"Search for driver software in this location".

It's worth reading these previous posts:

<//www.freelists.org/post/argyllcms/Colormunki-Windows-Driver,6>
<//www.freelists.org/post/argyllcms/Colormunki-Windows-Driver,15>
<//www.freelists.org/post/argyllcms/Colormunki-Windows-Driver,20>
<//www.freelists.org/post/argyllcms/Colormunki-Windows-Driver,23
<//www.freelists.org/post/argyllcms/Colormunki-Windows-Driver,25>

cheers,

Graeme Gill.

Other related posts: