Quote from: fred on September 30, 2011, 04:59:57 PM
1) BT uses 3 history files, so if one is lost the other one is used. So all 3 have to be corrupted for all to get lost, should be very very rare.
And they are regularly updated as well.
What could happen is that the files can't be read for some reason. E.g. locked by another program or another copy of BT in another user session. This should show in the logging.
You could check the logging C:\Users\username\AppData\Roaming\eFMer\BoincTasks\log
See if there is any error or warning close to the time this happened.
2) Memory management is a OS thing. Normally some memory that is'n in use is backed up to disk and becomes virtual.
If you show BT or switch, it may take some extra time to get everything back to ram.
But BT isn't very memory hungry so more memory wouldn't help much.
Another thing what happens, if BT request the messages, they are read from file by the client. As this isn't a recent event, the file is read from the disk itself.
If the event is more recent the date is probably read from cache (ram) instead of the disk.
In the next version I will allow the moving parts of the history to long term history. This should speed things up if you have a large history.
Yes,I looked at log and found
"29 September 2011 - 16:11:11 CHistory::ReadFile ---- Unable to read to history file: C:\Users\Jaspreet\AppData\Roaming\eFMer\BoincTasks\history\history_Jaspreet-PC.cvs, copy 1
29 September 2011 - 16:11:11 CHistory::ReadFile ---- Unable to read to history file: C:\Users\Jaspreet\AppData\Roaming\eFMer\BoincTasks\history\history_Jaspreet-PC.cvs1
29 September 2011 - 16:11:11 CHistory::ReadFile ---- Unable to read to history file: C:\Users\Jaspreet\AppData\Roaming\eFMer\BoincTasks\history\history_Jaspreet-PC.cvs1"
But I noticed that in History folder there are 3 files viz *.cvs, *.cvs1, *.cvs2
In the log there is no reference to *.cvs2 but in place it refers to *.cvs copy 1