If the upward threshold is 55, you need 56C to go to the next level (3 in your case). If you don't like it, just edit the script and change <, > to >=, <=.
sorry dont quite understand where to do this, i assume i have to edit ibm.cs? can you copy and paste the section in question so i know where to look/change mine.
i've also had to disable both the APS and GPU sensors as the temp reading for the cpu (in my systray) was different to the "actual temp" in the notebook fan control section. i like the cpu temp icon as its a good visual indicator for me so need it to match up to the fan control.
apart from not giving control back to the bios when nhc exits, is there any other drawbacks it has? i do like the fact that so far nhc isnt cluttering up my system event log with lots of errors every second..
i have nhc set to run as a service (registered nhc), shouldnt this get around nhc quitting unexpectantly then automatically restarting the program to give fan control back to nhc? or am i misinterpreting how letting nhc run as a service works? i've even set the service to automatically restart after 60 seconds if theres a problem.
edit: with nhc running as a service, its set to log on as the local system account
but the allow service to interact with desktop
is not ticked, what is controlling the fan when i reboot and then at the login screen: the bios or nhc's service?
same goes for logging off the current user then back at the login screen, whos got control, bios or the nhc service?
edit2: i guess what would be useful (for me at least) if there was a nhc tray icon which displays what level the fan is set to, be it coloured coded icon (ala FC) or even a icon that simply displays "fan: off/low/med/high/bios" would be great. of course this option would be greyed out if no acpi file was found.
hell, an option to change the fan status from a context menu when right clicking on the nhc icon (or the above fan icon), just so i dont have to go all the way into nhc to view what the fan is up to..