i just reboot system and all current time and work seem lost ?

dont exit bonic manager or reboot or work on the unit is reset

this dont make any sense, why work is not saved.

all timeslot vent from 2d to 50d and even 340days

this is because work progress keep reseting and dont save if you reboot or exit client. maybe even pause this can cause this ?

problem with this huge long work on a unit is lost work, because we reboot pc ( game pc ) require fresh system sometimes

Yes. the Windows client does not save the work when rebooted. The Linux client is ok though.

---

LZ Loon
The Most Handsome Man on the Interweb (TM)

here is a warning to all Windows user, leave this project of DOOM, they dont have a clue what they are doing, any pause with workunit will reset current work and it dont save current work to disk, they dont follow bonic standard, if you dont know this every 60minute there is a chance that bonic will switch to other project if you have such. so you can actual waste your time no matter what your doing a never ending workunit that have waste your time on the pc and the deadline can never been reach at all.

ps.
this project should be closed and kicked out of communty for waste people goodwill in let there cpu core work for a cure

such project that doing this should have red flag raised and not been allowed to be research on global scale, THIS is not even a alpha test app what a joke, who do we contact and can vote this for terminated project until fixed

That's why it's Beta - lots of other projects that are not. Use the Remove project command on the Boinc Manager and we'll let you know when it's not Beta anymore.

---

LZ Loon
The Most Handsome Man on the Interweb (TM)

Hi Mantakno,
We have to apologize you for the problems with the last version. We are the first ones that want to solve this issue. We don't want to waste your computation time.

We have removed all the tasks of the queue and now we are running tasks only in the app marked as beta. We need to run in volunteer computers now because the problems showed in the windows versions never happens in our window machine, but now, we are only using clients that agree to use the beta version. You can choose it in your preferences (the default value is not).

We have uploaded a new version this morning. As soon as we detect that the problem with the checkpoint is solved we will notify you.

I'm sorry if you think that this project should be closed. We are trying to solve it as fast as possible. I think that the new configuration will avoid all of you to waste your time.

To all this ones that are running the beta version, ¡thank you! Your effort is helping us a lot.

Best regards,
Jesús.

---

Jesús Carro
Universidad San Jorge
@InSilicoHeart

Thanks for the update on the client problems :)

---

LZ Loon
The Most Handsome Man on the Interweb (TM)

yes, i know its beta, that is not the issue at all, actual even the the workunit we try to help you is maybe up for total abandon for wrong calculations , shit happends fair is fair, but is work is not saved or even have worst crush time apox 45 days fair enough, but then deadline cant be kept or give a year ahead , its okay we dont get angry on such long test, but the minute we cant save that is Total RED flag. i have seen games work fine with this run while im playing skyrim
and other 3d games ... quite odd and then i play a game that need way more cpu cores because it use caculations directly so pause and save workunit is a most needed functions aven the result is useless because you found out its data is corrupted, i only get mad then we sort of get a never ending workunit that keep reset itself doing no save or pause or project is switch, and waht about power failiur ( fuse-plugs can go off not the first time we have seen this in our homes ) maybe try see this in global perspective , no project should not be allowed if basic workunit can get lost in neverending loop ) ( so save and deadlines should be extended and a most no matter what ( i dont care if get a block for several month just we do know its legit in the end, you are not the first project where we see deadlines is screwed up then we run multi project, that is waht is wrong with bonic manager it dont work on shortest time first, but more on then we load the workunits from diffrent project ) this is not your fault but its still part of the global issue and deadlines and workunits is lost because deadline runs out. another red flag here. you battle to much with eachother and waste people time seen this in global cordinations

but the minute we cant save that is Total RED flag.

Your passion is appreciated. However, as the project admins have said (repeatedly), the problems reported on Windows machines were not seen on their Windows machine. And as we have reported the issues, they've pulled units from production, launched additional Beta tests, even looked into granting credit for runtime instead of just a valid result.

I know it sounds fishy that they ran it on their Windows machine and all was well. But I have 2 ThinkPads, each with Win 7 SP1 (64-bit). One is a i5-5300U and the other a i5-2520M. The 5300 loops units repeatedly. The 2520 chews them up and spits them out, no looping required. It's completed 11 units from the 1.03 Beta test. The 5300 has looped 4 it received, and I'm waiting to see what happens on these last 2 from 1.03. (I'm guessing they will loop as well.) The point is, if two fairly similar machines can exhibit very different behavior, then it would be feasible for the admins to release work thinking all would go smoothly. They aren't just blindly sending work trying to clog up our machines.

i dont recall then i got the WU's i have I7 denis project had 4 of my cores run them, but as i mention bonic manager switch project every 60 minutes if other project require it. and i now you can change value of this but then they cant do a first priority if this is needed someday, so we still fall back at save data most work, im not debat wish for lost work, i only hope the have the courage to take this debat up with bonic manager team so it sont happend again,
the data and lost time is irrelevant even what project name that did it, all of them can do same mistake, just so you get a bettre or global view of this i have 6pc that run project's and i dont keep a eye on them, i wait for ping(log then pc dont respond, so they are on auto and dont need my attension on daily WU

and i notice alot of user have several device that do this.
we can only hope denis project take the issue up with bonic team so this cant happend again,

well anyway... gl with it.

It's BOINC, not bonic