![]() |
|
|
#166 |
|
"Kieren"
Jul 2011
In My Own Galaxy!
2·3·1,693 Posts |
I'm sure you are correct, though this did have all the trappings of a Federal Court notice and the described faults jibed with some of my experiences. However, in this case there is not really anything that Symantec can discover about me that they don't already know. I've been a customer for too long. I suppose that does presume that any part of this was as it claimed to be. But still, any common info on me is undoubtedly easily searchable.
Last fiddled with by kladner on 2013-07-28 at 23:41 |
|
|
|
|
|
#167 | |
|
Aug 2012
New Hampshire
23·101 Posts |
Quote:
Symantec has been getting sued for decades for one thing or another. Last fiddled with by swl551 on 2013-07-29 at 01:21 |
|
|
|
|
|
|
#168 |
|
"Kieren"
Jul 2011
In My Own Galaxy!
2×3×1,693 Posts |
http://www.computerworld.com/s/artic...awsuit_charges
The suit alleged that Symantec offered free online tests which ALWAYS FOUND SERIOUS ERRORS!!!!! In other words, they were running the classic Scareware scam. This seems to be unrelated to my suspicions of bad results from using their Norton Utilities software. Note that I was not lured into buying by the scare tactics. I was lured in by a really cheap offer when I renewed my Internet Security subscription. I have used a number of versions of Norton Utilities over the years so I did not expect problems. I emphasize that these are only suspicions, and that I do not have unequivocal evidence connecting weird behavior by MISFIT to running their registry cleaner and various optimizing functions of the Speed Disk defragmenter. I do know that it happened twice after a Windows rebuild when I ran the various utilities shortly after. After the second time, I rebuilt yet again after removing NU 16 from the system. Since, MISFIT has worked without problems. I repeat that I had used these functions of the suite for some time previously without these particular malfunctions occurring. This is circumstantial, at best, but I got really tired of fixing things and did not care to experiment further. Last fiddled with by kladner on 2013-07-29 at 01:43 |
|
|
|
|
|
#169 |
|
Aug 2012
New Hampshire
23×101 Posts |
The good the bad and the ugly. It is all there on the MISFIT download page.
Please do not interpret the release of the source as a sign I am no longer supporting MISFIT. |
|
|
|
|
|
#170 |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
230238 Posts |
|
|
|
|
|
|
#171 |
|
"Mr. Meeseeks"
Jan 2012
California, USA
23×271 Posts |
|
|
|
|
|
|
#172 |
|
"Kieren"
Jul 2011
In My Own Galaxy!
2×3×1,693 Posts |
Same here!
|
|
|
|
|
|
#173 |
|
Romulan Interpreter
Jun 2011
Thailand
23×419 Posts |
+1 from here too!
I consider that Scott did a very good move by releasing the sources, in spite of the fact that I was in the "privileged" set of the users from the beginning: Scott gave me the source code to "shut my mouth down", hehe, when I told him that I won't run exe files from "untrusted" sources, and he continued to send me the sources without my request, for every new version he has done. Yet, this has nothing to do with me "lobbying" the program, the program is very well written, he invested a lot of time into it, and from the user point of view, as I said, since I have MISFIT, I almost forgot to write batch files... no joke! The program is doing everything for you, if is set right. Its utility is better when you have more cards or when you run mfaktX in more computers. Try it and see. What you have to do is set your copies of mfaktX, set MISFIT, go to the beach and relax...
Last fiddled with by LaurV on 2013-09-30 at 02:30 |
|
|
|
|
|
#174 |
|
Aug 2012
New Hampshire
23×101 Posts |
As Laurv mentioned he was silently providing verification of my builds in-case a concern of my credibility became an issue. I also suspected that getting his approval was a sure-fire-way to increase MISFIT usage. The more users, the more ideas, the more fun.
Thanks. |
|
|
|
|
|
#175 |
|
Aug 2012
New Hampshire
80810 Posts |
VERSION 2.5.6
1. Added option to have Stalled Process Detection suspended on startup. This is useful if you have scheduled start/stop events and MISFIT is starting up but the next scheduled start event's time is greater than the Stalled Process Detection threshold. 2. Added ability to resume Stalled Process Detection regardless of what triggered the suspension. A warning is provided if trying to resume when no MFAKTx instances are running. 3. Added CurrentGHzDaysWorkToDo and StagedGHzDaysWorkToDo to the productivity reports 4. Fixed some minor UI bugs when MISFIT is put into MONITOR MODE GET FROM http://mersenneforum.org/misfit/ |
|
|
|
|
|
#176 |
|
Aug 2012
New Hampshire
23·101 Posts |
VERSION 2.5.8
1. Changed the MISFIT support email address to MISFIT.SUPPORT@OUTLOOK.COM 2. Additional small fixes GET FROM http://mersenneforum.org/misfit/ Due to the lack of activity in the MISFIT forums I will no longer be checking them. If something comes up please contact me via email at MISFIT.SUPPORT@OUTLOOK.COM |
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| released: MISFIT for MFAKTx version 2.11.0 (31-Jan-2017) | swl551 | MISFIT | 19 | 2020-11-18 14:29 |
| MISFIT 2.9 | swl551 | MISFIT | 44 | 2014-12-15 12:46 |
| MfaktX Controller (Windows) | Mini-Geek | Software | 52 | 2014-02-18 18:27 |
| MFAKTx speed menu (windows) | swl551 | Software | 8 | 2013-03-07 00:16 |
| (archive)mfaktXHelper - utility for managing mfaktX installations | swl551 | MISFIT | 57 | 2012-08-12 03:37 |