Bug 1686824 Comment 9 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

That seems almost right. Not sure if you really have to run as admin but guess it won't hurt to try just running it as a normal user. If tb runs and produces a log, you are OK either way.
Looks like your batch file tries to get tb from the x86 program files. If you are running a 64 bit tb version it is probably installed to just "Program Files" w/o the 86.
You probably still the need the quotes around the last line of the batch since there are spaces in the path..
The resulting logfile has .moz_log appended to the name so it will be at c:\users\<your-user-name>\Desktop\imap.log.moz_file. (This trips up a lot of loggers and is mention only down in the "fine print" of the logging web page.)
Yes, I would suggest restarting tb between runs since erases  the log file at tb startup. I think I suggested running once and saving and posting the log with a good wakeup. Then shut down and run again until you get a bad wake up. So I want to see a log with one good wakeup and one with a bad wakeup. (If bad occurs first, that's OK.)
Also, for each log posted, describe exactly what you were doing in tb while recording it.
That seems almost right. Not sure if you really have to run as admin but guess it won't hurt to try just running it as a normal user. If tb runs and produces a log, you are OK either way.
Looks like your batch file tries to get tb from the x86 program files. If you are running a 64 bit tb version it is probably installed to just "Program Files" w/o the 86.
You probably still need the quotes around the last line of the batch since there are spaces in the path..
The resulting logfile has .moz_log appended to the name so it will be at c:\users\<your-user-name>\Desktop\imap.log.moz_log. (This trips up a lot of loggers and is mention only down in the "fine print" of the logging web page.)
Yes, I would suggest restarting tb between runs since the log file is erased and starts fresh at tb startup.
I think I suggested running once and saving and posting the log with a good wakeup. Then shut down and run again until you get a bad wake up. So I want to see a log with one good wakeup and one with a bad wakeup. (If bad occurs first, that's OK.)
Also, for each log posted, describe exactly what you were doing in tb while recording it.

Back to Bug 1686824 Comment 9