LIGHTNING UK!

CD-TEXT info is being written, it says so right there in the log. Switch to Read mode and click the 'View Media Information' button. Do you not see the CD-TEXT stuff listed in the window that comes up?

Try the current version, that one is ancient. If that doesn't work, please provide a debug enabled log - as per the post about this issue in the FAQ.

Get yourself some of these. http://www.totalblankmedia.com/jvc-dvdr-16x-50-spindle-taiyo-yuden-p-2216.html If the drive(s) still error out, buy a new one.

What you're burning is not the problem.

I can't tell you the answer to that based on the info you've provided. The drive should be burning without erroring out, but obviously that isn't the case. There are little tweaks you could attempt in order to get it working - like enabling 'Perform OPC Before Write' or switching the 'Write Type' to 'Incremental'. Both of those could potentially alter how the drive tries to do things with the disc and could provide a workaround for its current issue with them.

It's better if you copy+paste the contents of the log window, the screenshot doesn't provide enough info. Buffer recovery kicking in is normally a sign of a slow source drive, not an issue with the destination one. I assume you're low on RAM and that's why you only have a 20MB buffer. At one point, it took 14 seconds to fill that 20 MB buffer... that's awful throughput from your source drive / system.

Try the 2 other supported write speeds if the drive is doing a bad job of burning at 4x. After that I'd just say to buy better discs.

Just find the nearest (optical) drive selection box. Once verify has finished, you'll be back on the main 'Write' mode screen and can get at it in the 'Destination' box. Verbatim 2.4x DVD+R DL is all you need to look for.

Can't you get it off the JMicron controller and onto the Intel one? If you can't, at least ensure you have the latest driver installed. ftp://driver.jmicron.com.tw/SATA_Controller/Windows/ At the moment it looks like you're losing the initial I/O error message - i.e. the bit that is actually useful.

That's the same version of VobBlanker... 2.1.3.0. You must have just clicked the wrong thing and that's why you're seeing a different screen.

The fields are just set to allow a max length of 128 as that's what ISO9660 supports. File systems that have lower string length limits just use a truncated version of the string - so yeah, that's 64 for Joliet (Unicode version of ISO9660) and 23 for UDF.

If you're in 'Standard' Input mode, it would already be going to the root folder if all you've done is dragged it into the 'Source' box. If you're in Advanced input mode, it should be obvious where things are going. If it isn't ending up there, you've probably enabled the 'Preserve Full Pathnames' option. Turn it off again.

The program burns, cycles the tray and then starts to verify the disc. It doesn't burn/write twice. As for the errors, that could be due to a bad burn or they're bogus messages caused by bad controller drivers. Right click the drive selection box and pick 'Family Tree'. Close the prompt and then copy + paste all of the lines from the log window.

Yup, go for it.

If it made a backup folder, I guess you could give it a try. Don't be concerned, that's normal.

Yes, you made a mistake in VobBlanker. You want to split the cell, not cut it. You'll probably have to recreate the VIDEO_TS folder again from your vid editing software.

I'm pretty sure that ImgBurn would have made that folder if it didn't exist.

I have no idea then. If it burns and verifies ok, the disc is at least readable in the drive that burnt it. Playback in other devices comes down to them being able to read the disc full stop, and then being happy with what's burnt to it (i.e. the source files you just burnt). None of that is anything to do with ImgBurn.

Some fields may not apply to the file system(s) you've got on the disc. No, there's no way in ImgBurn to extract that info from the disc - via command line or otherwise.

1. The firmware. 2. Depends on the media format. 3. To be honest, I don't know. If it records it at all, I'd assume it to be from the last burner that burnt it. 4. Yes. Additional Google searches for your drive model and 'pioneer' would confirm that.

ImgBurn displays a few more in the tooltip that comes up when you hover over the 'Label' field in the 'Source' box within Read mode.

Maybe it just can't read them very well. The media you're using might not be a good match for your burner or something.

Put it in the root folder of the disc, then you won't have to 'browse' anything. If you want to convert it to DVD Video format, use something like DVD Flick or ConvertXtoDVD.

Why is your image suddently coming out to 15GB in size? Obviously that's never going to fit on a standard double layer disc. Has the folder you're pointing it at got more than 1 set of DVD Video files in it?

More detail please. Read mode and build mode both tell you how much space is on the destination drive. I see no point in displaying it for the source drive.