Log for Heidi

PhiloVance

New Member
I had a question in and apparently it was lost, the following is the gist of it, though it's not the original post.

Just d/l Eraser 5.6 and ran a check this noon. I went to File/View Log and get a file in the Eraser folder called schedlog.txt but it has old entries in it.

Questions.

1. Where is the current log.
2. If there is none, is there a way to start one.

Thanks.

A Portion of the log follows:
Code:
31/08/2002 11:07:25: Scheduler (5.5.2.0) starting.
31/08/2002 21:46:27: Scheduler (5.5.2.0) starting.
01/09/2002 02:18:09: Scheduler (5.5.2.0) starting.
01/09/2002 02:21:25: Scheduler quitting.
01/09/2002 14:11:03: Scheduler (5.5.2.0) starting.
02/09/2002 10:49:53: Scheduler (5.5.2.0) starting.
Just d/l Eraser 5.6 and ran a check this noon. I went to File/View Log and get a file in the Eraser folder called schedlog.txt but it has old entries in it.

Questions.

1. Where is the current log.
2. If there is none, is there a way to start one.

Thanks.

A Portion of the log follows:
Code:
31/08/2002 11:07:25: Scheduler (5.5.2.0) starting.
31/08/2002 21:46:27: Scheduler (5.5.2.0) starting.
01/09/2002 02:18:09: Scheduler (5.5.2.0) starting.
01/09/2002 02:21:25: Scheduler quitting.
01/09/2002 14:11:03: Scheduler (5.5.2.0) starting.
02/09/2002 10:49:53: Scheduler (5.5.2.0) starting.
Just d/l Eraser 5.6 and ran a check this noon. I went to File/View Log and get a file in the Eraser folder called schedlog.txt but it has old entries in it.

Questions.

1. Where is the current log.
2. If there is none, is there a way to start one.

Thanks.

A Portion of the log follows:
Code:
31/08/2002 11:07:25: Scheduler (5.5.2.0) starting.
31/08/2002 21:46:27: Scheduler (5.5.2.0) starting.
01/09/2002 02:18:09: Scheduler (5.5.2.0) starting.
01/09/2002 02:21:25: Scheduler quitting.
01/09/2002 14:11:03: Scheduler (5.5.2.0) starting.
02/09/2002 10:49:53: Scheduler (5.5.2.0) starting.
 
did you check that the log settings are correct?

Delete the current log and start again. I would aslo use file find Win+F
to search for it, perhaps the log is getting stored elsewhere for some reason.

Just checked mine here and is is all ok.

Garrett
 
Back
Top