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.
Messages are sometimes shown with an interrupt.
The dissable network access message will sometimes shown with the next one generated by the client.

greetz Mike

---

With each crime and every kindness we birth our future.

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.....

---

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.

good job fred. i still kick myself for missing boinc alpha and E@h alpha got the other two plus alphaed cpdn

---

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

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

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

4.13 IS the current Version.....Public release....

> i don't think that they even update the boinc alpha
> site anymore anyways. They are saying that 4.56 is the
> most updated version
> when the boinc page gives you 4.57.


This is the current version! of Boinc
http://boinc.berkeley.edu/download.php

This is where you'll find the info you need
to post Alpha problems,,,

Go Here!
http://boinc.berkeley.edu/community.php

Under
Mailing lists

---

how yor message got there before mine i dont know since it wasn't there when i hit the reply button i don't know but here is the alpha site
http://setiboinc.ssl.berkeley.edu/boinc_alpha/
Account creator is perpetually closed and no one updates the news since they started the e-mailing system. so its totally useless.
just to let you know 4.57 fixed some of the issues in 4.56. A big one being that it won't kill your cpdn stuff if you ever decide to run it.
Mr anderson is working on 4.58 right now and when you suspend a project it won't be allowed to still connect to the web. that should fix all your issues.

---

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

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

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.

Since the BOINC client must always be manually downloaded & installed, you have never been "forced" to run anything, but if an upgraded version "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 have screwed-around on your machine, or for that matter if you're sleep-walking or something...

Seti-"classic" have reportedly a problem with the cli refusing to shut down under win9x, and the same solution will maybe also work under BOINC, but don't remember the solution...

timmy the problem is that you have to be a member of the alpha site to post there. plus janus is the only one that is ever there and as far as i can tell he/she is only in control of the message boards at the boinc alpha\beta sites and the people here use his\hers creations here. The seti site has been where we have been told to report to by the other boards (cpdn lhc etc.) about client problems anyways. i don't think that they even update the boinc alpha site anymore anyways. They are saying that 4.56 is the most updated version when the boinc page gives you 4.57. and sir if you want it you can get it here. http://boinc.berkeley.edu/download.php?dev=1

---

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

> Suggestion,
>
> 1. If you are alpha testing then you should post this to
> the Alpha Newsgroups Not here!
>
> 2. There is a reason they warn
> you the the release is buggy.
>
> 3. Please report this to the Alpha site.
>
>
> Thanks,
>
> Timmy
>

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.

Suggestion,

1. If you are alpha testing then you should post this to
the Alpha Newsgroups Not here!

2. There is a reason they warn
you the the release is buggy.

3. Please report this to the Alpha site.


Thanks,

Timmy

---

OK so before you read the rest of this, please take the time to read this little bit. I am not interested in recriminations though they WILL happen so this time I am not getting into it. Please note that comment is directed at the general populace, not the coders.

Report:

Win XPSP2:

An interesting sorta problem. I have a latop using a P3 1.13Ghz that I do Seti through Boinc on (which I will call Boinc/Seti for the hell of it. Note that I dont do other Boinc project work). On the laptop it is almost always not a problem. The occasional problem Boinc causes on XPSP2 on that machine cant be pinned down by me as yet so there's no use going on about it but note that I shut Boinc/Seti down and the rest of the laptop probs being experienced at that moment instantly go away - UNLESS, like yesterday, it was a stinking hot day (well it IS Summer!) in which case my laptop, known to play up when it gets that hot, plays up. Normal days and in Winter it isnt ever a problem so you can see that the biggest problem is I have a cheap (and I dont mean cost) brand laptop where the cooling isnt adequate in Summer if left on for extended periods. Turn it off and it is OK for an hour or so after turning it back on again when it has cooled down. This still doesnt get to why it plays up with Boinc/Seti on cooler days (such as happened last week with a top of 15C in Summer which was GREAT for a Summer day!). Still no leads on that.

XPSP2 on P4 3.4 with multithreading using, to put the term loosely, "2 CPUs". We all know - for clarity - it isnt a motherboard with 2 physical CPUs or even the slots for 2. OK? Anyway, I now have 1 gig of dual channel DDR running fast.

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. Terminating the prog then restarting it did nothing. Rebooting, once in a great while, did something but mostly didnt. I changed my prefs on the web site here to 1 CPU and removed Boinc/Seti and reinstalled which, as it turns out, allows the prog to run normally for that session only. I got it to update on the web site and it went to 1 CPU. I rebooted and still the problems. I uninstalled and reinstalled, finally getting rid of all transfers (7 to send back now lost to me) and all work ready to be done thinking that just maybe, in some way I couldnt work out, that had something to do with it. Nothing. No change after reinstall.

So, in a last ditch desperate effort before throwing the damned thing out as I was getting mighty upset with it, I uninstalled it AGAIN and then went on a hunt on C drive for anything with "boinc" in it and deleted it. Apart from the leftover folder containing the work and such, I found, interestingly, "boinc.MSI" which is the installer for the prog. It would appear that boinc.MSI is never cleaned up after the install successfully completes. So, I had a Boinc.MSI sitting there never overwritten by the install routine and taking over from it. I have no idea which VERSION of Boinc/Seti that was from so in case the MSI changed from some other version to 4.56, it may have been the whole reason for my heartache. WHY? Since finding and deleting it, I reinstalled 4.56 and for 12 hours of turning the machine off and on, now updated to use 2 CPUs again, there hasnt been a problem. I reserve judgement, naturally, as 12 hours isnt long enough to be 100% sure but there it is.

So, coders, how about deleting boinc.MSI after a successful install? It may save future problems.

WIN98SE

The problem still exists under 4.56 of Boinc/Seti with this OS. All runs quite OK but you can NOT shut it down with the Start button then Shut Down, nor can you reboot it using that nor can my backup prog do it either to backup (image backup using Drive Image 2002). In all of those cases, Boinc/Seti complains that IT has to be shut down FIRST thus my machines wont backup unless I remember to shut Boinc/Seti down manually, first. In fact the ONLY prog that I have that will cause the machines to shut down when Boinc/Seti is running is Wizmo by Steve Gibson set to rudely FORCE a shutdown no matter what. You can see that COULD cause problems, no doubt. So why wont Boinc/Seti respond to a Windows shutdown or an attempt to shut down using my backup prog which uses the normal windows shutdown procedure itself? Earlier versions of Boinc/Seti allowed it OK. Why the change here?

Anyway, that's all the info I have for now and as I said above, I am not entering into recriminations with anybody. This is JUST a bug report and as I have found out WHY it wasnt working well with my 2 CPU P4 and also how easy it is to fix for the coders, I hope it will be added to the code.

Thanks,

Greg.