Quote from: fred on May 04, 2010, 12:31:46 PM
Let it run for about 5 minutes with the Tasks view visible.
Copy the log file that's in the user folder datenumber.log and mail it to me. (This is a plain text file.)
Sadly, it froze again, so I followed your directions and have mailed you a log. In case others try this, just two extra tips:
1. At least on my Windows XP Pro system, the log file appeared in Documents and Settings\ (user here) \Application Data\eFMer\BoincTasks\log,
2. I had to actually kill BoincTasks (by hand from Process Explorer) before the Gmail web client would attach the log file--presumably it was locked in some sense.
Quote from: archae86 on May 05, 2010, 04:51:05 PM
Quote from: fred on May 04, 2010, 12:31:46 PM
Let it run for about 5 minutes with the Tasks view visible.
Copy the log file that's in the user folder datenumber.log and mail it to me. (This is a plain text file.)
Sadly, it froze again, so I followed your directions and have mailed you a log. In case others try this, just two extra tips:
1. At least on my Windows XP Pro system, the log file appeared in Documents and Settings\ (user here) \Application Data\eFMer\BoincTasks\log,
2. I had to actually kill BoincTasks (by hand from Process Explorer) before the Gmail web client would attach the log file--presumably it was locked in some sense.
After XP this location is C:\Users\username\AppData\Roaming\eFMer\BoincTasks\log
And as there is a constant stream of data to the file it's indeed locked.
At least I know something more after reading the log.
If there are others with exactly the same problem let me know.
Quote
Collatz Conjecture 2.09 Collatz x64 ATI Opt. (ati13ati) collatz_1272807464_341328 07-05-2010 18:02 20000-state:
Collatz Conjecture 2.09 Collatz x64 ATI Opt. (ati13ati) collatz_1272807464_341172 07-05-2010 18:02 20200-state:
all the Collatz units got it when restarted, probably with a wrong date.
what are "20000-state:" and "20200-state:" ??
this has been after a major crash of computer caused by my stupid finger
:'( :'( :'(
in the BIOS configuration and there was one problem while restarting after
2 hours fixing the bug with the PC clock, USB devices, etc.
::) ::) ::)
after the previous crash in my computer, from such time Collatz finished work is not registering in the log,
but only in that computer the other computers work done is properly registered.
BT x32 & x64 - host with Win 7 x64 Pro and BOINC 6.10.43 x64
why ??
Quote from: Corsair on May 07, 2010, 11:20:37 PM
after the previous crash in my computer, from such time Collatz finished work is not registering in the log,
but only in that computer the other computers work done is properly registered.
BT x32 & x64 - host with Win 7 x64 Pro and BOINC 6.10.43 x64
why ??
The history logging only records tasks that are uploaded and reported.
Quote from: Corsair on May 07, 2010, 05:09:56 PM
Quote
Collatz Conjecture 2.09 Collatz x64 ATI Opt. (ati13ati) collatz_1272807464_341328 07-05-2010 18:02 20000-state:
Collatz Conjecture 2.09 Collatz x64 ATI Opt. (ati13ati) collatz_1272807464_341172 07-05-2010 18:02 20200-state:
all the Collatz units got it when restarted, probably with a wrong date.
what are "20000-state:" and "20200-state:" ??
this has been after a major crash of computer caused by my stupid finger
:'( :'( :'(
in the BIOS configuration and there was one problem while restarting after
2 hours fixing the bug with the PC clock, USB devices, etc.
::) ::) ::)
20000 is ready to start
20200 is Running
Strange that you get a number from a known state.
Str