dbminter

I hadn't thought of that, so it's entirely possible the OP is attempting to erase WORM discs, which may explain the failures. To the OP: attempt another erase of a disc but copy and paste the log of the operation in its entirety.

The first log portion shows it's a DVD-RW. I failed to notice that before, but that could be a key point. This drive may not be a DVD-RW capable one. It may not write to DVD-RW, only DVD+RW. Oh, wait, just now noticed the 2nd portion of that log said it was trying to erase a DVD+RW. So, it can't be that.

You could try changing the I//O Interface, but I doubt that will help. Tools --> Settings --> I/O tab --> Page 1 --> Interface Try each one one at a time and see if it gets better. I'd recommend you close and restart ImgBurn after each change of the I/O Interface. However, I'd lean more towards the drive you're using. It's most likely either defective or just a pretty poor device. You may want to try a different make, model, and manufacturer and see if it's repeatable. You're also using a half height drive in a USB enclosure, it looks like. Or that drive was bought as an external. The LH-18A1H is a half height model, but you could have always bought it as an external version that came in its own enclosure. Either way, I'm saying the problem could be the USB enclosure. If you're using a separate USB enclosure you bought yourself, what manufacturer and model is it?

Copy protection could be a cause, but it generally doesn't matter in cases like these. First, is this a PC game disc or something for Playstation, Dreamcast, etc.? Generally, freezes at Tracks are a conflict between the disc itself, the hardware being used, and ImgBurn. You could try using other drives to read the disc, but you will probably not get anywhere with doing that. The only solution I've come across for game discs that ImgBurn won't read is to download and install Alcohol 52%/120% free version. Particularly for Playstation game discs, Alcohol will often times read in discs that ImgBurn can't. It could also be a case where the disc simply has deteriorated over the years and suffered layer rot, which means it can't be read in.

Well, I'm not sure what to make of this. All of the failures are from the same day: 2024-06-25. All discs written between 2024-06-10 and 2024-06-24 Verify fine now. There was only 1 disc, a BD-R, written after that on 2024-06-26 and that Verified fine.

Now, it's possible that my ASUS may have simply reached the end of its life for writing BD-R. However, the fact that it STILL writes AND Verifies even though it's not doing it properly still means it's not reliable for long term storage. I am Verifying other BD-R's written before 2024-06-25 right now to see if there are any other failures. It's also always possible I've got a bad batch of BD-R's that were okay part way through and only corrupt at the point starting around 2024-06-25. Such things generally don't occur, though. Issues such as these are generally down to poorly designed drives. Particularly since this is my first long term introduction to this ASUS's use, it's hard to trust it for long term storage when the LG WH16NS60 has always been reliable for long term storage of BD-R.

ABSOLUTELY DO NOT USE THIS DRIVE! I had a BD-R that was written 2024-06-25 that was mostly unreadable on 2024-09-19. So, I started going over discs written around this time. The 2nd disc I attempted to read that was written on 2024-06-25 would not even read in the first sector! Not in the ASUS or a Pioneer. So, this drive is unreliable for long term storage when writing to BD-R. Now, I Verified a BD-R written on 2024-06-21 successfully. So, I need to test discs before then and the other disc remaining written on 2024-06-26. However, what this indicates is the drive is unreliable for writing quality VERBAT-IM BD-R for long term storage. This could be flukes with the BD-R's being bad, BUT IF they ARE, the ASUS is writing them AND Verifying them at the TIME! Which means the drive is not reliable.

Have you actually gotten the virus or is it just embedded in the BurnPlot installer file? If it's the latter, there's little you can do to remove virus packages from files.

ImgBurn has never done any DVD authoring. It only burned what you threw at it except converting files to Audio CD's.

Apparently, madFLAC is specifically for FLAC files only and doesn't add any support for WAV. As reported to me by the OP.

I don't know if it will help in this case, but I have to install madFLAC for FLAC files to work correctly. Just as something to try in the meantime while waiting for someone else to chime in with a possible fix, try searching the web for madFLAC, install that, and try again. See if that helps.

I did a little research. DDP is Disc Description Protocol. Those files are intended for disc mastering for duplication. So, they're probably for disc pressing hardware to make mass copies of a DVD. Which means you probably can't do anything with them without a mass disc duplicator.

I've no idea what you have there. Generally, it's not easy to determine what files exactly are on Layer 0 and which are are Layer 1. .DAT files could be anything. I just know they're not DVD Video. Is this some kind of car navigation disc, possibly? What contents are in the Layer 1 folder? Depending on what these files are for, this may or may not work. In Build mode, add all the files and folders from the Layer 0 folder to the root directory of the Project and repeat for the Layer 1 folder. If you are prompted to replace any files, you may as well give up because it's probably impossible to determine which files are the "real" ones (From Layer 0 or Layer 1.) and which are not. Then, create an ISO from this Build job and burn the ISO to a DVD DL disc.

I should have thought of that. I don't know if Virtual CloneDrive, what I use, supports CDI, but a search reveals Daemon Tools Lite does. As does MagicDisc. However, with this method, I can't see a way to automate the conversion of dozens of CDI's. Also, what is the origin of the CDI files? If they're not audio CD's, then I don't think you'd even be able to make BIN/CUE out of them. But, I could be wrong.

I tried to find ANYTHING, but there are a few utilities that convert BIN/CUE to CDI, but none I could find that would do it the other way around.

This post is about the expected lifespan of Imation 8x DVD+RW (RiData second generation) RICOHJPN-W21-01. I'll be keeping track of how many writes are done to this media before it fails. I'll update this post with the final value when the disc dies. The writer is an ASUS BD BW-16D1HT with firmware 3.11 is a VanTech USB 3.0 first generation enclosure. One write is already accounted for by Full formatting of the disc. Just reached the 40th write mark thus far. Still going. Verify failed on the 43rd write. So, this disc got 42 writes before failure.

This post is about the expected lifespan of RiData 8x DVD+RW (First generation) RICOHJPN-W21-01. I'll be keeping track of how many writes are done to this media before it fails. I'll update this post with the final value when the disc dies. The writer is an ASUS BD BW-16D1HT with firmware 3.11 is a VanTech USB 3.0 first generation enclosure. One write is already accounted for by Full formatting of the disc. Just reached the 35th write mark thus far. Still going. FINAL RESULT: Verify failed after the 37th write. So, this disc got 36 successful writes before it died.

I sometimes think LUK and I are the only ones from the old guard who still regularly post here and help out.

As far as I am aware of, there's nothing preventing you from opening 4 different instances of ImgBurn and burning 4 different ISO's to 4 different drives. I know I have had 2 instances of ImgBurn open at the same time, but not doing 2 different burns. However, it may not be PRACTICAL to do it. If these 4 drives are all attached by USB, there may be throughput issues writing to 4 different USB burners at the same time. I've never tried it before so I can't say.

Any burned disc will return the same information. It may not do it in Write Mode so you may have to go into Read Mode. Somewhere in the right hand pane of info, there should be something that says Manufacturer ID. The burner in your PC probably doesn't have a problem with those Ritek discs, but your BD player apparently does, if you're using a standalone BD player. I've used primarily Verbatim BD-R for the past 10 years. I tried a few Sony; they were junk. Memorex's Ritek's caused playback problems on the PS3. It would skip over entire title sets, including the opening one and some it would play only partially, skipping over parts of it. The same contents burned to Verbatim BD-R all played back normally. So, I've got experience with Ritek's poor playback quality with BD-R on the PS3. I'd expect the same sort of results on other BD players. I would try some of the Verbatim BD-R and see if those work better. Since you also purchased from NewEgg and your account info verifies it, it says you're in the US like I am. I get my Verbatim BD-R from Amazon.com. You can find them at Office Depot brick and mortar stores, too. And you can order just like 10 of them at a time from Amazon.com to test out and see if you get better results without having to invest much to see if they're better.

Generally, cleaning discs for standalone optical devices have been recommended to avoid. At best they do nothing and at worst they scratch the lens. General grinding issues are the result of the laser being unable to properly read the data. And this is generally down to a conflict between the media itself and the laser. For instance, on the PS3, it hated MEMOREX/RITEK BD-R but had no issues with VERBAT-IM BD-R. The easiest way to check further is post the log of a full write of a burn of one of these BD-R that causes the grinding. If you can't get one and don't want to burn another test BD-R, you can put a disc in the drive, open ImgBurn in Write Mode, and check the pane of information on the right hand side. Look for what it says under Disc ID (DID) or Manufacturer ID (MID). What does it say is the manufacturer of the BD-R? If it says CMC anywhere in it, that's probably the issue. Although RITEK and RICOH can be a cause. If it says VERBAT anywhere in it, then the issue is not necessarily so clear cut.

I've no longer got the input source files at hand to see if I can repeat it after being able to repeat it before. I was using Advanced.

I've got 2 different folders I wanted to add to a project. One in a folder called 2 and one in a folder called 3. 2 and 3 have the same folder structure except one subfolder is labeled Disc 1 Of 2 in 2 and the other is labeled Disc 2 Of 2 in 3. I dragged and dropped the subfolder in 2 to the project, but dragging and dropping the same folder in 3 wants to replace the contents already existing in 2. Wants to overwrite the contents of Disc 1 Of 2, which there is NO Disc 1 Of 2 in 3, only in 2. I triple checked. The contents in 3 are NOT entirely the same as in 2. There is the Disc 2 of 2 folder in 3 and there is NO Disc 1 Of 2 in 3. I triple checked to make sure I was dragging the folder from 3 and not 2. I was. I repeated this several times and got the same result. I closed ImgBurn, reopened, and repeated. Same results. Thanks!

This happens only rarely, but it does occasionally happen. Because it is so rare, it seems impossible to debug such an issue. What happens is sometimes in Build mode, dragging and dropping a folder into the Project does not add the folder. Instead what gets added are all of the files and subfolders in the ImgBurn installation directory. So, files like ImgBurn.exe and other executables get added. This just happened to me for the first time in a long time, but it does occur from time to time. What generally happens is deleting those ImgBurn folder files and dragging and dropping the same folder again works. Thanks!

To the first question: no. USB 3.x devices reporting as USB 2.x is a cosmetic error in the software. Back when the last gold release of the software came out, there was no USB 3.0. So, ImgBurn identified USB 3.0 as USB 2.0. This has been fixed in later betas and when the next version of the software comes out (And, no, don't ask when that will be.) it will be addressed. In the meantime, ImgBurn will (In general.) use USB 3.x speeds on USB 3.x devices. To the second question: depends on what you mean by "properties." If you mean what Device Manager will return, as far as I know, no. However, in Write mode, if you right click on a drive, there is a Capabilities list that displays some meaningful hardware properties of the drive.