"Logos 4 Not Responding"

I get the same

The same happens to me. I guess (in my case) it is because I am overseas with a slow internet connection.  Have you tried configuring Logos to work without connecting to the internet? Just to see if that is causing the delay.  In my case, even working without internet access, my Logos feels so much unresponsive. The GUI seems with a lot of lag all the time; it is very dissapointing.  My computer is pretty decent, with enough power and well tunned to run any normal application fast, but Logos 4 menus take so long to display and very often the screen takes over ten seconds to regenerate itself. My Logos 3 is more responsive.

Blessings,

Gabe.

Ronald et-al,

This can be one of a few issues.

1. video drivers may not be up to date.
2. Computer lag as a result of just too much stuff trying to happen at the same time, and the screen draw is lowest priority.
3. A bug.  In this case it would be very helpful if you could find a pattern, kind of a "I did this, and then this, and this is the result" kind of report.  If you or any of you could come up with this, please start a thread titled "Bug: screen blanking" and provide the steps to reproduce it along with your machine specifications.
4. Related to #2 it could be that your computer doesn't fit the target that Logos set when they started programming this thing four years ago.  They were aiming for systems built within the last two years (2007 and following).  Of course they didn't plan on netbooks, nobody did - the idea that people would intentionally buy and underpowered machine and expect it to do powerful things is an anomaly in the history of the computer market.

This happens to me as well.  It's typically due to the fact that the thread that handles the UI refresh is blocked on (i.e. waiting for) another operation completing.  As this is new software, I fully expect that the Logos developers will address this resource contention issue in due time.  I've monitored thread activity and I/O when this occurs, and it's not due to a saturation of the system resources.  It's a blocking issue.

Matt

Thanks Josh, I tried that and it works better.  Logos 4 is more responsive now. 

Michael Lyman said:

Now if I can just get the indexer to stop crashing.

The Logos Indexer if I understand correctly should only run when you first run the program or when you add a resource…  At least that is what I have seen on my computer…  Ok one thing you can do to give a little more power to the Logos Indexer is by going to the windows task manager (Control + Alt + Delete) then clicking “start task manager”.  Next find “logos indexer” under the processes tab, then right click and set priority to high.  This will keep some other processes from getting in the way of the indexer…  You may need to let the Logos Indexer run for a while so it will finish.  I think they told me when I purchased Logos 4 that it could take 1o or more hours to index my library (Bible Study) and it was best to leave the application and computer running until that finished.  If it still crashes then try to close all other applications.  Be careful with this tool it can make your computer unstable especially if you set multiple items with high priority.  By the way, this setting is automatically reset to normal when you reboot your computer.

Josh

Another thing you should consider is defragging your hard drive this should help. The data base for Logos is quite large and sometimes your computer does not fit it all neatly into the same area of your hard drive, so as it is Indexing the computer is having to run two and fro to gather the data.

The next thing you might look at is what the weakest link is. Press (Control + Alt + Delete) then click “start task manager”. On the Performance tab click “resource monitor …” it will ask you for admin permissions click continue. There will be some bar graphs at the top of the page if you see one that is at max capacity this may lead you to the problem… if it is CPU look at what processes are using all the processing power likewise with memory and hard drive.

If all else fails check your error logs and let the Support Team know what is going on…

Josh