I ran both images through isovfy version 3. At this point I decided it was time to start digging into some specs. From this I learnt that the Primary Volume Descriptor which is a data structure that is present on all ISO images contains two interesting fields:. In theory, multiplying both figures should give the expected size of the ISO image, and this would provide a useful way to check if data are missing.
Running the script against some 20 ISO images I had lying around showed that for 7 files the expected size was indeed identical to the actual file size.
For most images, the actual size turned out to be marginally larger than expected typically about kB. For 3 images, the actual size was about twice the expected size.
Digging deeper, I found out that these were hybrid images that contain an Apple partition on top of the ISO file system. According to this Wikipedia article , these hybrid discs come in two varieties:.
In my case all of the 3 hybrid images turned out to be of the first category. For my hybrid images, multiplying both figures resulted in a value that was close to but again marginally smaller than the actual file size. I wrapped up the results of the above analyses into Isolyzer , which is a dedicated Python tool for checking the size of an ISO image.
What it does is this:. In addition to this, Isolyzer also extracts and reports technical metadata from the Primary Volume Descriptor and the Zero Block. Currently the test results are reported in the following format this may well change in upcoming releases :. In this case both are identical. Below some output for a truncated ISO:. Do others find this useful? Are things missing i. The difference is typically in the order of about kB.
If anyone knows more about this, please let me know! Isolyzer can be found here on Github. It can be installed using pip ; see the instructions here. Thank you for the link to your older blog post!
Isobuster is nice tool and I like it, but in our library we are using lot of open source software and I would like to continue with it. I know that isolyzer is not ISO image validation tool. I am using it just as one of more tools to check new ISO image after creation. No, but I have downloaded it.
I haven't gotten around to installing it, because I only want to do it when I have moved all my wanted clips off, and to minimize waste I can only do that when I have a full burn batch of clips. I will try that eventually. I'll do that if I need to do another build, but I think I'll be using only Read mode for a while. That's okay, no harm done, except a little wasted time.
I'll probably waste a lot more time before I solve this problem. By using this site, you agree to our Terms of Use. Share More sharing options Followers 0. Recommended Posts. DWRoscoe Posted December 12, Posted December 12, Hello folks. Has anybody else seen this problem? Or is this a bug that can be fixed? I have appended below the log file and the disc information pane text from the test Read. Thanks for your help. I Operation Started! I Operation Successfully Completed!
Link to comment Share on other sites More sharing options It's already doing everything it can. DWRoscoe Posted December 13, Posted December 13, Connect and share knowledge within a single location that is structured and easy to search.
I am trying to read the contents from the ISO image using Rust. I have installed libisodev and libcdio-dev on my Linux machine to get access to the header files. Libiso is a library to work with ISO filesystems development files. I used bindgen to generate bindings to the library.
Until this point, everything was pretty straightforward. Here is the example that I want to replicate in Rust line 89 is where I am at this point. I assume that I am not calling the method as I should because of the types, but other than that, I have nothing. Any hint or help would be highly appreciated.
Thank you! It is a double pointer. Here is what the C example code is doing:. The Rust code is passing in a null pointer for this parameter, which is the issue. How are we doing? Please help us improve Stack Overflow.
0コメント