I have a P4/1300 which doesn't have an Internet connection.
So, to get work units to and from it, I copy the whole prime95 directory to
my K6/333 laptop which *does* have an Internet connection, and then run
prime95.exe to get it to talk to the server.
The K6/333 is something like a factor 24 slower than the P4/1300, and is
often turned off, so I don't run any prime95 computations on it at all.
The problem is, the P4 code in prime95.exe obviously won't work on the
laptop. So when I run on the laptop, it rewrites local.ini to indicate that
it's a Pentium [though it _doesn't_ change the MHz figure], and then
collects work units as if it were a Pentium/1300.
All I can think of is telling the K6/333 that it's actually a K6/8000,
waiting for it to contact the server and collect work sized for a K6/8000,
which the P4 should be able to run through at the correct rate, and then
copying the worktodo.ini file obtained by this subterfuge to the P4 to get
the work done. This seems somehow inelegant, particularly in that my account
report now says that I have an 8000MHz K6 machine called Tom_s_P4 ... what's
the right way of doing it?
As another point, I have five Athlon/850 machines in the computer lab at
college; so I've installed mprime in five separate directories on the shared
file space, and let it allocate its own computer names. Yesterday I got fed
up with trying to remember that CA1C7B916 was actually the machine called
ouzo, so I stopped mprime on each machine, edited local.ini to change the
name, and restarted mprime. Has this confused everything horribly?
_________________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
