Which of these Logos 4 Resources Are Obsolete?

Are any of these Logos 4 resources now obsolete? They do not match up with the files in my second (laptop) PC install, so I want to remove them if they have been replaced with newer Logos 4 files (these might be "left-over" files from when I was beta testing that are now obsolete, I am speculating).
I think that the first 4 files have had a change in their file extension from "lbx___" to "lbs___".
In the middle section of three files, I think the file names have changed. For example, I suspect that "LEXBIBLE.logos4" is now "LEB.logos4", but I do not know for certain.
For the last file, I think that the file extension has also changed.

OrphanFiles.jpg

Find more posts tagged with

Comments

SteveF

DELETE

LexhamSGGNT.lbxdv

LEXSGGLOSSARY.logos4

These are now Cascadia Files

these might be "left-over" files from when I was beta testing

YES!

I suspect that "LEXBIBLE.logos4" is now "LEB.logos4", but I do not know for certain.

- Maybe David can help here?

(Dave Hooten has posted on this one a number of times)

Steve

Tim Lord

https://community.logos.com/discussion/comment/77639#Comment_77639

Thank you, Steve. Maybe some other readers can comment on the other files. Thanks in advance, everyone.

Dave Hooton

https://community.logos.com/discussion/comment/77647#Comment_77647

Tim

See your other thread re Lex Bible.

Delete LexhamSGGNT.lbssyn and LexhamSGGNT.lbxclv together with LexSGGlossary.logos4 from the L4 resource folder! All have been replaced by Cascadia Syntax Graphs.

Dave Hooton

Are any of these Logos 4 resources now obsolete? They do not match up with the files in my second (laptop) PC install, so I want to remove them if they have been replaced with newer Logos 4 files (these might be "left-over" files from when I was beta testing that are now obsolete, I am speculating).
I think that the first 4 files have had a change in their file extension from "lbx___" to "lbs___".

Correct. Delete the People/Places/things *.lbx files you list.

Delete everything you list!

BillS

https://community.logos.com/discussion/comment/77670#Comment_77670

This thread (& at least one similar thread) seems to reinforce the need for tools to manage our libraries. If we can't count on the "cloud" to ensure that obsolete (replaced) resources are deleted, then we need tools to make visible what's in our libraries & management tools to do it ourselves.

Don't get me wrong: I don't want to have to. I'm content to allow L4 to manage it--if it will actually do so. But if it won't, we need management tools....

I'm just sayin'..... [:)]

Blessings!

Tim Lord

https://community.logos.com/discussion/comment/77670#Comment_77670

Dave, thanks for your advice, this is what I suspected - "delete everything" on the list. I was able to create this list of file discrepancies using Microsoft's SyncToy utility (free) after doing a new Logos 4 install to a second PC, and having SyncToy report what was different between the Resources subdirectory on each PC. The first PC is the one I used for beta testing, so it is no big surprise there were these few remnant files that are no longer needed. But before deleting, I wanted to make sure, based upon feedback from others.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/77890#Comment_77890

This thread (& at least one similar thread) seems to reinforce the need for tools to manage our libraries. If we can't count on the "cloud" to ensure that obsolete (replaced) resources are deleted, then we need tools to make visible what's in our libraries & management tools to do it ourselves.

Don't get me wrong: I don't want to have to. I'm content to allow L4 to manage it--if it will actually do so. But if it won't, we need management tools....

It won't manage resources left over from pre-release beta testing.

BillS

https://community.logos.com/discussion/comment/78051#Comment_78051

It won't manage resources left over from pre-release beta testing.

Hi Bradley,

Given that we have little or no control of the resources Logos downloads to our machines, this seems an inadequate approach. If Logos downloads it & places it in a protected folder, shouldn't Logos clean up after itself?

Thanks for the response!

Damian McGrath

https://community.logos.com/discussion/comment/78080#Comment_78080

If Logos downloads it & places it in a protected folder, shouldn't Logos clean up after itself?

Agreed. We've been told that Logos doesn't want us playing with the resource directory (more or less).... Can't a future release just scan our folder and delet these files.

What about SESB2.0 - there's no reason why the old version should still be around. Why do we have to manually hide this file?

Matthew C Jones

https://community.logos.com/discussion/comment/78088#Comment_78088

What about SESB2.0 - there's no reason why the old version should still be around. Why do we have to manually hide this file?

I haven't looked at this particular resource to compare content but it raises another question in my mind: The International Standard Bible Encyclopedia (original version) has different content than the revised version now available in Logos content. Will Logos Version 4 overwrite the original ISBE resource when the revised resource is added to my library?

I hope it would maintain two resources.

Matthew C Jones

https://community.logos.com/discussion/comment/78080#Comment_78080

Hi Bradley, Given that we have little or no control of the resources Logos downloads to our machines, this seems an inadequate approach. If Logos downloads it & places it in a protected folder, shouldn't Logos clean up after itself?

Yes Bill.

Hi there Bradley, (I found this missing "r" from an earlier post [;)] Thought you'd want it back.)

Is a folder clean-up feature something we can look forward to? Microsoft & Java leave stuff on my system that eventually causes crashes if I don't go remove them myself. (earlier versions of Framework, for instance.)

Matthew

Dave Hooton

https://community.logos.com/discussion/comment/78080#Comment_78080

Given that we have little or no control of the resources Logos downloads to our machines, this seems an inadequate approach. If Logos downloads it & places it in a protected folder, shouldn't Logos clean up after itself?

Here's why an automated approach is needed:-

1. LexhamSGGNT changed to Cascadia during secret beta

2. L4 crashed if one attempted a syntax search on LexhamSGGNT

3. We were advised to delete 2 files (one was the database), but I found that a second resource (Glossary) also needed to be removed

4. The resources came back because they hadn't expired!

5. I hid them.

6. Repeat steps 3 - 5 with Lexham English Bible (I now have three hidden, expired, redundant resources).

7. Others "discover" redundant resources after the licence has expired

8. L4 crashes if attempting to hide them

9. I advise they now be deleted (some users don't know about hidden folders).

10. Incl. Biblical People/Places/Things there could be upwards of 500 MB (0.5 GB) of debris in the Resources folder.

11. And there are remnants (Lexham database) in the Downloaded folder that the Indexer keeps looking at!

Will Logos also keep a record of expired (hidden) resources in the "cloud"?

Damian McGrath

https://community.logos.com/discussion/comment/78251#Comment_78251

Here's why an automated approach is needed:-

Dave, that perfectly sums up the absolutely absurd situation we are in.

The frustration I experienced with the bad syntax files, causing a complete and very long re-index, has not been forgotten, Logos needs to delete these old files!!

Dave Hooton

https://community.logos.com/discussion/comment/78251#Comment_78251

11. And there are remnants (Lexham database) in the Downloaded folder that the Indexer keeps looking at!

After deleting the entry in Downloaded the Indexer still produces this:

2010-01-26 19:12:25.6467 6 Info Program Checking resource ID 'DB:SYNTAX-LEXHAMSGGNT' for update 'Resource DB:SYNTAX-LEXHAMSGGNT' to see if version '2009-10-06T03:08:43Z' is available.

BillS

https://community.logos.com/discussion/comment/78251#Comment_78251

Given that we have little or no control of the resources Logos downloads to our machines, this seems an inadequate approach. If Logos downloads it & places it in a protected folder, shouldn't Logos clean up after itself?

Here's why an automated approach is needed:-

1. LexhamSGGNT changed to Cascadia during secret beta

2. L4 crashed if one attempted a syntax search on LexhamSGGNT

3. We were advised to delete 2 files (one was the database), but I found that a second resource (Glossary) also needed to be removed

4. The resources came back because they hadn't expired!

5. I hid them.

6. Repeat steps 3 - 5 with Lexham English Bible (I now have three hidden, expired, redundant resources).

7. Others "discover" redundant resources after the licence has expired

8. L4 crashes if attempting to hide them

9. I advise they now be deleted (some users don't know about hidden folders).

10. Incl. Biblical People/Places/Things there could be upwards of 500 MB (0.5 GB) of debris in the Resources folder.

11. And there are remnants (Lexham database) in the Downloaded folder that the Indexer keeps looking at!

Will Logos also keep a record of expired (hidden) resources in the "cloud"?

Bump.

I find myself for the 1st time having to give Logos a grade of "F" on anything.[:(]

Absent a response that they're ever going to clean up their mess, and after discovering that the mess still exists in my installation, I've followed these instructions to manually delete the files.[:(]

I'll say again: if Logos makes the mess, & if they truly don't want us manually going into the hidden resources folder, then Logos needs to clean up after itself.

All that said, I still APPRECIATE this wonderful tool.... I still love Logos 4.

Mark

https://community.logos.com/discussion/comment/89319#Comment_89319

6. Repeat steps 3 - 5 with Lexham English Bible

This thread is a bit confusing for me. I have the Lexham English Bible. Do you mean to say that this file has been updated under a different name and this file we are no longer supposed to have?

Dave Hooton

https://community.logos.com/discussion/comment/89435#Comment_89435

This thread is a bit confusing for me. I have the Lexham English Bible. Do you mean to say that this file has been updated under a different name and this file we are no longer supposed to have?

The history of obsolete resources goes back to the secret Beta & doesn't involve those who got L4 after it was released last year.

If you notice duplicate resources in Library then you are affected, but the resources we know about are listed in this thread and it only requires the deletion of those files to remove the duplicate.