Did a couple of short tests:
* copied over a .dcupdate file of one of my programs into an empty folder and ran it. As the dcupdate was current nothing happened even though no folder is installed (unexpected but makes sense - except when installing as we don't want to create a seperate dcupdate for installs)
* changed version to out of date one: dcupdate runs and says the installation is out of date and opens the .zip url in the browser resulting in a download box (unexpected as method used was unzip not visit. personally as I was hoping it would download and install it in the folder with the .dcupdate - it must do a check for the program and then get confused when it cannot find it).
* downloaded the latest FARR, extracted the .dcupdate file from it, downgraded the version and ran it: dcupdate downloaded the FARR installation exe and ran it, YAY. the installer isn't defaulting to the folder it is ran from - which makes sense as the installer wasn't built for this scenario).
Interesting findings anyway and should make it easier to add this feature if mouser thinks its a good idea