4.0a RC 2 Release Notes

Bradley Grainger (Logos)
Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

4.0a RC 2 (v4.01.3.4533) is now available for installation.

To install, download and run this link: http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe


Bug Fixes

  • Fixed crash moving/opening media resources
  • The Message has a title when copying from CBV
  • Fixed crash in Word by Word section if surface text resource is unavailable/hidden
  • Fixed crash creating a new reading plan when Home Page tools disabled

The release notes for 4.0a RC 1 are available at: http://community.logos.com/forums/t/7480.aspx

Comments

  • Jeff Loven
    Jeff Loven Member Posts: 99

    Will I have to go through the many-hour re-indexing process with this RC?

     

    Thanks, 

    Jeff

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    Will I have to go through the many-hour re-indexing process with this RC?

    Only if you have a corrupted index. (If you merged with any of the betas, and haven't reindexed with RC 1, your index may be corrupted.)

  • Kevin Becker
    Kevin Becker Member Posts: 5,604 ✭✭✭

    Will I have to go through the many-hour re-indexing process with this RC?

     

    Thanks, 

    Jeff

    You shouldn't have to. I never had a full -reindex in the entire beta cycle after the initial index. I didn't have to do a full index with RC 1. Granted, I haven't had the chance to update to RC 2 but I don't imagine it would need to index again based on my experience.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    There was a bug in 4.0a RC-1 which it's too late to fix now!

    It looks for updates from the stable.xml RSS feed not the beta.xml feed, so Update Now doesn't work. So we have to download the installer again, as Bradley says.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Jeff Loven
    Jeff Loven Member Posts: 99

    When I run the "Update Resources" function manually it only takes about 3 seconds before it informs me that no updates are available. My library contains 1776 resources; shouldn't it be taking longer than this?

     

    Thanks again, great update Logos crew!

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    There was a bug in 4.0a RC-1 which it's too late to fix now!

    It looks for updates from the stable.xml RSS feed not the beta.xml feed, so Update Now doesn't work. So we have to download the installer again, as Bradley says.

    That was by design; we didn't want to have to re-release it just to change the channel from "beta" to "stable" (if no other bugs were found). RC2 also checks the stable channel.

  • Adrian Frost
    Adrian Frost Member Posts: 77

    Thanks Mark, that would explain why "Update Now" hasn"t worked for me. Problem is that the installer doesn't work correctly for me. It says: "Please wait while Setup downloads files" and underneath the non-moving progress bar: "Downloading Logos 4 Web Script... Progress..." Then nothing happens at all.

    If I press "Cancel" then the installer quits saying it was unable to download a required file.

    I'm using Windows Vista SP2 with all the UAC stuff enabled and running in a limited account.

    (And on non-preview I see that Bradley has explained the stable/beta thing...)

    Eglise Protestante Evangélique de Libramont, Belgique - www.epelibramont.com

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    That was by design; we didn't want to have to re-release it just to change the channel from "beta" to "stable" (if no other bugs were found). RC2 also checks the stable channel.

    You're obviously an optimist! Perhaps that suggests a new command would be useful "set update to beta" whereby we could ask Logos to permanently monitor the beta RSS rather than the stable RSS.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    That was by design; we didn't want to have to re-release it just to change the channel from "beta" to "stable" (if no other bugs were found). RC2 also checks the stable channel.

    You're obviously an optimist! Perhaps that suggests a new command would be useful "set update to beta" whereby we could ask Logos to permanently monitor the beta RSS rather than the stable RSS.

    You mean the "set update channel to beta" command? [;)] Use "set update channel to default" to turn it off.

    We haven't publicised it much because (a) it overrides the default setting (of beta vs stable) so you're not testing that feature exactly as it will be in the release version, and (b) it seems quite possible that someone would forget that he had turned it on, and automatically get upgraded to 4.0b Beta 1 only to find out that it crashes his system, but not before upgrading all his local files so that he can't downgrade to 4.0a. If you have a dedicated testing machine/account, though, it probably won't hurt anything to change that setting, and you'll get all the latest betas as soon as they're available.

    However, it's definitely a "use at your own risk" command.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    Bradley, I think this could be your most productive day in the office yet!!

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Jeff Loven
    Jeff Loven Member Posts: 99

    Hey ya'll, 

    I'm running RC-2 and everything was fine, until I purchased several resources. Logos now appears to be re-indexing my entire library....at this point my status indicator reads "12 Hours Remaining." Any ideas on why this has happened?

    Thanks!

  • Mike  Aubrey
    Mike Aubrey Member Posts: 447 ✭✭
  • Keith Gant
    Keith Gant Member Posts: 118

    I'm new to this, having recently upgraded to L4. For someone who is not involved in beta testing, is it advisable to install beta's like this, or to wait until they release something which the automatic upgrader installs for you?

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • Donovan R. Palmer
    Donovan R. Palmer Member Posts: 2,661 ✭✭✭

    I'm new to this, having recently upgraded to L4. For someone who is not involved in beta testing, is it advisable to install beta's like this, or to wait until they release something which the automatic upgrader installs for you?

    This is actually "Release Candidate" which is considered very stable. I have been using L4 Windows since the beta stage as my primary Bible programme and I don't have any regrets.  This RC version will even be better than what we have been using, so I would say go for it if you are so inclined, but recognise there may be the occasional issue still being worked out.

  • Adrian Frost
    Adrian Frost Member Posts: 77

    Update problem resolved. I set the channel to beta, rebooted and the upgrade went fine. Then set it back to default as suggested. thanks Bradley for the tip.

    Eglise Protestante Evangélique de Libramont, Belgique - www.epelibramont.com

  • Dr. Charles A. Wootten
    Dr. Charles A. Wootten Member Posts: 286 ✭✭


    4.0a RC 2 (v4.01.3.4533) is now available for installation.

    To install, download and run this link: http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe

    The download option was given in two different postings. I downloaded one, tried it. Didn't work. Downloaded the other, tried it. Didn't work. I've no clue what the "unusual way" means....[:S]

    Here are screen shots that might give you an idea as to why nothing happened. I'm using Windows 7, 8gigs RAM, 850gigs HD free space, all programs closed except the Thunderbird e-mail program.

    Any ideas?

    thanX!!

    God bless

    {charley}image

    image

    running Logos Bible Software 6.0a: Collector's Edition on HP e9220y (AMD Phenom II X4 2.60GHz 8.00GB 64-bit Win 7 Pro SP1) & iPad (mini) apps.

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    I've had this message after rebooting after installing Logos. It doesn't seem to affect the installation in any way. To see whether the update has been installed, load Logos, click on the Help icon, and choose About Logos Bible Software. The version number listed should be 4.01.3.4533 is you're using RC2.

    This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

  • John Fidel
    John Fidel MVP Posts: 3,388

    I am getting this error this morning on my SR7 installation. It does not allow the update to occur.

  • John Fidel
    John Fidel MVP Posts: 3,388

    Charles,

    I was able to work around this by going to the command line and typing:

    set update channel to beta

    It updated to RC2

    Afterward, remember to change it back by typing:

    set update channel to default

    It did run a merge index under RC2, but I had many books that were not merged in before I updated from SR7

  • BillS
    BillS Member Posts: 3,805 ✭✭✭



    image


    Hi Charley,

    I got the same error... but the software does appear to have installed correctly, anyway. The version in help | about is the new one.

    Hope your problem resolves... :-)

    Grace & Peace,
    Bill


    MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
    iPhone 12 Pro Max 512Gb
    iPad 9th Gen iOS 15.6, 256GB

  • Melissa Snyder
    Melissa Snyder Member Posts: 4,702 ✭✭✭

    Charles, John and others with a Runtime error updating from SR-7 ~

    Try deleting the Install folder in the Logos 4 directory, then run the Logos4Setup.exe again.

    Thanks,
    Melissa

  • Kevin Becker
    Kevin Becker Member Posts: 5,604 ✭✭✭

    Charles, John and others with a Runtime error updating from SR-7 ~

    Try deleting the Install folder in the Logos 4 directory, then run the Logos4Setup.exe again.

    Thanks,
    Melissa

    Melissa,

    Why should we do this? I don't want to be difficult, but I had this error and it didn't seem to cause any problem with my install. Is there another issue that deleting this folder and running setup again with prevent/take care of?

  • Dr. Charles A. Wootten
    Dr. Charles A. Wootten Member Posts: 286 ✭✭

    I was able to work around this by going to the command line and typing:

    set update channel to beta

    It updated to RC2

    OUTSTANDING! It simply took moments to do. I thought I saw that statement about setting the update channel but ignored it out of sheer ignorance.

    Afterward, remember to change it back by typing:

    set update channel to default

    Done. It checked for updates and all is now well. I'm looking forward to using the "analysis" in the Search and a couple of the things that Mark used in his preaching videos. (They really are very cool!).

    I appreciate the responses this morning, gents and ladies! Thank you.

    God bless and Merry Christmas

    {charley}

     

    running Logos Bible Software 6.0a: Collector's Edition on HP e9220y (AMD Phenom II X4 2.60GHz 8.00GB 64-bit Win 7 Pro SP1) & iPad (mini) apps.

  • Melissa Snyder
    Melissa Snyder Member Posts: 4,702 ✭✭✭


    Charles, John and others with a Runtime error updating from SR-7 ~

    Try deleting the Install folder in the Logos 4 directory, then run the Logos4Setup.exe again.

    Thanks,
    Melissa

    Melissa,

    Why should we do this? I don't want to be difficult, but I had this error and it didn't seem to cause any problem with my install. Is there another issue that deleting this folder and running setup again with prevent/take care of?


    Some customers have not been able to get beyond the error, as you could, to continue the install. In their case, deleting the Install folder was the solution.

    Melissa

This discussion has been closed.