LIGHTNING UK!

Just don't pick the 'MajorGeeks Installer Version'. Going by the name, I assume that one gets you a repackaged version that uses MajorGeeks own installer. The (original) one I gave them was 100% clean.

DVD+RW yeah? Once formatted, they look like a burnt disc. It'll just read the entire disc from start to end as there's no way of knowing the 'burnt' size without being able to understand a file system that may or may not be present.

No, it’s for optical drives.

Have you tried burning at slower speeds? If max (6x) is producing unreadable discs, maybe try 4x and 2x.

Depending on what info your drive returns, the program can get stuck in a loop trying to find the real start of tracks. Some drives are worse than others at returning incorrect info that causes the looping - so if you have another drive you can try reading the disc in, that one may work. Another app that doesn’t work in the same way will also get around the issue.

It won't reproduce the tracks on anything other than CD, that's why it won't let you use Read mode. You'd be better off doing what it said an using Build mode. Just add the drive letter of your optical drive to the Source box and make a new image based on the contents of the disc. Then burn that image.

That log fitted with the screenshot in your original post. If you have another issue.... and you believe you aren't lacking in disc space, please post the log from that attempt at burning. We can only work with the info you provide

That wasn't the issue. That's why your drive errored out. You can't burn 6GiB of data to a 4.37GiB disc.

You’re trying to burn too much to the disc. The program did warn you.

Go into read mode and put that disc in the drive. ImgBurn should tell you which file systems are present on the disc.

Can you upload the ccd so I can take a look please? Also, how big is the .img file?

Yeah, if you’ve gone the route of flashing a modded firmware to your drive in order to gain booktype changing support, maybe you could ask the author of said firmware to also patch the layer type. Failing that, get yourself a new drive. I know some of the vinpower drives had this exact thing added to their firmware.

First and only failure? Try again. If it keeps happening, try some different discs. You've got the value Verbatim range there - not recommended. Do not believe everything you read on youtube or wherever regarding the buffer size. Changing it to 72MiB isn't going to magically fix anything.

At this point, you need to post the log from the burn+verify session. You can access the saved log via the help menu.

This is nothing to do with imgburn, your drive is doing it.

Indeed, the only fix is to buy a drive that does it (by design). It's not something the software has any control over - beyond sending the normal booktype commands.

As your optical drive is using E: for its drive letter, just pick 'create image file from files/folders' on the Ez-Mode picker screen when ImgBurn starts, type in E:\ in the 'Source' box, click the '+' button next to it and off you go. Pick your destination image file (iso) and press the start button.

I'm pretty sure it's on there somewhere. There are lots of fields you can fill in with that sort of data.

An ECC block is 16 sectors on a DVD, not 32. For that reason, the error isn't important. Which UDF version did you use on the disc?

Check (and perhaps replace) the cable / port the drive is attached to. If you're getting CRC errors with the transfer of data to/from the drive, something isn't right somewhere.

It’ll be the same deal as in the other threads. Take control of your AV software and get it to ask you what you want to do rather than just doing it. You also have the option of downloading from one of the other mirror sites.

Australian burner

Sorry, I've never played around with burning those DTS CDs and have no clue how they actually work. Generally speaking, ImgBurn would be trying to convert any audio files fed into it into 44100Hz, 16 bit, stereo.... as that's what CDDA is. The exception to that would be when you feed it a BIN file, as I'm pretty sure that just gets burnt as-is. So, if you're saying it's worked ok in the past, what format were those images / files in? Were they all BIN/CUE? What files do you have for this non-working disc?

What you've said there is the exact opposite of what this person is seeing though. You're essentially saying Build mode works and Write mode doesn't. They're saying Write mode works and Build mode doesn't. Programmatically, the code that does the writing doesn't know or care where it's getting the data from. Data is data and the exact same commands get sent to the drive to ask it to write it to disc.

Speaking from a technical point of view, I'm afraid it doesn't mean anything. There's no difference between Write, Build and Discovery modes where the actual burning of the disc is concerned. There's only 1 chunk of code that does the actual burning and it's used by all 3 modes. Also, there's no way to make a drive more or less capable of burning / reading the disc. That stuff is all controlled by the drive and its firmware.