dmaker2

File attributes, meaning file names, read-only, archive bits, etc. all are identical to the source. Yes, I would agree the difference seams to develop in the building process. Unfortunately my knowledge of the ISO structure is limited so I can't easily figure out what is the variable element in the ISO to understand this further. I guess my question about all this was is this normal behavior when using ImgBurn and I think that is what you are suggesting. Although to me it I would not expect the system time to play any role in creating the UDF file structure. What would be the logic to do so? Thanks for your replies.

I am using version 2.5.8.0. When I use the “Create image file from files/folders” mode I observe a behavior that I did not expect. I create an ISO (call it ISO1), then I mount it and do a binary comparison to the source data and it verifies correct. Then I create another ISO from the same source files and folders (call it ISO2), then mount it and it also verifies to the same source files correctly. BUT when I hash ISO1 and ISO2 they have different MD5. I also compared the file attributes between the ISO files and they are the same. I also checked the case of the files names and folders and they are the same too. I tried UDF and ISO9600+UDF and ISOs created are not identical. If I binary compare the ISOs files to each other there is a difference but it appears not to be with the file and folder data but in some other area of the ISO files. I also tried different source files and folders and still they are not the same. I have the ImgBurn setting to the default values. I always assumed that ImgBurn would create ISO files that would be identical. Can anyone help me understand why ImgBurn doesn’t create identical ISO files?