aritchie Posted February 1, 2010 Share Posted February 1, 2010 Is it possible to disable ImgBurn from giving up logging of a particular type of warning/error after 1000 occurrences? I'd like to see all such occurrences of warnings/errors, even though this may mean a substantially bigger log file. Is it possible to log the size of the final filesystems being generated for an image? i.e. how much space do each of the ISO9660, Joliet and UDF filesystems take up within the image? Is it possible to describe what criteria ImgBurn uses for identifying duplicated files (when using the "Optimize duplicate files" option? Is it filename/filesize/filedate or MD5 or some combination of these and/or some other criteria? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 1, 2010 Share Posted February 1, 2010 1. No. 2. Take file size away from image size. 3. MD5 Link to comment Share on other sites More sharing options...
aritchie Posted February 2, 2010 Author Share Posted February 2, 2010 1. No. 2. Take file size away from image size. 3. MD5 OK - thanks for that. I think I understand what you're saying regards for 2) - but that would only give me the combined size of all the included filesystems - is there any way to report on the size of each individual filesystem and, if not, could that be provided in a future release? I know it's not life or death - if you need a filesystem then you need a filesystem - but it may be useful to assess the impact of choosing to use a particular filesystem over, say, altering file naming to fit in with a more restrictive filesystem (e.g. using ISO9660 level 0 or 1 as opposed to UDF - as, choosing UDF, appears to have added nearly another 100MB to the image size in our case, up from about 60MB with IS09660+Joliet combined to about 160MB). Lastly, for 1) could the ability to specify logging thresholds be made configurable in a future release? Regards, Andrew Link to comment Share on other sites More sharing options...
Recommended Posts