On 31 May 2001, at 14:13, Thomas Womack wrote:
> 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.
Here's what I'd do. (I've used this method on many occasions in the
past to feed systems which can't use PrimeNet, usually because
they're running MacLucasUNIX, Mlucas or Glucas).
1) On your Primenet-connected system, in the Test/PrimeNet menu,
uncheck "Request whatever type of work makes most sense", and check
the "primality tests" box in the "Type of work" section (which will
become active once you've unchecked "makes most sense").
2) Now set "days of work" to more than you actually have at the
moment. Check "Contact PrimeNet server now" in the Advanced/Manual
Communication menu (after connecting to the net, if neccessary). The
client will now pull a new LL test assignment. (linux users note,
"mprime -c" causes an immediate server connection.)
3) Reset the "most sense" & "days of work" back to their previous
values. Print the contents of worktodo.ini then delete the last line
from it using a text editor (this is the assignment you just pulled
for the other system). The PrimeNet connected system will now run
normally, as though nothing had been done - except that the
assignment you just got will show in your personal account under its
system name.
4) Add the assignment to the end of worktodo.ini on the unconnected
system by copying the line from your printout to it using a text
editor.
5) If you wish, you can use the PrimeNet manual assignment form to
change the expected completion date, and set the system name if
desired. The unconnected system will probably show up as "type
unknown" in your personal report, but this doesn't matter.
6) Finally, the result can be submitted using the PrimeNet manual
assignment form - or, since you will be using Prime95 or mprime, you
could copy a very late Pnnnnnnn save file to the connected system
using "sneakernet", add the assignment line back into its
worktodo.ini file _at the beginning_ then stop & restart the client
so that the last few iterations are run on the connected system (as
well as the unconnected system) & the result sent automatically. This
latter method is a bit messier but does let you get the CPU credit.
>
> 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?
Probably not. But you could simply have used mprime -m to get at the
menu & changed the computer system name there. PrimeNet will be
informed the next time mprime checks in, or immediately if you use
mprime -c having exited the menu.
Regards
Brian Beesley
_________________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
