dbminter

I just burned that image to a Memorex 24x Ultra High Speed Mitsubishi CD-RW without any errors. However, there were Verify miscompares: I 13:34:24 Operation Started! I 13:34:24 Source File Sectors: 237,275 (MODE1/2352) I 13:34:24 Source File Size: 558,070,800 bytes I 13:34:24 Source File File System(s): ISO9660, Joliet I 13:34:24 Destination Device: [0:0:0] ASUS BW-16D1HT 3.11 (R:) (USB 3.0) I 13:34:24 Destination Media Type: CD-RW (Disc ID: 97m34s24f, Mitsubishi Chemical Corp.) I 13:34:24 Destination Media Supported Write Speeds: 16x, 24x I 13:34:24 Destination Media Sectors: 359,847 I 13:34:24 Write Mode: CD I 13:34:24 Write Type: SAO I 13:34:24 Write Speed: MAX I 13:34:24 Lock Volume: Yes I 13:34:24 Test Mode: No I 13:34:24 OPC: No I 13:34:24 BURN-Proof: Enabled I 13:34:24 Write Speed Successfully Set! - Effective: 4,234 KB/s (24x) I 13:34:24 Filling Buffer... (40 MiB) I 13:34:24 Writing LeadIn... I 13:34:41 Writing Session 1 of 4... (1 Track, LBA: 0 - 83374) I 13:34:41 Writing Track 1 of 1... (MODE1/2352, LBA: 0 - 83374) I 13:35:49 Synchronising Cache... I 13:36:01 Filling Buffer... (40 MiB) I 13:36:01 Writing LeadIn... I 13:36:06 Writing Session 2 of 4... (1 Track, LBA: 94775 - 117377) I 13:36:06 Writing Track 1 of 1... (MODE1/2352, LBA: 94775 - 117377) I 13:36:18 Synchronising Cache... I 13:36:25 Filling Buffer... (40 MiB) I 13:36:25 Writing LeadIn... I 13:36:29 Writing Session 3 of 4... (1 Track, LBA: 124278 - 230074) I 13:36:29 Writing Track 1 of 1... (MODE1/2352, LBA: 124278 - 230074) I 13:37:27 Synchronising Cache... I 13:37:33 Filling Buffer... (40 MiB) I 13:37:33 Writing LeadIn... I 13:37:33 Writing Session 4 of 4... (1 Track, LBA: 236975 - 237274) I 13:37:34 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 236975 - 237274) I 13:37:34 Synchronising Cache... I 13:37:45 Operation Successfully Completed! - Duration: 00:03:20 I 13:37:45 Average Write Rate: 3,162 KiB/s (18.4x) - Maximum Write Rate: 4,200 KiB/s (24.4x) I 13:37:45 Cycling Tray before Verify... W 13:37:58 Waiting for device to become ready... I 13:38:09 Device Ready! I 13:38:10 Operation Started! I 13:38:10 Source Device: [0:0:0] ASUS BW-16D1HT 3.11 (R:) (USB 3.0) I 13:38:11 Source Media Type: CD-RW (Disc ID: 97m34s24f, Mitsubishi Chemical Corp.) I 13:38:11 Source Media Supported Read Speeds: 4x, 8x, 10x, 16x, 24x, 32x, 40x I 13:38:11 Source Media Supported Write Speeds: 16x, 24x I 13:38:11 Source Media Sectors: 237,275 I 13:38:11 Source Media Size: 485,939,200 bytes I 13:38:11 Image File Sectors: 237,275 (MODE1/2352) I 13:38:11 Image File Size: 558,070,800 bytes I 13:38:11 Image File Volume Identifier: NEW I 13:38:11 Image File Volume Set Identifier: NEW I 13:38:11 Image File File System(s): ISO9660, Joliet I 13:38:11 Read Speed (Data/Audio): MAX / MAX I 13:38:13 Read Speed - Effective: 40x I 13:38:13 Verifying Session 1 of 4... (1 Track, LBA: 0 - 83374) I 13:38:13 Verifying Track 1 of 1... (MODE1/2352, LBA: 0 - 83374) W 13:39:26 Miscompare at LBA: 83373, Offset: 2064 W 13:39:26 Device: 0xAC W 13:39:26 Image File: 0x00 W 13:39:26 Total Errors in Sector: 52 W 13:39:26 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:26 Verifying Sectors... W 13:39:27 Miscompare at LBA: 83374, Offset: 2064 W 13:39:27 Device: 0x3D W 13:39:27 Image File: 0x00 W 13:39:27 Total Errors in Sector: 52 W 13:39:27 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:27 Verifying Sectors... I 13:39:27 Verifying Session 2 of 4... (1 Track, LBA: 94775 - 117377) I 13:39:27 Verifying Track 1 of 1... (MODE1/2352, LBA: 94775 - 117377) W 13:39:48 Miscompare at LBA: 117376, Offset: 2064 W 13:39:48 Device: 0x8D W 13:39:48 Image File: 0x00 W 13:39:48 Total Errors in Sector: 52 W 13:39:48 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:48 Verifying Sectors... W 13:39:48 Miscompare at LBA: 117377, Offset: 2064 W 13:39:48 Device: 0x3E W 13:39:48 Image File: 0x00 W 13:39:48 Total Errors in Sector: 52 W 13:39:48 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:48 Verifying Sectors... I 13:39:48 Verifying Session 3 of 4... (1 Track, LBA: 124278 - 230074) I 13:39:48 Verifying Track 1 of 1... (MODE1/2352, LBA: 124278 - 230074) W 13:40:34 Miscompare at LBA: 230073, Offset: 2064 W 13:40:34 Device: 0xF3 W 13:40:34 Image File: 0x00 W 13:40:34 Total Errors in Sector: 52 W 13:40:34 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:40:37 Verifying Sectors... W 13:40:38 Miscompare at LBA: 230074, Offset: 2064 W 13:40:38 Device: 0x62 W 13:40:38 Image File: 0x00 W 13:40:38 Total Errors in Sector: 52 W 13:40:38 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:40:38 Verifying Sectors... I 13:40:38 Verifying Session 4 of 4... (1 Track, LBA: 236975 - 237274) I 13:40:38 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 236975 - 237274) I 13:40:43 Operation Successfully Completed! - Duration: 00:02:27 I 13:40:43 Average Verify Rate: 3,758 KiB/s (21.8x) - Maximum Verify Rate: 11,969 KiB/s (69.5x)

The image can partially be burnt to DVD+RW. ImgBurn says it will do some conversions on the fly, but I'll retry on a CD-RW. I spoke with the OP via private message and they already tried Virtual CloneDrive per my suggestion. It's only displaying partial data, most likely from only one Session, either Session 1 or 4.

I think @LIGHTNING UK! may have to chime in on this. I got a next writable address invalid message while attempting to write Session 1. Does ImgBurn support multiple Sessions? I seem to recall at one point in the past that it did not support multiple Sessions. Here's what I got attempting to write the image to a DVD+RW: --------------------------- ImgBurn --------------------------- Next Writable Address is Invalid! LBA: 83375 / 18:33:50 NWA: 0 / 00:02:00 --------------------------- OK --------------------------- As another test, I attempted to burn this image to a DVD+RW as I said above and got a message saying the Image track format was MODE1/2352 but the Image track format for DVD is MODE1/2048. I'm no expert but an odd format value of 2352 seems to just be wrong to me. I have to wonder if the image is incorrect somehow. --------------------------- ImgBurn --------------------------- Your image doesn't appear to be of the correct format for burning onto a DVD. Session 1, Track 1 Image track format: MODE1/2352 DVD track format: MODE1/2048 Would you like the program to convert the data to the correct format 'on-the-fly' as it is written? Note: The actual image file is not changed. --------------------------- Yes No --------------------------- I 08:52:31 Source File Sectors: 237,275 (MODE1/2352) I 08:52:31 Source File Size: 558,070,800 bytes I 08:52:31 Source File File System(s): ISO9660, Joliet I 08:52:31 Write Mode: DVD I 08:52:31 Write Type: DAO I 08:52:31 Write Speed: MAX I 08:52:31 Link Size: Auto I 08:52:31 Lock Volume: Yes I 08:52:31 Test Mode: No I 08:52:31 OPC: No I 08:52:31 BURN-Proof: Enabled I 08:52:34 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 08:52:34 Filling Buffer... (40 MiB) I 08:52:34 Writing LeadIn... I 08:52:40 Writing Session 1 of 4... (1 Track, LBA: 0 - 83374) I 08:52:40 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 83374) I 08:53:00 Synchronising Cache... I 08:53:03 Closing Session... E 08:53:04 Next Writable Address is Invalid! E 08:53:04 LBA: 83375 / 18:33:50 E 08:53:04 NWA: 0 / 00:02:00 E 08:54:46 Failed to Write Image! E 08:54:49 Operation Failed! - Duration: 00:02:14

I won't, but there's no guarantee there wont be unsecured cross talk and someone else can get access to your image. So, you're best off not posting a link in a reply here, but to send me a private message with the link to it.

Oh, I'm sorry! I was under the impression this was an Audio CD. Unfortunately, I got my wires crossed with another post where someone had downloaded some Audio CD images that were causing write errors attempting to burn them. Yeah, I would be wary to give me access to something like that.

Well, all you have to do is create a folder for that image file(s) and just give me access to that folder. In Google Drive and Microsoft One Drive, you have to give permissions to files and folders for others to view them. And if you create a subfolder somewhere there, you have to grant me permission to view that folder. And only files and subfolders in that folder you grant me permission to view can be viewed/downloaded by anyone else. Don't know how it is for DropBox or any other cloud solutions, though.

Most PC's don't have bays for internal half height drives anymore, which is why I suggested getting an enclosure for them. Half height bays are simply more reliable. The current Pioneer 2213 BD burner is okay, but it has a few firmware issues the company won't address. While they DID fix the 8x DVD+RW issue that had plagued them for over a decade, they introduced a NEW one! They only write at 6x! Also, 8x DVD+R DL will only write at 2.4x. The ASUS I recommended supports writing M-Discs. I never use that function, but it's nice to have it available should I ever partake of it. I only ever get slim drives to use as readers for CD, DVD, and BD discs. I wouldn't trust them to write anything.

Oh, sorry! I meant to tell you how to open the Log in my last reply and I forgot. Under Help choose ImgBurn Logs. The folder with the .LOG file opens. Actually, it may be easier to just open that folder with the .LOG file and attach the entire .LOG file to a reply here. I'll go through it and see if there's anything I can glean from it. If you have your own way of capturing screenshots, by all means use yours. The CTRL+C is not a screen capture function. It's the common Windows Copy keyboard shortcut. It will just copy all of the text in an ImgBurn error window, if it's the highlighted window, to the Clipboard in Windows. You can then Paste that info into a post. A screenshot is probably better as CTRL+C will only copy the text in the window and possibly not the entirety of the window's contents. I don't recommend slim drives at all. They're generally riddled with issues. I also don't recommend Pioneers for writing to 8x DVD+RW if you can find any because those have been borked in Pioneer firmware for over 10 years and they show no signs of fixing their errors. Since I don't recommend slim drives, what I recommend is a half height internal drive like the WH16NS60 or the ASUS BW-16HT (Recommended.) Blu-Ray burners and put them in a USB 3.0 enclosure from VanTech (Recommended.) or an OWC (Other World Computing) one. However, those are BD burners and you may not require burning to Blu-Ray media. But, I've not used anything but Blu-Ray burners for about 10 years now, so I don't know what's good anymore for just DVD burners.

If you've got a cloud account and want to up this image set to it and let me download it, I'll attempt to burn it on a CD-RW and see what happens on my end.

Could be the multiple Sessions in the image file. I thought ImgBurn was unable to burn images with multiple Sessions. But, that may have been at some point in the past and that is a limitation that no longer applies.

This is completely unexpected. In my 25 years of burning optical discs, I've never seen that before, either in my experience or anyone else's. As I said, it should be impossible, actually. If a burn ejects mid write, it should be impossible to resume. Try opening the Log and see if you can find anything in it that appears at the point when the disc ejects. Or try to copy and paste anything that appears in the Log on your next burn when this happens. Best yet, if a dialog window pops up asking you to insert the disc again, try pressing CTRL+C with the window highlighted and see if you can paste anything from that CTRL+C command into a post here.

Wait, if it ejects in the middle of a burn, you can't just reinsert it and get the burn to finish. An eject in the middle of a burn will leave the disc in an unfinished state. Are you sure it isn't just completing the burn and then ejecting it before the Verify stage? You can tell because if you reinsert the disc when it ejects in the middle of a burn and Verify attempts to start, Verify will fail.

I took a look at the device listed. It appears to be a slim model drive. Slim models cannot automatically reload the disc on eject. This is by the design of slim line drives. Removing that ability saved on manufacturing costs. Plus, this model appears to be a slot drive as opposed to a tray drive, which means it requires human action to insert a disc. It cannot reload a disc even if you wanted it to. The bottom line is with this model drive, you MUST reinsert the disc on eject if you have the option to do so checked. You can try disabling it and see if it works better for you. Under Tools --> Settings --> Device --> Eject Tray After... --> Uncheck the Write box. This should prevent the disc from being ejected after the burn completes. So, Verify should start right away after the burn finishes.

Forgot to mention this. No, you don't use Write Files/Folders to disc to burn Audio CD image files. That just writes whatever files/folders you select to the disc 1:1. Yes, as was said, if they are Audio CD image files, you will need BIN/CUE format files.

It's nearly 20 years old and the shown images may be out of date, but the steps should be relatively the same in this old guide:

This is just a guess, but it could be different metadata causing the different contents. The 2nd ISO's files and contents, though the same, may have different time stamps since those files would have been added later. I don't know if ImgBurn uses the file metadata on the source device or if it creates its own time stamps based on when the files were added to the ISO. Again, this is just a guess, and it's pretty much all I've got on what may be happening here. When you said you compared the file attributes, does that mean the date and time stamps are the same for the files in both ISO's? If they are, then that blows the above theory out of the water, and I've got nothing else.

I know Verbatim used to make inkjet printable CD-RW's but that was years ago. So, I don't know if they still do. They still make inkjet printable DVD-R and DVD+R DL, because I do use those. If I ever got an inkjet printable CD label printer, I'd be future proof. Plus, you can write on them with a marker and not have to worry (Too much.) about the ink leaking through to the data surface. And now I only get the inkjet Verbatim DataLife Plus BD-R. I had some of those already for certain cases where I may want to write a label on them. 90% of my BD-R burns were temporary archive contents, so the branded surface was fine by me. Not anymore, though. I say NO Chinese drives are legit. I once tried to order an LG WH16N60 off of this one web site. The website looked legit even though the price was too good to be true. Had I known the site was Chinese, I would have avoided it. I only ordered from them because Amazon nor anyone else stocked it. What did I get? A cloth COVID face mask for $40 that shipped from China. After speaking with someone in broken English and providing proof they asked me for me the mask they knowingly sent me, the site mysteriously disappeared and the contacts stopped. China either makes junk not worth your paying for or they will actively rip you off. Just look at all the flash drive scams on Amazon.com. Offering ridiculous obvious scams like 16 TB flash drives, which don't exist, for $30. And what you get is hacked firmware that states incorrect free space on a flash drive that's like 32 MB only. So, you don't even get what you wrote to it because the firmware is hacked to overwrite existing data while returning a lie of how much free space is left. Avoid Chinese products and sellers as much as you possibly can.

Generally, "bad" images don't result in bad burns. Meaning, there's very little data in a disc image that can result in a failed burn. Failed burns are the result of media issues, incompatibility between drive and media, or a dying/dead/defective drive. But, if you're curious and want to test it, you can create a new image in ImgBurn with some dummy data and then write that new image to these same CD-RW in the same drive. I would be willing to bet you'd probably get the same failure results, though. I was pretty sure you couldn't find those DataLife Plus Ultra Speed CD-RW anymore. I was just curious if you bought them new. Then, maybe I could, too. I don't think anyone manufactures Ultra Speed CD-RW anymore. Like how no one manufactures 8x DVD+RW anymore.

But, they are two different beasts. Ultra Speed CD-RW are manufactured differently from standard CD-RW. So, even though Mitsubishi made both, they are not the same. And, for whatever reason, your drive is probably not liking one and liking the other. A firmware update would need to be made to fix that, but no one fixes firmware anymore. Firmware updates are only released for Ultra HD BD's anymore and those are only to shore up encryption vulnerabilities to prevent copying Ultra HD BD. NOT to address any performance issues. It also makes sense the standard CD-RW is working but the Ultra Speed one is not. The 2nd writes faster and therefore needs different firmware instructions to accommodate that. As you increase speeds in media, you get compatibility error increases, particularly as a drive gets older. BTW, can you still get those DataLife Plus Ultra Speed Verbatim CD-RW anymore? If you know of where I can get them, I'd be interested to know. I can only find some straggling Memorex Ultra Speed CD-RW on eBay. They're pretty good quality as far as I can tell, particularly for Memorex, which usually uses CMC crap, but apparently farmed out to Mitsubishi for their Ultra Speed CD-RW. At least, I've had no issues with the Memorex Ultra Speed CD-RW. Thanks!

That seems to indicate it's most likely a compatibility issue. Your drive likes the 97m34s23f CD-RW but doesn't like the Mitsubishi CD-RW. Not much you can do if you're dead set on using the Mitsubishi CD-RW except try a different make, model, and manufacturer of burner drive. It's also possible the Mitsubishi disc came defective from the factory or its reached the end of its write cycle life.

You're using the Mitsubishi good media, so it's not that, for a change. My only guess at this point is that your burner doesn't like that particular brand of media. Or the drive may have reached the end of its life or is defective. It's possible a firmware update for that drive might have fixed the incompatibility issue. In Write mode, right click on the drive letter for the target device and choose the last option in the drop down context menu that appears. Should say something like Check for firmware update.

Well, I've never used those other non Verbatim BD-R, but I would be worried about this: I 06:11:10 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000) I would never trust any media with CMC in its DID. I would also be worried that your drive is 2 years old. 2 years is a fairly above average lifespan for an optical drive. However, I have gotten 2 years out of Pioneer DVD drives in ages past. One of things I've seen when drives wear out is write speeds being capped at lower rates when the discs are rated for higher speeds. As for no longer trusting Verbatim BD-R, that would have been my posts. That applies to the branded blue and white BD-R discs. The inkjet printable DataLife Plus BD-R are still high quality. However, you're paying an extra premium for the printable surfaces you may never use. I never print on printable surfaces, but they appear to be the only high quality option BD-R out there anymore, so I pay the extra.

Those CD-R tests parallel the CMC Pro DVD-R tests I performed a few years ago. From what I gathered, the CMC Pro TY DVD-R were still of the same high quality that TY used to produce itself. And on par with Verbatim DataLife Plus/AZO DVD-R made by Mitsubishi.

How about I don't supply any more help? I, at least, offered an opinion. Doesn't mean it's right.

It's probably what I suspected before even opening the log. This goes a bit toward explaining it: I 19:54:52 Source Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) but it does not as readily explain why the Sony disc also failed. However, I have a feeling it's related. CMC Magnetics Corporation makes the absolutely worst discs out there. They are utter trash. You most likely bought the Verbatim Life Series CD-R from a brick and mortar store. The Life Series are junk. Now, Sony isn't as easily dismissed, but, over the past 23 years, Sony has also made little but junk. So, I'd be willing to wager their CD-R are just as much garbage as their BD-R's are. First thing I'd concentrate on is not using the trash media. Get yourself some Verbatim DataLife Plus (NOT the Life Series.) or AZO CD-R. Mitsubishi makes those. Those and Taiyo Yuden were the best out there for decades. Don't know about the state of TY's anymore after CMC Magnetics bought them. CMC Pro DVD-R media is still quality TY discs, though, last I used them.