I got the new device, the serial device was != -1 and argyllcms did not complain (the version that checks on the sn!=0xffffffff). So Argyll did not break the Huey, as expected. :) Now I just have to learn how to use it, the hard part. Thanks everybody for the support. --Tommaso Graeme Gill wrote: > Tommaso Schiavinotto wrote: >> I have some news, an operator of the support told me that they are going >> to replace the device after having me asked to run a windows program to >> obtain the serial number (that was -1, as in Argycms). > > Interesting. > >> They asked me as soon I get the new device to run the program for >> getting the serial number in Windows and only after using Argyllcms. >> They told me that they want to be sure argyllcms is not going to rewrite >> the EEPROM. Althought they admit this would be the first report of such >> a kind. > > It would be a strange incident if Argyll had written the serial number, > given that although there is code in the driver to write the EEPROM, > it is not called by anything. In fact a smart code optimizer would > leave the code out of the object file... > > cheers, > Graeme Gill. > >