http://blog.logos.com/archives/2010/05/logos_40c_is_now_available.html
I just tried update now and nothing.
I am not sure what to think. I see the blog....It says its out.
It's definitely not Gold at this time! I've got 6 hours of "today" whereas the US has up to 22 hours!
Nope, not out here (Texas) yet! [:(]
The text in the article says "later today"...so that could mean anything!
Really wish they'd wait until the update is released before telling us about it. Perhaps they're worried about their servers overloading. Still........
Gerry
They are probably still sleeping out on the west coast. When someone gets to the office in a few hours the "on" switch will get flipped.
The blog posted at 12:00 am their time. It did not say a time. It was also on my homepage.
Use this link: http://downloads.logos.com/LBS4/InstallerBeta/Logos4Setup.exe. It was down at the bottom of the announcement.
Just run the install program. It works great!
Don't be afraid of the "beta" word in Bill's link. If you use this, it will get you to the latest RC, which is the same as the final release.
Or you can wait until later... but I bet most of you don't!
Jerry
That's not what we are talking about, Bill. Note the /InstallerBeta/ bit - this may be the "gold" version but it has not officially been released as gold until you can get it via Auto Update or Update Now (or a weblink without Beta in it).
In some parts of the world isn't it currently "tomorrow", today? Does that mean they got it a day early, or did they still get it today? If they did get it today, since it is really tomorrow there, does that mean we got today or yesterday?[:^)]
I guess the real question is, are they still indexing?[:D]
I guess the real question is, are they still indexing?
Nope! I finished indexing yesterday[:)]
Since I set the update to use the Beta to get the Release Candidate, do I need to set it back for the normal updates?
You may already have it! Yes, set the update to Default so you don't get 4.0d beta.
My experience is that you need to set the update to STABLE to not get the next beta. At least that is the only way I was able to stop the beta downloads during the 4.0c beta cycle.
It's 8:30 am (Pacific Time) and mine still says No Updates Available.
If you are running the 'gold' version, setting the update channel to default will only allow updates to the 'gold' version.
If you are running the beta version, setting the update channel to default will allow program and resource updates to the beta version, and resource updates to the 'gold' version.
If you are running the 'gold' version, setting the update channel to beta will allow updates to all next or current beta updates.
If you are running the beta version, setting the update channel to beta will do the same thing as setting the update channel to default.
In other words the 'default' channel is the default for the category of program ('gold' or beta) you're currently running.
If you set the update channel to stable, it will only allow 'gold' updates, even if you're running the beta.
My experience is that you need to set the update to STABLE to not get the next beta. At least that is the only way I was able to stop the beta downloads during the 4.0c beta cycle. If you are running the 'gold' version, setting the update channel to default will only allow updates to the 'gold' version. If you are running the beta version, setting the update channel to default will allow program and resource updates to the beta version, and resource updates to the 'gold' version. If you are running the 'gold' version, setting the update channel to beta will allow updates to all next or current beta updates. If you are running the beta version, setting the update channel to beta will do the same thing as setting the update channel to default. In other words the 'default' channel is the default for the category of program ('gold' or beta) you're currently running. If you set the update channel to stable, it will only allow 'gold' updates, even if you're running the beta.
What about setting to default when running a release candidate? Is a release candidate treated the same as a beta in that context?
An RC is not 'gold' so it falls in the beta camp. I'm not sure what happens every time when the RC one is running becomes 'gold.'
However, last time participating in the 4.0b program updated me to the RC and when 4.0c b1 was released I did not update automatically that time, until I changed my update channel to beta. I don't know if that's expected behavior for every instance of an RC that goes gold (and there may have been an interim update in there between the RC that went gold and 4.0c b1). All I can say is that I think that when an RC becomes a 'gold' release, the update channel must be set to beta to get the next beta release, but I'm not 100% sure.
It's 9:00 am (Pacific Time) and mine STILL says No Updates Available.
An RC is not 'gold' so it falls in the beta camp.
Not true. RCs use the stable channel by default. RCs are released in the hope that they will become gold. So 4.0c gold will be exactly the same build as 4.0c RC4.
Yet those running the 4.0b 'gold' didn't go through the RC regimen of RC2-4, and the initial release of RC-4 wasn't gold until today sometime. One running the beta, setting the update channel to default or to beta would get the RC updates 1-4. I don't know what would happen if someone, having RC1, set their update channel to stable. Would they get RC-2, RC-3, and RC-4 (before it went gold)? I'm not sure, but I don't think so, hence my conclusion. An RC is still a Release Candidate, so it's not considered a stable release -- yet.
If you know something I don't about this, I don't mind being corrected.
Let me explain. There are two channels:
Here's which channels different releases use by default:
So if you're using RC1, and your channel is set to "stable" or "default", you will not receive RC2, RC3, etc. You would only get the release (aka gold) version.
If you're using beta 2, and your channel is set to "default", you'll get all the betas, and the first release candidate. Then you'll get no more releases until gold, because the RC uses the stable channel by default, whereas the betas use the beta channel by default.
As I stated in the blog post, the plan is to release it sometime today. We don't have a more specific ETA than that. We announce new versions slightly in advance of the release so you can know why you're getting a download and what it includes.
Removed by poster.
So if you're using RC1, and your channel is set to "stable" or "default", you will not receive RC2, RC3, etc. You would only get the release (aka gold) version. Mark, I am set to Beta and I have received all 4 RCs via update.
Mark, I am set to Beta and I have received all 4 RCs via update.
Which is what he said...he said if you are set to "Stable" or "default" when running RC1, you won't get anything else until Gold. You aren't set to "Stable" or "default", you are set to "beta" [;)]
I don't know what would happen if someone, having RC1, set their update channel to stable. Would they get RC-2, RC-3, and RC-4 (before it went gold)? I'm not sure, but I don't think so, hence my conclusion. An RC is still a Release Candidate, so it's not considered a stable release -- yet.
That has been my experience. I installed RC-1 via the posted installer file. My update channel was still set to default and I didn't automatically get RC-2. In order to get it, I changed my update channel to beta, then back to stable after installing. I didn't automatically get RC-3...again I changed to beta, then back to stable after installing...etc.
Well there are 3 update channel setting:
There are 3 kinds of releases
It seems that there are 2 "installers"
So what we have a three dimensional matrix of possibilities. What we need is for someone at Logos to let us know what goes in each cell in the matrix.
I seem to have gleaned from the forums that there is no way to reload the base product installer once you have downloaded the beta one. That is short of starting all over again.
Maybe I am all wrong, but what would be nothing new. [:)]
Really wish they'd wait until the update is released before telling us about it.
Which would then lead to multiple posts in the forum asking "I just got an update, what was it?"
As Phil stated above, doing it this way allows people to know what they will be getting shortly before the update comes. This seems like the best way to handle it given all the requests for what is in the updates [:)]
Not in Pennsylvania either - is there an issue? The blog does say 'by the end of the day.' But whose day? Pacific time 'day' or Eastern time 'day?' Can't wait to get my hands on the reverse interlinear!! How I have missed you... Thank you for bringing it back!!
Well Logos just posted to Facebook, "Logos 4.0c Is Now Available". And it still isn't.
The blog does say 'by the end of the day.' But whose day?
But do not forget this one thing, dear friends: With Logos a day is like a thousand... wait, that's not right.
We're working on it right now and are just double-checking everything to make sure the download and install is as smooth as possible for everyone upgrading directly from 4.0b to 4.0c.
we have a three dimensional matrix of possibilities
How about this?
Version you are running
Update channel
Version you will receive*
Stable
Release Candidate
Beta
Standard
Yes
Default
Note: You will always receive the latest version, by version number, not by date. So If you are running 4.0d beta 3 in June, you won't receive 4.0c SR2 in July, regardless of any of your settings here.
the care is appreciated - a less than smooth download and install will get you more blog traffic than this any day or as you say, 'a thousand is as... ' nah, that ain't right either... ;~)
Just started downloading 59.9MB.... I guess 4.0c is now live...
there must be lots of variations - mine is 1.19 GB
Yup.
Mine too. That's a lot of data.
Strange... I wonder why that is?
It seems to have worked though, it has installed and is now busy updating...
Mine was initially 59.9mb, installed automatically started L4 then started a new update of 1.19gb. Seems the initial update made L4 into 4.oc I guess the additional 1.19 gb is in reasorces? What all is being updated?
It's mostly the updated reverse interlinear files--which are large.
You are quite right... it is downloading another 1.19GB...!
How about this? Version you are running Update channel Version you will receive* Stable Release Candidate Beta Standard Stable Yes Default Yes Beta Yes Yes Yes Release Candidate Stable Yes Default Yes Beta Yes Yes Yes Beta Stable Yes Default Yes Yes Yes Beta Yes Yes Yes
Yes, assuming that there is only one version of the installer program. The instructions in the header of the beta forum suggest that there is a seperate "beta installer." If there were not two installer programs then one would not need to download the "beta installer." The URL in that post gets the installer from what looks like a beta directory. That is why I am suspicious that there are two installers. If there were not two installers, then all one would need to do is change the update channel. One would not need to download a different installer. Maybe I am "over reading" the instructions.
Thanks for your effort on the neat table. Assuming there is only one installer it would great to have on the wiki.
The URL in that post gets the installer from what looks like a beta directory. That is why I am suspicious that there are two installers. If there were not two installers, then all one would need to do is change the update channel. One would not need to download a different installer. Maybe I am "over reading" the instructions.
Frank,
The Table Mark documented is attempting to tell you what happens if you already have the application installed, and what it will do by itself.
If you instead manually run an installer, the table does NOT apply. The installer will do whatever its "payload" is. In the case of the Beta installer, expect to have the most recent beta stuff installed. (And, I'm guessing, you would then be enabled on the Beta channel too maybe.)
Note that some of the posted installer links on older posts seem to refer to an old and early copy of the Logos4 installer. Its important to NOT run a "random" installer from an old link in older postings.
In the case of the Beta installer, expect to have the most recent beta stuff installed. (And, I'm guessing, you would then be enabled on the Beta channel too maybe.)
Manually downloading and installing the latest beta will give you whatever you would have got from the beta channel (the channel will remain at default).
As far as I am aware, there are no 'old' copies of the Logos 4 installer. The file is replaced on the server, so I'm pretty sure it's impossible to install an old version, except perhaps from DVD.
Mark,
See http://community.logos.com/forums/p/15609/118975.aspx for comments about an OLD installer that is linked in a number of older posts.
The file version of the installer is OLD, but I don't know if it runs an old "payload'. Maybe it still uses the most current build, but has old install scripting.
If my caution in the above post has merit, it IS POSSIBLE to run an old installer.
Thanks, Jim, I hadn't noticed that. I've replied at that post to say that the install scripting and payload are the same for new and old versions of the installer.
That answers the question! I remember reading those posts. That is what gave me the idea that there were different kinds of install packages. Once one has the Logos up and running Mark's table applies. Please publish the table.
What caught me was not considering the possibility that the current state (beta, RC, or stable) would affect the meaning of "set update channel to ..."
I enjoyed being part of the 4.0b and 4.C beta cycles. (I relived a former life as a system designer and programmer.) I will opt out for 4.0d since I will be on the tundra in the Alaskan bush and then in the Collegiate Peaks Wilderness area of Colorado until August. Downloads of 10+ gigabytes are impossible in those places should I have crash and need to start over. Yes, I am taking a backup.
Mine was initially 59.9mb, installed automatically started L4 then started a new update of 1.19gb. Seems the initial update made L4 into 4.oc I guess the additional 1.19 gb is in reasorces? What all is being updated? It's mostly the updated reverse interlinear files--which are large.
Hmm. That explains why, when I checked my interlinear resources after the intial 59.9mb update, I could not find the "Display" button to change the behaviour of the interlinears! And yes, the bigger update began shortly thereafter. I'll just be patient now! [:)]
