I just downloaded and installed the latest version 6.6.7. All of my attached projects are set to not get new tasks. However, immediately after the install completed, a CUDA task for GPUgrid appeared on my machine before I had a chance to do anything other than simply start the BOINC manager. I haven't run any GPUgrid in many days. After the install completed, all projects still say 'Won't get new tasks'. Also, I noticed in the messages tab, there are no messages showing the task being downloaded or even requested. In fact, here are the only messages I have.

2/13/2009 10:25:02 PM SETI@home URL: http://setiathome.berkeley.edu/; Computer ID: 4795615; location: home; project prefs: default
2/13/2009 10:25:02 PM GPUGRID URL: http://www.gpugrid.net/; Computer ID: 24701; location: (none); project prefs: default
2/13/2009 10:25:02 PM Artificial Intelligence System URL: http://www.intelligencerealm.com/aisystem/; Computer ID: 12227; location: (none); project prefs: default
2/13/2009 10:25:02 PM General prefs: from Einstein@Home (last modified 12-Feb-2009 09:26:12)
2/13/2009 10:25:02 PM Computer location: home
2/13/2009 10:25:02 PM General prefs: no separate prefs for home; using your defaults
2/13/2009 10:25:02 PM Preferences limit memory usage when active to 3680.51MB
2/13/2009 10:25:02 PM Preferences limit memory usage when idle to 4907.34MB
2/13/2009 10:25:02 PM Preferences limit disk usage to 25.00GB
2/13/2009 10:25:02 PM Running CPU benchmarks
2/13/2009 10:25:02 PM Suspending computation - running CPU benchmarks
2/13/2009 10:25:34 PM Benchmark results:
2/13/2009 10:25:34 PM Number of CPUs: 8
2/13/2009 10:25:34 PM 2537 floating point MIPS (Whetstone) per CPU
2/13/2009 10:25:34 PM 8173 integer MIPS (Dhrystone) per CPU


So, I don't know why it pulled a task when it was set not to, and why there are no messages documenting the task request and download.

Update: When I first saw the task appear, I put BOINC in snooze. After checking things out and doing the first post above, I decided to let it resume and see what happens. When I did, it did not get any further tasks. However, like clockwork, once the CUDA task resumed, my nVidia GTX cards immediately began to heat up until the point of failure when they crashed and caused a BSOD. That's exactly why I stopped running GPUgrid and other CUDA tasks. I have the latest drivers and everything in my system, yet for some reason, the nVidia boards refuse to crank up the fans to keep themselves cool when they start heating up. Once the temp gets in the mid to upper 60's, they become unstable and eventually crash. CUDA is the only thing I've ever found that will cause a problem with the nVidia boards. Even the most intense games such as Crysis with all settings at max don't bother these cards. I think CUDA just drives them to the point of failure with no way to throttle the work load, and with fans that won't speed up over the idle setting, that's a fatal combo. Anyway, that's the topic of other threads.

In any case, the question remains why it decided to pull in a task for a project set not to, and why it didn't document the process of getting the tasks in the message tab. However, it has not requested any other tasks for any other projects since, even after rebooting due to the BSOD.

Another Update: I've been doing some test runs for the temp problem in another thread, switching projects, and all sorts of activities and so far this version has worked flawlessly. Only that one glitch of getting a task when I installed that I mentioned in the first post of this thread. Otherwise, haven't had a single problem. It appears stable on my machine so far.

However, immediately after the install completed, a CUDA task for GPUgrid appeared on my machine before I had a chance to do anything other than simply start the BOINC manager.

This is a scheduler problem. The GPUGrid scheduler ignores the client's preferences of no new work and sends work anyway. GPUGrid will have to update their scheduler to the fixed version.

---

I just downloaded 6.6.7 and this is what I got in the message queue:

Host Project Date Message
ELEMENTS --- 2/14/2009 12:56:23 PM Processor: 2 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 2 Stepping 9]
ELEMENTS --- 2/14/2009 12:56:23 PM Processor features: fpu tsc sse sse2 mmx
ELEMENTS --- 2/14/2009 12:56:23 PM OS: Microsoft Windows XP: Home x86 Editon, Service Pack 3, (05.01.2600.00)
ELEMENTS --- 2/14/2009 12:56:23 PM Memory: 2.00 GB physical, 5.85 GB virtual
ELEMENTS --- 2/14/2009 12:56:23 PM Disk: 74.53 GB total, 29.06 GB free
ELEMENTS --- 2/14/2009 12:56:23 PM Local time is UTC -7 hours
ELEMENTS --- 2/14/2009 12:56:32 PM No CUDA devices found
ELEMENTS --- 2/14/2009 12:56:32 PM No coprocessors
ELEMENTS --- 2/14/2009 12:56:34 PM Not using a proxy
ELEMENTS Neural Networks simulation 2/14/2009 12:56:34 PM URL: http://193.144.240.190/nnsimu/; Computer ID: 330; location: (none); project prefs: default
ELEMENTS ABC@home 2/14/2009 12:56:34 PM URL: http://abcathome.com/; Computer ID: 14930; location: (none); project prefs: default
ELEMENTS 3x+1@home 2/14/2009 12:56:34 PM URL: http://allprojectstats.com/collatz/; Computer ID: 432; location: (none); project prefs: default
ELEMENTS RND@home 2/14/2009 12:56:34 PM URL: http://arcoboinc.unex.es/rnd/; Computer ID: 344; location: (none); project prefs: default
ELEMENTS CPDN Seasonal Attribution Project 2/14/2009 12:56:34 PM URL: http://attribution.cpdn.org/; Computer ID: 20571; location: home; project prefs: default
ELEMENTS wanless2 2/14/2009 12:56:34 PM URL: http://bearnol.is-a-geek.com/wanless2/; Computer ID: 2145; location: home; project prefs: default
ELEMENTS BelgianBeerAtHome 2/14/2009 12:56:34 PM URL: http://bebeer.dyndns.org:2222/bebeer/; Computer ID: 1729; location: (none); project prefs: default
ELEMENTS proteins@home 2/14/2009 12:56:34 PM URL: http://biology.polytechnique.fr/proteinsathome/; Computer ID: 24523; location: (none); project prefs: default
ELEMENTS AlmereGrid Boinc Grid 2/14/2009 12:56:34 PM URL: http://boinc.almeregrid.nl/; Computer ID: 656; location: (none); project prefs: default
ELEMENTS boincsimap 2/14/2009 12:56:34 PM URL: http://boinc.bio.wzw.tum.de/boincsimap/; Computer ID: 71351; location: home; project prefs: default
ELEMENTS malaria 2/14/2009 12:56:34 PM URL: http://boinc.cs.uct.ac.za/malaria/; Computer ID: 823; location: (none); project prefs: default
ELEMENTS DistrRTgen 2/14/2009 12:56:34 PM URL: http://boinc.freerainbowtables.com/distrrtgen/; Computer ID: 3324; location: (none); project prefs: default
ELEMENTS Leiden Classical 2/14/2009 12:56:34 PM URL: http://boinc.gorlaeus.net/; Computer ID: 22766; location: (none); project prefs: default
ELEMENTS SHA-1 Collision Search Graz 2/14/2009 12:56:34 PM URL: http://boinc.iaik.tugraz.at/sha1_coll_search/; Computer ID: 420; location: (none); project prefs: default
ELEMENTS Riesel Sieve Project 2/14/2009 12:56:34 PM URL: http://boinc.rieselsieve.com/; Computer ID: 17724; location: home; project prefs: default
ELEMENTS The Lattice Project 2/14/2009 12:56:34 PM URL: http://boinc.umiacs.umd.edu/; Computer ID: 630; location: (none); project prefs: default
ELEMENTS vtu@home 2/14/2009 12:56:34 PM URL: http://boinc.vgtu.lt/vtuathome/; Computer ID: 7119; location: home; project prefs: default
ELEMENTS BURP 2/14/2009 12:56:34 PM URL: http://burp.boinc.dk/; Computer ID: 39802; location: (none); project prefs: default
ELEMENTS superlinkattechnion 2/14/2009 12:56:34 PM URL: http://cbl-boinc-server2.cs.technion.ac.il/superlinkattechnion/; Computer ID: 738; location: (none); project prefs: default
ELEMENTS Cels@Home 2/14/2009 12:56:34 PM URL: http://cels-at-home-dev.dyndns.org/cels/; Computer ID: 203; location: (none); project prefs: default
ELEMENTS test1 2/14/2009 12:56:34 PM URL: http://dawn.ynet.sk/test1/; Computer ID: 1156; location: (none); project prefs: default
ELEMENTS sudoku 2/14/2009 12:56:34 PM URL: http://dist2.ist.tugraz.at/sudoku/; Computer ID: 245; location: (none); project prefs: default
ELEMENTS Docking@Home 2/14/2009 12:56:34 PM URL: http://docking.cis.udel.edu/; Computer ID: 7410; location: (none); project prefs: default
ELEMENTS geneticlife@home 2/14/2009 12:56:34 PM URL: http://genlife.is-a-geek.org/genlife/; Computer ID: 384; location: (none); project prefs: default
ELEMENTS NCSSM Grid 2/14/2009 12:56:34 PM URL: http://grid.ncssm.edu/ncssm_grid/; Computer ID: 460; location: (none); project prefs: default
ELEMENTS Hydrogen@Home 2/14/2009 12:56:34 PM URL: http://hydrogenathome.org/; Computer ID: 189; location: home; project prefs: default
ELEMENTS Cunning Plan 2/14/2009 12:56:34 PM URL: http://isaac.ssl.berkeley.edu/cplan/; Computer ID: 388; location: (none); project prefs: default
ELEMENTS MindModeling@Beta 2/14/2009 12:56:34 PM URL: http://MindModeling.org/beta/; Computer ID: 1430; location: (none); project prefs: default
ELEMENTS Project Neuron 2/14/2009 12:56:34 PM URL: http://neuron.mine.nu/neuron/; Computer ID: 2102; location: (none); project prefs: default
ELEMENTS NQueens@Home Project 2/14/2009 12:56:34 PM URL: http://nqueens.ing.udec.cl/; Computer ID: 237; location: (none); project prefs: default
ELEMENTS Predictor @ Home 2/14/2009 12:56:34 PM URL: http://predictor.scripps.edu/; Computer ID: 337689; location: (none); project prefs: default
ELEMENTS ralph@home 2/14/2009 12:56:34 PM URL: http://ralph.bakerlab.org/; Computer ID: 8490; location: (none); project prefs: default
ELEMENTS ibercivis 2/14/2009 12:56:34 PM URL: http://registro.ibercivis.es/; Computer ID: 35; location: (none); project prefs: default
ELEMENTS AlmereGrid TestGrid - Boinc 2/14/2009 12:56:34 PM URL: http://server1.almeregrid.nl/testgrid/; Computer ID: 407; location: (none); project prefs: default
ELEMENTS SZTAKI Desktop Grid 2/14/2009 12:56:34 PM URL: http://szdg.lpds.sztaki.hu/szdg/; Computer ID: 272473; location: (none); project prefs: default
ELEMENTS UH Second Computing 2/14/2009 12:56:34 PM URL: http://vcsc.cs.uh.edu/second-computing/; Computer ID: 588; location: (none); project prefs: default
ELEMENTS APS@Home 2/14/2009 12:56:34 PM URL: http://www.apsathome.org/; Computer ID: 1369; location: home; project prefs: default
ELEMENTS chess960@home alpha 2/14/2009 12:56:34 PM URL: http://www.chess960athome.org/alpha/; Computer ID: 48321; location: (none); project prefs: default
ELEMENTS DepSpid - Spider 2/14/2009 12:56:34 PM URL: http://www.DepSpid.net/; Computer ID: 2436; location: home; project prefs: default
ELEMENTS gerasim@home 2/14/2009 12:56:34 PM URL: http://www.gerasim.boinc.ru/Gerasim/; Computer ID: 1399; location: home; project prefs: default
ELEMENTS malariacontrol.net 2/14/2009 12:56:34 PM URL: http://www.malariacontrol.net/; Computer ID: 41798; location: (none); project prefs: default
ELEMENTS yoyo@home 2/14/2009 12:56:34 PM URL: http://www.rechenkraft.net/yoyo/; Computer ID: 1770; location: (none); project prefs: default
ELEMENTS uFluids 2/14/2009 12:56:34 PM URL: http://www.ufluids.net/; Computer ID: 48840; location: (none); project prefs: default
ELEMENTS World Community Grid 2/14/2009 12:56:34 PM URL: http://www.worldcommunitygrid.org/; Computer ID: 386135; location: (none); project prefs: default
ELEMENTS http://xw01.lri.fr:4320/ 2/14/2009 12:56:34 PM URL: http://xw01.lri.fr:4320/; Computer ID: not assigned yet; location: (none); project prefs: default
ELEMENTS --- 2/14/2009 12:56:34 PM General prefs: from superlinkattechnion (last modified 12-Feb-2009 07:36:34)
ELEMENTS --- 2/14/2009 12:56:34 PM Host location: none
ELEMENTS --- 2/14/2009 12:56:34 PM General prefs: using your defaults
ELEMENTS --- 2/14/2009 12:56:34 PM Reading preferences override file
ELEMENTS --- 2/14/2009 12:56:34 PM Preferences limit memory usage when active to 1637.38MB
ELEMENTS --- 2/14/2009 12:56:34 PM Preferences limit memory usage when idle to 1637.38MB
ELEMENTS --- 2/14/2009 12:58:30 PM Preferences limit disk usage to 31.46GB
ELEMENTS AlmereGrid Boinc Grid 2/14/2009 12:58:30 PM Restarting task vtwns_ad3407x21-SET6B_0 using cargoship_dbg version 503
ELEMENTS MindModeling@Beta 2/14/2009 12:58:32 PM Restarting task SASTNM_10-3-68814_1234230760_0 using mm_ACTR version 345
ELEMENTS --- 2/14/2009 12:59:04 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 12:59:09 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 12:59:22 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 12:59:24 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 12:59:32 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 12:59:33 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 12:59:43 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 12:59:44 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 12:59:53 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 12:59:54 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:00:04 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:00:05 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:00:14 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:00:16 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:00:25 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:00:26 PM Internet access OK - project servers may be temporarily down.
OFFICE FreeHAL@home 2/14/2009 1:00:27 PM Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
ELEMENTS --- 2/14/2009 1:00:36 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:00:37 PM Internet access OK - project servers may be temporarily down.
OFFICE FreeHAL@home 2/14/2009 1:00:37 PM Scheduler request completed: got 0 new tasks
ELEMENTS --- 2/14/2009 1:00:46 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:00:48 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:00:57 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:00:58 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:01:07 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:01:08 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:01:18 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:01:20 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:01:29 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:01:31 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:01:38 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:01:39 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:01:48 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:01:49 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:02:11 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:02:12 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:02:20 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:02:22 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:02:31 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:02:32 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:02:40 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:02:41 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:02:51 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:02:53 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:03:02 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:03:04 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:03:11 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:03:12 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:03:22 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:03:23 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:03:32 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:03:33 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:03:43 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:03:44 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:03:52 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:03:53 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:04:03 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:04:04 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:04:14 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:04:15 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:04:23 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:04:24 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:04:34 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:04:35 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:04:44 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:04:45 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:04:55 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:04:56 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:05:05 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:05:06 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:05:15 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:05:17 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:05:25 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:05:26 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:05:36 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:05:37 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:05:45 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:05:46 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:05:55 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:05:56 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:06:06 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:06:07 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:06:16 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:06:18 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:06:27 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:06:28 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:06:42 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:06:44 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:06:52 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:06:54 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:07:01 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:07:02 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:07:12 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:07:14 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:07:22 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:07:23 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:07:33 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:07:34 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:07:44 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:07:46 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:07:54 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:07:56 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:08:04 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:08:06 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:08:14 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:08:17 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:08:24 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:08:26 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:08:36 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:08:38 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:08:46 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:08:48 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:08:55 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:08:57 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:09:05 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:09:07 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:09:15 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:09:17 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:09:26 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:09:28 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:09:36 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:09:38 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:09:46 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:09:48 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:09:57 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:10:00 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:10:07 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:10:09 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:10:17 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:10:19 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:10:27 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:10:29 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:10:37 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:10:39 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:10:48 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:10:50 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:10:58 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:11:00 PM Internet access OK - project servers may be temporarily down.
ELEMENTS --- 2/14/2009 1:11:08 PM Project communication failed: attempting access to reference site
ELEMENTS --- 2/14/2009 1:11:10 PM Internet access OK - project servers may be temporarily down.

At this point I went back to 6.4.5

---

I just downloaded 6.6.7 and this is what I got in the message queue:
{snip}

Please follow the instructions on how to report these things to the Alpha email list.

---