Misfit "unsupported feature"

LaurV · 2017-08-19, 15:36

The mfaktc's uid/password lines are for a while accepted by the server. Therefore the "unsupported feature" error should be removed from Misfit.

Scott? Still reading here around?

(if not, a PM/mail will follow soon)

LaurV · 2019-11-22, 04:13

BUMP !

In the light of the parallel discussion, about the server stopping accepting results without UID soon... The alert message in MISFIT is extremely bothering.

OTOH, does anybody know anything about Scott? I hope he is ok. His last visit here was in August 2018, and he didn't reply to my email long ago.

Edit: Any C# experts here?

I assume that the "dirty fix" is as simple as downloading the sources from the forum, modifying the line 227 in frmMisfit.cs file, and recompiling. Unfortunately I can't compile C# right now (but I will re-install some stuff over the weekend).

LaurV · 2019-11-22, 14:52

Ok, I killed that "true" and recompiled with VS2019, the free one. It seems to work, and the ugly popup is gone. Here is the exe, for the gullible guys. The astute one should compile their own. In any case, use an antivirus before playing with it.

Chuck · 2019-11-22, 19:30

Quote:

Originally Posted by LaurV

BUMP !

In the light of the parallel discussion, about the server stopping accepting results without UID soon... The alert message in MISFIT is extremely bothering.

Is the requirement for UID only for James' site? This doesn't matter for the PrimeNet server does it?

swl551 · 2019-12-08, 15:18

Hi.
Just checking in.

All is OK with me..

Did I hear there is a desire for quick fix?

Chuck · 2019-12-09, 01:33

Quote:

Originally Posted by swl551

Hi.
Just checking in.

All is OK with me..

Did I hear there is a desire for quick fix?

Yes, prefacing a result with UID information should not generate an alert message.

chalsall · 2019-12-10, 22:21

Quote:

Originally Posted by swl551

Hi. Just checking in. All is OK with me. Did I hear there is a desire for quick fix?

Cool to hear from and of you.

Your MISFIT has been quite a worthwhile contribution to the GIMPS community. Truly "fire-and-forget" in many cases; non-trivial to achieve.

Are you going to be around the next few months? Some interesting things have happened recently, which will likely result in one or more APIs being exposed and/or being updated.

swl551 · 2019-12-11, 22:05

Quote:

Originally Posted by chalsall

Cool to hear from and of you.

Your MISFIT has been quite a worthwhile contribution to the GIMPS community. Truly "fire-and-forget" in many cases; non-trivial to achieve.

Are you going to be around the next few months? Some interesting things have happened recently, which will likely result in one or more APIs being exposed and/or being updated.

Yes I plan on being around. You know MISFIT was the last coding project I did (of any substance).. So I'm up for something....

Also it is good to see all these names again. You guys are really dedicated. I know folks come and go, but wow you guys are anchors!

LaurV · 2019-12-12, 09:44

We wish you to find us here in 50 years or so, and by that time we will have found 80 mersenne primes or so, totally...

kriesel · 2019-12-12, 14:30

Quote:

Originally Posted by LaurV

We wish you to find us here in 50 years or so, and by that time we will have found 80 mersenne primes or so, totally...

Highly unlikely. The expectation is 5 more in p<10⁹. That range is likely to take a very long time. At our current rate of progress, about 120 years. https://www.mersenneforum.org/showpo...5&postcount=11

To find the next Mersenne prime, compared to the current largest. R D Silverman lays it out at https://www.mersenneforum.org/showpo...58&postcount=8 as approximately 8 times as much effort, based on conjectures about the expected distribution. GIMPS has had a very lucky run for the past several years where the Mersenne primes have been more closely spaced recently, than expected on the average. 8²⁹ is a large number of years at current throughput (~10^26.2) and Moore's law won't hold long enough. Moore's law is mostly due to reducing feature size, and atomic diameter of silicon or any known element imposes an absolute limit on that. Quantum effects are already being felt at current fabrication sizes.

kracker · 2019-12-12, 15:20

Quote:

Originally Posted by kriesel

Highly unlikely. The expectation is 5 more in p<10⁹. That range is likely to take a very long time. At our current rate of progress, about 120 years. https://www.mersenneforum.org/showpo...5&postcount=11

To find the next Mersenne prime, compared to the current largest. R D Silverman lays it out at https://www.mersenneforum.org/showpo...58&postcount=8 as approximately 8 times as much effort, based on conjectures about the expected distribution. GIMPS has had a very lucky run for the past several years where the Mersenne primes have been more closely spaced recently, than expected on the average. 8²⁹ is a large number of years at current throughput (~10^26.2) and Moore's law won't hold long enough. Moore's law is mostly due to reducing feature size, and atomic diameter of silicon or any known element imposes an absolute limit on that. Quantum effects are already being felt at current fabrication sizes.

I think you missed the "totally" and

2017-08-19, 15:36	#1
LaurV Romulan Interpreter "name field" Jun 2011 Thailand 3·5²·137 Posts	Misfit "unsupported feature" The mfaktc's uid/password lines are for a while accepted by the server. Therefore the "unsupported feature" error should be removed from Misfit. Scott? Still reading here around? (if not, a PM/mail will follow soon)

2019-11-22, 04:13	#2
LaurV Romulan Interpreter "name field" Jun 2011 Thailand 3·5²·137 Posts	BUMP ! In the light of the parallel discussion, about the server stopping accepting results without UID soon... The alert message in MISFIT is extremely bothering. OTOH, does anybody know anything about Scott? I hope he is ok. His last visit here was in August 2018, and he didn't reply to my email long ago. Edit: Any C# experts here? I assume that the "dirty fix" is as simple as downloading the sources from the forum, modifying the line 227 in frmMisfit.cs file, and recompiling. Unfortunately I can't compile C# right now (but I will re-install some stuff over the weekend). Last fiddled with by LaurV on 2019-11-22 at 04:37

2019-12-08, 15:18	#5
swl551 Aug 2012 New Hampshire 2³·101 Posts	Hi everyone Hi. Just checking in. All is OK with me.. Did I hear there is a desire for quick fix?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Who "manages" Misfit and can answer a question?	Madpoo	MISFIT	9	2017-02-05 17:27
Feature request @ "too few cycles" after filtering	Andi47	Msieve	2	2010-01-11 08:50
"Spare" work feature request	Xyzzy	Software	0	2009-08-23 06:25
"Feature" request: Keep new B2 value when memory allotment increased	JuanTutors	Software	3	2006-12-18 06:31
Prime95 Version 24.13 "Feature"	RMAC9.5	Software	2	2006-03-24 21:12

2019-12-12, 09:44	#9
LaurV Romulan Interpreter "name field" Jun 2011 Thailand 3×5²×137 Posts	We wish you to find us here in 50 years or so, and by that time we will have found 80 mersenne primes or so, totally...