Today, I installed the distributed.net client to run RC5-72 for the first time on my 766MHz Celeron "work" computer with Windows 2000 Pro (doing sound recording and powerpoint for a church). It runs almost all the time (unless the janitor or someone else who thinks they know better shuts it down), but only has a dialup connection once a week (when I bring one up manually, each Sunday afternoon). For that reason, I thought that RC5-72 would make the best project for this system, since it has the ability to cache units for periods of offline-ness. And yes, I do have permission to install software on this system, so that's not a problem.
Anyway, the client installed fine (I downloaded the latest - as of this morning - zipped client from distributed.net). I set it up to use my email address, to only work on RC5-72, to queue enough units for 168 hours, and to run in dial up detection mode where it will automatically send if a connection is available; I did not mess with the network interfaces part, assuming that was best left at its default settings. When I run the client, it says it is not able to find a network interface (that might not be the exact message, but it is something like that; the error message was displayed even when a connection was up), and proceeds to work on a random unit. When I go back tonight, I should be able to post the exact error message. Until then, is there any advice you can give me to try to get this thing crunching away for Team AnandTech?
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)
Discussion Intel current and future Lakes & Rapids thread
