Sneak Peek
 

Since Scott is swamped by real work, I retrofitted support for the current PrimeNet server into the development version of prime95. Because y'all have been so patient, I'm making a sneak peek of the future client available.

While I'm not asking for beta testers, I will look at any bugs you report. Dual core machines and weird firewall/proxy situations are most likely to exercise the new code paths and thus find bugs.



from the readme.txt:

WARNING: Pre-beta software. Read this file carefully.

[B]Do not install over your existing prime95.[/B] Copy your existing prime95
folder to a new folder and then replace the prime95.exe in the new folder
with this pre-beta version.

[B]Save files created by this prime95 cannot be read by previous versions.[/B]

There are no dialog boxes for entering your password, user name, and email
address. These must be in the prime.txt file.

Your prime.ini, local.ini, worktodo.ini files will be renamed with a .txt
extension. Primenet.ini will become a section within prime.txt.

In prime.txt, in the [PrimeNet] section, add the line "debug=1". This
version uses the cURL library for communications.

Multiple threads are now supported. In Worktodo.txt, the assignments
for the second cpu come after the [Thread #2] section header. To merge
two v24 folders into one v25 client, you'll have to move the save files
and update the worktodo.txt file manually.

Expect bugs. Multi-threading has introduced massive changes to the source
code. Also, this client was designed to work with a new server protocol.
I've retrofitted it to work with the current server. Obviously, the new
work types are not supported by the old server.

Linux version is not available.

User interface comments are welcome. Bug reports are welcome.


Download address is: [url]ftp://mersenne.org/gimps/p95v251.zip[/url]

BTW, multi-threaded means it can run multiple LL tests in different windows. It does not mean using multiple threads to run one LL test on multiple cores.

nice george,
i will test and moan about problems
one possible thing i see is allow people to highlight text on the 3 console windows, also i like the broken up look your using for data display

Will you be doubling the maximum number of tests in the worktodo.ini/worktodo.txt file?

This version is no faster than version 24. It should be an unobservable few clocks slower (it can no longer access global data).

If you have a hyperthreaded CPU could you run two benchmarks and email it two me. Run one test with "ThreadsPerTest=1" in local.txt and the other with "ThreadsPerTest=2" in local.txt.

I don't need benchmarks from any other cpu!

[QUOTE=Prime95;90808]Since Scott is swamped by real work, I retrofitted support for the current PrimeNet server into the development version of prime95. Because y'all have been so patient, I'm making a sneak peek of the future client available.

While I'm not asking for beta testers, I will look at any bugs you report. Dual core machines and weird firewall/proxy situations are most likely to exercise the new code paths and thus find bugs.



from the readme.txt:

WARNING: Pre-beta software. Read this file carefully.

[B]Do not install over your existing prime95.[/B] Copy your existing prime95
folder to a new folder and then replace the prime95.exe in the new folder
with this pre-beta version.

[B]Save files created by this prime95 cannot be read by previous versions.[/B]

There are no dialog boxes for entering your password, user name, and email
address. These must be in the prime.txt file.

Your prime.ini, local.ini, worktodo.ini files will be renamed with a .txt
extension. Primenet.ini will become a section within prime.txt.

In prime.txt, in the [PrimeNet] section, add the line "debug=1". This
version uses the cURL library for communications.

Multiple threads are now supported. In Worktodo.txt, the assignments
for the second cpu come after the [Thread #2] section header. To merge
two v24 folders into one v25 client, you'll have to move the save files
and update the worktodo.txt file manually.

Expect bugs. Multi-threading has introduced massive changes to the source
code. Also, this client was designed to work with a new server protocol.
I've retrofitted it to work with the current server. Obviously, the new
work types are not supported by the old server.

Linux version is not available.

User interface comments are welcome. Bug reports are welcome.


Download address is: [url]ftp://mersenne.org/gimps/p95v251.zip[/url][/QUOTE]
The communication thread says it's 'inactive'.

I started it originally without the 'debug=1' because there was no [PrimeNet] section, and it was unable to connect. After I shut it down and started it again having added the "debug=1" line, it now says Communication is disabled. Here's the PrimeNet section I have:

[PrimeNet]
debug=1
ProxyHost=
ProxyUser=

I just tried the new version since I have the problem with proxies at work.

prime.txt
With or whithout the line "UseHTTP=0"

I always get the same result :

[Nov 7 14:34] Updating computer information on the server
[Nov 7 14:34] URL:
[Nov 7 14:34] [url]http://mersenne.org/cgi-bin/pnHttp.exe?uu&4&232&4&7055&14219&S000000&AAAAAAAA&JJWVISSER-251Jacob[/url] Visser&Jacob+Visser&smtpaddress@smtpdomain.org&&&0
[Nov 7 14:34] Port number too large: 17797704
[Nov 7 14:34] Visit [url]http://mersenneforum.org[/url] for help.

Hereunder the PrimeNet section of Prime.txt:

[PrimeNet]
Debug=1
ProxyHost=pxybebr004.europe.unity:80
ProxyUser=Domain\UserID
ProxyPass=FFFFFFFFFFFFFFFFFFFFFFFFFF
ProxyMask=1

I have tried with and whithout "http://", with and whithout portnumber,the result remains the same.

Drew, is "UsePrimenet=1" set? Did you try forcing a communication with Advanced/Manual Communication?

Jacob, a new zip file has been uploaded for you to try. There are some cURL options I don't know how to set for proxies. This may take a few iterations to get right.

[QUOTE=Prime95;90864]Drew, is "UsePrimenet=1" set? Did you try forcing a communication with Advanced/Manual Communication?[/QUOTE]

Yes to both...I was able to communicate manually.

With new new version configured from the PrimeNet/Connection menu item the reported faulty port number changed:

[Nov 7 17:27] Port number too large: 18846280
[Nov 7 17:27] Visit [url]http://mersenneforum.org[/url] for help.

Jacob, are you sure you are running the executable dated today at 9:55 AM?

Also, try setting debug=2 -- although I don't think that will give us significantly more debug information.