Ok, the Fresh WU's I downloaded this morning still where bad, 1 completed successfully & 1 still showed the Computation Error...
So I Detached that Computer from the Project, Un-Installed BOINC from the Computer, went through the Registry & got rid of any reference to BOINC. Then I reinstalled BOINC to get a different Host # for it and Re-Attached the Computer back to Einstein...
The 1 WU I downloaded to the Computer so far showed it as Application v4.79 instead of v4.75, so I take it then that is a good thing & hopefully the Computer won't show the Computation Error anymore ... ???
PS: I'm not even going to Merge the Computer with the old host # for awhile just to be safe from getting those same WU's again ... :)
BTW, if you have one of the CCs which is part of the development branch (aka 4.62, 4.66, or 4.20 for instance) one can abort the result for the WU that uses 4.75. Personally I wouldn't do that or recommend doing it, unless 4.75 isn't running on your comp properly (aka the computation error someone was reporting).
Otherwise, I d/l a 4.79 WU today, but it's still working on a 4.75 unit...so it has taken care of itself without intervention...
Just an update on this bug ... I had to reset another PC because of the v4.75 Exit Bug but so far I've not had one single Error with the new v4.79 Clients. I had a total of 8 WU's in all on 2 Computers Error Out when they finished ...
Ok, the Fresh WU's I
)
Ok, the Fresh WU's I downloaded this morning still where bad, 1 completed successfully & 1 still showed the Computation Error...
So I Detached that Computer from the Project, Un-Installed BOINC from the Computer, went through the Registry & got rid of any reference to BOINC. Then I reinstalled BOINC to get a different Host # for it and Re-Attached the Computer back to Einstein...
The 1 WU I downloaded to the Computer so far showed it as Application v4.79 instead of v4.75, so I take it then that is a good thing & hopefully the Computer won't show the Computation Error anymore ... ???
PS: I'm not even going to Merge the Computer with the old host # for awhile just to be safe from getting those same WU's again ... :)
BTW, if you have one of the
)
BTW, if you have one of the CCs which is part of the development branch (aka 4.62, 4.66, or 4.20 for instance) one can abort the result for the WU that uses 4.75. Personally I wouldn't do that or recommend doing it, unless 4.75 isn't running on your comp properly (aka the computation error someone was reporting).
Otherwise, I d/l a 4.79 WU today, but it's still working on a 4.75 unit...so it has taken care of itself without intervention...
Just an update on this bug
)
Just an update on this bug ... I had to reset another PC because of the v4.75 Exit Bug but so far I've not had one single Error with the new v4.79 Clients. I had a total of 8 WU's in all on 2 Computers Error Out when they finished ...