Indexing
I downloaded and install 4.0 today. All went ok until indexing. It crashed often. I took advice about removing pre-2006 & lix/lsf files from Libronix 3.0 resource folder. Got me a bit further into indexing but still crashed. The real problem is that it goes right back to the beginning instead of picking up where it crashed at 2 files to go (grrr). Next step was to empty the resource folder completely & crashed at about 590 files to go.
Well, I'm at a loss and am looking for advice please on what to do.
Specs: Laptop Toshiba P30; P4 3.2 ghz; 2gb RAM; 128mb video card; running XP
David
https://echucacommunitychurch.com
MacBook Pro (13-inch, M1, 2020), 8 gig RAM, macOS Ventura.
Find more posts tagged with
Comments
Sort by:
1 - 1 of
11
Sorry, I meant to say that when I emptied the resource folder of lix/lsf & pre 2006 files, the indexer got to 2 files to go before it crashed.
David
David
https://echucacommunitychurch.com
MacBook Pro (13-inch, M1, 2020), 8 gig RAM, macOS Ventura.
David,
I also had to remove E4 resources as well as PBB files for my indexer to finish compiling. I'm not sure which title in these categories are the chief offenders, but third party book files at this time seem to be problematic. By the way E4 wasw a company that created a lot of books but didn't do a great job of makeing a quality product and Logos dropped them from being able to make and distribute Libronix books.
Bobby
Logos,
We need a list of known book titles that are causing Logos 4's indexer to hang/crash, is such a list possible?
Bobby
It's hard to say, really, sometimes a resource can become corrupt and cause this, sometimes it can be caused by something specific to the user's machine and setup.. We are looking into getting the indexer to resume from where it left off after a crash or unexpected close, however I'm not guaranteeing anything, this is a difficult situation..
Hi after speaking with the devs resources that cause problems are usually specific to that user because all the resources are actually fine, sometimes a specific user may encounter a corruption one way or another and thus it isn't relevant to the other users.
I'm having the same problem probably due to the E4 books. Has anyone reported this a a bug? Before Logos releases the program, it needs to be able to get around this problem, even if it skips indexing the books within the program itself.
Perry
Are you getting a crash? Can you post your logs? Thanks.
In case you missed it, Bradley has advised elsewhere to remove all E4 books and also recommends removing all lbxlls resources prior to Feb 2006. Not all of this have been optimized and so can cause issues. No conformation on when these lbxlls files will be sorted out and the future of the E4 books either ..at least that I have seen...too many posts to be able to keep up with them all.
Right forgot about that, thanks Andrew.