(Sad that it's been potentially confusing, yes.)įinally, no, Adobe no longer offers the installers for CF2016 or before on their site, now that CF2018 has come out. That's another reason to know which installer you are using.
Checksum md5 update#
It had added update 3, among other things, and in fact these new installers will also come with the latest available ColdFusion and JVM update. One had mistakenly turned on session persistence, for instance, which was corrected by a new installer in Jan 2015.Īnd that blog post about the mistaken CF11 installer update indicates that it was released in Dec 2014, as a replacement of the original CF11 installer from early 2014.
Checksum md5 install#
Or I help people often who install ColdFusion on a new machine using an installer they had used on a previous machine, some years ago.Īnd note that there were different CF11 installers over time, also. Of course, Adobe would typically just put the latest one on their site, but people often had downloaded it in the past and were then using it later, and didn't realize it was not "the same". The names are all the same (for a given version on a given OS and bit level.) So when you are installing CF, it would help to know which installer is which.
Checksum md5 for windows 10#
Then finally in Apr 2017 yet another installer (for Windows only) was released which DID add support for Windows 10 and Server 2016. Then in Dec 2016, a new installer came out (for all OS's) where they thankfully removed the API Manager, bringing it down to several hundred meg (still to large for some tastes, but that's not the point of this post). The original installer (in early 2016) included the API Manager (which made it a huge 1g plus!, and it did not happen to work yet for Windows 10/Server 2016). I was helping two different folks today with questions about their CF11 and CF2016 installers (because in both cases, there were different installers over time, even for the same version and OS and bit-level), and it's what prompted me to share that info above with them, and now to create this post.įor instance, did you know that with CF2016, there have been 3 installers? Why this can be helpful, especially with CF installersīut this can be especially helpful with ColdFusion installers, for a number of reasons. (Of course, if you had both files you could do a compare, but this is typically still faster.) The file the other person has may have the same name (and could even have the same date and file size) and yet NOT be identical.
Checksum md5 how to#
I leave that as an exercise for the interested reader.)Īnother reason knowing how to easily get the checksum can be when you are wondering if an installer you have is the same one that someone else says they have or used (see below for a real example of such confusion). (Such tools exist for other OS's, of course. It's been my observation that most folks never bother, but at least now if you want to (but didn't know how, on Windows), you can. You may have noticed that web sites often will offer the checksum value of a file you're about to download, with the intent that you could check that after downloading it-to make sure you got the file they intended you to get. (It's basically a hashing of the file contents into a small string that can be used to determine whether a given file shares the checksum with another file.)
There are at least a couple of uses of knowing/finding the MD5 or SHA-1 checksum for a file.
Regardless of what OS you use, for more on why knowing the checksum can be useful (and why comparing file sizes instead may not be enough), and especially with regard to some interesting info about installers for CF2016 and CF11, do read on.
Tools like it are included in other OS's, but I'm sharing the above for Windows users. The tool is built into Windows 7 and above, and Server 2008 and above (at least).
0 kommentar(er)
