OK just updated to Boinc v4 and when i'm trying to send/receive WUs BOINC is eating up all my CPU time and usually even crahsing the machine. Have no idea at this point - gotta check this with Win2K...

Describe your issue a little more. Are you getting Fatal errors with Boinc_gui? Is the machine/boinc "locking up" just after starting boinc?

These are a couple of the issues I am facing with some of my W9x clients.

Rob
<A>

Same problem here, the machine freezes slowly when Boinc is running. It is getting slower and slower until total stop.

Killing the task lets the machine run normally.

Volker

As long as network access is disabled everything is working fine but when sending CPU usage is over 75%, machine unusable even lowering priority doesnt help. And it doesnt produce error messages at all; stderr.txt is empty.

Win 98/ME: Please note that CPDN/BOINC does not seem to be compatible with
Windows 98 & ME, we are looking on fixing this compatibility problem by the
time of the launch in a few weeks or in a beta upgrade in a week.

This was in the e-mail I got when I joined the CPDN/BONIC beta test. I don't know if there is still a problem with Win 98/ME but it might be a starting point for more information. Win 98 never was much good for memory intensive programs anyway.
Hope some of this helps. Anyone else got any ideas?

same problem under win me, computer get very slow, ctrl+alt+del and boinc_gui (not
responding)

Yes but BOINC v3 was working fine. Hope someone will get this dome somedays...

I just proxied into the remainder of my 98 machines and they are ALL sitting with invalid page fault errors. I'm pulling Boinc off these PC's till the next update. Good thing they all have classic on them still. ;-)

Here's a glimps at one:

BOINC_GUI caused an invalid page fault in
module KERNEL32.DLL at 018f:bff88396.
Registers:
EAX=c00309c4 CS=018f EIP=bff88396 EFLGS=00010212
EBX=006effec SS=0197 ESP=005efe98 EBP=005f0010
ECX=00000000 DS=0197 ESI=00000000 FS=3367
EDX=bff76855 ES=0197 EDI=bff79060 GS=0000
Bytes at CS:EIP:
53 56 57 8b 75 10 8b 38 33 db 85 f6 75 2d 8d b5
Stack dump:

Rob
<A>

> same problem under win me, computer get very slow, ctrl+alt+del and boinc_gui
> (not
> responding)
>
>
I'm glad I was not the only one. Everything was smooth until this last upgrade. I'm going to leave BOINC network access turned off for now and just keep checking in here to see when it is fixed. I have enough to keep it busy for about 3 or 4 days - then I'll just go back to classic.

hmmm... got one too:

------------------------
BOINC_GUI verursachte einen Fehler durch eine ungültige Seite
in Modul KERNEL32.DLL bei 019f:bff88396.
Register:
EAX=c0030930 CS=019f EIP=bff88396 EFLGS=00010212
EBX=006effec SS=01a7 ESP=005efe98 EBP=005f0010
ECX=00000000 DS=01a7 ESI=00000000 FS=10b7
EDX=bff76855 ES=01a7 EDI=bff79060 GS=0000
Bytes bei CS:EIP:
53 56 57 8b 75 10 8b 38 33 db 85 f6 75 2d 8d b5
Stapelwerte:
-----------------------

blah...

BOINC 4 (specifically the GUI program [boinc_gui.exe]) doesn't seem to be very happy with some windows 98/ME machines. I haven't seen or figured out a reason yet, but i do stress that my windows 98 machine has boinc 4.05 running SETI ONLY. and fully working too.

-Fox
[/url]

Roger that...my PCs that have 98SE on them are all working fine with BOINC 4.05. Of course that's all they do is crunching for SETI.
L24

Just tested it with the BOINC cli - same thing so maybe it's the seti client and not BOINC?

Over in the "Questions and Problems -> Windows" forum (where it seems such a thing should be posted), I posted details about the BOINC 4.05 + SETI 4.03 clients appearing to have corrupted the FAT on the C: drive of my WinME system. See here for details. NOTE: BOINC 3.19 worked just fine on WinME.

It went through the "slower and slower" phase reported in this thread, then the "freezing" phase, and now it is unable to complete a boot sequence.

Has anyone else suffered from a corrupt FAT since installing the new clients?

I suggest everyone temporarily stop the BOINC client and run a disk health checking utility (like Windows' ScanDisk or Norton's DiskDoctor) to see if you have a developing problem. If all is well, restart BOINC.

(Aside: I only came to this forum because it seems that the people involved in creating/maintaining the BOINC/SETI clients don't visit the "Questions and Problems" forums, but only post their wisdom locally here. When problems are noticed, they will likely be reported first in the "Questions and Problems" forum and people will be looking for answers there.)

I have been having problems with this since SETI@BOINC has gone public. I had gone back to classic SETI due to all the aggravation, but thought it might have been fixed with BOINC 4.X and installed BOINC again on my humble Win98 PC to test it before I went and installed it on my two other Win XP PC's.

Still the same problem, it stops responding after it completes each WU. The PC has to be restarted with a hard restart (I'm not a big fan of doing that) and it all ways happens at the same time with 100% completion of one WU & 0% completion of the next WU.
I'm not sure if its corrupting the file system or not, due to having to have the PC reset, that causes it to run ScanDisk at start-up.

I know this is a BOINC problem because I have had it running stable with over 30 days up time using SETI classic with no problems.
BTW...That is all this PC is used for, except for occasionally watching a DVD in the bedroom, so no other changes have been made other than installing BOINC.

> I have been having problems with this since SETI@BOINC has gone public. I had
> gone back to classic SETI due to all the aggravation, but thought it might
> have been fixed with BOINC 4.X and installed BOINC again on my humble Win98 PC
> to test it before I went and installed it on my two other Win XP PC's.
>
> Still the same problem, it stops responding after it completes each WU. The PC
> has to be restarted with a hard restart (I'm not a big fan of doing that) and
> it all ways happens at the same time with 100% completion of one WU & 0%
> completion of the next WU.
> I'm not sure if its corrupting the file system or not, due to having to have
> the PC reset, that causes it to run ScanDisk at start-up.
>
> I know this is a BOINC problem because I have had it running stable with over
> 30 days up time using SETI classic with no problems.
> BTW...That is all this PC is used for, except for occasionally watching a DVD
> in the bedroom, so no other changes have been made other than installing
> BOINC.
>
>
>
>

>
> It went through the "slower and slower" phase reported in this thread, then
> the "freezing" phase, and now it is unable to complete a boot sequence.
>
> Has anyone else suffered from a corrupt FAT since installing the new clients?
>
> I suggest everyone temporarily stop the BOINC client and run a disk health
> checking utility (like Windows' ScanDisk or Norton's DiskDoctor) to see if you
> have a developing problem. If all is well, restart BOINC.
>
Just did a defrag and all is fine - no FAT issues - but am still concerned about the hangs on both Win98 and ME. Has anyone found a cure for this yet?

See here and here for reports of disk corruption following the BOINC 4.05 upgrade. There are several other threads about serious problems, as well. And there are certainly going to be other folks that have had serious problems (with or without disk corruption) but haven't posted anything in the forums.

Has anyone seen any of the Devs recently???? They don't seem to have noticed any of these posts, nor have they put any news about the problems on the front page.

I need someone to fix my system drive's corrupted FAT, caused by the BOINC 4.05 + SETI 4.03 upgrade!!

Running Win98 here. Same thing - Boinc wants to eat all of the memory and hangs from time to time. Didn't any testers report this before offering it to us?

I've wasted too much time with this. I realize that a lot of the people intimately involved may be volunteers but I'm willing to bet at least a few in charge are paid. Or is anyone really in charge or responsible?

I'll check from time to time and IF the kinks get worked out I'll probably try it again. For now I'll hang w/ Classic.

> Running Win98 here. Same thing - Boinc wants to eat all of the memory and
> hangs from time to time. Didn't any testers report this before offering it to
> us?

They likely didn't have a Win9x system to test things on. They should still have had some volunteers test it on Win9x systems, or they should have specified that it is NOT known whether it will work on Win9x.