Logos slowing down and KJV interlinear not working
I'm not sure what's causing this but I did a re install last week after my upgrade to Silver. And it seem that each days it's getting slower and slower. Now this evening my KJV interlinear has stopped work, or it never worked since the upgrade.. not sure. I know it was working before the upgrade. I can get the button to show the interlinear area but its black and doesn't sem to respond to any mouse selections. In fact Logos sort of freezes for a few second.
Am I going to have to install it again to get the preformance back?
Comments
Sort by:
1 - 1 of
11
Sorry for all the type-O's. It was late at night and I have had a few nights of insomnia, coupled with Logos issues.
Corrections to my post:
I'm not sure what the cause is but I did a reinstall Logos last week after my upgrade to Silver. And it seems that each day the programs responsiveness has gotten slower and slower.
Now (yesterday) my KJV interlinear has stopped work, or it hasn’t worked since the upgrade, not sure because it is the first time I have used it since the upgrade.
I know it was working before the upgrade. I can get the button to show the interlinear area but it’s blank and doesn't respond to any mouse selections of the text. In fact, Logos sort of freezes for a few second.
I have deleted “KJV1900” and allowed logos to re-download the file but now Logo’s crashes every time I launch the KJV interlinear (blue icon one but not the one with the apocrypha) in Logos.
Help?
New Log file and screen capture.
88587.Logos4.log
--------- a selection from the log file ----------
2010-02-17 15:13:58.3705 14 Error OurApp Unhandled exception: System.NullReferenceException: Object reference not set to an instance of an object.
at LDLS4.Panels.ResourcePanel.ReverseInterlinearPane.<DoUpdateFromMilestone>d__51.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution()
at Libronix.Utility.Threading.AsyncAction.Continue()
at Libronix.Utility.Threading.ThreadPoolAsyncAction.<Start>b__0(Object )
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
Anthony,
I don't know if this will work so delete these files (in \Resources) to the Recycle bin so they can be recovered:-
KJV1900NT.lbsrvi
KJV1900OT.lbsrvi
Start L4 and they should be re-downloaded.
Dave
===
Windows 11 & Android 13
I gave it a shot... no go. It still crashes Logos when I open the resource.
My interlinears did NOT download yesterday. They downloaded this morning though. We will see if they work once B10 stops crashing. Check and see if they are actually in your resource folder.
Just so we're clear... I'm not running a beta.... though I suppose resources are resources.
If resources are children and the engine is the play area... I have the children running around in 4.0a and one of them is being very bad.
[:O]
Interlinear still does not populate the boxes in kjv1900. Any ideas?
I've sent off a report via email to support... [^o)]
bump!
Dave
===
Windows 11 & Android 13
About four business days has been my usual response time. It will probably be Wednesday or after.
Will post what I know, when I know.
[;)]
Well, I haven't heard anything yet. I took it upon myself to reinstall LOGOS and see if it fixed it.
NOPE!
Anthony
I've created a Bug Report at http://wiki.logos.com/Bug$3a_Error_accessing_KJV1900
That should get some attention from Logos.
Dave
===
Windows 11 & Android 13
thanks
Just wanted to update...
I was contacted by support today and although we don't have a solution yet, it is being looked into.
A very attentive and polite guy by the name of Steve from tech support check through his tool box of fixes and has turned it over to the dev. dept. guys.
Now I know the tendency might be to be down (half empty mindset) since they (He) was unable to fix it.
But I had an excellent experience with tech support: WHY?
Kudos to Steve W. at LOGOS Tech support! <--- Are you listening Mr. Bob Pritchett, your caliber staff is responding well! [Y] [Y] [:)]