Closed GoogleCodeExporter closed 9 years ago
Can you please click on "Details" and upload the picture again?
Original comment by sven.wit...@gmail.com
on 8 Oct 2011 at 5:30
I'll handle this one.
Original comment by sven.wit...@gmail.com
on 8 Oct 2011 at 5:30
Everything from the details is in the pastebin link.
Original comment by miha.ele...@gmail.com
on 8 Oct 2011 at 5:31
Sorry, I missed that in your first comment.
Please try the following: Execute regedit and remove everything under
HKEY_LOCAL_MACHINE\SOFTWARE\BrazosTweaker. Likely there is a setting, which is
saved to the registry and causes this exception.
-Sven
Original comment by sven.wit...@gmail.com
on 8 Oct 2011 at 8:39
That solved the problem. Thank you.
Original comment by miha.ele...@gmail.com
on 9 Oct 2011 at 7:05
The same problem:
V1.0.6 x64, Windows 7 64, AMD E-240 (Lenovo x120e netbook)
http://pastebin.com/5UEGNtfp
HKEY_LOCAL_MACHINE\SOFTWARE\BrazosTweaker is empty, so I can't fix the issue by
cleaning registry.
Original comment by mail...@gmail.com
on 9 Oct 2011 at 10:39
Attachments:
Try deleting the whole BrazosTweaker "folder". That's what I did.
Original comment by miha.ele...@gmail.com
on 9 Oct 2011 at 10:42
Unfortunatelly, it doesn't help
Original comment by mail...@gmail.com
on 9 Oct 2011 at 10:44
A value, which got set to 100 in the GUI somewhere seems to cause the
exception. Can you please check, which value is set to 100 other than CLK,
before you try to click "Service.."?
-Sven
Original comment by sven.wit...@gmail.com
on 9 Oct 2011 at 5:09
Only CLK is set to 100. When it try to set it to something else before clicking
"Service..." I've got exactly the same message.
Original comment by mail...@gmail.com
on 9 Oct 2011 at 5:15
You did exit the app when you messed with registry, right?
Original comment by miha.ele...@gmail.com
on 9 Oct 2011 at 5:31
Yes, I did.
Original comment by mail...@gmail.com
on 9 Oct 2011 at 5:34
I suspect that the cause is here: CnQProfileControl.Designer.cs:127
thresholdUpNumericUpDown.Value is 100 in my case since I have single-core CPU,
but allowed maximum value is 99. Unfortunatelly, I haven't Visual Studio to
check this.
Original comment by mail...@gmail.com
on 9 Oct 2011 at 6:19
It really might have something to do with the single core CPU. I had no one
until now, with a single core CPU. I'm going to look into that and will try to
fix it as soon as possible. I bet the default value is going to be wrongly
calculated on a single core system.
Thanks for the help,
Sven
Original comment by sven.wit...@gmail.com
on 9 Oct 2011 at 7:58
[deleted comment]
I have uploaded version V1.0.7 with a fix for this issue and some other
modifications. Please check the download section and let me know, if everything
works now as it is supposed to. Thanks for the help.
-Sven
Original comment by sven.wit...@gmail.com
on 12 Oct 2011 at 7:34
I'll handle this one.
Original comment by sven.wit...@gmail.com
on 17 Oct 2011 at 7:47
Original comment by sven.wit...@gmail.com
on 18 Oct 2011 at 7:38
Original issue reported on code.google.com by
miha.ele...@gmail.com
on 8 Oct 2011 at 2:33Attachments: