Or if you happen to browse the /dl directory you can also get it.

> That CANNOT happen! YOU as a user
> must go to a totally different web page to download the Alpha software, it is
> NOT located anywhere NEAR the public stuff!

Actually, the default download-location for all BOINC-clients is now from http://boinc.berkeley.edu/download.php and by adding a little switch at the end you also get the alpha-client.

But this doesn't stop the fact v4.5x is marked as "Development version (latest features, possibly buggy)" and isn't recommended used.

> >
> > So if I understand this correctly. You are the ONLY person on this
> planet
> > that is actually having seti clients forced on their system? You are
> using
> > 4.56 out of necessity? I guess the 4.13 version won't run on your
> special
> > computers?
> >
>
> Like I said, I am not getting into recriminations. Figure out what is a puzzle
> to you for yourself. I can only tell you what happened.
>
GregH, what people are trying to tell you is to dump everything Boinc on your computer, download version 4.13, the PUBLIC release, and then go from there. If the problems remain then there is a problem that we can help you with. If you continue to use an Alpha version of the program, for whatever reason, there is little to no help we can give!
You are running software you are supposed to be running and then asking for help with it. Alpha and Beta sotware testers are "asked" to particpate! They "volunteer" their computers for the cause, you say your computer was "forced" to download an Alpha version of the program. That CANNOT happen! YOU as a user must go to a totally different web page to download the Alpha software, it is NOT located anywhere NEAR the public stuff! The software did NOT "force you" to upgrade, it CANNOT!
If you just dump 4.56 or 4.57 and go back to 4.13 we can help, but if you continue the way you are, you are out on a limb and someone is cutting your tree down.

---

> The BOINC client (I think) does "force" you to upgrade
> at certain intervals, by virtue of the message I seem
> to remember which is along the lines of "you can't have
> any new work, please upgrade to the newest software" (I am
> liberally paraphrasing.....), whereas the project SW
> (like SAH) actually upgrades itself automatically.

Yes. This is correct. The project can impose a minimum value for the version of the BOINC Manager and BOINC Deamon. However, if this was the case here we all would have been asked to ugrade. Since I haven't had a problem, and you haven't had a problem, why is he the only one with this problem?

In an earlier thread gregh stated the software for BOINC is the one and only thing that does not run correctly on his systems. And, collectively, we have been telling him to remove 4.5x and install 4.13 and have been met with insistance that he should be able to run 4.5x versions ...

> My $.02, and worth every penny.

Yes it is good advice ... and well worth twice as much.

@Dunc,

Yes, it must have sailed right over my head ... :)

Maybe I should stand up when I am reading?

---

There are a lot of people in this thread that know
a lot more about BOINC than I do: given that disclaimer -
and the fact that some of the facts as stated contradict
my wild theory, consider this, and feel free to correct me:

The BOINC client (I think) does "force" you to upgrade
at certain intervals, by virtue of the message I seem
to remember which is along the lines of "you can't have
any new work, please upgrade to the newest software" (I am
liberally paraphrasing.....), whereas the project SW
(like SAH) actually upgrades itself automatically.

While the BOINC client SW is not an automatic update, and
it does not physically perform an upgrade, at that point you
must upgrade BOINC to do more WUs. Maybe that's where
gregh found himself at some point, if he had been running
the production SW and then somehow retrieved a WU from the
beta site. Maybe beta was telling him the production 4.13
SW was too old.

Maybe thru some chain of events involving the alpha/beta
sites and the production sites (I know I've had to look
carefully at just what URL should be used for each, and
there have a number of them over the history of BOINC/SETI),
this troubled machine got "converted" from the production site
to the beta site, which then insisted on having the BOINC
client SW upgraded, and then auto updated the SAH SW to
match.

Unless you *want* to run the beta SW, I'd have to think the
way to go is to uninstall/delete all traces of BOINC/SETI and
reinstall from a fresh download of the 4.13 BOINC client.

My $.02, and worth every penny.

Dave

> Like I said, I am not getting into recriminations. Figure out what is a puzzle
> to you for yourself. I can only tell you what happened.
>
>


And the folks here are telling you that 4.53 (or any version for that matter) was NOT forced onto your system! And what I was saying was if it did happen to you then you would be the ONLY ONE that this has happened to. Now like has been pointed out to you for some time now, if you want to run stable code the go back to 4.13.

i have copies of every client since 3.22 except 4.52. I never saw that one come out and i dont have any copies of 3.23 and up if any came out since i alphaed cpdn and had to switch to 4.05. i can send out any of the installers through e mail if you want them.

yes there was a 4.53 but i didnt like it and rolled back to 4.13. I kept updating till i got to 4.55. That really sucked. that got me to roll back to 4.54. 4.56 was
ok. and i would reccomend 4.57 to anyone. ive ran it since the 23 of december and it hasent gliched running 247 since then.

When i ran 4.50 and .51 the upload bug didnt exist. by the way

---

~boinc its not the credit or satisfaction its the screensavers~
S@h Berkeley's Staff Friends Club ©members

> > That's one point I missed.
> >
> > I am using those versions because it was forced on me. Boic/Seti forced
> an
> > update on me that basically deleted completed WUs before I could return
> them
> > if I wasnt connected to the net at the time. In order to stop wasting my
> time,
> > I had to move to 4.56.
> >
> > I am using the Alpha version 4.56 out of necessity and have no idea to
> what
> > you refer when you say Alpha Site so this is where I, along with others,
> > report bugs.
> >
> > Thanks for bringing that point up that I missed.
> >
> >
>
> So if I understand this correctly. You are the ONLY person on this planet
> that is actually having seti clients forced on their system? You are using
> 4.56 out of necessity? I guess the 4.13 version won't run on your special
> computers?
>

Like I said, I am not getting into recriminations. Figure out what is a puzzle to you for yourself. I can only tell you what happened.

> Did we have a 4.53?
>

Alpha have tested all builds v4.50 to current v4.57, there v4.52 to v4.55 had fatal upload-bug, not sure if pre-v4.52 also had this bug... Most of these builds is "work-in-progress" with missing dialogues and other known problems before release, v4.56 among other things did purposefully disable service-install. Not sure if v4.57 was expected to be "feature-complete", but there's still some bugs to squish before ready for release...

For next build, the "suspend project" will actually pause the project and not continue asking for work if out of work, while a new choise of draining your work-queue for one project and not ask for more apparently also have been added. :)

> 4.13 WAS what I was using on all systems here until one day, 4.53 was forced
> on me and my system auto updated. From the moment that happened, I started
> losing WUs whenever the computers finished WUs and were not connected to the
> net. So, I updated to 4.55 hoping to overcome that but it didnt fix that
> problem and had to go to 4.56 which fixed that one.
>
> > Since the BOINC client must always be manually downloaded &
> installed, you
> > have never been "forced" to run anything, but if an upgraded version
>
> See above where it states I *WAS* forced when each of my computers contacted
> to get more WUs. There's the proof!

I think you are missing a key point here gregh...

The core client (BOINC) isn't capable of updating itself. The new version wasn't "forced" on you. The code isn't in place to make this happen. It was decided that an auto-updating core client was too big a system security risk.

The only code that is auto-updating are the project executables. (Meaning, the seti@home applications that do the work) The only way the core client can be updated is by manually downloading and installing the .exe.

So a new project .exe can/will be "forced" on you as you get more WUs, but the core client will remain untouched.

As others have already stated. Go back to 4.13... Alpha releases aren't intended for general consumption.

---

Did we have a 4.53?

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

he's running 4.56 anyways. i ran that for a cople months and it was rather glichy but nothing like what he says happened to me. my problem was that the window would blank out and look like i lost all my work but i didn't i would just have to press the corner close button and open another boinc manager button. All the stuff would be back because manager doesn't actually do the work the core client does and manager just displays stuff and would miss a rpc from the client.

---

~boinc its not the credit or satisfaction its the screensavers~
S@h Berkeley's Staff Friends Club ©members

@Paul D. Buck

I agree 100%

I think perhaps the sarcasm was buried a little too deeply ;-)

I for one have asked him in more than one thread now to roll back to 4.13 and see if he still has problems. However he insists that it 'forced him to upgrade' which of course is impossible as you confirm.

Keep up the good work :-)

Dunc

---

> I think that the bug in 4.13 that causes it to allegedly upgrade to 4.5x is
> more interesting than the problems with the 4.5x clients. Considerering that
> this was suppose to be impossible, and that the only way to upgrade the CC was
> by doing it manually. I think that this what needs looking at before many more
> peoples CC upgrade themselves without warning ;-)

Dunc,

It is impossible. The BOINC Daemon and BOINC Manager cannot install themselves through some back door. This was a decision made way early in the program even though a number of us suggested that it should be an option.

The only way that this can happen is if the participant goes to the alpha test project site and downloads the alpha version and runs the installer. This is another place where many of us suggested that this is a bad idea for the very reason that started this thread.

Gregh has now insisted that there are problems with the version 4.5x series and we have tried to convince him to stop using the alpha test versions as they are not stable. They are intended for development purposes only, and if use by a non-alpha tester they are completely on their own. In many if not most cases they will run fine. During the Beta test I never had a program crash on any of my systems even though others were having a terrible time with the various builds.

Because I am trying to finsh the first cut of documentation I had little interest in the ongoing testing. Besides, they did not ask me ... :)

---

I think that the bug in 4.13 that causes it to allegedly upgrade to 4.5x is more interesting than the problems with the 4.5x clients. Considerering that this was suppose to be impossible, and that the only way to upgrade the CC was by doing it manually. I think that this what needs looking at before many more peoples CC upgrade themselves without warning ;-)

Dunc

---

> That's one point I missed.
>
> I am using those versions because it was forced on me. Boic/Seti forced an
> update on me that basically deleted completed WUs before I could return them
> if I wasnt connected to the net at the time. In order to stop wasting my time,
> I had to move to 4.56.
>
> I am using the Alpha version 4.56 out of necessity and have no idea to what
> you refer when you say Alpha Site so this is where I, along with others,
> report bugs.
>
> Thanks for bringing that point up that I missed.
>
>

So if I understand this correctly. You are the ONLY person on this planet that is actually having seti clients forced on their system? You are using 4.56 out of necessity? I guess the 4.13 version won't run on your special computers?

> Hi
>
> I´m not sure if it helps on P4 but it works for me.
> I´ve deleted the autostart option manually and created a new one.
> What i´ve find out at 4.57 all is working but only at second time you try.

You sound like you are having some of the probs I had. Uninstall the prog, delete boinc.msi and reinstall after a reboot. You will find it goes away after that point and problems dont occur (well, 4.56 anyway). DOnt worry about losing partially done WUs. As long as you dont delete the dir, they all stay there and start where they left off so far as I have ever seen, taking into accoun that I havent run 4.57 before.

> Messages are sometimes shown with an interrupt.
> The dissable network access message will sometimes shown with the next one
> generated by the client.
>

I got absolutely nothing like I hadnt connected to a project. When I tried connecting, still nothing. Like I said above - try it!

Greg.

> Had this problem after upgrading to 4.57, "The problem with the P4 was that
> Boinc/Seti would not show the project, would not show the work listed being
> done or to be done, wouldnt show work to be transferred and wouldnt show
> anything" all I did was deleted the short cut and make a new one and all is
> well, running on a p4 3.0 HT.....
>

Yep. Did all that, too. It wasnt till I had uninstalled 4.56 AGAIN and then went on a search for anything with "boinc" in it that I found boinc.msi and deleted it. After it was gone from my system, it occurred to me that I should have looked at it. ;-} It could have been the one from 4.13 for all I know and thus not relevant to 4.56 but still in use when installing/uninstalling.

Anyway, since deleting it, all has gone well. Still about 24 hours only since that was done but it is about 18 hours better than my last "worked right" session! ;-}

Greg.

> @ gregh
> I forward you message to Rom, as he is on vacation in Alaska probably won't
> get a reply untill next week.
> Fred
>

Thanks. No probs waiting. You sorta expect it this time of year on anything. Just as long as when he gets back, he looks at it. ;-}

Alaska!! I once saw a White Xmas (back in 1996) when I went to Banff for Xmas. It was -45C when you stood outside NOT in the wind. I actually felt really good in that sort of cold and had a lot of fun but ALASKA????

I wondered where Runners went when they turned 30! ;-}

Greg.

> Boinc.msi very likely is used during uninstallation, so is therefore not
> deleted before you've uninstalled BOINC...
>

Still doesnt get over the problem though, does it? If you UNINSTALL Boinc/Seti entirely - eg, you have NO other project related to Boinc on your system after uninstalling Boinc/Seti - then the boinc.msi should be gone. It wasnt. Further, there is always the chance someone HAD Boinc/Seti on their computer, gave it up for a while and uninstalled it then came back to it some time later. The boinc.msi not being changed presents a problem - or at least a potential one.

> The last released client is v4.13, while the last alpha-build is v4.57, and
> you're using neither of these. And no, v4.57 have it's own bugs so it's not
> ready for release, so the recommended client is still v4.13.
>

4.13 WAS what I was using on all systems here until one day, 4.53 was forced on me and my system auto updated. From the moment that happened, I started losing WUs whenever the computers finished WUs and were not connected to the net. So, I updated to 4.55 hoping to overcome that but it didnt fix that problem and had to go to 4.56 which fixed that one.

> Since the BOINC client must always be manually downloaded & installed, you
> have never been "forced" to run anything, but if an upgraded version

See above where it states I *WAS* forced when each of my computers contacted to get more WUs. There's the proof!

> "magically" started running some day would take a very close look on thatever
> other person(s) have access to your computers, or whatever virus or hacker

I work in the job. No-one is on my machines and in fact they arent always connected to the net either and no, I dont have wi-fi as yet.

> Seti-"classic" have reportedly a problem with the cli refusing to shut down

When I last used the classic Seti V3.08 I think it was, no it didnt have that problem and neither did Boinc/Seti till 4.56 came out.

> under win9x, and the same solution will maybe also work under BOINC, but don't
> remember the solution...
>

There being no problem with classic Seti last I ran it, there was no soultion that could be applied to fit. About the only thing you can do is rudely shut down using a 3rd party program but that doesnt help when all you want to do is reboot to do an image backup.

Greg.