MD5 of Backup images changes (entire ... Log Out | Topics | Search
Moderators | Edit Profile

X-Ways Support Forum » Hex Editing » MD5 of Backup images changes (entire .whx file) « Previous Next »

Author Message
Top of pagePrevious messageNext messageBottom of page Link to this message

Wayne Plumtree (Wayne384)
Posted on Saturday, Dec 28, 2002 - 1:23:   

Hi,
I have noticed that when I make a backup (personal backup) image of a disk (usually floppy disks, in my case) and compare the entire .whx file to another .whx file made earlier, the MD5 values don't agree.

In two recent cases that I examined, three bytes were different. The difference between two images were located in offsets 323, 324 and 325. In another they were located in offsets 339, 340 and 341.

Are these three bytes a variable? If so is there a way to make it a constant?

Thanks again,
Wayne

PS Thanks for your other responses.
....And start on that wish list ;-)
Top of pagePrevious messageNext messageBottom of page Link to this message

Stefan Fleischmann (Admin)
Posted on Saturday, Dec 28, 2002 - 12:31:   

The .whx file format is fully documented (see main web site). What you are noticing is probably a time stamp. You may want to integrate the MD5 into the backup file itself, digesting the actual disk contents only, not the entire (variable!) backup file.

The wish list is currently more than 100 items long and is constantly being populated, and suggestions are implemented into the software since more than 5 years.

Add Your Message Here
Post:
Username: Posting Information:
Only registered users may post messages here, i.e. you need to have an account.
Password:
Options: Enable HTML code in message
Automatically activate URLs in message
Action:
Forum operated by X-Ways Software Technology AG.