>> So far so good. Now, what I don't understand is why did the program went >> through a second round of instrument calibration below? > > Seems like a second instance of dispcal was being run. Hi Graeme, By the time you read this you may be in Scottsdale -- ah! The sun. Anyhow, good news! I found the 'bug'. It was a usage problem. Remember what my command line for dispcal was : > dispcal -v -yl -w 0.3457,0.3585 -b90 -gl -e1 -K -H 245bw Well, it turned out that the -K parameter was the culprit. As indicated in the online documentation, the K parameter is designed for the DTP92 and Optix. I'm having difficulty with specifying the -w parameter? It seems dispcal only accepts "-w 0,3457 0,3585". But that causes the target white point to be garbled as evidenced by the following: > Display type is LCD > Target white = xy 0.000000 3457.000000 > Target brightness = 90.000000 cd/m^2 > Target gamma = L* curve The online documentation says the following: > Note that the x,y numbers must be specified as a single string (no space > between the numbers and the comma). But does not give any example of how to specify x and y. I tried typing: "-w 0.3457,0.3585" or "-w0.3457,0.3585" or "-w 0.3457,0,3585" and each time I got an error. The only way I found to specify the target chromaticity is "-w 0,3457 0,3585" but, as I indicated, this results in garbled chromaticity to be reported by dispcal. Maybe this is only in reporting and internally dispcal is really using 0.3457 and 0.3585 but I don't have anyway to know that. Roger Breton