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.

Find more posts tagged with

Performance

Comments

Robert Pavich

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.

Simon’s Brother

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 ?

Robert Pavich

Andrew,

what files are we suppose to work with in V3 only??

Bradley Grainger (Logos)

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.)

Simon’s Brother

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.

Simon’s Brother

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...

Simon’s Brother

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.....