iopbetter.blogg.se

1. Does sniperspy actually work how to#
2. Does sniperspy actually work manual#
3. Does sniperspy actually work software#
4. Does sniperspy actually work zip#
5. Does sniperspy actually work free#

Does sniperspy actually work how to#

So, how to get around this? My solution was to create a batch (.bat) file (below) to end the processes and then restart them immediately, and I changed my Corsair Link shortcuts to run this instead of CorsairLink.exe. Therefore, the existing processes in must first be ended in Taskmanager, which will probably cause the devices to stop adhering to your setting, as the governing CorsairLink.exe process is no longer running. NET Framework errors and made the devices completely unresponsive to CL. The problem is that, while it will open the console, is will also create duplicates of the above processes, which, for me, led to. However, since there is no icon in the tray at this point, the only way to reach the console and see the settings or even the devices and node themselves is to open the console via CorsairLink.exe or CorsairLINK.exe (see above for the difference), right? Well, yes and no. Located in "\Corsair\Corsair Link\Frontend". I found that this must be started before the fans will adhere to the custom curve, apparently even if the window isn't actually opened on screen and the icon does not appear in the tray.

Does sniperspy actually work software#

The software and firmware that worked for me are Corsair Link v and Cooling Node v1.2.5 (attached), and I'm using Windows 7.Īfter startup, there are two CL processes running that can be seen in the Taskmanager: bat files (outlined below), and I'll try to give details of the settings that ended up working in the hopes that it may help others.

Does sniperspy actually work zip#

But I don't know how and the only thing that I can think of that differs from previous attempts that have failed is that the registry key "UIFirstLoaded" is now set to True, though I don't know what this key does.Īnyway, I'll attach a zip containing screenshots of my settings and the scheduled startup task (I modified the task that CL created when "Run at Windows Startup" was selected in the CL console Options tab) along with my own.

Does sniperspy actually work free#

all my free time after work up to 3am every night), I have finally gotten CL to work such that the fans adhere to the custom curve on startup without having to manually start the console.

Does sniperspy actually work manual#

Items/events immediately after a Reboot = observed results after the reboot and before manual action is taken."Reflash" = reflashed Cooling Node firmware to the version shown at the top of the page (usually to reacquire unresponsive nodes/devices)."firmware" = updated Cooling Node firmware to the version shown at the top of the page."not adhere" = fans did not adhere to the custom curve."adhere" = fans adhered to the custom curve."Console" = manually started CL console."Stress" = manually increased H100i temp by running Prime95 to heat up the CPU.

I tested Node 1.2.11 before I started taking notes. Is there something I'm doing wrong? Should I downgrade my Commander firmware? If so, where can I find an older version? I'm currently using Cooling Node 1.2.5 but I have tested 1.2.11 and 1.2.9 as well.Įdit: Attached the handwritten notes/tests/results from last night for: However, with v, both axis correctly respond in unison, adjusting the fans to the temp to follow the curve, but only after I have manually started the console. So why won't CL do that now with either v or v? Since installing the Commander and Cooling Node, v, on the curve graph, only the H100i temp axis changes but the RPM axis remains where it is.

That's how my H100i (v) seemed to work when I used it as the controller instead of the Commander. I get the impression that the current settings are supposed to be saved on the Cooling Node so CL can get everything running without the console being opened. Do you have it tasked for startup? I tried that but it still didn't adhere on startup, and when I opened the console afterwards to get it to adhere, it created duplicate processes for both CorsairLink.exe and CorsairLINK.exe with, I believe, those being the underlying service and the frontend/console respectively. You guys have the fans automatically adhering to a custom curve as soon as Windows starts without having to open the console? How do you make it do that? As I said, the best I can make it do is to adhere to the curve only after I have started the console.