LIGHTNING UK!

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.

Is this in Read mode? Are you configuring the 'default destination' option on the Read tab in the settings?

You probably need to look for an updated SATA controller driver for your motherboard. That command should not cause the drive to be removed from the OS.

The 'insert next disc' box also displays which copy you're on. I don't know where else you could want/need it?!

There's only 1 way of doing it. http://forum.imgburn.com/index.php?showtopic=6380

The purpose of Verify is to discover if the disc is actually fully readable and that all the data on it is present and correct. A successful burn means nothing on its own. The drive can think it's been burning ok and yet you end up with a totally unreadable disc at the end of it - as was the case here.

No, they aren't copied if the OS reports they're 'In use' and won't let me open them for reading. If you want to backup your computer's entire hard disk, use a proper hard disk backup tool (Acronis True Image, Macrium Reflect, Norton Ghost etc.)... not ImgBurn.

All you can do is keep trying different DVD+RW's until you find one that the drive actually works with properly. Make sure you do 1 full erase on them with ImgBurn before using them.

The main buffer level shouldn't be affected by which bit of the disc is being burnt, it's filled by a different thread. If it dropped off to the point where buffer recovery came into play, it's probably just that something happened on your machine and it stopped the flow of data for a while - or you've modified the buffer recovery settings and it's now kicking in when it shouldn't do. Sorry, there are no nice eeprom type settings for Optiarc drives. They're just plug 'n' play and you have to rely on the write strategies in the firmware. The point is though, things aren't supposed to go wrong I've got some FalconMedia DL's on order. They're meant to use the RICOH MID (and be the best version of it). So if the strats were built around those, I might see some better results. As mentioned at MyCE, MCSE doesn't support these firmwares yet.