Jump to content

Cobra951

Members
  • Posts

    8
  • Joined

Reputation

10 Good
  1. I'm here to support DevBiker's wisdom. App-level code CANNOT crash an NT-based OS. Such a crash requires a hardware issue, or a driver-level issue. Now, it is possible for an app to install a driver, which if it has a defect or conflict, may cause a BSOD. Does iCUE install drivers? That's a question I can't answer.
  2. Thank you for your helpful replies, here and elsewhere on the boards. I am new to Corsair, and RGB keyboards. It took me 2 weeks to go from initial setup of my Strafe Mk 2 to being able to create a specific color scheme, and save it to the KB. Poor printed directions in the box, and poor directions at the Corsair repository of software had me install CUE 1.16, which failed even to detect the KB, and had me thinking it was an issue with HID devices. That took a while to get past. I eventually ignored the directions, and went for 2.24.50, which works (but it turns out to be deprecated now as well, so eventually I'll move to iCUE--not anytime soon, though). Like the OP, I like the idea of saving my profiles to the KB memory. I understand that the ARM processor and memory in the device are limited compared to their PC counterparts. The CUE 2 software makes the limitations clear, if I do too much in a profile, and then try to save it to the hardware. Fortunately, all I want is a sensible color scheme, with no more than 5 total static colors. However, at least it lets me overwrite the HW1 - HW3 profiles from those I create. Are you saying that iCUE does not, and that this is actually a good thing?
×
×
  • Create New...