1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
|
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<meta name="GENERATOR" content="Mozilla/4.73 [en] (WinNT; I)
[Netscape]">
<title>Argyll Installation on Microsoft Windows</title>
</head>
<body style="color: rgb(0, 0, 0);" vlink="#551a8b" link="#0000ee"
alink="#ee0000">
<h1> <u>Installing the software on Microsoft Windows<br>
</u></h1>
<h3 style="background-color: rgb(255, 255, 255);"><span
style="color: rgb(51, 153, 153);">Unpacking the .zip archive:</span></h3>
You will need to unzip the downloaded file in the location you have
chosen to hold the executable files (perhaps somewhere like <span
style="font-weight: bold;">\bin</span>). I would <span
style="font-weight: bold;">NOT</span> put them in <span
style="font-style: italic;">\Program Files</span>, since spaces in
directory or file names and command line environments are a very bad
mix, and will cause you endless problems. The archive will create a
<span style="font-weight: bold;"></span> top level directory <span
style="font-weight: bold;">Argyll_VX.X.X</span>, where X.X.X is
the version number, and the executables will be in <span
style="font-weight: bold;">Argyll_VX.X.X\bin</span>.
<h3><span style="color: rgb(51, 153, 153);">Making the tools
accessible:</span></h3>
You should also configure your %PATH% environment variable to give
access to the executables from your command line environment.<br>
<br>
For <span style="font-weight: bold;">Windows 8</span>, <b>8.1, 10
& 11</b>, look in<br>
<span style="font-weight: bold;"></span>Desktop
-> Settings -> Control Panel -> System And Security ->
System -> Advanced System Settings -> Environment Variables<br>
<br>
For <span style="font-weight: bold;">Windows 7</span>, look in<br>
Start Menu -> Control Panel -> System And
Security -> System -> Change Settings -> Advanced ->
Environment Variables<br>
<br>
For <span style="font-weight: bold;">Vista</span>, look in<br>
Start Menu -> Control Panel -> System And
Maintenance -> System -> Change Settings -> Advanced ->
Environment Variables<br>
<br>
For <span style="font-weight: bold;">XP </span>look in<br>
Start->Settings->Control
Panel->System->Advanced->Environment Variables<br>
<br>
You want to add the directory you've chosen to your %PATH%, which is
a System Variable. Normally you would add this to the end of the
current setting, separated by a ';'. <br>
<br>
So if the current value of PATH is
"%SystemRoot%\system32;%SystemRoot%" and you unpacked Argyll version
3.1.0 in <span style="font-weight: bold;">d:\bin\</span>, then you
would modify PATH to be
"%SystemRoot%\system32;%SystemRoot%;d:\bin\Argyll_V3.1.0\bin", -
i.e. you append the path to the Argyll binaries to your PATH,
separated by the ';' character. The change will take effect when you
start a new command shell, which you start from Start
Menu->Accessories->Command Prompt, or Start
Menu->Programs->Accessories->Command Prompt. You can check
that the environment variable has been set by running the command
"echo %PATH%" in the command shell.<br>
<br>
The .zip file also contains several useful reference files (such as
scanner chart recognition templates, sample illumination spectrum
etc.) in the ref sub-directory, all the current documentation in a
doc sub-directory, and instrument USB drivers in the usb directory.<br>
<br>
<span style="font-weight: bold;">NOTE: </span><span
style="font-weight: bold;">Vista 64/Windows 7, 8,8.1,10 &
11 64 bit</span> and <span style="font-weight: bold;">Beep</span>
prompt<span style="font-weight: bold;">: </span>Microsoft (in its
infinite wisdom) has removed the built in speaker driver, and now
relies on systems having a sound card and speakers's installed and
turned on to hear system beeps. So if you're wondering where the
beeps have gone when using <a href="chartread.html">chartread</a>,
now you know.<span style="font-weight: bold;"></span><br>
<br>
<span style="font-weight: bold;">NOTE: Microsofts generic VGA Driver</span>
does not appear to support setting the graphics card VideoLUTs. You
will need to install a display driver for your specific display
hardware to enable this. Note also that it is possible in many cases
to use Windows 7 video drivers on Windows 8 systems etc.. If you are
having trouble accessing the VideoLUTs, then check in Device Manager
that you are running the correct driver for your card, and not using
the fallback generic driver.<br>
<br>
<hr style="width: 100%; height: 2px;"><br>
<span style="font-weight: bold;">NOTE</span> that if you wish to use
Argyll tools (<a href="dispwin.html">dispwin</a>) to control display
calibration, that you will have to disable any other display
calibration loader programs.<br>
<h3><u><font color="#cc0000"><a name="BadSoftware"></a>Other
software that may interfere with display calibration loading
and USB instrument access:</font></u></h3>
There are other programs that will interfere with calibration
loading, such as igfxpers.exe that gets installed with <b>nVidia
"Optimus"</b> technology.<br>
You may have to disable both the igfx tray module
(c:\windows\system32\igfxtray.exe) and the igfxpph Module
(c:\windows\system32\igfxpph.dll) in addition to the persistence
Module (c:\windows\system32\igfxpers.exe).<br>
<br>
A good tool for this is <a
href="http://technet.microsoft.com/en-us/sysinternals/bb963902">AutoRuns</a>.
Note that the igfxpph module may exist in several locations and you
have to disable all of them. Reboot after changing settings.<br>
<br>
It has also been reported that some RGB LED driver services will
interfere with USB instrument access. A known culprit is the <b>Logitech
LampArray Service</b> which may be have been installed with
Logitech software or by default in <b>MSWindows 11</b>. Other <b>RGB
LED drivers</b> and services such as <b>Gigabyte RGBFusion</b>
have also been reported as interfering with USB instrument access.
You may need to identify all such services and disable or uninstall
them.<br>
<br>
Also reported to interfere with access to instruments, is <b>TeamSpeak3.</b>
You may need to disable or upgrade to TeamSpeak5 to avoid issues.<br>
Some services are reported to interfere with access to instruments,
such as Mountain's <b>BaseCamp.Service</b>. You may need to disable
or uninstall this service for instruments to be recognized.<br>
<br>
<hr style="width: 100%; height: 2px;">
<h3><u><font color="#009900"><a name="Serial"></a>Serial
Instruments:</font></u><br>
</h3>
If you are using a serial connected instrument, then there is
nothing special to do to enable this.<br>
<h3><font color="#ff6600"><u><a name="USB"></a>USB Instruments:</u></font></h3>
If you are using a USB connected instrument, then suitable <span
style="font-weight: bold;">USB system drivers</span> may need to
be installed.<br>
<span style="font-weight: bold;"><br>
</span>Note that the <span style="font-weight: bold;">Huey</span>,
<span style="font-weight: bold;">i1 Display Pro</span>, <span
style="font-weight: bold;">ColorMunki Display</span> and <b>ColorHug</b>
colorimeter appears as an <b>HID</b> (USB Human Interface Device
Class) device, and hence will be assigned to the default MSWindows
HID driver. You therefore <span style="font-weight: bold;
text-decoration: underline;">don't need</span> to install an
Argyll <span style="font-weight: bold;">usb</span> system driver
for these instruments, although it is possible to select the
libusb0.sys driver as an alternative to the default HID driver.<br>
<br>
If you are using the <b>JETI</b> specbos <b>1211</b><b>, </b><b>1201</b><b>,
1511, 1501</b> and the <b>Klien K10A</b><b></b> then you may need
to install the <a href="http://www.ftdichip.com/Drivers/VCP.htm">FTDI
Virtual COM Port Drivers</a> (VCP), if they are not already on
your system. You may have to update to the latest FTDI driver to
work with the FTDI FT231XS chip that the <b>JETI</b> specbos <b>1511,
1501</b> use.<br>
<font size="+1"><u><br>
</u></font><br>
<br>
<a name="libusb"></a>For all operating system versions you can
install the ArgyllCMS libusb0.sys driver by navigating to your
ArgyllCMS installation usb directory, and running <b>ArgyllCMS_install_USB.exe</b>.
This will trigger a UAC prompt which you will have to agree to to
proceed. You may have to re-plug an instrument for the new driver to
be picked up.<br>
<br>
To uninstall the ArgyllCMS libusb0.sys driver, navigate to your
ArgyllCMS installation usb directory, and run <b>ArgyllCMS_uninstall_USB.exe</b>.
This will trigger a UAC prompt which you will have to agree to to
proceed.<br>
<br>
If you need to update the driver because support for a new
instrument has been added, then run <b>ArgyllCMS_uninstall_USB.exe</b>
followed by <b>ArgyllCMS_install_USB.exe</b>.<br>
<br>
<span style="color: rgb(51, 153, 153); font-weight: bold;"><span
style="color: rgb(0, 0, 0); text-decoration: underline;">Using
Argyll drivers with existing OEM drivers:<br>
<br>
</span></span> If you currently have applications other than
Argyll accessing your USB connected instrument, then you will have
to manually install the Argyll driver, and then switch back and
forth between the Argyll and other drivers if you want to switch
between applications.<br>
<br>
If you are using a recent version of Microsoft Windows and want to <u>often</u>
switch between using ArgyllCMS and the OEM driver, you can try using
a different physical USB port for each installation, as this
reportedly avoids the need to manually switch drivers.<br>
<b><br>
</b> Jump to your operating system version for the details of how to
switch drivers:<br>
<br>
<a href="#WIN8">Windows 8, 8.1, 10 & 11</a><br>
<a href="#WINV7">Windows 7</a><br>
<a href="#WINV7">Windows Vista</a><br>
<a href="#WINXP">Windows XP</a><br>
<br>
<hr style="width: 100%; height: 2px;"><a name="WIN8"></a><font
size="+1"><span style="font-weight: bold;">Windows 8, 8.1, 10
& 11</span></font><font size="+1"><span style="font-weight:
bold;"></span></font><br>
<br>
<span style="color: rgb(51, 153, 153); font-weight: bold;"></span><span
style="text-decoration: underline;">To switch between drivers:</span><br>
(Plug in the instrument)<br>
Desktop -> Settings -> Control Panel ->
Hardware and Sound -> Device Manager<br>
(Locate the instrument in the device list. It may
be underneath one of the top level items.)<br>
Right click on instrument -> Update Driver
Software... -> let me pick from a list of device drivers on my
computer<br>
(Choose either the Argyll driver or another
driver from the list)<br>
-> Next -> Close<br>
<br>
<hr style="width: 100%; height: 2px;"><a name="WINV7"></a><font
size="+1"><span style="font-weight: bold;">Windows Vista &
Windows 7</span></font><br>
<br>
<span style="color: rgb(51, 153, 153);"></span><span
style="text-decoration: underline;">To switch between drivers:</span><br>
(Plug in the instrument)<br>
Start -> Control Panel -> Hardware and
Sound -> Device Manager<br>
(Locate the instrument in the device list. It may
be underneath one of the top level items.)<br>
Right click on instrument -> Update Driver
Software... -> let me pick from a list of device drivers on my
computer<br>
(Choose either the Argyll driver or another
driver from the list)<br>
-> Next -> Close<br>
<br>
<hr style="width: 100%; height: 2px;"><a name="WINXP"></a><font
size="+1"><span style="font-weight: bold;">Windows XP</span></font><br>
<br>
<span style="color: rgb(51, 153, 153);"><span style="color: rgb(0,
0, 0); text-decoration: underline;"></span></span><span
style="text-decoration: underline;">To switch between drivers:</span><br>
(Plug in the instrument)<br>
My Computer, Right Click -> Manage ->
Device Manager<br>
(Locate the instrument in the device list. It may
be underneath one of the top level items.)<br>
Right click on instrument -> Update Driver...
-> No, not this time -> Next<br>
->Install from a list or specific location
(Advanced) -> Next -> Don't search. I will choose the driver
to install -> Next<br>
->let me pick from a list of device drivers on
my computer<br>
(Choose either the Argyll driver or another
driver from the list)<br>
-> Next -> Finish<br>
<br>
<br>
</body>
</html>
|
