Machine is a W2K athelon, was 640K RAM. Shut it down, properly, pulled out the old stuff and put in 2 512Ks in the other slots, rebooted. Now BOINC says that it can't connect to hostname ..... I have checked, and I can connect to the rosetta_cgi/cgi through a browser.

Do I need to un-install and re-install? All of the settings seem to be what they have been.

Thanks for reading.

berk

---

I'm assuming that you started off with a 512 Meg simm and a 128 Meg simm, and have added 2 more 512 Meg simms on a Athlon motherboard with 4 memory slots.

If you remove the 2 new 512 Meg simms, does it connect like it's supposed to? And if so, do the new 512 Meg simms work if they're the only simms added to the system (in the slots that the original simms were in)? Some of us prefer to upgrade in powers of two.. 256Megs, 512Megs, 1024Megs, 2 Gigs, etc, from bad experiences with certain pentium cpus that couldn't handle 48Megs or 96Megs of ram properly.

Mixing memory timing can cause errors, but not letting a DC program connect to get more work is a peculiar result. The above steps should help determine if you've got corrupt memory, bad memory slots, or if you're overclocking, if you need to relax the timing so you can use all 4 memory slots at once.

To identify or rule out memory errors as being the source of this error, download and run memtest86+ - which I've generally tried to run overnight to prove that the new memory works fine in a system.

For help specific to your motherboard, there's sections of the Rebel's Haven Computer Forum setup for both 32 and 64 bit Athlon motherboard advice broken down by the major manufacturers (MSI, DFI, etc). Feel free to stop by www.rhcf.com and ask there.

If the problem ends up being software related, by the time you've run through the preceeding steps, perhaps those more familiar with Boinc & Rosetta will have ideas on what might be corrupted.

---

Questions should be posted in the "Number Crunching" forum. When you post there, please include the messages from the Messages tab that say "cannot connect" etc. We'll need the error numbers at the very least. Thanks!

---

Well, whatever it was, the problem seems to have become an item of history. Things are working again as they should.

Thanks, all.

b-

---