The XP is P4 2.4 GHZ.
The Vista is a Pentium Dual Core 4300
And another Vista is a Core Duo 2300

Mainly it was the XP machine but the others had some errors too.

When I checked the result status logs it would appear the "maximum runtime exceeded" message even though some Wu's took less than 6 or 12 hours.

This was back in 2010.I havent done any HCMD2 Wu's since then.

I'm not sure about the swapSpace thing but as far as memory is concerned, I happen to have done an intensive (about 1.5hrs for two passes) Memtest_v4.1 (comes with Ubuntu_10.10 install) RAM check just 3-days ago and no fault was detected in that test.

As far as my desires for CMD2 goes, I want to add my contribution there, but I'm discouraged by the large Invalid results. Nobody gains from a cruncher's Invalid results: not the science nor the cruncher possibly chasing badges. All along, electricity is spent, and for naught. That has got to hurt.

Slim chance I'd say; some systems/mechanisms/problems seem to be kept hidden and either solved behind closed doors or just never resolved. I don't recall seeing too many minor bug fix notices here.
In the past I have seen systems that were just prone to errors for some tasks. They ran other tasks fine, but occasionally started failing tasks for one project, sometimes resulting in run-away errors (one failure after the other). For this reason I usually run more than one project. Others have succumb to this in the past. WCG might perceive these issues as very minor; they only affect the odd user now and again, so I can understand not wanting to spend lots of time investigating the problem or even announcing a solution. I put most of the blame down to system hardware/ operating system combinations; some setups just seem prone to failure, but use a different operating system on the same hardware and all is well.
For some perspective I have not seen one task fail from any project in 2months at WCG - that's 10K results without error. Wish I could say the same for some other project that don't seem to understand the concept of Beta testing.

If what affects CMD2 as discussed earlier in this thread is classed as a bug and falls below the 5% eventHorizon for elevatedBugHunting, then never mind adding other concerns like those related to wingman/quorum matching issues -- which would only add burden to an already apparently overtaxed system.

Now that I've heard indications suggesting that chances are high that the CMD2 issue I raised will not be addressed, let alone solved, I can settle for simply changing to whatever project works for my machines. Happy Crunching, everyone !

[OT]Good points, but might have been better raised in another/new thread.
A couple of things I appreciate about limited run times are that tasks will never continue indefinitely, and it also means you get through a reasonable number of tasks on an average system each day.[/OT]