I see a problem in transitioning my SETI@Home Classic team to the SETI@Home under BOINC.

I am the founder of a team under the SETI@Home Classic structure. I recognize the need to go to BOINC. I set up an account under BOINC and Searched for my team since it was reported that all teams were transferred. It wasn't so I created it. Now I see my team listed and it shows my team has almost the same number members it shows under the Classic team page, but none are listed. I must assume from this that they don't show up till they actually install the BOINC software and officially switch. Thus they don't run in parallel. Here lies the rub. According to the transition page FAQ:
http://setiweb.ssl.berkeley.edu/transition.php
------------
"Can I run both versions at once?"
"No; if you do this, SETI@home/BOINC won't get any CPU time because it runs at a lower priority. You must uninstall SETI@home Classic before running SETI@home/BOINC."
------------

I can not uninstall the Classic version, I am a Team Founder. I am not the top scorer but it is obvious that I am listed and turning in packets to everyone on the team page. I am the one who motivates them to keep at it, welcomes new members, comments that users are doing good, etc.

I had intended to set up a new account/E-mail for BOINC and run them in parallel for a while so I can answer questions about it as I ask them to transfer. I can understand how it will not be doing as many packets under one while the other is running. But I need to be in both at the same time to evaluate and administer both. It probably would not be such a big deal for a an average member, but for a Team Founder, it is necessary, regardless of how much time is calculated by my computer.

Also, the Team page should have the team members from Classic and BOINC listed in both with an indicator as to which they are using.
We even had an enthusiatic time member that died. His name and work unit credit is still listed on the page in rememberence and credit to the team.
If the Classic and BOINC are truly the same team it should not matter if the old data is transferred.

Other features would be nice, but these are a must.
I need to be the last one out the door under the Team page under the Classic structure. The alternatives to allowing Founders to be in both Classic and BOINC simultaneously, as I see it, are for us all to buy another computer for BOINC, wait till the Classic server is shut off, or have other team members take over for us under BOINC.

BTW: If it makes a difference, my PC uses multiple CPU's but I am running Folding@Home on that one. This arrangement works fine with Classic, I would think that it should be set to work under BOINC.

Re running SETI Classic and SETI BOINC at the same time, I hope this will be of help:

When I first downloaded BOINC, I uninstalled SETI Classic but soon reinstalled it as I was getting no work units from SETI BOINC. When I did get work units, I let them run. Now, I've got a Mac and that doesn't have a screensaver for BOINC, so you either have to run it all the time, in which case it uses any free processsor capacity all the time, or you switch it on and off as you want to use it. As most of the time there's nothing to process on BOINC, I'm still using SETI Classic in screensaver mode much of the time.

The only adverse effect is if you actually have both versions actually crunching data at the same time, which is when SETI Classic hogs most of the processor capacity.

Hi there...

Yes, it's true that Seti Classic takes priority over BOINC, however, if you're running XP, and possibly other systems that allow you to set priorities, you can Ctrl-Alt-Del, choose the Processes tab, hightlight The BOINC .exe and up the priority by one notch, which will give equal time to both Seti BOINC and Seti Classic. It will also, of course, extend how long it takes to do either.

Does this help or have you sorted it already?



Schi

---

<br>------
Anything the mind can conceive and believe can be achieved.... or.... May the fleas of a thousand camels infest your body and may your arms be too short to scratch. :)