dbminter

I had wondered why BD-R SL's didn't migrate to using 33.3 GB layers, since they did exist in BD-R TL discs.

The good news that's not "sparking" but I figured you probably were aware of that. That sounds more like the laser having difficulty switching between the layers. Actually, another possibility is it's not a BD-R/RE DL layer on the other side. It could be one of those single layer 33.3 GB BD layers. Triple layer BD's use layers that are 33.3 GB each. (So, yes, technically 100 GB TL discs are not 100 GB but 99.9 GB.)

34 GB is a double layer Blu-Ray or HD DVD. The fact that Windows asks if you want to format it as a giant floppy (Packet writing.) indicates it's a BD-R DL or BD-RE DL layer. A BD drive wouldn't be able to read anything from an HD DVD layer. However, it is practically unheard of to create CD-R flippers with a CD-R on one side and a BD-R/RE DL on the other.

If you've got a CD with a branded surface, like those CD-RW's in your other post, you could try putting one of those in your drive with the label side down and see how ImgBurn behaves. See what it returns. See if it returns a Logical Unit Not Ready - Cause Not Reportable error. (I've never seen that 2nd part before.)

It's always possible. I've never seen such a thing and I can't see much use in producing one because people might be confused which side you're supposed to put face down into a device. Plus, given that the drive tries to do something to it as opposed to just returning no disc in the device indicates the other layer has a surface for a laser to pass through, indicating the layer is intended to be read.

Yeah, when you're a new member, you're limited in the # of posts you can initially make to 5 a day. This deters potential spammers. After a few days, you should have unlimited posting privileges. The different colored layer lends credence to my theory it's an HD DVD layer. Also the BD drive being unable to read it makes me think that, but it's virtually unheard of for a CD-R to have an HD DVD or Blu-Ray layer on its flipper side. Maybe it's a weird hybrid CD where one side is a CD-R and the other is a Super CD or something like that. Super CD were closer to DVD's but I'm not entirely sure DVD drives can read Super CD.

Hm, well, that was unexpected. Normally, flippers for CD's were reserved for Audio CD layers on one side and a DVD Video layer on the other for music videos or assorted data files. It's decidedly unusual for a CD-R flipper to exist. Those would normally be recordable CD layers on each side. About the only thing I can think of is the other layer is a CD-R side that hasn't been recorded yet, but the fact it attempts to find a track indicates there is something recorded on that layer that the drive can't read. It would be unheard of, IMO, for a CD flipper to have a CD-R on one side and an HD DVD layer on the other. What's on the CD-R layer? What happens when you try to open that side in Windows? Is it an Audio CD? Does it attempt to play as an Audio CD or does File Explorer open a folder?

If it's an HD DVD layer, then a BD drive or Blu-Ray player won't read it.

What does ImgBurn say the one side you can read is? It would say in the Log, probably, or, at least, the pane of disc info on the right hand side. If I had to hazard a guess, this is a dual format flipper. One side is a DVD Video layer and the other side is an HD DVD or Blu-Ray. Probably an HD DVD side since your drive can't apparently read from it. I know there was one Star Trek original series complete series release that had DVD layers on one side and HD DVD layers on the other.

Yeah, Verify speeds on BD-R are stupid. While I've rarely seen 2x, I have seen some that start at 3x and then cap out at 4. And it is entirely random. Sometimes you get really good Verify speeds that start at 5x and then sometimes you get really slow ones.

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.