For some reason when I tried to start 5.1 b5 this evening it kept crashing. An install of 5.1 b6 did not help. A complete uninstall and removal of all folders and resources did not help.
I wound up giving up and installing 5.0 stable latest version.
Where are your logs?
Did not know how to generate logs when it would not even open. And I needed Logos for a writing project today and sermon prep tomorrow. So I just went back to stable.
Would it not open, or did it crash (there is a difference)? You can find info on logging by following the links in my signature line.
I guess you could say crash upon opening. When trying to open, the "Program has stopped working" error box came up every time. Maybe this will not help, but I have what appear to be two contemporaneous log files. The ZIP folder is several months old, and so no good.
8865.LogosCrash.txt
7457.LogosError.log
I guess you could say crash upon opening. When trying to open, the "Program has stopped working" error box came up every time.
That is a good sign, and crash logs most likely would have been generated IF you had enabled logging. You may have been able to save yourself a great deal of time by uploading logs to the forum.
The ZIP folder is several months old, and so no good.
The Zip folder is old only because you didn't have logging enabled. Some logs are always produced, but logging needs to be enabled to get "the good ones."
How do you enable logging when you cannot even get the program to open?
there's a script to enable it - follow the link im Alabama's posting footer.
Enabling of logging must happen outside of the program. Otherwise, the programmers wouldn't be able to "see" what is going on if something happens, say, like the program crashing on startup. [:P]
The links I provided explain this further. I understand you are busy today, but you should look it over when you get a chance. Feel free to ask questions if you don't understand something.
For some reason when I tried to start 5.1 b5 this evening it kept crashing.
The LogosCrash.txt file you posted was helpful in identifying the problem; we should have a fix for this in 5.1 Beta 7. (And if you ever do upgrade to 5.1 Beta 6 again, I think I can supply a workaround.)
For some reason when I tried to start 5.1 b5 this evening it kept crashing. The LogosCrash.txt file you posted was helpful in identifying the problem; we should have a fix for this in 5.1 Beta 7. (And if you ever do upgrade to 5.1 Beta 6 again, I think I can supply a workaround.)
Do you have any idea how long until Beta 7 (weeks? months?)? What was the problem? What would the workaround be?
Probably a week; we try to ship fairly regularly.
I believe the problem was that the installed program was named "logos.exe"; renaming it to "Logos.exe" should have worked around the crash. (A sensitivity to casing was inadvertently introduced in Beta 5 & 6; it'll be removed in Beta 7.)
Thanks. One last question: are the resources for the latest stable and Beta 6 compatible? The biggest pain is re-downloading 15GB of resouces when you change versions.
are the resources for the latest stable and Beta 6 compatible?
No problems.
Thanks. One last question: are the resources for the latest stable and Beta 6 compatible?
No, 5.1 has some resources (mainly datasets) that are not compatible with Logos 5.0 and earlier.
The biggest pain is re-downloading 15GB of resouces when you change versions.
By "when you change versions" do you mean "when you downgrade from beta to stable"? This is not supported, but if you needed to do this, you could save a copy of all of the files in the ResourceManager\Resources folder and "scan" them into the program after downgrading. If the file isn't supported by the stable version, it won't be installed by the scan. You could then run "update resources" to download any missing resources.
