dbminter

Yeah, I discovered some years ago that that plugin was somewhat problematic. And that was back on like Windows 7. Maybe 8. I eventually removed it/stopped installing it.

Well, the log would still show up USB 2.0 even on USB 3.0 connections. It's a feature limitation in the current version of ImgBurn. It will be fixed in the next release. Even on my USB 3.0 ASUS BD drive, it showed up as USB 2.0.

I looked up the CORRECT model this time. I've used that drive for many years, with a few different copies of it over those years, since it needs replacing about every 11 months. I never encountered a problem with DVD writing. However, you mentioned a new USB cable, which implies you've put that model in an enclosure, since that's an internal drive. Did you mean SATA cable, the internal connection for the internal drive internally? Or did you mean a USB cable because that internal drive is an external enclosure connected by USB?

You might also want to try switching the discs you're using. CMC makes the worst discs out there. It might be you got lucky in your previous discs had no problems but this one did cause a problem. That was my experience with CMC. 50% of them worked and 50% of the 200 disc cake stack failed to either burn or verify.

Oh, sorry. Ignore what I said earlier about your drive's age, etc. I googled the wrong product. I misread the log and thought the target drive was the first one in the list.

That was my experience with the CMC's from Optodisc. About 50 percent of the discs would complete writes (and verifies if applicable) and half would fail to complete burns or verifies. You may want to see if you get the same random failures on the Verbatims. A drive can be bad out of the box. I've had 2 Pioneer BD drives that were that way and 1 LiteOn DVD burner that was.

I wouldn't trust CMC with anything. I spent hundreds of dollars before I learned CMC was the problem with everything I was experiencing. More discs, replaced DVD burners, replaced DVD video recorders. Then, on another forum, I randomly came across CMC being cheap and problematic. When I checked my discs, sure enough, the Optodiscs that used to work and were good were made by Optodisc and all the ones that were failing were CMC because they had switched manufacturers! So, both Optodisc and CMC went on my list. Anyway, I'd still try Verbatims. If you know the known really good stuff doesn't work on your drive, the problem is the drive and probably needs replacing. I looked up your drive. It's not a slim line junk model, so that's not the cause. It does appear to be about 5 years old, so it could be the age. Your drive's firmware may not simply support a newer CMC Pro type of disc. Try updating the firmware of your model. In Write mode, right click on the drive target and choose Check for firmware updates. See if there any.

Are those actual Taiyo Yuden media or cheap knockoffs? TY no longer makes media and it's good name may have been sold to cheap manufacturer CMC. Since I question whether those are legitimate TY media, I'd first try Verbatim DataLife Plus series DVD's and see if your problem goes away. If it doesn't, then your drive probably is the problem. You can only find Verbatim DataLife Plus media online. DON'T get the Life Series you find in stores. They're cheap CMC.

It apparently says "Allocating File Data Storage Area." I had multiple reads, writes, etc. being performed during a Build and the system had become so slow I was able to see the message this time.

Ah, never heard of them. So, they're not standard CD's. They do, however, appear to be DVD's, as I wondered. That page says they're in DVD-5 and DVD-9 formats, which is single layer and dual layer DVD's. Do you need a proprietary player for them? If so, even if you did copy them to DVD+-R DL, there's no guarantee they'll play on your player. Your player would have to support reading recordable DVD discs.

What are SACD musical discs? They can't be audio CD's. Audio CD is capped at less than 1 GB total size. So, they could be DVD-Audio discs. 7.97 GB would fit on a DVD+-R DL. You're better off not merging the contents from the ISO's in this case. You're better off inserting the original source SACD and copying the contents from it. Inferring they're not CD's, which they can't be. Not at 7.97 GB. If they are audio CD's, then something else is up because no audio CD can be 1 GB or greater. Since I don't know what SACD's are, I don't know if they're proprietary. If they're not actual audio CD's, then you can copy the contents. If they are audio CD's 1.) you can't copy the contents in Build mode and 2.) something is wrong because CD's can't be 1 GB. Actually, you may be better off in this case inserting the SACD disc that Super Author made 2 ISO's out of and using ImgBurn's Read mode to read to a single double layer ISO file. Then use ImgBurn to burn that. You'd have a better likelihood of success and getting an exact copy doing that, probably.

Um, I don't know what's going on here but any program worth its salt will NOT generate two separate ISO's, one for each layer, for a double layer target image. What are the sizes of these two ISO files? Maybe the first ISO is already a double layer disc and the 2nd ISO was generated for a 2nd disc because it exceeded a DVD+-R DL. In that case, the ISO would need to be burned to a BD disc. But, the program should still have created only 1 ISO. I just don't see why this program couldn't just create 1 ISO with both layers on it. Anyway, you can't burn more than 1 image to an disc. Your best bet is to use ImgBurn's Build mode and merge the contents from the two ISO's into a new image it builds. Open each ISO in File Explorer and copy the contents to a temporary folder from each ISO. Then, add those files in Build mode. Unless you need something specific like a bootable disc. Then, you're better off injecting the files into one of the ISO's with something like UltraISO.

I was going by it was one of only 3 clickable options there because there were 3 highlights. And I know aqui means here, so I guessed at the possible word being click because it was spelled similarly. Usually, links at the bottom are generally ones for the user agreement and other general software manufacturer links. So, I ruled those out.

Ah, I didn't think about the OS might have been assigned a different language. And that the OP might be multilingual or using a translation engine to post in English. Yeah, sometimes I'm pretty stupid.

I believe the Clique aqui line means Click here to customize your install. That might have been the necessary step to prevent installation. However, admittedly, what good does it do when the bundleware being offered is in a language you can't read?

I did decide to look it up, smart guy! In fact, it seems I had a DVD burner that probably had a 2nd laser in it. Came across an instance of a BD burner with 3 lasers! One for CD/DVD, one for Blu-Ray, and the third for burning Lightscribbe labels. So, it seems that Lightscribe capable DVD burners might have had a 2nd laser for burning the Lightscribe label side. I had a few LiteOn DVD burners that were Lightscribe capable.

That explains why a Blu-Ray can fail to start burning correctly, but CD's and DVD's can. Or the other way around. Doesn't explain how a burner can start failing on all DL DVD media but not SL media. I had wondered if Blu-Ray might be closer to Violet Ray. Why jump from red to blue but stop short of the last two colors of the spectrum, indigo and violet? So, there's nowhere to go from Blu-Ray, then? There won't be an Indigo Ray or Violet Ray?

Are Read speed rates set as a flag on each disc? Like how recordable discs have their rated Write speeds set on the physical media itself? Or is that even relevant? Is it entirely set in the drive's firmware? Or is it a combination: there's a maximum rated Read speed on the media and it's down to the drive's firmware to support that maximum speed or less? Thanks!

There are 2 different lasers in a BD burner? Is that true? I did not know that. Why is that? Are there 2 different lasers in a standalone Blu-Ray player, one for CD/DVD and one for Blu-Ray?

One thing I just happened to come across randomly, but after testing it a few times, I've determine it does seem to be happening. ImgBurn can eject a disc with the Eject command even when a "write operation" to a formatted disc as a giant floppy in File Explorer has not completed yet. I don't know if there's a way to check for this before ejecting, but if there is, can it be added to ImgBurn? The way I do it now, to be safe, I don't use ImgBurn's Eject command when a disc formatted as a giant floppy by File Explorer is in a drive. I use File Explorer's Context Menu Eject command. If the write operation hasn't been completed yet, File Explorer won't eject the disc. Thanks!

You can retrieve the Log from Help in ImgBurn.

The "easiest" solution, for me, is to use DVDShrink to shrink the DVD-9 VIDEO_TS contents you want to burn to a DL disc by a few percentages. Once you get a shrunk size that ImgBurn will accept, you can burn that. With most modern DVD players, you generally get upscaling on DVD playback from recordable DVD discs. (It's a long story on media versus video connection combination about whether you'll get upscaling or not.) With upscaling, you won't notice the difference. Plus, if there are audio tracks you don't need, like foreign language tracks you'll never listen to, you can remove them with DVDShrink and maybe not need to shrink the contents by anything.

I think I may have been the victim of a possibly messed up Windows configuration. I restored back to my last image made after the installation of Fall Creators Update and updated Windows Update updates to the latest Windows 10. I don't seem to have the light constantly flashing anymore or the slow down. I'll have to see if any thing I installed or updated since then, in my list of things I've done, causes the issue to return. I had hoped to put off doing this until the new Windows 10 version came out. That way, I could update Windows 10 and all of my applications at the same time. Theoretically, an install of a new Windows 10 version from the ISO may have fixed my slow down issue. Well, I've updated a few things and so far everything is going well.

I'm not entirely sure how I'd do that. I don't even know what speed this HDD is rated at. I believe it's a 7,200 RPM, but I don't know. I do think it's the Spectre/Meltdown BIOS update. I restored an image of Windows a bit back to test it, with nothing else installed, and it did the same thing with the HDD light.

That does help, thanks! I'm mostly concerned about this because of my most recent BIOS update to patch Spectre/Meltdown. I did take some noticeable hits. For instance, Freemake Video Converters conversion of 1 hour MP3's to MP4 video container files leaped from 2 hours for 4 of them to 8 hours! I'm also getting some slow down in creating image files in ImgBurn to HDD. However, my PC was bought in 2014, so its Spectre/Meltdown hit is going to be higher. However, I've been getting more and more buffer recovery hits lately burning media. That's because ever since I updated the BIOS, my HDD light stays on pretty all the time for extended periods of time. And it's constantly, pretty much, going off and on when it's not. So, the drive is being accessed more since the update. In fact, sometimes the access is so severe I have to restart the PC to "recover" from this slowing down. These buffer recoveries during Writes can last about 2 minutes. I'm just concerned that, some day, a write will never resume because the HDD is constantly being accessed.