There are some ideas about changing the way how differential updates work in tdm_update.
The goal is to make any update differential, even if you local copy is dirty, if you update between betas, or update backwards.
Here is the very early prototype of tdm_update with new algorithm (let's say it is "tdmsync"-based).
Ironically, a better approach has already been proposed, so this tdmsync prototype will die as soon as the better one is implemented.
However, this won't happen soon, and there is still some sense in testing this version, because both algorithms rely on the same underlying idea.
Which is: it is possible to download portions of a file from HTTP server.
Note: the prototype is hacky, and using it would be a rough ride!
It is not related to the 2.07 beta testing, and it is unofficial and unsupported.
Unless you have experience of beta-testing and joggling with TDM versions, better not use it.
Instructions for updating:
1) Place the tdmupdate_tdmsync.exe into TDM installation directory which you want to update.
2a) If you want to update to the latest 2.07 beta release, then download tdm_mirrors.txt file just as you usually do for beta-testing.
2b) If you want to update to some particular version, then create tdm_mirrors.txt file in the directory with the following contents:
[Mirror azure] url = http://tdmcdn.azureedge.net/beta207-XY weight = 1
Replace beta207-XY with the codename of the version you want to get.
Codenames for 2.07 beta releases are listed here. The two other supported codenames are: release206 and release205
3) Start tdmupdate_tdmsync.exe.
4) Go to Advanced settings, and enable two checkboxes there:
--keep-mirrors (if you forget this, you will download the full 2.06 release of TDM!)
--noselfupdate (if you forget this, you will be switched back to stock version of tdm_update)
5) Now click button Continue>>.
6) It will tell you it is going to download huge amount of data --- ignore that.
Check that the number of files to be downloaded is less than 60 (otherwise you have launched updater in the directory without TDM --- better not do that).
7) Click button Continue>>.
8) The progress reports are rather broken during update.
In order to see what's going on, open the directory with TDM installation being updated, and see how new files appear.
The files with extension .tdmsync are metainfo files (about 30 MB total), the files with extension .bindiff are actual pk4 differences downloaded.
9) When update is over, note the number in Total bytes downloaded: XX.X MB report --- let it be D.
Go to TDM directory and check how much space all .tdmsync and .bindiff files take --- let it be S.
Unless I am wrong, the real amount of data downloaded is (S + D).
For instance, updating from release205 to beta207-01 took me roughly 600-700 MB of download size.
10) Now that you have the version you want, note that:
1. Most likely you have to reset darkmod.cfg. The effect of new config on old version and vice versa is unpredictable!
2. You probably have to run vcredist_x??.exe manually if TDM crashes immediately when started.
3. The updater does not remove new files when updating to previous versions. In most cases it has no effect.
One funny case is that if you downgrade from 2.07 to 2.06, you'll get HRTF still enabled, because alsoft.ini will remain =)
11) You can remove all .tdmsync and .bindiff files: you won't need them ever again.
But please don't delete .zip files: they are needed for future differential updates.
Please don't perform full updates with this updater.
If you want to get a fresh 2.05 installation, better copy one of the TDM installs you have (any version except SVN would be OK), then update it using the tool.