Simple patching between to folders

[Asarhia]

Hello,

I'm trying to use Visual Patch to compare two folders and generate a patch file, but no application is actually installed on the system. Basically I have:

C:\Folder\20080824
C:\Folder\20080825

My idea is that someone who already has a copy of the entire "20080824" folder can just create a copy of it, rename it to 20080825, stick the patch file inside it, run it and have an up-to-date "20080825" folder.
The folders contain an application with executable files and stuff (just not for PC) and therefore nothing is actually installed on the system. I selected the executable file as the key file (different for each version) and also tried selecting both "Current Folder" and "File Search" with the name of the executable file from folder "20080824" (let's call it 20080824.axe), but no matter what I do, when I run the patch file it can't locate the right file and does not install the patch, not even after doing a full local hard drives search.

If anyone could point out what I'm doing wrong (including whether I'm trying to use this application for the wrong scope) that would be really appreciated!

Many thanks,
Asarhia

[jassing]

The problem you're going to have is that the exe's (key files) dont' exist in both versions so it has nothing to compare it against... I think that's why it's not finding anything to patch.

Can you post your .tu2 file?

-josh

[Asarhia]

Sorry, I'm a bit new at this, is that a file from True Updater? I'm only using Visual Patch 3.0 Trial at this time, the only file I can see is the .vp2 (project) file...

[jassing]

Originally Posted by Asarhia

Sorry, I'm a bit new at this, is that a file from True Updater? I'm only using Visual Patch 3.0 Trial at this time, the only file I can see is the .vp2 (project) file...

Sorry -- yes; I mean the the vp2 file...

[Lorne]

That should work fine -- VP doesn't need an application to be installed, it will work fine with plain data files.

In order to use the default version identification feature, you need to select an appropriate key file so the patch will recognize the "version" of that folder's contents as something it can patch.

For that you just need to choose a file that is unique to the 20080824 version, and that has never been modified at all by the user (so its MD5 signature matches the copy that you use when you build the patch). You also must not change the filename of the key file.

The user's guide has some information about key files, and if you search this forum you should be able to find some good advice on what kinds of files to choose.

[Asarhia]

Hello both,

Thanks for taking the time to reply to my post!
I've attached my vp2 project. Basically I have this structure for version 0822:

0822\MyApp_080822.exe
0822\Folder\Another Folder\Yet Another Folder\1\1.tmp
0822\Folder\Another Folder\Yet Another Folder\1\1.xyz
0822\Folder\Another Folder\Yet Another Folder\2\2.tmp
0822\Folder\Another Folder\Yet Another Folder\2\2.xyz

And then for version 0823:

0823\MyApp_080823.exe
0823\Folder\Another Folder\Yet Another Folder\1\1.tmp
0823\Folder\Another Folder\Yet Another Folder\1\1.xyz
0823\Folder\Another Folder\Yet Another Folder\2\2.tmp
0823\Folder\Another Folder\Yet Another Folder\2\2.xyz

I added version 0822 with "MyApp_080822.exe" as key file and version 0823 with "MyApp_080823.exe" as key file. The patch builds fine, finds "MyApp_080822.exe" as a new file and includes all of it, plus finds differences in the other four and creates a patch. If I run it from within the 0822 folder it is unable to locate the right version, however if I run it from version 0823 it will say that I already have the most current version.

Any inputs would be greatly appreciated!

Many thanks,
Asarhia

[Lorne]

Hmmm. Are you renaming the key file before you run the patch? When you copy the contents of 080822 over to 080823, you can't rename the keyfile from "MyApp_080822.exe" -- if you do it will no longer be considered a valid match for the original 080822 key file.

If you want to rename the file, you must do so after patching (for e.g. using a File.Rename action in the On Post Patch script).

Couple other things to check are that your destination paths are correct on the system where you're patching, and to verify that the MD5 checksums match for your key files (between your system and the target system). For example, verify the actual MD5 signatures using fsum.exe.

[jassing]

based on the test.vp2 file you posted,my initial comment is valid.
You need to have the key file be the same name in each version.

Keep all the files the same name (you can add/delete files;but files you want PATCHED need to be named the same) across all your versions; then you'll be OK