Hello Everyone, Krutonium here!
Note: This post is directed towards our Programming Users.
This is just a quick memo about a resource that we have available, should you wish to make any programs that for example check for new versions of our programs and such at set intervals or at boot or anything else.
We can also can provide other things if you need, but this is mainly if someone wants to code an update checker (and a downloader if you want).
First off, for the UnifL Video Driver, you can find a text file here:
Explanation of txt contents:
Currently this file reads:
1140422,14.4 WHQL UnifL v2.2,http://wp.me/p3rGaD-HY
Now I am going to explain what each part means:
This is the current release version. Each new release will have a value here that is one version higher than the old one, so to check if a new release is out, compare the value of this to a version stored locally (ill tell you where to find this later) in the registry. If the remote value is higher, then there is an update.
If there is an update, then you should process the rest of the file.
14.4 WHQL UnifL v2.2
This part is the name of the current release, to use in Dialogs and such, so you can for example tell your user: “There is an update to [14.4 WHQL UnifL v2.2] Available, would you like to update?”.
As a side note, you could also technically use this to check if there is an update, though we don’t recommend it, since we may update the version or the link, and not update the version name. This is unlikely to happen, but it is not impossible.
This link will either point to an article if applicable, or to a post on the forums if it is a minor release or revision (The Video Drivers are more likely to get a post for minor revisions, because the adb-USB UnifL Driver is very quickly developed and sometimes we release multiple versions in a couple of hours.) Use this link (from the txt file of course).
What if release went terribly wrong?
Now, there is a second txt that you should be aware of. This file is extremely important to check as well, because it only gets updated when something goes wrong.
This txt file contains just this at the moment:
This number represents a Killed version of the driver. Basically, we kill a release when either:
(A) It is corrupted internally
(B) Not installing correctly
(C) Causing extreme issues with whatever it is installed on
(D) Something just isn’t right (It’s never happened, but for example lets say a Virus sneaks into the CCC Installer – we would want to Kill that release).
Now, the purpose of this text file is so that you can check it to see if the current release (installed) has been killed. If it has, you should recommend to the user to upgrade or downgrade, basically try to get them off that version.
How to Parse the txt’s:
For the first text file (version.txt) You need to download the file and load it.
Split the string at the commas (,) and put each string into a variable, or put it all into an Array.
Then you can simply work with the values as you wish.
For the second text file, (killed.txt), you should download the text file, and take the currently installed version number, and do this:
if RemoteVer.Contains(LocalVer) then
//Your Code to handle a Killed release
//Whatever you want to do if it is not killed, likely nothing.
Now, for the adb-USB UnifL Driver, you will need to reference a different set of text files, but they use the same format:
Now you may be wondering:
How can I check the local version’s current version number?
UnifL Video setup stores local package information and current version in the Registry at:
In the values:
VersionNum (Local Package version)
Intel_DEVID (Part of UnifL Autoselector)
IsKilled (Determines if your Release is “Killed”)
Updater_Version (The Version Number of the Current Release)
Updater_Name (The Name of the Current Release)
Updater_Link (The Link to the Current Release Article)
And the UnifL adb-USB values can be found at:
With the ~same value names as above.
And with that, I bid you farewell!
(If anyone wants an example in Visual Basic, Please feel free to contact me via PM!)