SuperPI 2.0 on the horizon?

[IvanAndreevich]

Hey Fugger (or anybody else who's in charge of sPI database and upkeep)

You got some major misconceptions about Super Pi and who wrote it.

[5-Clicks]

You got some major misconceptions about Super Pi and who wrote it.

Uh...maybe you should look around a bit next time before you accuse me of "major misconceptions"

http://www.xtremesystems.org/forums/...ad.php?t=82419

We took over the project and now are the proud owners of Super Pi Mod.

For download or validation please visit:

http://www.xtremesystems.com/pi

Fugger, being the owner of XS, is also owner of SuperPI.

[charlie]

maybe one BILLION digits of Pi??

[kyosen]

Fugger, being the owner of XS, is also owner of SuperPI.

Yeah FUGGER is the owner of XS, but I cannot help feeling
huge incongruity for the expression "owner of SuperPI".
In terms of copyright, SuperPI-mod lives in "gray area", I suspect...
...I don't know whether FUGGER had received the formal permission of
modifying SuperPI from Kanada Labs. in University of Tokyo, though.
Of course, I have no intention to blame FUGGER or
any contributor of SuperPI-mod!!!
I love SuperPI-mod, and I appreciate many efforts to modify SuperPI
for obtaining several great functions...displaying millisecond and
generating validation checksum, etc....and it's enough for me

[mursaat]

What are you expecting to happen in a new superpi??

it calculates Pi to a specified amount of digits.. what exactly can you improve? LOL

Now it's you who hasn't thought this answer IMO.

He said on first posts to make 64M and 128M...


Well I don't think that's necessary, you can always prime for half an hour too

[corvus_corax]

I think that 64M or 128M options would be nice option, i mean, SuperPi is very used for tweaking RAM and with the new systems with 2GB+ 32M could be short about allocated memory, i think that 64M would allocate around 512MB and 128M around 1GB.

Nevertheless is possible more than one SuperPi instance

[blossa]

Yeah, a "multithreaded option selector" would be nice:
1. use all cores for ONE calculation

or (selectable)

2. run as many instances as there are cores (i know i can run four instances today but i have to do it 'manually')