Closed Log differences

[stapp]

EAM on Win 7 64bit  (a couple of days since this machine was on)

After the download of new beta I looked in Update logs and it says when I click 'view details'........

General Information:Update started: 31/07/2017 19:00:10
Update ended: 31/07/2017 19:02:46
Time elapsed: 0:02:36

Update successful

Detailed Information:182 modules, 34381181 bytes

In Forensics logs it doesn't show the amount downloaded when you click 'view details' it just shows..

General Information:
Version 2017.7.0.7797
Update started: 31/07/2017 19:00:10
Update ended: 31/07/2017 19:02:46
Time elapsed: 0:02:36
 Update successful

If I take a screenshot of Forensic Log it shows a different amount to the update log. Why is this?

 

 

 

 

[Frank H]

what is the different amount ?

do you mean 34381181 bytes and 33557Kb ?
33575Kb = 34380800 bytes and is probably a bit different because of rounding.

 

[stapp]

Why not use the same in both logs... either kb's or bytes?

(Strange ... I thought it equalled 33575000 bytes)

[Frank H]

  1 KB is 1024 bytes, not 1000bytes

well, as said earlier, forensics needs to be fine tuned,  such minor gui stuff things will be improved in a next release.

[stapp]

By the way, at the moment the update log, scan log and Forensics log are not updating themselves to the last event.

Technical explanation.... the blue highlight line is not moving.

[stapp]

The logs not refreshing themselves in a Windows Session happens on both Win 7 and Win 10.

Can you tell me why it is to improve permormance as stated here?

https://support.emsisoft.com/topic/25337-blue-line-in-logs-issue/#comment-159863

 

[Frank H]

hi stapp, the logs do refresh themselves if you move to another screen and back to the log, there is no relation with a windows session.

I cannot give you details about what Orlando mentioned in that post.

 

 

[stapp]

1 hour ago, Frank H said:

hi stapp, the logs do refresh themselves if you move to another screen and back to the log.

 

I am sorry Frank but they do not. At least on my machine they don't.

To discount any corruption from previous logs I reset all logs and counters.

Then I did a quick scan and closed the gui.

Then I did a custom scan of a txt file on my desktop.

Then I opened the GUI and went from screen to screen, log to log, the blue line doesn't move. The logs do not refresh themselves.

Can you give a run down of what steps you take to make logs refresh themselves please ?

 

[Frank H]

stapp, maybe i miss something, but your screenprint of the forensic log shows the 2 scans you executed, right ?
i did exactly like you described

 

Quote

 

Then I did a quick scan and closed the gui.
Then I did a custom scan of a txt file on my desktop.

 

when i open the GUI and go to the forensic log, it shows the scan records.

tested on w10 x64

[stapp]

The blue line Frank, look at the blue highlight line.

It does not move up to the top, it stays where it is.

[Frank H]

ah....

[Frank H]

On 8/1/2017 at 2:33 PM, stapp said:

The blue line Frank, look at the blue highlight line.

It does not move up to the top, it stays where it is.

btw stapp, this is expected behavior and valid for all logs

[Frank H]

I close this thread as it became obsolete after migration of all logs into forensics