Running SIV at the same time as Corsair iPOO or Link
Oct 28, 2018 9:14:29 GMT
element6 and tk7k like this
Post by siv on Oct 28, 2018 9:14:29 GMT
Both iPOO + CL4 are poorly designed and fail to correctly use the Global\CorsairLinkReadWriteGuardMutex lock so I can't in general support SIV reporting or controlling some Corsair hardware when the CorsairService (C:\Program Files (x86)\Corsair\CORSAIR iPOO Software\Corsair.Service.exe) or CLink4Service (C:\Program Files (x86)\CorsairLink4\CorsairLink4.Service.exe) are active so before starting SIV you need to Disable and Stop these services.
There are Menu->Windows->Services->Control CUE + Menu->Windows->Services->Control CL4 to check their state and it's also worth checking Menu->Help->Lock Handle to confirm they are not active.
Corsair fail to specify for which devices the Global\CorsairLinkReadWriteGuardMutex lock is correctly used by their software, I know they don't for the CLCP + CLNP and suspect they don't for the Pro Series of coolers. In general if Link Status reports errors when the iPOO or CL4 services are active these is likely to be caused by Corsair failing to correctly use the lock.
If you wish to use SIV to for control of Corsair Link hardware and iPOO for your keyboards + mice then once you disable the CorsairService service currently this works.
![]()
From SIV V5.38 Beta-08 it's also possible to select on a per device basis which devices SIV will report (-NOAIOCTL) and/or control (-AIOCTL). After changing the selections exit and restart SIV.
There are Menu->Windows->Services->Control CUE + Menu->Windows->Services->Control CL4 to check their state and it's also worth checking Menu->Help->Lock Handle to confirm they are not active.
Corsair fail to specify for which devices the Global\CorsairLinkReadWriteGuardMutex lock is correctly used by their software, I know they don't for the CLCP + CLNP and suspect they don't for the Pro Series of coolers. In general if Link Status reports errors when the iPOO or CL4 services are active these is likely to be caused by Corsair failing to correctly use the lock.
If you wish to use SIV to for control of Corsair Link hardware and iPOO for your keyboards + mice then once you disable the CorsairService service currently this works.
From SIV V5.38 Beta-08 it's also possible to select on a per device basis which devices SIV will report (-NOAIOCTL) and/or control (-AIOCTL). After changing the selections exit and restart SIV.
Attachments:
