Logos slowing down and KJV interlinear not working

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?

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]

I've sent off a report via email to support... [^o)]

Dave Hooton said:

bump!

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.

[;)]

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?

1. They (He) took the time to really check out the issue.
2. I didn't get a canned response from some person reading it off a sheet of paper
3. Nor did I get the "Gee, I don't know, let me hand you off to three other guys who don't know either" response. 
4. He was honest and real about the issue and didn't try to cover it with super-tech jargon.
5. He set a reasonable expectation on follow-up/solution-resolution.

Kudos to Steve W. at LOGOS Tech support!  <--- Are you listening Mr. Bob Pritchett, your caliber staff is responding well!  [Y] [Y] [:)]

I was told that the index file was bad.  Took the prescribed measures specified in the email.

It didn't fix it!  [:(]

I'm still patient. I'm perplexed, but patient.

It shouldn't be this hard to determine the problem. Logos, this may sound mean but are we sure we didn’t release a little premature. [:^)]

It was suggested today by support that "It seems like you have a bad index file".
Well let me say that immediately I knew that was probably NOT the issue and I responded in my email why.

My reasons why:
When I upgraded from the Scholar edition to the Silver on the 9th of Feb., I started having trouble with the KJV in question.

Thinking that something may have gone wrong in the upgrade/indexing I decided to do a fresh install of Silver but I also decided that since I was going to the trouble I would do a clean install of Vista first. That was on Feb. 13.

On Feb. 14 I installed a fresh copy of Logos4 on my clean install of Vista. Afterward the KJV (interlinear) in question still crashed.

Later I decided since I installed it at home on WiFi (thinking the connection could have caused some latency thereby corrupting data) I would give it one more try and did a new install of Logos4 on Feb 23rd.

 
In each case at the end of the process (which includes indexing) the KJV in question crashed.

In between the installations I tried deleting and re-downloading the offending files multiple times either through Logos4 or via the FTP site.

On the 25th Support did a remote connection and basically tried some of the same things and a few new things like deleting preferences and then said they were turning it over to the dev dept.

Question? Why would the indexer corruption always be related to the same file?

March 2nd, though I questioned the validity (the bad index file reason) I nevertheless did as they directed and removed the index files from the appropriate directory, launched L4 and indexing it "a-went".

 
At the end of the indexing process the results were the same. When opening the KJV interlinear L4 crashes.

 
I had heard that some of the issue could be with corruption of user created notes that are triggered when the KJV is launch, so wild-eyed I deleted ever L4 note, syntax search, clipping, favorite, custom guide, and remove any tags I had placed on the KJV and my rating (stars)… all gone.

Launched L4, opened KJV interlinear… CRASH!

I decided to go the full push and apply Vista IE 8 and Vista SP2. My argument was that Microsoft isn't going to support Vista SP1 forever and maybe some of the error could be related to platform updates, .net libs/C++ or other .dll’s that I hadn't got patched through SP1 or the usual windows update fair.

Let me tell you... big mistake!

Logos started freezing at random, while the passage guide try's to connect to power point sermons, it freezes when you tell it to “update now” from a command shortcut. Very unpredictable. The remedy was to shut off “use internet”… but that’s just a band-aid.

For those of you who would say...get a refund. I don't want a refund!
I want my Logos 4 Silver to work.

Just so everyone knows, I’m not mad.  My point is not to incite a riot or flame Logos.

I'm still patient. I'm perplexed, but patient. [:S]    [:'(]       [:$]   Thanks for listening... I feel better.

I am thinking about a new computer... but then I would have to deal with any windows 7 issues.

Dave Hooton said:

Anthony

Look in your resources folder C:\Users\su\AppData\Local\Logos4\Data\n2nhhvsy.jbs\ResourceManager\Resources\ (enable hidden files and folders) and look for *.lbxlls files. Is KJV1900 one of those (as opposed to being KJV1900.logos4)?

Do you have L3 installed and does it contain KJV1900.lbxlls?

What other *.lbxlls files do you have?

Can you upload your last logos4Indexer.log file from March 2nd?

Dave,

I did an experiment based on your questions. I deleted all of the .lbxlls files and did a "update resources". It download the files, some were in the old .lbxlls format other in the .logos4.

I took note to see what the kjv1900 was in the download folder (before Logos moved them to the resource folder). It was kjv1900.logos4. On restart it moved them over, then during the 1,2,3 stages after relaunch it removed kjv1900.logos4 and replaced it with kjv1900.lbxlls.

Is this some sync lic. issue since I have L3 and L4 installed?

Is there a way of circumventing L4 in its replacement of the .logo4 files?

Anthony

7080.01_Logos4_removeOldExt.log

2768.02_Logos4_DL_check.log

3386.03_Logos4_setScan.log

7802.04_Logos4_AfterScan.log

7506.05_Logos4_dl.log

5758.06_Logos4_SetScanM.log

7002.07_Logos4_L4_replaced.log

Anthony Hamlin said:

BUG! BUG! Combo BUG! BUG!

I think what I have discovered here is a combo bug. Part one ( http://wiki.logos.com/Bug$3a_Error_accessing_KJV1900 ) : is that kjv1900.lbxlls (interlinear) crashes L4. This kjv1900.lbxlls is pulled into L4 (by L4) from L3(?) and replaces the (kjv1900.logos4) L4 version for some reason (newer file- see bug link below). Part two: So the link below is the bug reported that .logos4 files are being replaced with .lbxlls files.

http://wiki.logos.com/Bug$3a_L4_not_updating_$2a.lbxlls_files_with_$2a.logos4_files

I have watched L4 download the kjv1900.logos4 file three times. Once L4 is restarted to add the new resource(s) it moves the new resources over from the download folder to the resource folder and then replaces the kjv1900.logos4 with kjv1900.lbxlls. (This also happens to approximately 28 other .logos4 files that are downloaded and replaced with equivalent .lbxlls, though I can't confirm that they cause any problems)

I have trashed my index files and I am attempt to pause L4 indexing long enought to place back the kjv1900.logos4 file and start indexing again to see if the file will hold (this is post "prepairing 1,2,3 stages".)

IT WORKED!

Though I had to do a 2nd update after the launch to force it to see the kjv1900.logos4 file (...among the others). It downloaded them as if it was going to go thru the process again but upon restarted it did a short index and when I opened the kjv1900 interlinear it worked... no crash.

Now the question is, if I have L4 scan my L3 will it revert back to kjv1900.lbxlls?

4405.Logos4Indexer.log

2845.Logos4_preManualFix.log

7142.Logos4.log

Performance site note: Thanks to Steve Sando I have a bit better performance by enabling Write Caching and Advanced Performance on the HDD and using a High-Speed USB disk under ReadyBoost (Vista) to enhance the systems responsiveness.

http://community.logos.com/forums/t/12829.aspx

Praise the Lord. Victory in Christ Jesus ... Victory in patience through Christ. [:D]