-   15k Search (
-   -   RMA.NET (

TTn 2005-10-07 04:23

RMA.NET 0.5 is now available!
View the files section, as a member to download.
(Requirements: Microsoft .NET framework)

It will help you find primes quicker.
This is a very stable version, as were all 0.x versions.
There is a multi-level help file included, in the menu.("Help")
It's entertaining, and functional with a built in screen saver.

Please give it try, and let me know what you think.

Flatlander 2005-10-09 12:23

Thank you for this useful tool.

I am using it for k=9345 from 205,000 to 505000. After running for about 18 hours the sieve is at 78 billion, LLR is at 206,350. I will report again later.

If I find a prime do I need a new proof code? Is recognised as a program by the database?


Val 2005-10-09 13:34

Awesome! :bounce:

RMA.NET is not yet recognized as program, by the database.
If enough people find it usefull as well, then maybe a
request letter will be issued. :help:

It has just entered the pre-release stage. :geek:
Chris Caldwell has known about the program for some time now, but stressed to me, that it takes a long time, to get a stable release candidate.
He was indeed right. :bow: Both versions took a long time to patch out, all the microsoft component bugs, along with a couple of my own injections.

Keep us posted.
Shane F.

Flatlander 2005-10-09 23:16

Update, about 30 hours. (I lost track when I had to reboot because my daughters rabbit bit through my keyboard cable! :surprised )

LLR @ 207872 (2.5 minutes per test)
NewPGen @ 105billion (30-40 secs. per rejection)
Timer set at 30mins.

Closing by clicking the red X causes Windows to lose the taskbar, requiring a reboot. (XP Pro.)

BTW, which language did you write this in?

Flatlander 2005-10-10 00:02

Bug fixed by applying service patch to .net :smile:

Val 2005-10-10 00:15

screen bug?
RMA.NET is written in MS Visual Basic .NET.

Was the screen saver checked?
It may have tried to enter screen saver mode, when you clicked the close button. I'll look into this,... you should be able toggle the screen saver option in RMA preferences, to get the taskbar back without rebooting.
Ofcourse you'd have to reload RMA.NET.

Visual eye candy, should not harm the computational side of the application, nor should it harm a windows session.
Nonetheless, I'ts my responsibility to fix this, if it may be a problem for some configurations.

Shane F.

fetofs 2005-10-10 00:20

Closing by clicking the red X causes Windows to lose the taskbar, requiring a reboot. (XP Pro.)


Can't you just turn explorer on?

Flatlander 2005-10-10 00:24

Please see my post above.

Ironic that you code is more stable than Microsoft's!

Val 2005-10-10 01:31

I believe what must be happening, is that during one of the unload events, perhaps dispose, the new instantiation that .NET uses is flawed.
I had read somewhere, that it was a drawback to declare things every time.
Not to mention, a hassle for the programmer.
My code should definiately "not" be hiding the taskbar when closing the form.

BTW what version 0.5 or 0.6?

The difference is that a sendkeys.flush is used with the screen saver in 0.5.
Sendkeys.Flush is equivelant to Application.DoEvents, and so flushes the message que. Not always a desirable condition, however during screen saver useage, this should be ok. Although if the unload event triggers this flush then I could see a message foul up.

TTn 2005-10-10 01:53

My sentiments exactly Val,...
Oh wait I'm Val....

Val is no longer with us as a group, but was part of L9.
L9 was a prover group, that found prime numbers collectively.

She was my main inspiration for this work,
and she helped build the foundations for it.
In honor, I have dedicated RMA to her.

Shane F.

TTn 2005-10-10 06:02

RMA.NET 0.7 is now available!
View the files section, as a member to download.
(Requirements: Microsoft .NET framework)

I was right, the unload event was triggering the event to fire.
It did not involve the SendKeys.Flush though as I suspected.
It was triggering, a timer event, that it should not have been.

I added a call, in the unload event to make the taskbar visible, even though it should already be. You can still see the bug occur, but now it's just a flash, and it immediately becomes visible again.

All times are UTC. The time now is 01:47.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.