oh and i did get a response from matey although it dint actually say anything more than the web site (automated perhaps?)...
-----Original Message-----
From: Ken Reneris
Sent: 08 February 2001 00:45
To: Russ Bathurst
Subject: RE: SetiQ v3.03
1. The CPU usage thing is fixed in beta3.
2. The separate queues keep seti@home happy as the have revisioning
issues where when the send a WU they don't necessarily want a different
clients processing them.
3. If the status bar says "idle" then there's nothing to do and hance
the "connect now" option is grayed.
- Ken
---- MSG END -----
my msg (you may notice the questions wern't all answered):
I'm currently using 3.03Beta3a (started using beta2a)
It all looks very pretty but i prefered the old one, nice simple and it
worked, why is it neccesary to have a different q for each type of
client, winnt, solaris 2.6,2.7,2.8, linux etc etc, so that when a q runs
out for a particular client type it wont get any more WUs even though
there maybe plenty of WUs in a q for another type, this is not good.
For some reason today, Q is telling me that the seti server has 'run out
of work units' i find this hard to believe, seeing as if i dont point a
client (running on the same machine) to the Q it gets a unit fine, yet
the q is empty (for that client version) and it wont get any more for
the reason above.
Why is the connect now option under the file menu always greyed out in
the gui and it doesn't even have the option in the web interface, plus
the connect option on SQ.exe is very confusing, what does it actually
mean?
To sum up i miss the old version of q, pretty as this one may be, its
loseing me loads of WUs!
On another note, a freind of mine is running 3.03Beta2a on a machine and
it eats 12-16% of the CPU most of the time!
Any thoughts/comments/solutions? Like how i can get the old version to
work with the new clients and seti servers, because i think this is the
most efficient way of doing things!
Russ