NIBCNT: LBXLLS file versions are later than LOGOS4 file versions!

I just received the update of the 18 volumes of the NIBCNT. On the computer which has Logos 3 on it (which I downloaded the files there first, after doing the unlock sent to me by email), Logos4 has two files that are in lbxlls format, with later file dates than the logos4 file versions - NIBCNT81PE and NIBCNT87REV. Scan does not bring in the Logos4 versions of the files because the lbxlls versions are newer, and I guess the one computer grabbed them out of the Logos 3 folder? (JUst guessing that's where it got them)

Here are the specifics:

1 + 2 Peter, Jude NIBCNT:

lbxlls version: 2010-01-13T21:47:46Z

logos4 version: 2010-01-12T23:08:10Z

Revelation NIBCNT:

lbxlls version: 2010-01-13T21:46:21Z

logos4 version: 2010-01-12T22:03:44Z

Is the lbxlls version really later, or was there just a mistake in the version stamping?

I hope this can be easily fixed, thanks!

Find more posts tagged with

Comments

Graham Owen

Is the lbxlls version really later, or was there just a mistake in the version stamping?

The more likely explanation is that there was a bug or problem in the lbxlls version that required a fix that was not in the logos4 version.

NetworkGeek

https://community.logos.com/discussion/comment/100770#Comment_100770

Thanks Graham, could be....but now we get the lbxlls version instead of the logos4 version on computers with logos 3, that can't be preferred....?

Dave Hooton

https://community.logos.com/discussion/comment/100775#Comment_100775

Thanks Graham, could be....but now we get the lbxlls version instead of the logos4 version on computers with logos 3, that can't be preferred....?

It's a known bug - http://wiki.logos.com/Bug$3a_L4_not_updating_$2a.lbxlls_files_with_$2a.logos4_files and I don't know when it will be fixed. But it is disastrous when a reverse interlinear lbxlls resource is preferred over the logos4 file (eg KJV1900). You will experience this problem if you downloaded your new L4 resources that were converted for use in L3.

If you have a working L3 I advise moving these resources to a new folder and including its path in L3's Resource Paths option. Temporarily rename that folder during a download and L4 will not be able to copy it over! There are some shortcomings of that approach so a better solution is:

change Automatically Download Updates to NO in L4 (this will let you know that a download is available and you can allow it when ready)
temporarily rename the L3 resource folder (will require Admin elevation in Vista/Win7).

You will have to do this for all downloads until a fix is available.

NetworkGeek

https://community.logos.com/discussion/comment/100971#Comment_100971

What's the best way for me to fix this, I don't want to hose anything up.... is it as simple as:

1. Exit both L4 and L3

2. Rename L3 Resource folder

3. Delete 2 .lbxlls resources in L4 Resources folder

4. Start L4 and do 'Update Resources'

Thanks!

Dave Hooton

https://community.logos.com/discussion/comment/101015#Comment_101015

What's the best way for me to fix this, I don't want to hose anything up.... is it as simple as:

Yes! Then continue to protect those & other similar files as I indicated.

NetworkGeek

https://community.logos.com/discussion/comment/101019#Comment_101019

Thanks Dave!

NetworkGeek

https://community.logos.com/discussion/comment/101021#Comment_101021

As a follow up, it did not download the 2 resources with Update Resources, so I copied the files over to a folder and did a Scan on it. I now have my Logos 3 resources folder renamed and sufficiently hidden, nay crippled [^o)]

Not sure why Update Resources doesn't always work, it's like it holds something about the state it was in, so when you delete a file(s) it isn't aware of it.

Dave Hooton

https://community.logos.com/discussion/comment/101167#Comment_101167

I now have my Logos 3 resources folder renamed and sufficiently hidden, nay crippled

You can revert to normal when the download has finished (read what I said about Auto Downloading Updates = NO ).

Not sure why Update Resources doesn't always work, it's like it holds something about the state it was in,

Delete the Updates.db!