[futurebasic] FBII and ResCompare 2.6

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : March 1998 : Group Archive : Group : All Groups

From: RMMerrill <RMMerrill@...>
Date: Sat, 14 Mar 1998 16:43:54 EST
I have a project coded in PG and FBII. I have several versions of this 
project - let's say v1.1.3, v1.1.3+, and v1.1.4 - for starters.

I am using ResCompare 2.6 to create updater patches. I made a new patch 
for the update from 1.1.3 to 1.1.3+. Then I duplicated that patch and 
renamed it to v1.1.4 patch. I compared v1.1.3+ to v1.1.4 and appended the 
patch to v1.1.4 patch. I also compared a help file dated 20 Nov 1997 with 
a help file dated 21 Dec 1997 and appended that to the v1.1.4 patch. As 
instructed by Michael Hecht - ResCompare's author, I then created a ZFIL 
resource in ResEdit using a template provided in ResCompare.

If you have followed this so far - we are approaching my problem area...

I did an original install of v1.1.3 onto my PowerBook 5300. I was able to 
update this to v1.1.3+ - no problem.

I again did a clean install of v1.1.3 and I was able to update this to 
v1.1.4 - no problems.

I again did a clean install of v1.1.3 and I updated it to v1.1.3+, but I 
was unable to update this version v 1.1.3+ to 1.1.4. I kept getting the 
message "Sorry, the patch was unsuccessful. The contents of this file are 
different from what was expected. (CODE 132)"

I may be wrong here, but I expected the v1.1.3+ that was created by 
updating from v1.1.3 with the 1.1.3+ patch would have been the same as my 
clean install v1.1.3+ (which _will_ patch to v1.1.4). I have no clue as 
to why CODE resource 132 was singled out as having changed - it is 
patched from a size of 15324 in the original 1.1.3 to 15752 in v1.1.3+ 
and then to 15822 in v1.1.4 - since these size numbers are proper I 
assume that the resources are proper.

Can anyone follow the above sufficiently well and give me a hint as to 
what the problem might be? I have to make this work, because I now have 
v1.1.5,6,7,8 and v1.1.9 all of which need to be able to be patched by 
this single patcher application. And I'm working on v1.2.0 :)

Glory be where do we go from here...8-)

Thanks, for all the help you can provide.

     -=  Bob (-: