[QUOTE=japelprime;306676]I have prpclient-4.3.0beta-windows-gpu version to play around with. Is that the latest gpu-version for windows?[/QUOTE]

PRPNet is not a GPU application, but it can run geneferCUDA and wwwwcl, which are GPU applications. PrimeGrid has PRPNet servers that accept clients that can run these programs.

I am having trouble getting my new server to start. I installed mysql and the odbc connector. I created the database and ran the script on it.
Whatever I do I can't get the server to connect to the database. Is there a way I can work out at which point it is failing to connect so I can sort it?

[QUOTE=henryzz;311847]I am having trouble getting my new server to start. I installed mysql and the odbc connector. I created the database and ran the script on it.
Whatever I do I can't get the server to connect to the database. Is there a way I can work out at which point it is failing to connect so I can sort it?[/QUOTE]

Set debuglevel=1 in the server. It is most likely an issue with your database.ini file. What OS is this on?

[QUOTE=rogue;311852]Set debuglevel=1 in the server. It is most likely an issue with your database.ini file. What OS is this on?[/QUOTE]

It is windows 7 64-bit. The database.ini is the same as it was when it worked on my old windows installation except that I changed the database name from prpnet5 to prpnet.
[code][2012-09-16 16:49:51 GDT] 2: ODBC Connection via a driver: <Driver={MySQL ODBC 5.1 Driver};Server=localhost;Port=3306;Database=prpnet;User=root;UID=root;Password=nopw;PWD=nopw;Option=3;>
[2012-09-16 16:49:51 GDT] Connect to database failed: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, native code=0
[/code]

[QUOTE=henryzz;311853]It is windows 7 64-bit. The database.ini is the same as it was when it worked on my old windows installation except that I changed the database name from prpnet5 to prpnet.
[code][2012-09-16 16:49:51 GDT] 2: ODBC Connection via a driver: <Driver={MySQL ODBC 5.1 Driver};Server=localhost;Port=3306;Database=prpnet;User=root;UID=root;Password=nopw;PWD=nopw;Option=3;>
[2012-09-16 16:49:51 GDT] Connect to database failed: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, native code=0
[/code][/QUOTE]

Is the driver name correct? Maybe you have a different driver version of MySQL. The name should match the ODBC driver name you see in ODBC administrator. Also, make sure that you are using the 32-bit driver, not the 64-bit driver as the server is a 32-bit app (unless you rebuild it).

[QUOTE=rogue;311861]Is the driver name correct? Maybe you have a different driver version of MySQL. The name should match the ODBC driver name you see in ODBC administrator. Also, make sure that you are using the 32-bit driver, not the 64-bit driver as the server is a 32-bit app (unless you rebuild it).[/QUOTE]
I am using the 64-bit driver. Can I suggest adding that to the readme.txt for future versions?

edit: installing the 32-bit driver solved it

[QUOTE=henryzz;311863]I am using the 64-bit driver. Can I suggest adding that to the readme.txt for future versions?

edit: installing the 32-bit driver solved it[/QUOTE]

Certainly. When I originally released the Windows builds most people were still on 32-bit Windows. I think that has changed, which is a good thing as Window 7 is far superior to any previous version of Windows. Now if M$ could only rid themselves of the registry.

Discovered a slightly odd bug/feature today. I loaded a lot of fast work(280k candidates) into a riesel/sierp server. While I was loading the work clients were able to get candidates and return primes. The problem is that while it was still loading candidates(sorted by n) it continued testing a k after finding a prime(once all candidates were loaded the riesel/sierp code came into play). On several occassions it found a second prime for a k before the candidates finished loading. Both primes were put in the logs which is fine. However the larger of the 2 primes would be in the smallest prime column(on the webpage stats) rather than the smaller one. Next time I will shut down the clients. This couldn't be done for something like a CRUS public server though.

In addition to this I have a feature request:
Could there be a way(quite possible started by the prpadmin) to make the server output all the ks with no prime? Currently I put 200 ks into prpnet and get ~40 out. Unless I used lots of regex's and command line trickery I would have to manually make a list of the remaining ks.

[QUOTE=henryzz;312981]Discovered a slightly odd bug/feature today. I loaded a lot of fast work(280k candidates) into a riesel/sierp server. While I was loading the work clients were able to get candidates and return primes. The problem is that while it was still loading candidates(sorted by n) it continued testing a k after finding a prime(once all candidates were loaded the riesel/sierp code came into play). On several occassions it found a second prime for a k before the candidates finished loading. Both primes were put in the logs which is fine. However the larger of the 2 primes would be in the smallest prime column(on the webpage stats) rather than the smaller one. Next time I will shut down the clients. This couldn't be done for something like a CRUS public server though.

In addition to this I have a feature request:
Could there be a way(quite possible started by the prpadmin) to make the server output all the ks with no prime? Currently I put 200 ks into prpnet and get ~40 out. Unless I used lots of regex's and command line trickery I would have to manually make a list of the remaining ks.[/QUOTE]

I could fix the first issue you mention, but it would hurt performance when loading the server.

You can get that data via mysql by looking at the CandidateGroupStats table.

[QUOTE=rogue;312997]I could fix the first issue you mention, but it would hurt performance when loading the server.

You can get that data via mysql by looking at the CandidateGroupStats table.[/QUOTE]
I will investigate this once my machine with a server on it has internet after the 10th.

I've posted PRPNet 5.1.0. It has the following changes from 5.0.9:

prpserver: Fixed debug message.
prpclient: Allow only one instance of a client to run at a time from the directory.

You can d/l 5.1.0 from [URL="http://home.roadrunner.com/~mrodenkirch/prpnet_5.1.0.zip"]here[/URL].