red-ray Originally Posted by Interlocking access to Corsair Link hardware, the history: 22-Sep-2014 - I propose a lock and ask for CL3 to support this, see http://forum.corsair.com/forums/showthread.php?p=729115 31-Dec-2014 – by now HWiNFO + SIV correctly interlock access to CL hardware using the Global\Access_CorsairLink named mutex so both can report my CL hardware at the same time. 01-Aug-2015 - I created a thread showing all of AIDA64 + HWiNFO + SIV all reporting CL hardware and pushing for Corsair to implement support. This used to be http://forum.corsair.com/forums/showthread.php?p=792672 before Corsair deleted the thread . 19-Nov-2015 - Corsair specify CL4 uses "something similar", see http://forum.corsair.com/forums/showthread.php?p=820892 . 27-Jan-2016 - CL 4.2.0.162 does not use the Global\Access_CorsairLink named mutex , see http://forum.corsair.com/forums/showthread.php?p=833499. 24-Feb-2016 - I learn that CL does implement a lock, but it's a named Binary Semaphore rather than a named Mutex. Using a Binary Semaphore rather than a Mutex is a poor decision and indicates the CL4 developers need aditional training. I ask for it to be changed. I also point out all the errors in the Corsair supplied specification. 14-Mar-2016 - SIV V5.08 released which supports Global\CorsairLinkReadWriteGuard . Note I used Global\Access_CorsairLink to interlock access to the semaphore so SIV could recover CL4 messing up. 15-Apr-2016 - I contact Corsair again and explain why they should use a Mutex. They declined to change to use a Mutex. 12-May-2016 - I discover 4.2.3.41 sometimes exits while still holding the lock. Had Corsair used a Muted this would be impossible as the thead cleanup code in Windows would set the Mutex state to abandoned . This is why a Mutex should be used, see http://forum.corsair.com/forums/showthread.php?p=851701. 19-May-2016 - I recieve an e-mail from Corsair which specifies " Corsair will not be implementing the Mutex as requested and this is not a bug or issue as you call it. " 23-May-2016 - I post http://forum.corsair.com/forums/showthread.php?p=854006 all about why Corsair should use a Mutex and I e-mail Corsair. 02-Jun-2016 - I get a reply to my e-mail and again Corsair decline to change to use a Mutex. 02-Jun-2016 - Corsair specify " In the future George will assign someone moving forward for you to contact with your concerns on an ongoing basis. ". I am still waiting for this to happen. 20-Jul-2016 - Corsair notify me the next CL4 release will use a Mutex , but rather than using Access_CorsairLink a different name of CorsairLinkReadWriteGuardMutex is implemented meaning all of AIDA64 + HWiNFO + SIV needed to be changed. 21-Jul-2016 - CL 4.2.4.25 is released less than 24 hours after I was notified of the change. 26-Jul-2016 - CL 4.2.4.25 thread is created, see http://forum.corsair.com/forums/showthread.php?p=864130. 08-Aug-2016 - I discovered that CL 4.2.4.25 probably fails to correctly implement the defined locking semantics, see http://forum.corsair.com/forums/showthread.php?p=866159. 14-Aug-2016 - SIV V5.13 released which uses Global\CorsairLinkReadWriteGuardMutex rather than Global\Access_CorsairLink . 16-Sep-2016 - CL 4.3.0.154 is released and the issue I reported on 08-Aug-2016 and not been addressed, see http://forum.corsair.com/forums/showthread.php?p=871675 10-Feb-2017 - CL 4.5.0.55 is released and the issue I reported on 08-Aug-2016 has been partially fixed, see http://forum.corsair.com/forums/showthread.php?p=892949. 21-Mar-2017 - CL 4.6.0.86 is released and the issue I reported on 27-Feb-2017 has not been addressed, see http://forum.corsair.com/forums/showthread.php?p=896054. 06-May-2017 - I update this post with the itemised list showing what I feel is Corsair incompetence. Currently SIV can be used at the same time as CL 4.2.4.25 and later with minimal issues, but Corsair should fix CL4.

