Open BD-RE opened 4 months ago
Hello,
Theoretically, the behaviour shouldn't be different between BD-R and BD-RE once the augmented image has been written, AFAIK.
Did you enable "find and recover RS03 signature" in the options, just in case ?
Alternatively, did you try to use dvdisaster to read both media into distinct image files, and comparing them ? And also comparing them to the original augmented image file produced by dvdisaster, if you still have it ? The 3 files should be exactly the same.
Pre-preparation, i deinstalled 0.79.1 07-02-2010 to prevent those old DLLs from being on the path, which shouldn't be on the path anyway in the portable version. I made the ISO with cyperlink Media Suite 10 power to go. I augmented the ISO with dvdisaster-v0.79.10-pl3-win64-portable. I burned the ISO on a BD-R, with cyperlink Media Suite 10 power to go. Furthermore, I made a BD-R disk read test and an image read from the BD-R disk test. And comparing the burned image and the read image was successful. This was a proof of concept only. Starting with the BD-RE test.
I burned the ISO on a BD-RE, with cyperlink Media Suite 10 power to go. Furthermore, I made a BD-RE disk read test and an image read from the BD-RE disk test. And comparing the burned image and the read image was not successful. The size was significantly different. May I get better results with imgburn? Can you suggest settings? BD-RE_P2GoLog.txt BD-R_P2GoLog.txt
Hello, and thanks for the details, this helps.
Comparing your two log files, I see that the main difference is that for the BD-RE, your burning software enabled "PACKET_INC" burning mode. It's difficult to find information about that online, but all the references I found were used for reinscriptible media (DVD-RW, BD-RE). My assumption is that it's some kind of packet writing (https://en.m.wikipedia.org/wiki/Packet_writing), which would explain why the resulting burned data is completely different and dvdisaster can't find the augmented ECC data. You should disable packet writing in your burning software (it can probably be found somewhere in the options). This is surprising that packet writing is enabled when burning an image (ISO) file, because this mode is incompatible with image files.
If you can't find where to disable this mode, I would recommend using another burning program, imgburn is indeed known to be simple and just working.
I burned the ISO with ImageBurn (see the log) on a BD-RE Disk and read the disk back as an image with DVDisaster. Again, the ISO is bigger. And again no ECC Data recognition.
But I am happy DVDisaster is further developed, so I can try bigger BD-R with 100gb.
Got problem by burning RS03 ECC 10% to BD-RE 25GB : ECC Data is not recognized by dvdisaster-v0.79.10-pl3-win64-portable
I burned it (the same augmented ISO) also successful to an M-disk BD-R and ECC Data is recognized. I also burned an augmented ISO with 20% ECC RS02 to BD-RE and M-disk BD-R successful.
May I use wrong settings? Is BD-RE the Problem?
Tel me if you need more information.