LIGHTNING UK!

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.

Your drive can't burn DVDs. It's a CD burner that can *read* DVDs (but not write to them).

Have you switched the output to 'Image File' rather than 'Device' ?

Your INDEX 00 markers do not leave a short time between tracks. That's the point I was making The TRACK commands give you the ability to skip (tracks). You can't do anything with indexes at all - as in, you can't jump between them. They're invisible to software / hardware players. The table of contents on the disc only records where track x / index 01 is and that's considered the start of a track if you skip through them. So really, INDEX 00 of a track actually looks like it belongs to the previous one. The PREGAP command instructs the program to insert digital silence between tracks (that data is not taken from the file).... so if you had a single large file with digital silence in it between tracks, that's where you might choose to use INDEX 00 (for when it starts) and then INDEX 01 for when the music starts again. INDEX's consume data from the file.

You can do without the INDEX 00 entries, there's no point in them being there. INDEX 01 is what players jump to when you skip tracks etc. Plus you'd only made the index 00 1 frame long... which is 1/75th of a second! Well done for figuring it all out though. No idea about the browser thing. Remove the password from your saved password list and try again.

That would have power cycled the drive I guess - something a restart doesn't do.

Why are you using such an old version? Even the latest version is old, so that's the one you should be using. It's not worth anyone's time trying to troubleshoot when you aren't up-to-date with the app in question. Once you've updated (and I suggest you reset back to the default settings), copy and paste everything from the Log window once you've opened the program and left it until it's found the drives - I'm assuming that's the bit yours is taking ages on - going by the screenshot.

Maybe you rebooted your machine? There's no reason for it to get stuck where it did.... it would have been due to something outside of ImgBurn, but a bit more info (in the form of a debug enabled log) would have helped me to help you figure out what it might be. Hopefully it stays working ok for you now.