Can't seem to find this answer anywhere.
I have two machines that are identical - one of them has the beta version of Logos on it, while on my main machine I've kept on the official SR track.
Now that 4.0b is at RC stage I'm considering installing it on my main machine as I've not encountered any substantive issues with it on the test machine and I would like to access some of the new functions (prayer lists) on my main machine.
My question is this - I recall reading somewhere that once you get on the beta track it will keep doing beta updates. What I don't want to happen on my main machine is that we get to 4.0b SR1 and then my main machine then proceeds to update itself to 4.0c beta 1.
Can someone who knows tell me whether this is the way it will happen or alternatively confirm that once you get to a SR level release it locks to only downloading subsequent SR releases and not betas unless you specifically download one?
Scripture set to music for worship and aid memorization. https://www.youtube.com/channel/UC-DojPa0TlpCGhtUJq1e3Pw
If you install 4.0b RC1 from the link provided below, it won't put that system on the beta track. It will only download updates to future 4.0b releases.
http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe
Jeremy,
You can also alter this by typing in the commandbar:
set update channel to beta
or
set update channel to default
Sarcasm is my love language. Obviously I love you.
Melissa Snyder: If you install 4.0b RC1 from the link provided below, it won't put that system on the beta track. It will only download updates to future 4.0b releases. http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe
Melissa,
I downloaded and installed from the link but it does not say RC just the 4ob and the long number. Everything seems to work just fine but it's indexing and keeps indexing. It started at under an hour, stayed between 45 and 40 minutes for a while, down to 15 minutes, then up to over an hour and now it's over 2 hours (2hris 40 min) remaining, to be exact at this exact moment. I saw in another message somewhere than indexing problems were fixed in 4ob but this has been going on now for about 3 hours. Is this normal? Also, if it doesn't say RC 1 is it a beta that I'm on the train for?
April
Melissa, to find out if you have the latest, go to the question mark in the upper right hand corner of the software andleft click it. Then left click "About Logos Bible Software". The numbers should read " 4.ob (4.02.3.7243)
Lynden Williams Communications https://www.lyndenwilliams.net
Sorry that should have read April.
Lynden Williams: Melissa, to find out if you have the latest, go to the question mark in the upper right hand corner of the software andleft click it. Then left click "About Logos Bible Software". The numbers should read " 4.ob (4.02.3.7243)
I know you corrected to April.
Yes, it I've checked the number and that is what I've now got. I did type the command to rebuild the index and it's working now. Started at 17 minutes then to 1 hr 20 minutes and is now at 1hr 40 minutes. Seems to be going up again. 1hr 48 minutes....
The time is estimated. The size of your libray determines how long it will take to index. Computer speed, ram, apps open, all of these affect indexing time.
Lynden Williams: The time is estimated. The size of your libray determines how long it will take to index. Computer speed, ram, apps open, all of these affect indexing time.
It's at 2 hrs 40 min remaining. I've only got 650 resources and only web browser open to this forum. My computer is fast for everything except Logos 4. Everything runs with no crashes, but processes are slow. Only 1376 mhz processor with none the that dual or quad stuff.
I seem to remember one time before it was saying over 2 hours then suddenly it was finished, so who knows. Number is now starting slowly down (2 hr 23 min now)
Will just leave it going all night and see where it is in the morning. Thanks for your help.
April,
How did it turn out?
Regarding your system having speed issues with Logos, It definitely wants beefier hardware than many other applications, part of this is due to the WPT/.NET backbone that it is built on. In particular I've found, as have others that the video card tends to be a potential bottleneck.