A beta tester of my patch has come up against a problem. He gets this message as shown below :-His Error Message
I've been trying to reproduce the issue and I *think* I now know what it is - I would just like a little confirmation if you could...
It seems to be that the patch requires enough free disk space on the disk which the patch is being applied to in order to complete successfully. For example, my patch modifies about 5.5GB of files, so I think it needs at least that amount of free space in order to successfully patch my product.
When I tried my patch on a system which only had 2GB of free space, I got the same error, albeit with a different file (I presume depending upon when the disk runs out of space the file it errors on will be different).
Once I clicked on abort, I realised that the patcher rolls back the changes - this was confirmed by trying to run the patch again and the patcher telling me it still had the old (pre-patched) version.
So, does the patch system keep a backup copy of every file it patches until all files have been patched successfully ? If so, in my case, an end user needs to have 5.5GB of free disk space in order to install the patch.
I can see why all files need to have a backup until all files are patched - otherwise one could end up with an installation in a state which is half patched/half unpatched.
I'd just like some confirmation of my theories so that at least I know and can inform the end users...
I think actually PatchFactory needs the 5.5GB of free space on the disk which contains the Windows TEMP folder - it so happens that this is the same drive that my product was installed...[Edit2]
It seems that PatchFactory creates a 'good' copy of the files it updates based upon the older versions (already installed on the end user's PC) and the differences PF knows about. Then once all 'new' files are created, it moves them to the end user's installed location and overwrites the old ones. This post has been edited by JoePublic on December 14, 2006 05:46 am