LIGHTNING UK!

I've already answered your email about this. Feel free to bring the conversation here instead if you prefer.

Correct. ImgBurn exe stayed the same, just the installer changed.

Is it a DVD Video disc or is it something else? The only things I ever really saw that were oversized were xbox360 images.

Have you actually tried to burn it and the program has told you it won't fit?

How did you burn the discs in the first place? Put one of them in the drive and open ImgBurn in Write mode. Now please copy and paste everything from the box on the right of the main window.

It's probably just down to the media you're using. Although you say they're Verbatim discs, I'm afraid they're the wrong ones.... perhaps the 'value' range? Yours use the CMC MID/dye rather than the MCC/MKM one. Look for the 'Azo' label on Verbatim media and avoid their value range. If you get the decent stuff and the drive still errors out, you'll have to invest in a new drive.

Maybe... yes. Use Read mode to make an image of the disc. Mount that image using any method available to you and the OS you’re running. Either directly in Explorer or via a virtual drive program.

You’ll have to do as it says. Go into build mode, change the output to image file, put the drive letter of your optical drive in the source box (D:\ or whatever) and then build your new image.

If that status is accurate, your drive is returning ‘medium not present- tray closed’ at the point when you abort. So, it hasn’t detected the disc in the drive. Sounds like a fault with the drive to me. Is the tray locked and stopping you from just ejecting / reinserting manually? The would be better than aborting and starting a manual verify operation.

Nope, more space on a dvd-r.

Ok, so your drive still thinks the disc is empty. You're going to have to try to buy some better discs, your drive doesn't like those.... and avoid anything with the RITEK MID/dye - which is what you've tried using there. You get a tiny bit more space on a DVD-R, but there's no difference in the burn process where an end user (such as yourself) is concerned.

It looks like your drive did a bad job of burning the disc and now can't recognise that it burnt anything to it. If you keep that disc in the drive and go into Read mode, please copy and paste everything from the box on the right of the main window. Then, eject the disc, reinsert it and copy and paste the info again please.... just to see if anything changes.

Burning with low quality discs is always hit and miss. I'm afraid that's the nature of burning optical discs. As for the log... this should help

Please post the log. It contains information that helps us help you. The issue is nothing to do with the program, your drive has a problem with the discs you're using. It could be that your discs are no good, or it could be your drive has had it... or a combination of the two.

Ah ok, yes, something like that would be possible using a batch file. Sorry, I must have missed the bit where you said 'separately' and instead focussed on the 'hundreds of files'. All the command line options are still there. I've looked through some of my previous examples and they seem to be for converting a folder full of folders into individual ISO files. I've made a few tweaks and it might now work for files... but it's untested. Edit: now tested Make sure Explorer is set to show file extensions. Make a folder (let's call it 'Conversion'), create a text file in it (via right click, new -> text document), rename it to something like 'make images.bat', edit it (right click, edit) copy and paste the following into it... @for /r %%i in ("Source Folder\*.*") do "%ProgramFiles(x86)%\ImgBurn\ImgBurn.exe" /MODE BUILD /BUILDINPUTMODE STANDARD /BUILDOUTPUTMODE IMAGEFILE /SRC "%%i" /DEST "Output Folder\%%~ni.iso" /FILESYSTEM "UDF" /UDFREVISION "2.50" /VOLUMELABEL "%%~ni" /NOIMAGEDETAILS /START /CLOSESUCCESS Copy your folder full of files you want put into ISO files into that same folder and rename it 'Source Folder'. So you now have something like... C:\Conversion\ C:\Conversion\make images.bat C:\Conversion\Source Folder\ C:\Conversion\Source Folder\(all of your files) Now run the 'make images.bat' file. You should then end up with an additional folder in your 'Conversion' one. C:\Conversion\Output Folder Inside that you'll find all of your ISO images files.

The queue is for Write mode... for the mass burning of existing disc images. I'm afraid there is no way to do what you're after.

OpenCandy was never 'installed', it's what powered the adverts offered during the installation process. OpenCandy shut down years ago, so no, it isn't bundled.

Your drive reported a 'Write Error' early on during the burn - right at the start actually. I guess it has an issue with the media. If say you've tried multiple different ones (not just different brands, but with different MIDs), maybe your drive is at fault? There are firmware updates available for the drive that may or may not help. v1.03 and a recent v1.05.

Indeed, that is the job of the CUE file. Open it in notepad and you'll probably see that it contain numerous 'track' entries. Load the CUE in Write mode and burn. *That's assuming you have a directshow filter installed that's capable of decoding flac files. If you don't, please refer to the bottom of the Audio CD guide here:

You already asked this question here -

I guess because that's just what it defaults to? You can't make something from nothing though and 2048 bytes images only contain 'user data'. Nothing that writing in RAW mode would do anything for. Should you be so inclined, you can look up the structure of a CD sector and see the difference between 2448, 2352 and 2048 byte sectors. 2448 being the same as 2352, but with the added 96 bytes of subchannel.

I suggest you take a 2nd look at the name of the application you're using. What part of 'InfraRecorder' looks like 'ImgBurn' ? Getting back to the application this support forum is actually for... ImgBurn... that doesn't offer RAW at all. Your other thread is beginning to make a little more sense now. It seems you have your apps confused. btw, as an ISO is meant to just be 2048 bytes per sector, you're wasting your time even looking at RAW writing. You don't have any data in the image that would benefit from being written that way.

ImgBurn outputs iso or bin/cue. I do not understand where you’re getting this toc and subchannel from?!

Your disc is copy protected.

As verify re-reads the image and compares it at bit level against what's read from the disc, it can actually be better at finding problems. For example, if there's an issue with data corruption when reading from the source drive (but no 'hard' error) or a memory issue (faulty ram), verify would give you a 'miscompare' error. Hardware Defect Management won't notice that kind of thing. As you say, it's pointless formatting with spare areas and then turning on fast write. Just format without spare areas. Only if I really wanted to make sure everything was ok would I use hardware defect management AND verify. I don't think I'd rely on hardware defect management alone (as in, verify being disabled), but I'd certainly rely on verify alone (as in, without HDM being active during the writing phase). Yes, spare areas are transparent to software. The drive handles remapped blocks itself internally.