Lexham English Bible: Why do I have two copies of it?

Mark A. Smith said:

Rosie Perera said:

Why do I have two copies of this?

Beta testing. Find the file name by looking at the info on the resource. Move lexbible to the hidden resources. That's the out-of-date one.

I couldn't even open one of them to look at the filename info. I got a message saying "You own this resource but for some reason it's not in your library." So that was the lexbible one, I presume. I've now hidden it. Thanks.

I wish the filename info were available in the Library info panel without us having to open the resource.

Dave Hooton said:

You have to delete it (lexbible.logos4) from \Resources now the licence has expired!!

Also see http://community.logos.com/forums/p/9797/78005.aspx

 

EDIT: having read your post in full I think there will more Q's, but I don't want our posts to cross .....Waiting

Thanks, Dave. I vaguely remember seeing that thread, or at least hearing about the issue, when people were first discovering it around Jan 1 when the licenses expired, but at the time I didn't have any crashing problems, and hadn't noticed anything else amiss (the duplicate resources), so I didn't do anything about it.

Now I'm worried that if I go deleting files for resources I have hidden, there will still be mentions of that file in some database somewhere, and I'm opening myself up to crashing problems down the road. It seems from that thread you pointed me to that people are still awaiting word from Logos as to whether they are going to do anything about cleaning up after themselves. I would join my voice to that chorus.

In the meantime, until Logos does anything about this, do you think I'm more likely to encounter problems down the road if I do delete the file or if I don't delete it?

Dave Hooton said:

Rosie Perera said:

Now I'm worried that if I go deleting files for resources I have hidden, there will still be mentions of that file in some database somewhere, and I'm opening myself up to crashing problems down the road.

I'm worried about what you have hidden!

Why are you worried? I'm just trying to avoid crashes. I've got a bunch of hidden resources (all the Targum fragments and a few other resources that were in my face all the time that I never expect to use; nothing to worry about).

The only resources I'd be considering deleting the files for in addition to hiding them would be this Lexham Bible, and if that doesn't cause any problems, then I'd do the same with the other resources mentioned in that thread you directed me to, e.g., LexhamSGGNT.lbssyn and LexhamSGGNT.lbxclv.

Dave Hooton said:

But restart L4 to ensure it is deleted...

Yes, I restarted L4 and the extraneous Lexham Bible is indeed gone, but it still showed up in my Hidden Resources list in Program Settings, which means Logos must be keeping track of that resource name in a database somewhere so that I could "unhide" it if I wanted to. In fact, before deleting the file, I did try unhiding it (just for kicks) and it didn't reappear in my Library. So now it seems to be truly gone, but read on below...

Dave Hooton said:

The leftover bible should be fully accessible with an Interlinear panel and Resource Information should show that it is LLS:LEB, 2010-01-05T21:44:02Z,  file LEB.logos4.

In your resource folder you should see LEB.logos4 and LEBNT.lbsrvi (the Greek interlinear part). Both should have a date modified of about 12-13 Jan 2010. You should not see LEXBIBLE.logos4.

Yup, I've got both of those files and, without even having to delete it, I've got no LEXBIBLE.logos4. So why does Logos still know about lexbible? If I type lexbible in the command bar, I still get the message that says "You own this resource but for some reason it's not in your library." The word lexbible appears to be lurking in some database somewhere. Where, and what are the possible consequences of this?

Dave Hooton said:

I was concerned which version had been hidden. Others reported crashes hiding the lexbible.logos4 (as opposed to deleting it), so you might have hidden the leb.logos4 by mistake!

 

I don't think so. This is the one I have still in my library:

Dave Hooton said:

Rosie Perera said:

Yup, I've got both of those files and, without even having to delete it, I've got no LEXBIBLE.logos4. So why does Logos still know about lexbible? If I type lexbible in the command bar, I still get the message that says "You own this resource but for some reason it's not in your library."

 

I have the same problem, having hidden lexbible before it expired. An obsolete resource should not remain hidden, nor should its abbreviated name be retained. There are references in Indexer logs to updating the LexhamSGGNT database which I had to delete (you can't hide the db), but I had hidden the two resources. 

In general it is better to delete an obsolete resource. Why keep an unnecessary record that Logos isn't handling properly? 

I agree. But I can't delete it because the file is already gone. So its name is somewhere in one of the many Logos .db files. I'm not sure which one Logos looks in to find a match when you type a filename in the command bar. But they should remove it. If I type some random gobbledygook there which doesn't match a command name nor a known filename, it does a search on it. But if I type lexbible, it proposes this:

Why is that still around anywhere?! They should completely obliterate all references to it everywhere if it's obsolete.

I don't know of a way to do a recursive FIND (a Windows command line program) on *.db from my Logos4 folder on down, which I'd really like to do, and I don't have time right now to go through each folder and do it manually; but I did at least do find /i "lexbible" resourcemanager.db in the ResourceManager folder, and it found a hit. Now how to regenerate that database and hope lexbible gets expunged from it. Can I just delete it and let Logos regenerate it for me?

UPDATE: I figured out how to do a recursive find (grep), using findstr, which comes with Windows. The result is disconcerting. All of these files contain the string lexbible in them:

Data\{random}\BibleIndex\LibraryIndex.db
Data\{random}\DownloadManager\DownloadManager.db
Data\{random}\HistoryManager\history.db
Data\{random}\LibraryCatalog\catalog.db
Data\{random}\LibraryIndex\LibraryIndex.db
Data\{random}\ResourceManager\logos\Discovered.db
Data\{random}\ResourceManager\logos\Identified.db
Data\{random}\ResourceManager\ResourceManager.db
Data\{random}\Statistics\Statistics.db
Data\{random}\UpdateManager\Updates.db
Data\{random}\Updates\Metadata.db
Documents\{random}\LayoutManager\layouts.db
Documents\{random}\ResourceManager\ResourceSyncManager.db
Documents\{random}\UserPreferences\PreferencesManager.db

Should I delete them all and have Logos regenerate them?

Bradley Grainger said:

Rosie Perera said:

Should I delete them all and have Logos regenerate them?

I'd strongly advise against that.

Is the only problem you're experiencing that typing "lexbible" into the command bar offers to open a hidden resource? That is a bug and should be fairly simple for us to fix.

It's more than just a hidden resource, it's a non-existent resource (or should be so). It was left over from my being a beta tester so I wanted to get rid of it. I dragged it to Hidden Resources and then just out of curiosity deleted it from there (unhid it), and now it doesn't appear in my Library or my list of Hidden Resources. I don't have a resource file for it (I presume it was deleted when I hid the resource). So it shouldn't be recognized in the command bar. And yes, as far as I know that's the only problem I'm experiencing. Evidently some of my databases are corrupt if they still have mention of lexbible. Please do fix the bug.

Bradley Grainger said:

Rosie Perera said:

Evidently some of my databases are corrupt if they still have mention of lexbible. Please do fix the bug.

They're not corrupt; they remember resources that have been seen in the past (by design). (In this case, we know the resource is never coming back, but it may be the case for another resource that the file was accidentally deleted, and will be restored. In that situation we wouldn't want to permanently delete the record for that resource, because that would lose your ratings, tags, title changes, etc.)

The bug is that the command box isn't filtering out unavailable resources; this will be fixed in the next beta.

Good point. Thanks!