It's a known problem that on Win98/ME the boinc client doesn't stop to count the CPU time when the app is suspended, so it reports the whole run time instead of just the crunching time.
> It's a known problem that on Win98/ME the boinc client doesn't stop to count
> the CPU time when the app is suspended, so it reports the whole run time
> instead of just the crunching time.
>
> BM
>
Yeah.
The only workaround that I know of at this point is to setup a venue that removes apps from memory when swapping applications. That seems to do the trick quite nicely, as long as you can keep the client from reverting back to the default venue [grin]
> It's a known problem that on Win98/ME the boinc client doesn't stop to count
> the CPU time when the app is suspended, so it reports the whole run time
> instead of just the crunching time.
>
> BM
>
Well, this machine (233 MHz P II) is dedicated to run 100% Einstein at the moment, so this is not an issue to me... ;-)
> Well, this machine (233 MHz P II) is dedicated to run 100% Einstein at the
> moment, so this is not an issue to me... ;-)
Yes, you can see that because the claimed credit is quite normal. If the Win98/Me bug was the problem you would have claimed over 300 credits. Like my host (5000) that claimes 250 credits for example. :-)
Nice time. Maybe I should try it once on my PII 266MHz Win95. ;-)
> I have this error on win98 since I upgraded to Boinc 4.19... :-(
>
> Einstein@Home - 2005-02-13 15:27:12 - Message from server: No work available
> (there was work but your computer doesn't have enough memory)
Currently the very last stage of our app uses up to 70MB of memory, so we had to increase the limits. Bernd is working on a bit of code restructuring so that less memory is needed. So in a few weeks at the most we should have a trimmed-down version that doesn't need nearly as much memory.
i'm proud of this result! ;-)
)
> http://einsteinathome.org/workunit/316637
>
> take a look at the cpu time of my host id 9207
>
> t_wolf
It was well worth the crunching time.
It's a known problem that on
)
It's a known problem that on Win98/ME the boinc client doesn't stop to count the CPU time when the app is suspended, so it reports the whole run time instead of just the crunching time.
BM
BM
> It's a known problem that
)
> It's a known problem that on Win98/ME the boinc client doesn't stop to count
> the CPU time when the app is suspended, so it reports the whole run time
> instead of just the crunching time.
>
> BM
>
Yeah.
The only workaround that I know of at this point is to setup a venue that removes apps from memory when swapping applications. That seems to do the trick quite nicely, as long as you can keep the client from reverting back to the default venue [grin]
> It's a known problem that
)
> It's a known problem that on Win98/ME the boinc client doesn't stop to count
> the CPU time when the app is suspended, so it reports the whole run time
> instead of just the crunching time.
>
> BM
>
Well, this machine (233 MHz P II) is dedicated to run 100% Einstein at the moment, so this is not an issue to me... ;-)
> Well, this machine (233 MHz
)
> Well, this machine (233 MHz P II) is dedicated to run 100% Einstein at the
> moment, so this is not an issue to me... ;-)
Yes, you can see that because the claimed credit is quite normal. If the Win98/Me bug was the problem you would have claimed over 300 credits. Like my host (5000) that claimes 250 credits for example. :-)
Nice time. Maybe I should try it once on my PII 266MHz Win95. ;-)
I have this error on win98
)
I have this error on win98 since I upgraded to Boinc 4.19... :-(
Einstein@Home - 2005-02-13 15:27:12 - Message from server: No work available (there was work but your computer doesn't have enough memory)
Maybe it helps to increase
)
Maybe it helps to increase the setting for
Use no more than xx% of total virtual memory
in your general preferences
> I have this error on win98
)
> I have this error on win98 since I upgraded to Boinc 4.19... :-(
>
> Einstein@Home - 2005-02-13 15:27:12 - Message from server: No work available
> (there was work but your computer doesn't have enough memory)
Currently the very last stage of our app uses up to 70MB of memory, so we had to increase the limits. Bernd is working on a bit of code restructuring so that less memory is needed. So in a few weeks at the most we should have a trimmed-down version that doesn't need nearly as much memory.
Cheers,
Bruce
Director, Einstein@Home