Force fans to go faster?

[sparker]

Here is the log. I converted it to .txt so it could be attached. If that ruined it let me know.
log.txt

[Meaker]

Meaker, to run the macros using OpenOffice:

Tools > Macros > Run Macro > GX640... > Standard > Module1 > btnProfile1_Click > Run

Don't forget to enable macros in the options.

thornduck

Hey cheers for your help but I don't see that macro:

http://i4.photobucket.com/albums/y143/Meaks/PICMAC.jpg

I've changed the security level, tried redownloading the fanspeed changer but it never shows up.

[thornduck]

Hey cheers for your help but I don't see that macro:

http://i4.photobucket.com/albums/y143/Meaks/PICMAC.jpg

I've changed the security level, tried redownloading the fanspeed changer but it never shows up.

This is what it looks like on this end. Second screenshot shows you what I enabled prior to executing.

thornduck

[Pherein]

Here is the log. I converted it to .txt so it could be attached. If that ruined it let me know.
log.txt

Thanks, and changing the extension is fine as the file itself is just a regular txt file with a log extension.

I just spent a bit more time bug hunting and this new release should fix the problem. If it still doesn't fix it can you post a screenshot of the error; it doesn't seem to be writing to the log file. As with 1.0.1 make sure you delete the old configuration file to start using this version as I made a few changes that won't work with the old config.

Link: MSI_P1KeyFanToggle_1.0.2_By_Pherein.rar

[sparker]

Thanks, and changing the extension is fine as the file itself is just a regular txt file with a log extension.

I just spent a bit more time bug hunting and this new release should fix the problem. If it still doesn't fix it can you post a screenshot of the error; it doesn't seem to be writing to the log file. As with 1.0.1 make sure you delete the old configuration file to start using this version as I made a few changes that won't work with the old config.

Link: MSI_P1KeyFanToggle_1.0.2_By_Pherein.rar

Here is the error, with 1.0.2, still the same thing. One thing has me curious, would storing the toggle on a separate drive than RWEverything cause this? Maybe I'll put it on the same drive and try.



As I said, as soon as I relink the P1 button to the .exe it works fine. Edit: Changing to the same drive didn't help.

[Meaker]

This is what it looks like on this end. Second screenshot shows you what I enabled prior to executing.

thornduck

Woot, cheers.

Looks like mine is happy to turn the fan off

[Pherein]

Here is the error, with 1.0.2, still the same thing. One thing has me curious, would storing the toggle on a separate drive than RWEverything cause this? Maybe I'll put it on the same drive and try.



As I said, as soon as I relink the P1 button to the .exe it works fine. Edit: Changing to the same drive didn't help.

Hmm...by the look of it the program is still looking for relative paths instead of absolute paths. If you haven't tried this already can you extract
MSI_P1KeyFanToggle_1.0.2_By_Pherein.rar
to a new folder and try running it from there? Sorry about all the hassle.

Edit: If that still doesn't work check FanToggleSettings.ini, specifically Profile1Path and Profile2Path
in 1.0.1 and earlier they should like like:
Profile1Path = Profiles\Default.rw
Profile2Path = Profiles\Max.rw
CurrentProfile = Profiles\Default.rw

However in 1.0.2 they should look like:
Profile1Path = C:\Users\Chris\Downloads\MSI_P1KeyFanToggle_1.0.2_By_Pherein\Profiles\Default.rw
Profile2Path = C:\Users\Chris\Downloads\MSI_P1KeyFanToggle_1.0.2_By_Pherein\Profiles\Max.rw
CurrentProfile = C:\Users\Chris\Downloads\MSI_P1KeyFanToggle_1.0.2_By_Pherein\Profiles\Default.rw

If yours don't look like 1.0.2 change them so they = the full file path.

[sparker]

Hmm...by the look of it the program is still looking for relative paths instead of absolute paths. If you haven't tried this already can you extract
MSI_P1KeyFanToggle_1.0.2_By_Pherein.rar
to a new folder and try running it from there? Sorry about all the hassle.

Nope, that still doesn't fix it. And you are the one doing all the work so don't worry.

Edit: If that still doesn't work check FanToggleSettings.ini, specifically Profile1Path and Profile2Path
in 1.0.1 and earlier they should like like:
Profile1Path = Profiles\Default.rw
Profile2Path = Profiles\Max.rw
CurrentProfile = Profiles\Default.rw

However in 1.0.2 they should look like:
Profile1Path = C:\Users\Chris\Downloads\MSI_P1KeyFanToggle_1.0.2_By_Pherein\Profiles\Default.rw
Profile2Path = C:\Users\Chris\Downloads\MSI_P1KeyFanToggle_1.0.2_By_Pherein\Profiles\Max.rw
CurrentProfile = C:\Users\Chris\Downloads\MSI_P1KeyFanToggle_1.0.2_By_Pherein\Profiles\Default.rw

If yours don't look like 1.0.2 change them so they = the full file path.

The paths are correct, even in the first version I made the full path to where the profiles are to see if that fixed it. If I run the .exe directly it works ever after reboot. If I relink the .exe to system control manager it works again until reboot.

Something is off, and I don't think it is the path to the profile, or it shouldn't work at all.

EDIT:
If I exit SCM and start it again, it works... I'm going to try a delayed start from task scheduler.

[sparker]

OK, the delayed start did not fix the issue, and here is where it gets weird.

If I close SCM and start it again from any shortcut, it will give that error.

However, If I close SCM and search the start menu for it, and open SCM from the search results it works fine.

Running SCM as admin does not fix it either. Could it be a firewall issue, or some protection in the OS?

[sparker]

I uninstalled system control manager, deleted every folder that had settings of it, and reinstalled it.

The errors are still there, but they have changed. Now Windows error reporting asked me if I wanted to send the error, so I tracked down the info.

After that, now instead of the profile missing error, the mouse cursor just goes to busy mode and nothing happens. If I run SCM from the search results, it gives a new popup message.



The data from the windows error is here: ERROR! Not sure if you can use it or not.

I have a feeling the problem is not necessarily with your program, considering how the error changed after reinstalled SCM. Maybe I need to wipe the registry of that program and start over.

Edit:

Tried making a batch file to run the exe to see if that worked. I started with a simple start command which worked at first, after reboot the batch file wouldn't run either.

I put a pause on the batch file to see what was going on, and for some reason it was changing to a new root directory after reboot C:\Windows\syswow64, which makes me think that is why your program can't find the profiles, it doesn't know where it is rooted.

I have tried a couple other programs like GPU-Z and HWmonitor and they both launch after reboots.

Here is the batch file I came up with to fix it for now: