Right now I am a total loss understanding how L3 and L4 are suppossed to be working together....
Can someone at Logos Please explain.....
On inital install I had issues with older files and was told to remove some 1300 files from main l3 resource path on c drive. I was under the impression that L4 would only look at the first path listed in L3 resource path settings, so I put these other 1300 files on J drive (j drive is actually where I would normally keep resource files b4 L4 beta come along) and made this path the secondary path in L3.... however L4 seems to be reading this secondary L3 path and tyring to use the resources that are suppossed to be getting excluded from my L4 install. If I remove this secondary path from L3, then I'm in the situation where I can't access these 1300 resources at all, and this is not the impression I got was going to be the case.
Can someone explain what is suppossed to be happenng hear and how I can setup my system so the two application can work alongside each other and L4 won't try and read the resources it is not supposed to access.
Comments
-
Andrew,
I was under the impression that L4 would read ALL PATHS that are specified in L3's resource path area.
Although, it never seemed to work that way for me.
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
Robert Pavich said:
Andrew,
I was under the impression that L4 would read ALL PATHS that are specified in L3's resource path area.
Although, it never seemed to work that way for me.
If that is the case how are we then suppossed to work with the files we have been told to use in L3 only ?
0 -
Andrew,
what files are we suppose to work with in V3 only??
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
AndrewMckenzie said:
If that is the case how are we then suppossed to work with the files we have been told to use in L3 only ?
Error handling (for older resources) has been improved for Beta 4; it should be able to scan all LDLS3 paths without crashing. (Of course, it is a beta, so there may still be some kinks to work out of the system, but hopefully that should be the end of having to divide LDLS3 resources into two categories.)
0 -
Robert Pavich said:
Andrew,
what files are we suppose to work with in V3 only??
I was told to remove all lbx files prior to feb 2006 date, plus all LLS files... a total of around 1300 resources because it was difficult at that point for Logos to determine which files in that set were causing problems with indexing etc.
0 -
ahh...now I get what you are saying.
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
Bradley Grainger said:AndrewMckenzie said:
If that is the case how are we then suppossed to work with the files we have been told to use in L3 only ?
Error handling (for older resources) has been improved for Beta 4; it should be able to scan all LDLS3 paths without crashing. (Of course, it is a beta, so there may still be some kinks to work out of the system, but hopefully that should be the end of having to divide LDLS3 resources into two categories.)
Thanks Bradley for the quick resposne...
0 -
Bradley Grainger said:AndrewMckenzie said:
If that is the case how are we then suppossed to work with the files we have been told to use in L3 only ?
Error handling (for older resources) has been improved for Beta 4; it should be able to scan all LDLS3 paths without crashing. (Of course, it is a beta, so there may still be some kinks to work out of the system, but hopefully that should be the end of having to divide LDLS3 resources into two categories.)
Bradley I have spent another sleepless night trying to nurse the re-indexing process. The probelm is we are still on beta 3 and you have re-introduced these older resources into the mix. You say the improvement comes in beta 4. The only way I have been able to get past stage 1 on indexing is to change my libronix path so it doesn't look at j drive where the older files are and in particular it seems the LLS files... Every time the indexer on stage 1 would dummy spit on LLS resources so in allowing the indexer to look at older resources in beta 3 but not having the improved handling of these files out until beta 4 you have created a situation where the cart is trying to pull the horse instead of the horse pulling the cart.... another 4030 resources to go...hopefully now I've pulled those LLS files out of the equation I will get through redindexing this time.. it will probably finish up about 2 days after this latest re-indexing was required of us.....
0 -
AndrewMckenzie said:
The probelm is we are still on beta 3 and you have re-introduced these older resources into the mix. You say the improvement comes in beta 4. The only way I have been able to get past stage 1 on indexing is to change my libronix path so it doesn't look at j drive where the older files are and in particular it seems the LLS files... Every time the indexer on stage 1 would dummy spit on LLS resources so in allowing the indexer to look at older resources in beta 3 but not having the improved handling of these files out until beta 4 you have created a situation where the cart is trying to pull the horse instead of the horse pulling the cart....
We didn't change the indexer between Beta 1 and Beta 3 (in terms of the types of resources discovered), so the advice has remained unchanged: limit the number of LBXLLS and LSF resources being discovered if you are having problems indexing. This is best done by temporarily removing those files from your LDLS3 discovery paths, or temporarily removing the folders from the Resource Paths list in LDLS3 options. When Logos 4 has finished preparing, put the files (or the paths) back.
0 -
Bradley Grainger said:AndrewMckenzie said:
The probelm is we are still on beta 3 and you have re-introduced these older resources into the mix. You say the improvement comes in beta 4. The only way I have been able to get past stage 1 on indexing is to change my libronix path so it doesn't look at j drive where the older files are and in particular it seems the LLS files... Every time the indexer on stage 1 would dummy spit on LLS resources so in allowing the indexer to look at older resources in beta 3 but not having the improved handling of these files out until beta 4 you have created a situation where the cart is trying to pull the horse instead of the horse pulling the cart....
We didn't change the indexer between Beta 1 and Beta 3 (in terms of the types of resources discovered), so the advice has remained unchanged: limit the number of LBXLLS and LSF resources being discovered if you are having problems indexing. This is best done by temporarily removing those files from your LDLS3 discovery paths, or temporarily removing the folders from the Resource Paths list in LDLS3 options. When Logos 4 has finished preparing, put the files (or the paths) back.
This is not what I was told by Bob. He said lsf file would contiue to work in L3. I am now into my third day of trying to get indexing complete after the license server muck up so I am a littel frustrated at the moment.
0 -
AndrewMckenzie said:Bradley Grainger said:AndrewMckenzie said:
The probelm is we are still on beta 3 and you have re-introduced these older resources into the mix. You say the improvement comes in beta 4. The only way I have been able to get past stage 1 on indexing is to change my libronix path so it doesn't look at j drive where the older files are and in particular it seems the LLS files... Every time the indexer on stage 1 would dummy spit on LLS resources so in allowing the indexer to look at older resources in beta 3 but not having the improved handling of these files out until beta 4 you have created a situation where the cart is trying to pull the horse instead of the horse pulling the cart....
We didn't change the indexer between Beta 1 and Beta 3 (in terms of the types of resources discovered), so the advice has remained unchanged: limit the number of LBXLLS and LSF resources being discovered if you are having problems indexing. This is best done by temporarily removing those files from your LDLS3 discovery paths, or temporarily removing the folders from the Resource Paths list in LDLS3 options. When Logos 4 has finished preparing, put the files (or the paths) back.
This is not what I was told by Bob. He said lsf file would contiue to work in L3. I am now into my third day of trying to get indexing complete after the license server muck up so I am a littel frustrated at the moment.
http://community.logos.com/forums/p/1714/14628.aspx#14628
Bradley, obviously there has been a communication diivide happen somewhere. I believe that has now been bridge. I apolgize that if in the pain and frustation of reaching that point I have said anything that has come across badly towards you or anyone else. I have found the directory where L4 is storing the resouce files moved anything out of there pre feb2006 that had slipped into that directory. Since I was at point where I needed to force indexing to start again. I took the opportunity to install a pre-pub I had put aside, gave my computer a reboot and it is now working through stage 2 of indexing. Stage 1 went smoothly. Thanks for your assistance.
Andrew
0 -
AndrewMckenzie said:
Bradley, obviously there has been a communication diivide happen somewhere.
Hi Andrew,
I think this has been the case, and I apologise for anything I've said that's caused confusion.
We have designed Logos 4 to read all LBXLLS and LSF resources and to be as backwards compatible as possible. (Logos 4 can successfully read every single LSF file we have on the network storage at Logos.) However, some of the changes we made between LDLS3 and Logos 4 Beta 1 actually made the program more unstable when processing corrupt LSF files.
Thanks to this beta test, we've been able to collect a lot of examples of corrupt resources. In one case, the real resource was 2.3MB, but one beta tester had a copy that was only 14K. In another case, a beta tester had a resource with the exact same date and size as the official file, yet some of the bytes in the file were somehow different. In your case, it seems that our copy of IVPUKOVB.lsf has gone missing (or is only in archive storage--it's over 10 years old) so we never tried to load it in our testing before Beta 1.
Thanks to these crash reports, we have been able to greatly improve the stability of Beta 4. I ran today's latest build on all the corrupt resources we have collected so far, and none of the crashes reported from Beta 1 through Beta 3 occurred.
All that to say that we expect that when Beta 4 is released (probably on Monday, US time), you should be able to discover/index all the resources that you've collected over the years. (And, in the unlikely case that there's still a crash, we can use the knowledge we gain from that to make Beta 5 even more robust.)
Thanks for all your help in this beta test.
0 -
Bradley Grainger said:
when Beta 4 is released (probably on Monday, US time)
Here I was hoping that it may be released on the Feast of Ss. Damian and Cosmas as a special gift for my Name Day.
0 -
The last re-index I kicked off last night has just completed
.png)
16 and half hours. later.
Logs:
0 -
Yeee Haaa!
Dave
===Windows 11 & Android 13
0
