Any idea as to what is making Logos close down when trying to bring up a passage in the Go command? I'll be away here for a few hours but will appreciate your reply when I get back. Thanks!
Windows or Mac?
Can you post your crash report file here? (If Windows, it should be in you Logos Log Files folder and is called Logos4Crash.txt; I'm not sure about Mac.)
Also if this is a repeatable crash, then could you enable diagnostic logging and make it happen again and then upload the log file here. That will help greatly in diagnosing the cause of the problem.
Luckily, it doesn't close down for me (Win 7, 32bit) when I type Gal 4:1 in the Go box and execute. However, this will run all the Passage Guide and Exegetical Guide thingies, open half a dozen bibles, compare versions and even make a handout with a WordFind puzzle. Based on your configuration of these guides and the available memory at the time you run this (e.g. running a photo conversion tool or streaming HD video in parallel?), maybe it just blew your machine. Or it accessed one broken resource file in the process.
Rosie is right, the experts need to see your logs.
Thanks for the replies. Here's the log file(s) I think you're after ... I am using Windows 7 Home Premium.
4135.Logos4Crash.txt
Thanks for the replies. Here's the log file(s) I think you're after ... I am using Windows 7 Home Premium. 4135.Logos4Crash.txt
Bootjack.
Greetings, I just got two win7 ibm's and have finished loading L4, and have not had any problems. I did as you stated above and it loaded a prearranged layout. There may be a wiki page somewhere's and someone may know the link.....
I did a "rebuild index" and that apparently fixed the problem. I downloaded a couple books that I had ordered up from the pre-pub, so it might be that did something that wasn't too pleasing to the present Logos program. If there is something in the log file that I posted here that you see that is awry, please advise. Thanks!
Observation: crash report was attached, but diagnostic log files were not. The crash file has one error: "Index was out of range. Must be non-negative and less than the size of the collection." (suspect an index error for an interlinear resource, but not know which one).
Rejoicing with you that "rebuild index" worked [8-|]
Keep Smiling [:)]
Please advise as how to send a diagnostic file - what is it called?
The diagnostic log file will only be there if you'd enabled diagnostic logging at one point. See the links about diagnostic logging and uploading log files in my previous post. The file will be called Logos4.log, but if you've run Logos again since the crash, then it will have been overwritten by a newer session, so no point in posting it now. In the future though, if you have a bug to report, make a copy of that file before restarting Logos (or zip it to a zip file) for posting later once you've had a chance to retry the steps you did that caused the bug so that you can describe how the problem occurred.
Thank you Rosie. I'll remember (or attempt to) what you advise regarding a crash. Would you see the Logos download throwing the Logos program off and thus the *rebuild index* fixing it?
And if that is so, is this a common thing for a download to throw the index into turmoil or is it something that is rare?
Thank you Rosie. I'll remember (or attempt to) what you advise regarding a crash. Would you see the Logos download throwing the Logos program off and thus the *rebuild index* fixing it? And if that is so, is this a common thing for a download to throw the index into turmoil or is it something that is rare?
I'm glad *rebuild index* fixed the crash for you. It should never happen, though. Downloading new resources is a common scenario which Logos ought to be able to handle just fine without the index getting messed up. If it ever causes problems for you again, zip together all of the Logos log files that you find in Logos Log Files folder (could be any or all of DigitalLibraryInstall.log, Logos4.log, Logos4Crash.txt, Logos4Error.log, Logos4Indexer.log, Logos4IndexerCrash.txt, Logos4IndexerError.log, logos4setup.log) and post them to help Logos diagnose the problem.
